Thread: Cannot Load ROM
View Single Post
  #8 (permalink)  
Old 11-18-2007, 05:28 PM
No Strings's Avatar
No Strings
N00b
Offline
Threadstarter
Location: Shabbona, IL
 
Join Date: Nov 2007
Posts: 27
Reputation: 0
No Strings is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by TMB_XV6700 View Post
Neal,
The fundamental difference between the "x.04+ build" and the original "Verizon Bootloader" build is that the two use a slightly different Rom Upgrade Utility (RUU) to flash the image to the phone. The "x.04+" selection in the kitchen uses the NewBootloader RUU rather than the old standard RUU that you tried before. The actual rom image being flashed is not affected.

People who flashed the Verizon 3.3 upgrade directly (not the sanitized version from ppcgeeks) got a new bootloader version that had two key effects: 1) the standard RUU no longer worked (e.g. error 201), and 2) the amount of memory for the rom image was reduced on some devices (not yours, lucky for you). The uber-geeks developed the NewBootloader RUU to workaround the first issue and developed a bootloader "reversion" procedure (http://forum.ppcgeeks.com/showthread.php?t=7820) for those affected by the second issue. All affected phones (even those with "reverted" bootloaders) still need to use the NewBootloader RUU.
[By the way, I'm definitely not an authority on this stuff, just an information addict. All kudos to the originators: helmi_c, naigaman, et al].
Ahh that makes it much more clear. As I was (mis)understanding it the new bootloader that had the problem was the 2.04 not the 1.04. I guess I was just not reading it correctly. So anything with a .04 revision ending bootloader needs the new RUU, correct? I will give the x.04 compile with the phone in bootloader mode a run tonight, got to go get the new puppy (chocolate lab) first. Thanks for the information!

Neal
Reply With Quote