• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Droid Inc 2 Borked by OTA?

T

tangobar

Lurker
Hey all,

I've searched through a lot of threads and my head is spinning. Last year I successfully rooted my Dinc2 via TheSentinel's method from here:
http://androidforums.com/incredible-2-all-things-root/396098-how-root-gingerbread-2-3-3-a.html and have used CM7 since then.

Four days ago, my phone shut off and when I tried to turn it on, it went into a bootloop. I got it into recovery, and received various "PG32diag.zip/nbh is missing" messages. When I try to use "Recovery" from the bootloader, it hangs on the white HTC screen. Attempting a factory reset just got it into a bootloop. I SUSPECT it was the OTA that caused it, but I didn't think CM7 would even get that.

I found the "Back to Stock Gingerbread 2.3.4" zip at xda, put it in my SD's root folder and managed to get the phone back up and running, since I'm on a business trip and I can't afford to be out of touch. Then, a day later, I got the latest OTA update and let it run, but the boot seems to hang. I re-flashed the Back To Stock again, and late last night the OTA struck again. I can't afford to have the phone get hung in a boot sequence at random times. Now, if the BTS zip is not in root, the phone does not boot up properly. If I try to go into the bootloader, it reflashes from the BTS zip, then prompts for restart.

I still have S-Off:

Vivo_w XB SHIP S-OFF RL
HBOOT 6.13.1002
RADIO 1.09.01.1111

I assume root is gone, but I haven't found a thread that deals with this particular circumstance. All I want to do is get the hell away from this OTA and back to CM7. And on top of it all, I cannot get adb to recognize the phone, despite having reinstalled the HTC drivers and adb a couple times.

The BTS is running 2.3.4, Sense 2.1, software 5.10.605.9. Since I still have S-Off, should I just run the entire "Downgrade to 2.3.3" process posted by TheSentinel in this thread, or is this on a whole different level? There are just too many variables here for me to be sure what I should be doing.

I am on my way back home, where I have an old rooted Eris that I plan to get back up and running so I have a reliable phone before I start playing with this thing.

Can anyone offer any suggestions, or have any questions? I'll be back online sporadically through the day, and I'd love to hear from anyone who can help this noob.
 
bberryhill0 said:
S-off is root. Sounds like you need to re-flash your recovery. I use 4ext.
Click to expand...

My understanding was that S-Off signifies that the bootloader is unlocked - root is when you have the SU binary running on the phone.

For example my phone is both rooted and has S-off set. If I ever have to return to stock (and loose root) then upgrade to GB I can still reroot - however I'd not be able to do that if I was on S-on since no-one has found a way to get root on GB on the Droid Incredible otherwise.
 
You're right- I do not have root anymore. 4ext won't run, and now I need to figure out how to get root back. I still can't get adb to locate the phone...
 
tangobar said:
You're right- I do not have root anymore. 4ext won't run, and now I need to figure out how to get root back. I still can't get adb to locate the phone...
Click to expand...

Success! I found that my original folder of the hack-vivow.cmd tool was OK. I fixed the ADB problem by re-reinstalling-repairing the HTC drivers while the command line window was open- all of a sudden, device found. Ran the hack, and now have 2.3.3 installed.

My biggest concern, though, is how to STOP the OTA from running. I thought I saw somewhere that if you change the name of the "otacerts.zip" file, that will do it? I was having trouble attempting that earlier, and left it for later since it wasn't the immediate problem. Still and all, this is a marked improvement- I found that the path was still open.

To summarize, I had CM7 running. I assume the OTA screwed it up. I managed to get the Back To Stock 2.3.4 running, but every time I went to the recovery screen, it would reflash the update, so I could not do anything in recovery.

Aaaaaand now adb isn't connecting again. What the heck? Helps if I check to make sure debugging is ON, fastboot is OFF, and non-Market apps is ON.
 
OK, I'm about at my wit's end here. I cannot load any recoveries on the phone. I've adb'd and fastbooted a ton, and revolutionary.io SEEMS to complete loading, but I cannot use the RECOVERY option on the HBOOT menu- selecting it causes the phone to immediately load the white "HTC" screen and stay that way for... well, for several minutes.

Am I being in too much of a rush? Does it need to take a while to load anything?

When I VOLDOWN and PWR to get into fastboot, here's what I see:

-Revolutionary-
VIVO_W XB SHIP S--OFF RL
HBOOT-6.13.1002
RADIO-1.09.011.622
eMMC-boot
apr 1 2011, 18:34:39

-- then the phone searches for the PG32DIAG/IMG files every time I go to the HBOOT screen- say I hit the PWR button while FASTBOOT is hightlighted, then again to go back to the bootloader, it'll run this again:

SD checking
loading... PG32DIAG.zip
image not found!
loading... PG32DIAG.nbh
No image or wrong image
loading... PG32img.zip
Image not found!
loading... PG32img.nbh
No image or wrong image!

I have done mulitple instances of letting it run the 2.3.4 Back To Stock RUU by renaming that to PG32img, and it always looks for it again.

I have seen a couple threads that refer to a damaged partion table, but the fact I have been able to get the 2.3.3 downgrade on here tells me it's not really damaged. I'm just about tearing my hair out for not being able to get a recovery working on here, though.

Does anyone know of a thread or discussion that addresses this problem? I'm trying to dig this up myself, but I also don't want to really wreck the phone.
 
You must log in or register to reply here.
Back
Top Bottom