Posted by noreply@blogger.com (Zibri) on under th project, e care, exchange support, iphe, phe, itunes, magda, crypto, 3g, lena, mms, photo courtesy, few days, amp, proposal | 
In the past few days I have been busy disassembling
and analyzing what we could call a "gold" 2.0 firmware.
I say gold because it's expiration date is the
4th of June so all features are there already.
Well 2.0 will not have MMS, not have cut & paste,
no new applications (guess why!). So, aside from exchange
support and appstore what did they change ? I'll tell you: security !
Yes, Apple tightened iPhone security (their security not yours)
a new crypto algo has been introduced
(and promptly defeated as expected).
No more "8900" files but IMG3. Firmware 2.0 will require
a new iTunes version and a new "mobiledevice" framework.
If it were for me I would not even bother to hack this version
but I know many of you are going to upgrade so I will release
a new ziphone version after the official release.
I already patched activation (lockdownd)
and unlock / Fake IMEI (baseband firmware).
To fully test this version I will need a Mac (I don't have one yet)
and thanks to the help of ModMyApple.it forum
I will probably have one soon.
About the 3G iPhone:
The 3G iPhone will share almost the same firmware
of the actual iPhone, so, again, no big news.
I wish the community could react to all this and start
developing on the actual firmware version but I know
that will not happen.
I am getting bored lately but even
if I received a big proposal to acquire ziphone
I will not let you down.
Please stop complaining about your bricked phone
if you used other methods.
And keep donating if you want this project to live.
Take care and have fun!
Zibri
Tagi: th project, e care, exchange support, iphe, phe, itunes, magda, crypto, 3g, lena, mms, photo courtesy, few days, amp, proposal
Posted by planetbeing on under grunt work, community style, boot menu, heart of the problem, optis, pixel data, collaborative community, geometries, e mail, gradients, opti, data structures, peek, proposals, peoe, proposal, linux, blog |
I think the best way to handle this is for anyone interested to submit a proposal via e-mail to me about the boot menu. Then, I can put up the pictures on the blog for people to comment and have an opinion about. We can then figure out which one to use or maybe some combination of proposals or in any case, figure it out in a collaborative community style process.
I don't really have an opinion on what the logo should look like, whether it should be cartoony or not. I only think it should look good. =P
There are very few technical constraints on the boot menu. I'm willing to figure out whatever technical solution there needs be in order to get things to display properly. One thing to keep in mind is that space on the NOR is at a significant premium, and raw pixel data is expensive but procedurally generated stuff like gradients are possible. The only two current menu options are the iPhone OS and the openiboot console, but eventually a Linux option will be added. I can try animation as well, but again, you'd have to have an idea of how it can be done without using up a lot of NOR space.
But yeah, make us pretty!
Some progress on the NAND: Thanks to a huge amount of initial grunt work by CPICH, the NAND project is off the ground. We already have enough to get the proper drive geometries, and I've written and tested the DMA routines that are near the heart of the problem today. Hopefully, we can dump the raw NAND soon and take a peek at what kind of wear leveling data structures we're dealing with.
Tagi: grunt work, community style, boot menu, heart of the problem, optis, pixel data, collaborative community, geometries, e mail, gradients, opti, data structures, peek, proposals, peoe, proposal, linux, blog
Posted by planetbeing on under raw hardware, e care, bad blocks, locati, ftl, data structures, slew, gadget, amount of time, algorithms, kernel, sectors, ace, yaffs, proposal, benefit, linux |
We've made some progress on the USB gadget driver for Linux, and we're now running a generic serial gadget for communication. This implementation is important because USB is now a lot less laggy and things like ethernet over USB, etc., can eventually be supported, easing access.
We've also got pretty far with porting the NAND driver to Linux. Most of the read support is now there, and we've isolated the routines in the iPhone kernel where the raw hardware write occurs. CPICH and c1de0x are working on reversing it. Hopefully, it will be analogous enough to reads that it won't take a huge amount of time to work out.
This is different from reversing their FTL, however, which is a complicated slew of data structures, merge buffers and other exotic algorithms that take care of evenly distributing writes throughout the device and also making writes take less time.
I think reversing all of that would take too much time and effort. Instead, my proposal is to just reverse the hardware NAND writes. Instead of using a partition, we would have a loop-mounted root filesystem (similar to how Wubi is setup), with the root filesystem being a file on the Media partition. Since there's a non-empty file at that location, the FTL system, whatever it is, must create a one-to-one mapping from logical sectors to physical NAND pages. We can already read the mapping it creates (we have already reversed the read-side FTL code), and so all we have to do to alter the data is to write to the same pages we would've read from. Of course, this means that wear-leveling and bad block handling is not performed. However, if we use a filesystem that's aware of bad blocks and can wear-level (YAFFS or JFFS2), then it amounts to the same thing. The wear-leveling would then take place over the particular physical pages belonging to the rootfs image, rather than the entirety of the NAND. This would make the physical pages belonging to the rootfs image wear out a little faster than the rest of the NAND, but the actual effect of this should be inconsequential.
The additional benefit of this setup is that there's no repartitioning required, so setup is cinch. See
this wiki document for specific proposed implementation details.
Tagi: raw hardware, e care, bad blocks, locati, ftl, data structures, slew, gadget, amount of time, algorithms, kernel, sectors, ace, yaffs, proposal, benefit, linux
Posted by blogs@bobvila.com (Dave) on under superstar michael jordan, nba superstar, jupiter florida, airness, michael jordan, kmart, square foot, elevator, square feet, three times, neighbors, bedrooms, peoe, proposal |
NBA superstar Michael Jordan unveiled plans for a 37,942-square-foot in Jupiter, Florida.His Airness's home plans include an elevator, 11 bedrooms, cottage and guard gate. For those who lack a sense of scale, 37,000 square feet is about the size of your local Kmart.Being a full three times the size of the neighbors' houses, some people are not thrilled with the proposal. "It's insane, a waste. Cities see nothing more than a tax base in these giant homes, but I can't imagine anyone needing ...
Tagi: superstar michael jordan, nba superstar, jupiter florida, airness, michael jordan, kmart, square foot, elevator, square feet, three times, neighbors, bedrooms, peoe, proposal
Posted by on under public interest groups, brookings institute, fcc chairman, net neutrality, keynote speech, veriz, slashdot, gatekeepers, traffic management, fcc, comcast, principals, amp, proposal |
wiredog writes "From The Washington Post comes news that the FCC is preparing to propose net neutrality rules on Monday. Quoting: '[FCC Chairman Julius Genachowski] will discuss the rules Monday during a keynote speech at The Brookings Institute. He isn't expected to drill into many details, but the proposal will specifically be for an additional guideline on how operators like AT&T, Verizon, and Comcast can control what goes on their networks. That additional guideline would prevent the operators from discriminating, or act as gatekeepers, of Web content and services. ... The agency is expected to review what traffic management is reasonable and what practices are discriminatory. The guidelines are known as "principals" at the agency, which some public interest groups have sought to codify so that they would clearly be enforceable.'"
Read more of this story at Slashdot.
Tagi: public interest groups, brookings institute, fcc chairman, net neutrality, keynote speech, veriz, slashdot, gatekeepers, traffic management, fcc, comcast, principals, amp, proposal
