- 07-27-2010, 06:37 PM #76
- 07-27-2010, 06:41 PM #77
- 50 Posts
- 0 Post(s)
- 0 Thread(s)
- Rooted Stock Jelly Bean
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
- 07-27-2010, 06:55 PM #79
- 07-27-2010, 09:48 PM #80
- 07-27-2010, 10:37 PM #81
- 1 Posts
- 0 Post(s)
- 0 Thread(s)
Half-completed, now bricked? :'-(
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-v22.214.171.124 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-28-2010, 08:00 AM #82
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 126.96.36.199
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, 11:07 AM #83
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
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, 11:18 AM #85
- 07-28-2010, 11:39 AM #88
- 07-29-2010, 10:11 PM #89
- 07-30-2010, 11:18 AM #90
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, 12:00 PM #92
- 07-30-2010, 04:19 PM #94
- 07-31-2010, 03:06 PM #95
- 08-01-2010, 02:22 AM #96
- 08-01-2010, 10:30 AM #97
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, 08:27 PM #98
- 08-03-2010, 12:43 AM #99
- 08-03-2010, 01:56 AM #100