Cannot Load ROM

[No Strings]

Hey guy, new to the PPCG scene. I am using the kitchen to build a ROM for my Verizon 6700. I get though the building process fine and into the RUU, however after the first data query I run into problems. It seems that after the RUU puts the unit into bootloader mode it cannot communicate with it anymore and I end up getting a 201 error every time. I did recently update with AKU 3.3 from Verizon's website and that worked just fine. Any ideas??

Neal

[TMB_XV6700]

NS,
Couple problems: build rom for the x.04+ RUU, and put your phone in bootloader before connection.
http://forum.ppcgeeks.com/showpost.p...&postcount=547
[This post belongs in the Apache Upgrade subforum. It would have been easy to search that forum (using the button at upper right) for "error 201".] Good luck, tmb

[meatball]

[I am a robot, it is easy to search and easier to point out. thank you 1001010100]
Thanks for answering the question. Could have stopped there.

[colonel]

Originally Posted by meatball

[I am a robot, it is easy to search and easier to point out. thank you 1001010100]
Thanks for answering the question. Could have stopped there.

Not sure what you mean or where you are going with this, but I would suggest slowing down a bit. You have 3 posts so far and all three are borderline offensive/unacceptable. Did this post have a point? Were you the original poster?

[No Strings]

Originally Posted by TMB_XV6700

NS,
Couple problems: build rom for the x.04+ RUU, and put your phone in bootloader before connection.
http://forum.ppcgeeks.com/showpost.p...&postcount=547
[This post belongs in the Apache Upgrade subforum. It would have been easy to search that forum (using the button at upper right) for "error 201".] Good luck, tmb

Thanks for the reply I will try that. I did try the original Verizon Bootloader ROM that was out before the kitchen was introduced (as I understand) and that had the same results. Is the x.04+ build any different than the original stand alone build where the unit needs to be in bootloader?

Sorry for posting in the wrong forum.

Neal

[No Strings]

Originally Posted by colonel

Were you the original poster?

No, that was not me. ,

Also, I currently have bootloader 1.04, is there any reason for me to upgrade it?

Neal

[TMB_XV6700]

Originally Posted by No Strings

Thanks for the reply I will try that. I did try the original Verizon Bootloader ROM that was out before the kitchen was introduced (as I understand) and that had the same results. Is the x.04+ build any different than the original stand alone build where the unit needs to be in bootloader?
Sorry for posting in the wrong forum.
Neal

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. [Edit: this last might not be true, as I understand some people with reverted bootloaders are flashing with the NoIDRUU, a slightly different animal whose distinctions are beyond me.]
[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].

[No Strings]

Originally Posted by TMB_XV6700

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

[No Strings]

Worked slick as a whistle, thanks! Now I need to find that nice dialer that has huge keys for my fat digits.

Neal