02-12-2016 04:17 AM
493 ... 23456 ...
tools
  1. Tattrpuff's Avatar
    After I did toasts part 2, I ran the latest RUU and still got the 170 usb error. I then tried the 1.32.651.6 RUU and it worked like a charm.

    Do you guyz think that the person checking my phone will look at the pri version to see if i had rooted it?? theres a way to flash 1.40 but i just unrooted and dont want to have to go down that route again until i get my new phone.

    Thanks guyz
    YEAH!!!! Perfect. If you are at RUU'ed 1.32.651.6, you should be able to update your PRI through system update, if you are on stock shouldn't you? I believe I did when I turned mine back in. But the guys at radio shack didn't check anything on it at all! Have you tried to up date it now you are stock with the latest RUU? I wouldn't think you would have any problem what so ever.
    07-27-2010 05:37 PM
  2. Bikram72's Avatar
    I ended up doing the ota update to 1.47 so now i everything is stock and upto date cept for the pri which is basically stuck at 1.34 because it is modified by the eng hboot and stays that way even after running a RUU.

    best solution, but i have already unrooted so i cant do it.
    xda-developers - View Single Post - [Partial GUIDE] Flashing Images to EVO Partitions
    Tattrpuff likes this.
    07-27-2010 05:41 PM
  3. trooper54's Avatar
    I ended up doing the ota update to 1.47 so now i everything is stock and upto date cept for the pri which is basically stuck at 1.34 because it is modified by the eng hboot and stays that way even after running a RUU.

    best solution, but i have already unrooted so i cant do it.
    xda-developers - View Single Post - [Partial GUIDE] Flashing Images to EVO Partitions
    isnt there an option some where to update pri?

    i dont think its a big deal, i dont think they'll notice, but if they do play dumb.
    07-27-2010 05:50 PM
  4. Bikram72's Avatar
    isnt there an option some where to update pri?

    i dont think its a big deal, i dont think they'll notice, but if they do play dumb.
    haha will do

    and there is an option to update the prl, but not the pri.
    07-27-2010 05:55 PM
  5. Tattrpuff's Avatar
    haha will do

    and there is an option to update the prl, but not the pri.
    Your right...I was thinking PRL. No way to update it as such. The link you posted only fakes it, doesn't actually update it.
    07-27-2010 08:48 PM
  6. beandog's Avatar
    I was running DC 3.2.3, and so I ran the first RUU (1.32.651.1_Radio_1.39....). After several tries, it started going through the process of getting me back to normal. But it failed partway through, and thereafter I couldn't get it to even make it past the first USB connection error, and I swear I tried 20 times. Now, I get in a boot loop where I just see the white HTC logo for a little bit and then it reboots.

    I can get into my RA-evo-v1.7.0.1 recovery after taking out the battery. So I tried restoring my Nandroid backup... No dice, I get the same boot loop. I tried flashing DC 3.2.3, and same boot loop. I tried flashing CM 6, it fails on the assertion on the bootloader version. It seems I'm back to version 0.79 of the bootloader, rather than 0.76.

    So I can't boot up, I can't flash either of my ROMs, I can't get back to my backup, and I can't get into adb from the PC because I can't boot up.

    Am I totally screwed? What should I do?
    07-27-2010 09:37 PM
  7. streetzlegend's Avatar
    Greetings, I have not yet attempted to unroot as stated in this thread, I just want to verify that I will be able to do so successfully.

    I did the toast root method part 1 and 2, have used a few roms but my current Rom and Kernel are:

    Fresh Evo 1.0.1.
    netarchy-toastmod kernel version 3.7.5
    ClockworkMod recovery 2.5.0.1

    I got the phone on release date and did the OTA for updating the SD card issue, after that I rooted and never applied any other OTA update that came out. Should I be safe unrooting and going back to stock using the method on this thread? How can I also verify what version RUU I should use?

    Any help will be greatly appreciated.
    07-28-2010 07:00 AM
  8. Tattrpuff's Avatar
    I was running DC 3.2.3, and so I ran the first RUU (1.32.651.1_Radio_1.39....). After several tries, it started going through the process of getting me back to normal. But it failed partway through, and thereafter I couldn't get it to even make it past the first USB connection error, and I swear I tried 20 times. Now, I get in a boot loop where I just see the white HTC logo for a little bit and then it reboots.

    I can get into my RA-evo-v1.7.0.1 recovery after taking out the battery. So I tried restoring my Nandroid backup... No dice, I get the same boot loop. I tried flashing DC 3.2.3, and same boot loop. I tried flashing CM 6, it fails on the assertion on the bootloader version. It seems I'm back to version 0.79 of the bootloader, rather than 0.76.

    So I can't boot up, I can't flash either of my ROMs, I can't get back to my backup, and I can't get into adb from the PC because I can't boot up.

    Am I totally screwed? What should I do?
    Have you tried any of the other RUUs?
    07-28-2010 10:07 AM
  9. trooper54's Avatar
    I was running DC 3.2.3, and so I ran the first RUU (1.32.651.1_Radio_1.39....). After several tries, it started going through the process of getting me back to normal. But it failed partway through, and thereafter I couldn't get it to even make it past the first USB connection error, and I swear I tried 20 times. Now, I get in a boot loop where I just see the white HTC logo for a little bit and then it reboots.

    I can get into my RA-evo-v1.7.0.1 recovery after taking out the battery. So I tried restoring my Nandroid backup... No dice, I get the same boot loop. I tried flashing DC 3.2.3, and same boot loop. I tried flashing CM 6, it fails on the assertion on the bootloader version. It seems I'm back to version 0.79 of the bootloader, rather than 0.76.

    So I can't boot up, I can't flash either of my ROMs, I can't get back to my backup, and I can't get into adb from the PC because I can't boot up.



    Am I totally screwed? What should I do?

    Wow, that sounds terrible. I dont know where to start.

    I guess if you can load into recovery, while your in recovery you should be able to get ADB to work. Run adb devices" It will show your device serial number as well as the state its in, in this case recovery. Give that a shot.

    Down load this link
    http://geekfor.me/evo/rom/Supersonic...1.1_rooted.zip

    And try to flash that through recovery. Make sure you do a full wipe.


    If that goes through, you should be able to run the 1.47 RUU.

    Let me know if that works. We'll go from there.
    07-28-2010 10:17 AM
  10. Tattrpuff's Avatar
    Greetings, I have not yet attempted to unroot as stated in this thread, I just want to verify that I will be able to do so successfully.

    I did the toast root method part 1 and 2, have used a few roms but my current Rom and Kernel are:

    Fresh Evo 1.0.1.
    netarchy-toastmod kernel version 3.7.5
    ClockworkMod recovery 2.5.0.1

    I got the phone on release date and did the OTA for updating the SD card issue, after that I rooted and never applied any other OTA update that came out. Should I be safe unrooting and going back to stock using the method on this thread? How can I also verify what version RUU I should use?

    Any help will be greatly appreciated.
    Just to be safe...I would return back to a rooted stock rom. I would use the ENG-PC36IMG in toasts part two. I believe you will have to do toasts part 2 over again so you can back down. This will put you at version 1.17. Then use the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe RUU and stick with it if it errors out and you should be good. After that do any OTA updates available, you'll be set!
    07-28-2010 10:18 AM
  11. trooper54's Avatar
    Greetings, I have not yet attempted to unroot as stated in this thread, I just want to verify that I will be able to do so successfully.

    I did the toast root method part 1 and 2, have used a few roms but my current Rom and Kernel are:

    Fresh Evo 1.0.1.
    netarchy-toastmod kernel version 3.7.5
    ClockworkMod recovery 2.5.0.1

    I got the phone on release date and did the OTA for updating the SD card issue, after that I rooted and never applied any other OTA update that came out. Should I be safe unrooting and going back to stock using the method on this thread? How can I also verify what version RUU I should use?

    Any help will be greatly appreciated.
    You should be fine, however i recommend wiping and then flashing the rooted stock i posted above prior to running the RUU. If that works i will adjust my guide appropriately.
    07-28-2010 10:19 AM
  12. trooper54's Avatar
    Just to be safe...I would return back to a rooted stock rom. I would use the ENG-PC36IMG in toasts part two. I believe you will have to do toasts part 2 over again so you can back down. This will put you at version 1.17. Then use the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe RUU and stick with it if it errors out and you should be good. After that do any OTA updates available, you'll be set!
    haha one step ahead of me =P
    07-28-2010 10:20 AM
  13. Tattrpuff's Avatar
    haha one step ahead of me =P
    Just trying to help out!
    07-28-2010 10:39 AM
  14. caseydietz's Avatar
    Dude, this worked like a charm... unrooted and awaiting froyo tomorrow.
    Many thanks!!!
    Cheers
    07-29-2010 09:11 PM
  15. slvrprelude's Avatar
    soi if i update on tuesday withoiut returning to stock will it mess me up? and so iff the ruu doesnt work n im on hboot .79 then i need to run the RvU1.0 as update.zip from my recovery? then do the ruu? i have a stock rom with root and the netarchy/toasty kernal
    07-30-2010 10:18 AM
  16. trooper54's Avatar
    soi if i update on tuesday withoiut returning to stock will it mess me up? and so iff the ruu doesnt work n im on hboot .79 then i need to run the RvU1.0 as update.zip from my recovery? then do the ruu? i have a stock rom with root and the netarchy/toasty kernal
    The RUU should work with the .79 Hboot, however if it doesn't, you could go the eng hboot route.

    Installing the update may not mess you up, but will most likely break your root.

    Wait until the rooted version comes out, then flash.
    07-30-2010 10:45 AM
  17. slvrprelude's Avatar
    whats the eng route? the ruu has given me the usb error over 30 times uninstalled and reinstalled drivers atleast 5 times
    07-30-2010 11:00 AM
  18. trooper54's Avatar
    whats the eng route? the ruu has given me the usb error over 30 times uninstalled and reinstalled drivers atleast 5 times
    .76 bootloader is referred to as the engineering boot loader.

    i believe this is most easily attained with toasts method part 2
    07-30-2010 12:11 PM
  19. slvrprelude's Avatar
    so can i just do the simple root program? oposed to the toasty part 2? or do i have to be in the loader white screen/ cuz if i dont go to white screen the ruu works
    07-30-2010 03:19 PM
  20. Tattrpuff's Avatar
    so can i just do the simple root program? oposed to the toasty part 2? or do i have to be in the loader white screen/ cuz if i dont go to white screen the ruu works
    Yes you can do Simple Root and get the same result. Make sure you do a Nand backup first.
    07-31-2010 02:06 PM
  21. campanth's Avatar
    I have read through this entire thread and did not see this mentioned. Can someone please confirm if this works if rooted using unrEVOked 3? I would like to get back to stock.
    08-01-2010 01:22 AM
  22. slvrprelude's Avatar
    well i could flash custom roms with unrevoked n had the recovery stuff but no this didnt work untill i flashed some junk and tried simple root and not really sure what i did but finally got a root safe ruu to work and then the signed then did the ota updates and then flashed the new froyo. my hboot went down to .76 the back to .79 when i was thought i had to have .76 but idk it was confusing. and run the ruu not in the bootloader. u cant run the ruu from the white bootloader screen. you do it from the phone so it might work if u skip all the junk and install the windows 7 drivers(assuming ur on it) and just run the signed ruu or older root safe ruu from the home screen with usb debugging on and when it restarts your phone hold don the vol down key to help it in.... mine kept rebooting but didnt want to actualy install till i held the stupid button down. otherwise if u try from he bootloader or so on u get the battery error on a fully charged or you get the usb error even if u do the hboot usb andc wait for it to say plug
    08-01-2010 09:30 AM
  23. Tattrpuff's Avatar
    I have read through this entire thread and did not see this mentioned. Can someone please confirm if this works if rooted using unrEVOked 3? I would like to get back to stock.
    Yes..it will work. However it seems that the only way that this work in the least frustrating way is use Simple Root first which will put you back at 1.17. Then use the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe, then either OTA from there or use the newest RUU to get you back to 1.47. The original way that Liquidjesus has in OP works...just doesn't work as quickly as most people want with out the frustration. And this way seems like the long way, but less frustrating. As always NAND Backup before moving forward, even if you want to just return to stock for whatever reason.
    08-01-2010 07:27 PM
  24. yungwunn911's Avatar
    Yes..it will work. However it seems that the only way that this work in the least frustrating way is use Simple Root first which will put you back at 1.17. Then use the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe, then either OTA from there or use the newest RUU to get you back to 1.47. The original way that Liquidjesus has in OP works...just doesn't work as quickly as most people want with out the frustration. And this way seems like the long way, but less frustrating. As always NAND Backup before moving forward, even if you want to just return to stock for whatever reason.
    link to simple root method?

    im stuck too.
    08-02-2010 11:43 PM
  25. Tattrpuff's Avatar
    link to simple root method?

    im stuck too.
    Search...its your friend.

    http://forum.androidcentral.com/showthread.php?t=21619
    08-03-2010 12:56 AM
493 ... 23456 ...
LINK TO POST COPIED TO CLIPBOARD