Originally Posted by tangobar

No problem, I just wanted to make sure I wasn't missing something obvious. I'm downloading it now, once my phone is charged up I'll flash it and see if it gives root access again.

OK, up and running, but no root, and no change in the behavior at the bootloader- trying to access RECOVERY gives a white HTC screen. In fact, after letting the PG32IMG load, the initial reboot did not work- it hung for over half an hour on the white HTC screen. I pulled the battery and it rebooted into 2.3.4 on the second try.

One thing I noticed during the PG32IMG update, it's still skipping updates for the bootloader and the second "TP":

1  TP
2  RECOVERY
3  BOOTLOADER    BYPASSED
4  SPLASH
5  BOOT
6  USERDATA
7  TP    BYPASSED
8  SYSTEM
9  RADIO_VZ

I'm going to try adding SU and busybox to see if there's anything different, but for now RootCheck is saying "no root access".

EDIT This RUU is freezing all over the place and the radios are weak- it's reverting to 1X. Since it's not doing what I need in terms of regaining root, I'm going to have to go back to the last RUU.

Download busy box & super user from the market & see if that works

Sent from my Incredible 2 using xda app-developers app

I've had two 14 hour days, so tomorrow if I can catch a break I'll try re-flashing the 2.3.4 RUU and adding those. I couldn't have done that anyway- I was unable to get past the lockscreen. A process was freezing up and all I had was the option of waiting or force closing, and it would happen again immediately after the FC anyway.

Originally Posted by sjpritch25

Download busy box & super user from the market & see if that works

OK, back. I re-flashed the 2.3.4 RUU, but still no change. I cannot access recovery- it goes to the white screen. During the reflash, I got a message I don't recall seeing before:

1 tp  ok
recovery  ok
bootloader  bypassed
spalsh1  ok
boot  ok
userdata  ok
tp  bypassed
system  ok
radio v2  ok

Do not power down phone
cannot roll back hboot version

That last message- about rolling back the hboot, I don't think I've seen that before.

I'm going to try attn1's downgrade tool here again, to see if it'll make a difference this time. But the big thing is, I can NEVER ENTER RECOVERY and I can't find any relevant threads about that. Has ANYONE ever seen that?

EDIT: Should have mentioned I tried to install busybox, got the message that "I am unable to verify whether or not certain utilities needed for this app to run are present and functional on your device. This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured. Please try the install again." So that confirms that while I have S-OFF, I do not have proper root.

I'm at a loss to what the issue is. Sorry

Originally Posted by sjpritch25

I'm at a loss to what the issue is. Sorry

I appreciate your trying to help. I know this is an oddball case- I haven't seen anyone else who seems to deal with quite the same thing. It seems to me the bootloader itself isn't working right, but I have no idea how to go about repairing/replacing that. I just want to know what the hell happened. I figure it was the OTA that killed it, but i don't know HOW.

I also went ahead and tried the tacoroot method, but I couldn't get past attempting the --setup command for tacoroot.sh- at that point, the phone went to my favorite white HTC screen and just stays there. I don't know what's going on, but if I let it sit for any amount of time the battery gets pretty warm and will show a significant discharge the next time I get it to boot up normally.

I may start a new topic for this, since it seems to be a different issue from the one this thread was started for.

Ok not sure if this will help or not but thought I would throw it out there. When I had to go back to S-On on my recently returned Dinc2 it seems I read that the boot loader is from 2.2.1 and has not been updated since then. Now this is just an idea and no clue if it will work but try to go back to S On and then load the 2.3.3 RUU and then try to S Off again. Again just an idea.

Originally Posted by zackspeed

Now this is just an idea and no clue if it will work but try to go back to S On and then load the 2.3.3 RUU and then try to S Off again. Again just an idea.

Interesting, I'll have to do some looking into that. I suppose that an unexpected change to the bootloader could have messed something up. Thanks for tossing that in!

I need to resurrect this thread. I am trying to understand why I can't get a recovery to work on my DI2- I'm just about giving up on getting root access back, aside from implanting this phone in the forehead of a Verizon employee and getting a new one (phone, not Verizon employee. Their best use is as a phoneholder anyway.) As far as I can tell, no one else on this forum or several others has posted with this particular problem- I see a lot of people successfully regaining root.

I have:
Downgraded to 2.2.1 and confirmed 2.2.1, hboot 0.97, S-ON
Upgraded to 2.3.3, confirmed, still hboot 0.97, S-ON
Rooted via Revolutionary, added CWM (through Rev), now hboot 6.13, confirmed S-OFF but no root and when I choose the RECOVERY option, it gets stuck on the white HTC screen.

Started over, followed all the steps again- downgrade, confirm, upgrade, confirm, root via Revolutionary but now manually flash Amon Ra, confirm S-OFF. Says it successfully flashes, but when I try to select RECOVERY, again it gets stuck on the white HTC screen.

Someone, please, what is the deal here? I've flashed 2 RUUs but the same problem continues to occur. These are not the same RUUs I was using before, so... what stays the same on the phone when you change RUUs??

Seriously, is there anyone who can explain this?