A few weeks ago MuscleNerd released a baseband downgrading solution for any iPhone 3G or iPhone 3GS running the special iPad 06.15.00 baseband. This solution came in the form of a new feature in RedSn0w, and it easily allowed those who were previously trapped on 06.15.00 to downgrade back to a fully functional iPhone baseband. Unfortunately newer bootrom iPhone 3GS owners trying to use this solution had no luck, and often encountered “no service” errors.
A week ago, Musclenerd from the iPhone Dev-Team confirmed that there is a third kind of flash NOR that caused problems for some iPhone 3GS users when trying to downgrade the iPad 6.15 baseband. This resulted in redsn0w showing that baseband downgrade was successful but when the iPad reboots after baseband downgrade attempt, the baseband was unchanged. After quite a lot of research musclenerd via twitter confirmed that an update to redsn0w will be released to fix all the errors. He also confirmed that changing the payload would fix the issue. Today Musclenerd announced over twitter that an updated version of Redsn0w iPhone 3GS baseband downgrade tool would be released. This updated version of redsn0w will work on those devices which were unable to downgrade the 6.15 baseband. However, musclenerd has also confirmed that this version of redsn0w will not support those devices which could not initially get 6.15 baseband ( newer devices ). He mentioned that the revised payload seems to work fine on the devices that were unable to downgrade earlier.
Here is what he said:
"Musclenerd claims to have found a way to change the IMEI of the iPhone3GS. According to him that was the reason causing iPhone users to have no signal because of no reason and the only plausible reason was IMEI. Changing that would apparently fix the signal issue. Also, IMEI changing is considered as illegal in many countries and is punishable by law. The iPhone Dev-Team will not and never release any tool that allows unethical behavior and beaks any laws. When asked if the IMEI changing tool would be released, musclenerd simply mentioned that it is illegal in many countries to change the IMEA and that it would be a bad idea to release such a tool."
Yesterday release of redsn0w 0.9.14b2 improves the iPad baseband downgrade and should cover anyone who couldn’t downgrade with 0.9.14b1. This version covers 3 different types of NOR chips in the iPhone 3G and 3GS (the earlier version covered only the most prevalent NOR chip). We’ve also simplified the process and added logging to help diagnose any remaining stubborn iPhones.
The revised steps are:
NOTE: The original warning about 3GS units manufactured in early 2011 or later still holds! They have a NOR chip that’s incompatible with 06.15.00 and so trying to install it will brick the device. Please read and re-read the warning in our earlier post.
A week ago, Musclenerd from the iPhone Dev-Team confirmed that there is a third kind of flash NOR that caused problems for some iPhone 3GS users when trying to downgrade the iPad 6.15 baseband. This resulted in redsn0w showing that baseband downgrade was successful but when the iPad reboots after baseband downgrade attempt, the baseband was unchanged. After quite a lot of research musclenerd via twitter confirmed that an update to redsn0w will be released to fix all the errors. He also confirmed that changing the payload would fix the issue. Today Musclenerd announced over twitter that an updated version of Redsn0w iPhone 3GS baseband downgrade tool would be released. This updated version of redsn0w will work on those devices which were unable to downgrade the 6.15 baseband. However, musclenerd has also confirmed that this version of redsn0w will not support those devices which could not initially get 6.15 baseband ( newer devices ). He mentioned that the revised payload seems to work fine on the devices that were unable to downgrade earlier.
Here is what he said:
redsn0w 0.9.14b2 at is.gd/ZXwnxF improves the 06.15 baseband downgrade and adds niche "DFU IPSW" feature twitpic.com/a40mlk
— MuscleNerd (@MuscleNerd) July 5, 2012
Other than that testing hiccup, the revised payload seems fine...will release improved downgrade later today.Happy 4th of July!
— MuscleNerd (@MuscleNerd) July 4, 2012
After day of debugging why reverted 3GS had no service, found it was blocked for unrelated reason!OTOH I figured out how to change IMEI
— MuscleNerd (@MuscleNerd) July 4, 2012
"Musclenerd claims to have found a way to change the IMEI of the iPhone3GS. According to him that was the reason causing iPhone users to have no signal because of no reason and the only plausible reason was IMEI. Changing that would apparently fix the signal issue. Also, IMEI changing is considered as illegal in many countries and is punishable by law. The iPhone Dev-Team will not and never release any tool that allows unethical behavior and beaks any laws. When asked if the IMEI changing tool would be released, musclenerd simply mentioned that it is illegal in many countries to change the IMEA and that it would be a bad idea to release such a tool."
Yesterday release of redsn0w 0.9.14b2 improves the iPad baseband downgrade and should cover anyone who couldn’t downgrade with 0.9.14b1. This version covers 3 different types of NOR chips in the iPhone 3G and 3GS (the earlier version covered only the most prevalent NOR chip). We’ve also simplified the process and added logging to help diagnose any remaining stubborn iPhones.
The revised steps are:
- Connect your iPhone in normal mode, then click “Jailbreak” after redsn0w identifies its model and BB version (you needn’t pre-select the IPSW anymore).
- Choose the “Downgrade from iPad baseband” option (you needn’t worry about de-selecting Cydia anymore).
- Do a controlled “slide to power off” shutdown of your phone and proceed through the normal DFU ramdisk steps.
NOTE: The original warning about 3GS units manufactured in early 2011 or later still holds! They have a NOR chip that’s incompatible with 06.15.00 and so trying to install it will brick the device. Please read and re-read the warning in our earlier post.
Source : Dev - Team blog
