iPhone 2G to get iPhone OS 4.0 – take that, Apple!

At one point in the iPhoneOS 4.0 keynote I was almost sure I heard 1.7 million hearts drop. I’m talking, of course, about the announcement of the platform the new OS is coming to. Roughly 2% of iPhone users still use the original iPhone 2G. Apple, in its quest to win over the hearts and wallets of the general population built such a magnificent device that quite a significant amount of people are still quite content with it, despite all of the features, only present in the newer versions.

Well, it seems I’m not the only one who thinks the policy of shutting the original iPhone out of the new bright future of OS 4.0 is cruel and unusual punishment. Rebuilding OS Group – a small independent team led by William Campell and previously know for some hacks of the PSP and Nintendo OS’s among other things has recently announced they are already working on making a special version of the OS 4.0 adapted for the iPhone 2G.

This version will, of course be based on the one for the iPhone 3G as the two devices share very similar hardware. Work is hard in progress, but already roughly 40% of the functions work fine on the original Jesus Phone and the project has been moved to beta stage. I’m still on the fence whether this is a fake or not, but I’d like to beieve in a better brighter future where all iPhones are created equal.

[iphones.ru via fittingstorm]

-We are rewriting the 4.0 beta firmware released by Apple to create a custom firmware that can run on devices iphone 2g which is no longer available. To do this we studied the architecture of the firmware previously released by Apple on the device trying to understand how is it different from the released versions on other devices, in particular that of the iPhone 3G device, which is what most resembles the smartphones.

-We started rewriting some procedures are completely different from the other device, because this most likely hardware 2g iPhone which needs a different interface to the software side. We had to rewrite classes, procedures, protocols, and tunneling pipeling values and procedures, and drivers.

-We thought that the work was less demanding, but we have spent over 10 days in 3 people working five hours a day to rewrite an alpha of our custom firmware, all this because of the antiquated interface hadrware / software it needs the iphone 2g also because the 3G is almost identical to it.

-Obtained a first alpha release of custom firmware, we proceeded to write software that interacts with everything and bring the system on the device, we have relied on PwangeTool already had a basic concept of jailbreak and insertion of a custom firmware certificate . We decompiled in assembly code so you can take inspiration on the procedures we needed and adapt to our new tool for the custom firmware 4.0, firmware did not give us too many problems because now we have decided to take it to the beta instead of alpha.

Dai-Test that we have made the custom firmware after many attempts and rewrites was finally executed on device iphone 2g! There are many problems, 90% not working and there are often many crashes and freezes, but we took a step forward.

-We managed to correct some problems of stability that was unlocked and have the menu settings remained blocked, but there is much to be done, the smartphone is a brick in this state, we must work hard.

-We have started to analyze the Beta 2, there are procedures that had changed in this beta 2 are completely different!

-We created a script to execute Unix shell that will serve to analyze the various files and content of beta 2, and enter the changes manually in the beta 1 beta release when it recognizes the same syntax for this in order to save time and next beta and see where the beta making changes.

When the script is something new or some syntax changed manually are acting, but at least this way we should not start from 0% for each beta, indeed still gain time and it is hoped that this work will give us 80% of the work already done and prepared stable release 4.0 fw.

Beta-Test 2 Custom successful after three days of trial, much improved compared to our previous custom firmware.

-We have recently started working on beta 3 firmware, we’ve made changes to the system so fast thanks to our automated scripts that search through files and syntax strings, we managed to change previously manually querying a database that we have gradually populated manually, finding the strings to change to adapt to the device firmware 2g. We had the result that all the changes we made to the previous beta are going to succeed even on the beta 3, also sharing the work we have solved the serious mistake of crashes and reboots automatically that plagued our custom firmware. Working on a beta of the other more advanced and customized, the stability and reaction speed of the system pointed out differences, and since the beta 3 has corrected several bugs that were present on the previous beta have started working on some functions that gave problems before, but we could not touch because they were already in buggy beta firmware apple initial function as camera, screen, sms app, select Edit and remove applications. We are saying that when 40% of the system is working! but still many problems, although the main functions work well, the device seems to respond well to the architecture of the current firmware and we must find the various modules and classes that the slow, overloaded, and exploit more of the battery you have to download 12 hours of standby time! Many problems still remain, we have a serious error on a pipe that turns off the wifi when you try to connect with a password protected encrypted wep.Questa pipe is not present in the device firmware dedicated 2g but only those on the 3d and we understand how fit. There is a lot of work, we present results in a device which is a semi 2g itouch. Another big problem is still blocked the telephone, we are working on various baseband and the next update will soon announce the news on it.

-We are rewriting the 4.0 beta firmware released by Apple to create a custom firmware that can run on devices iphone 2g which is no longer available. To do this we studied the architecture of the firmware previously released by Apple on the device trying to understand how is it different from the released versions on other devices, in particular that of the iPhone 3G device, which is what most resembles the smartphones.

-We started rewriting some procedures are completely different from the other device, because this most likely hardware 2g iPhone which needs a different interface to the software side. We had to rewrite classes, procedures, protocols, and tunneling pipeling values and procedures, and drivers.

-We thought that the work was less demanding, but we have spent over 10 days in 3 people working five hours a day to rewrite an alpha of our custom firmware, all this because of the antiquated interface hadrware / software it needs the iphone 2g also because the 3G is almost identical to it.

-Obtained a first alpha release of custom firmware, we proceeded to write software that interacts with everything and bring the system on the device, we have relied on PwangeTool already had a basic concept of jailbreak and insertion of a custom firmware certificate . We decompiled in assembly code so you can take inspiration on the procedures we needed and adapt to our new tool for the custom firmware 4.0, firmware did not give us too many problems because now we have decided to take it to the beta instead of alpha.

Dai-Test that we have made the custom firmware after many attempts and rewrites was finally executed on device iphone 2g! There are many problems, 90% not working and there are often many crashes and freezes, but we took a step forward.

-We managed to correct some problems of stability that was unlocked and have the menu settings remained blocked, but there is much to be done, the smartphone is a brick in this state, we must work hard.

-We have started to analyze the Beta 2, there are procedures that had changed in this beta 2 are completely different!

-We created a script to execute Unix shell that will serve to analyze the various files and content of beta 2, and enter the changes manually in the beta 1 beta release when it recognizes the same syntax for this in order to save time and next beta and see where the beta making changes.
When the script is something new or some syntax changed manually are acting, but at least this way we should not start from 0% for each beta, indeed still gain time and it is hoped that this work will give us 80% of the work already done and prepared stable release 4.0 fw.

Beta-Test 2 Custom successful after three days of trial, much improved compared to our previous custom firmware.

-We have recently started working on beta 3 firmware, we’ve made changes to the system so fast thanks to our automated scripts that search through files and syntax strings, we managed to change previously manually querying a database that we have gradually populated manually, finding the strings to change to adapt to the device firmware 2g. We had the result that all the changes we made to the previous beta are going to succeed even on the beta 3, also sharing the work we have solved the serious mistake of crashes and reboots automatically that plagued our custom firmware.  Working on a beta of the other more advanced and customized, the stability and reaction speed of the system pointed out differences, and since the beta 3 has corrected several bugs that were present on the previous beta have started working on some functions that gave problems before, but we could not touch because they were already in buggy beta firmware apple initial function as camera, screen, sms app, select Edit and remove applications.  We are saying that when 40% of the system is working! but still many problems, although the main functions work well, the device seems to respond well to the architecture of the current firmware and we must find the various modules and classes that the slow, overloaded, and exploit more of the battery you have to download 12 hours of standby time!  Many problems still remain, we have a serious error on a pipe that turns off the wifi when you try to connect with a password protected encrypted wep.Questa pipe is not present in the device firmware dedicated 2g but only those on the 3d and we understand how fit.  There is a lot of work, we present results in a device which is a semi 2g itouch. Another big problem is still blocked the telephone, we are working on various baseband and the next update will soon announce the news on it.

Next ArticleDestination: Treasure Island set for iPad