yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Incredible 2] tangobar:
Back from the dead, another White Screen

Okay, I know this is resurrecting a long-dormant thread, but it describes EXACTLY the problem I'm having.

I rooted my phone last year with the "Root Your DInc2 Tutorial" - http://xdaforums.com/showthread.php?p=16671031 process, ran CM7 with no problems until early June when it began bootlooping. I believe the latest OTA was the culprit, but I still have S-OFF.

Initially I found the Back To Stock 2.3.4 RUU and used that since I absolutely had to have my phone working (was on a business trip). However, every few days the OTA would get pushed again, and I'd have to reflash the BTS RUU.

I finally had the chance to successfully re-run the "Root Your DInc2 Tutorial" method a few days ago, but I cannot access RECOVERY or FACTORY RESET from the bootloader- it goes to the white HTC screen from both. Using "adb reboot recovery" does the same thing.

At that time, I ran the Revolutionary.io tool. It of course mocked me for already having S-OFF, and offered to flash CWM. I also used the manual method from the tutorial. adb reports writing the recovery, but it doesn't seem to have any effect.

Every time I reboot into the bootloader, it checks for and does not find the PG32DIAG and PG32IMG files.

Is there something simple I'm missing? I have flashed back to 2.3.3, then to 2.3.4, then back to 2.3.3. I have tried flashing several different versions of CWM, 4EXT, and even Amon Ra recoveries. I've tried multiple methods, looked through multiple threads, but still cannot access the recovery.

One I have NOT tried yet is the TacoRoot method - http://xdaforums.com/showthread.php?t=1726134&page=5 , because I have read that it's riskier. Before I go that route, I'd like to hear from anyone who's successfully solved this problem, or anyone with any ideas. I'm pretty disgusted with the stock Sense and Verizon bullcrap. What am I doing wrong here?
[Verizon Droid Incredible 2] prototype7:
S-OFF is permanant, no need to do it again. Try flashing this RUU, rename it to PG32IMG.zip, put it in the root of your sdcard and boot into bootloader, when it checks, it'll find that and flash it for you, then you can just use a rooted stock ROM, there's a few out there.
[Verizon Droid Incredible 2] tangobar:
That's one of the RUU's I've already tried flashing a few times- I can't recall if it's 2.3.3 or 2.3.4. I'm currently on RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip In every case, the update skips updating the bootloader. The RUU's work fine after flashing except that I cannot load a recovery to achieve root and install a ROM, make a nandroid, or perform a Factory Reset- trying to select those from the bootloader causes an immediate reboot that then stalls on the white HTC screen.

Any ideas on how to get recovery to work? Do I have a corrupted bootloader? is there any way to fix that, or is this phone crippled?
[Verizon Droid Incredible 2] prototype7:
Flash a recovery with fastboot?
[Verizon Droid Incredible 2] sjpritch25:
Before, I help. You are still s-off
[Verizon Droid Incredible 2] tangobar:
Thanks for the reply! I do still have S-OFF. Here's what I have as a header on the bootloader:

-Revolutionary-

VIVO_W XB SHIP S-OFF RL

HBOOT-6.13.1002

RADIO-1.09.01.622

eMMC-boot

apr 1 2011, 18:34:39

I have checked with a rootcheck app and confirmed that I do not have root access.
[Verizon Droid Incredible 2] prototype7:
Can you use ROM Manager to flash CWM? Or flash 4EXT with the app? You won't have root until you flash the su binary, which you need recovery working to do.
[Verizon Droid Incredible 2] tangobar:
No, ROM Manager doesn't want to work UNTIL I have root (will not flash CWM Recovery, says an error occured while trying to run privileged commands). The Revolutionary.io tool SAYS it flashes CWM, shows writing data, but since I can't get to the RECOVERY screen on the bootloader, I can't tell whether it worked or not.

Trying to flash the 4EXT has had no effect- I've done it with PG32IMG zip files, no effect, and tried it with the apk (and I will try it again here just to confirm) but with no success.

EDIT: Retried installing 4EXT, no success. I tried 2 different versions of Busybox. Both say they cannot install because the phone is not properly rooted or SU settings are misconfigured.
[Verizon Droid Incredible 2] sjpritch25:
Just flash a recovery via fast boot then flash the su binary
[Verizon Droid Incredible 2] sjpritch25:
Download cwm from here

http://goo-inside.me/devs/aeroevan/cwm/recovery-clockwork-5.5.0.4-vivow.img

& save to your adb/tools folder

Open cmd adb remount

adb reboot bootloader

fastboot devices

fastboot flash recovery recovery-clockwork-5.5.0.4-vivow.img

Then you can flash the su binary
[Verizon Droid Incredible 2] tangobar:
The recovery you suggest is actually one I've already tried flashing, and that's the method I used. To be thorough I just tried it again, with the same result- I cannot enter the RECOVERY menu.

Here's the cmdline result of attempting the flash:

fastboot flash recovery recovery-clockwork-5.5.0.4-vivow.img

"sending 'recovery' (3742 KB) ... okay [ 1.88s]

writing 'recovery' ... okay [1.094s]

finished. total time: 2.01s​

When I select RECOVERY below FASTBOOT, it immediately pops up the white HTC screen and it will sit there for at least 30 minutes- that's been the longest I let it sit there.

I suspect this is not a standard case of a missing/corrupted file- I have tried renaming multiple RUUs to PG32IMG, I've renamed several recoveries (at the least, 5.5.0.4 and 4.*.*.* from clockwork as well as Amon Ra and several attempts to install 4EXT) with no change in the behavior of my bootloader. Whatever I'm doing, it's not changing the programming that has gotten altered and is preventing me from accessing RECOVERY or FACTORY RESET.

I'm just baffled by what could have done this- it literally came out of nowhere. One afternoon, the phone was working fine- I made a call, slept, was woken up by the alarm... and then 30 minutes later, I pulled the phone out to make a call and it was off. When I powered it up, it went into a bootloop on the whitescreen. All I can figure is that the OTA pushed in between dropping it in my pocket and pulling it out, but that's supposition on my part.
[Verizon Droid Incredible 2] sjpritch25:
What about hitting adb recovery.
[Verizon Droid Incredible 2] tangobar:
Nope, I addressed that in my first post- "...I cannot access RECOVERY or FACTORY RESET from the bootloader- it goes to the white HTC screen from both. Using 'adb reboot recovery' does the same thing."

any attempt to access recovery results in the white HTC screen immediately coming up, and then hanging there.
[Verizon Droid Incredible 2] sjpritch25:
try flashing the latest radio from here

Its From the 6.01.605.05 OTA:

http://xdaforums.com/showthread.php?t=1134451

Make sure you check md5 before flashing in bootloader.

2nd:

connect your phone to your computer

adb remount
adb reboot [b]right after the last command type[/b]
adb logcat > logcat.txt

You should get waiting for device and then it will start. The cursor will move down below waiting for device. Let it run a 30 seconds and close cmd and logcat.txt shall be in the same folder as adb. In your next post, please post it in

.
[Verizon Droid Incredible 2] tangobar:
1 of 3 of log.txt
[Verizon Droid Incredible 2] sjpritch25:
Did you successfully update the radio?

What RUU is this

Are you a Verizon customer
[Verizon Droid Incredible 2] tangobar:
Yep, I am a Verizon customer. The radio seems to have updated- it shows 1.09.01.0312 on the bootloader and I have wifi, 3g, and voice working fine.

The "BTS" RUU was posted on xda by Condemned Soul in the Return To Stock - PG32IMG thread. It's VZW version 5.10.605.9. I first flashed that because I was in the middle of a business trip and simply needed the phone working. When the OTA kept getting pushed (and kept causing a bootloop), I began working on getting BACK to a rooted condition and getting back on a ROM.

Also, no change in the behavior in the bootloader- after removing the PG32IMG.zip file, when rebooting to the bootloader it looks for the PG32DIAG and PG32IMG files, says none found or wrong image found, and then when I try to select the RECOVERY option, it immediately goes to the white HTC screen, Five minutes and counting now.
[Verizon Droid Incredible 2] sjpritch25:
The ruu you last flashed was unrooted. CD has a new RUU you can flash that's rooted with busybox and su. I would flash that and see if you can get into recovery again.

http://xdaforums.com/showthread.php?t=1737494
[Verizon Droid Incredible 2] tangobar:
Excellent, I'm downloading it now! I'll report back once I get it flashed!
[Verizon Droid Incredible 2] tangobar:
Sorry I haven't updated this, I've been on the go all day long. Are either of the Stock ROM files supposed to be flash-able as RUUs? CS refers to them as ROMs in the post, and when I tried both renamed as PG32IMG.zip, the bootloader won't get beyond parsing the 'stripped' version. The Full version, it didn't even get that far.

If you mean I should load them via RECOVERY... well, I still can't get to RECOVERY. the phone still immediately boots to a white HTC screen when I hightlight RECOVERY and hit the power button to select, then sits there until I pull the battery.
[Verizon Droid Incredible 2] Aldo101t:
just my 2 cents, doesn't the bootloader have to be relocked to flash an RUU?

CRAP HE IS ALREADY revolutuinary s-off, excuse please
[Verizon Droid Incredible 2] sjpritch25:
Did you check md5 before flashing?
[Verizon Droid Incredible 2] tangobar:
Yes. The "Stripped" had a matching MD5. I renamed it PG32IMG.zip and the bootloader found it, but only parsed it-

parsing PG32IMG.zip

After parsing, it did nothing- the main fastboot menu came up, with FASTBOOT, RECOVERY, FACTORY RESET, etc. At that point, I attempted to enter RECOVERY, and got the white HTC screen.

The "Full" did not have a matching MD5- I downloaded it twice to try and get a good match. I got the same MD5 on both downloaded files, different from the one listed at the download link. I ran that one second, and didn't intend to let it update because of the MD5 mismatch. I just wanted to see if the bootloader would read the file at all. It looked for the PG32DIAG and PG32IMG files, but ended saying "file missing or wrong file".

Let me ask again- CondemnedSoul referred to those files as ROMs- if they are indeed ROMs, don't I need to have access to a recovery to be able to load them? If not, I'm unaware of the method and haven't come across it in researching this issue.
[Verizon Droid Incredible 2] sjpritch25:
That was my bad. Here is a pg32img.zip for 2.3.4

http://jellybellys.minus.com/mvivow#1
[Verizon Droid Incredible 2] 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.
[Verizon Droid Incredible 2] tangobar:
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.
[Verizon Droid Incredible 2] sjpritch25:
Download busy box & super user from the market & see if that works
[Verizon Droid Incredible 2] tangobar:
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.
[Verizon Droid Incredible 2] tangobar:
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.
[Verizon Droid Incredible 2] sjpritch25:
I'm at a loss to what the issue is. Sorry
[Verizon Droid Incredible 2] tangobar:
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.
[Verizon Droid Incredible 2] zackspeed:
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.
[Verizon Droid Incredible 2] tangobar:
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!
[Verizon Droid Incredible 2] tangobar:
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?
[G Tablet Q&A, Help & Troubleshooting] treepog:
Guys,

I bought and rooted my Gtablet a while ago and I am thinking about trying some other ROMs now. I do not remember back when I did it which bootloader I have 1.1 or 1.2? I have been searching for a few hours but I am just going crazy with all the info. First I thought I had 1.1 but now I just don't know.

How can I be sure of my bootloader? also, if it makes any difference I am running CWM v4.0.1.5

Thanks in advance!!!
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
You can check which bootloader you have if you're running on a pershoot kernel (which is what comes with CyanogenMod):

1. Reboot tablet.

2. Run a Terminal Emulator app (or use adb), and then type:

gTablet$ [B]dmesg | fgrep VmaxIndex[/B]
[ 10.334790] Shmoo: s_CpuShmoo.ShmooVmaxIndex = 7

If ShmooVmaxIndex = 7, then you're running on a 1.1 bootloader. If it is 8, then you have a 1.2 bootloader.

ADDED:

You can also determine the bootloader version, without booting into a working kernel, by looking for a string in the bootloader files--either the binaries or the image files. On any Unix system, this command will work (use bootloader.bin, or part4.img, or whatever, instead of filename.ext in the command line below):

$ [B]fgrep -q recoverykey= [I]filename.ext[/I] && echo 1.2 || echo 1.1[/B]

On other systems, you can use a hex or binary editor and look for a recoverykey= string in the bootloader file (binary or image). If the string is present, then the bootloader version is 1.2; else it is 1.1. This is true on all the official (from ViewSonic) and unofficial (from the various nvflash packages available here on XDA) bootloader binaries that I've looked at (as of March 2013).

To extract the bootloader image from the gTablet, use this command after putting the tablet into APX mode using Power and Vol [-]:

C:\> [B]cd C:\SOME\PATH[/B] [I]Change to the dir. which has both [FONT=Fixedsys]nvflash.exe[/FONT] and [FONT=Fixedsys]bootloader.bin[/FONT][/I]
C:\SOME\PATH> [B].\nvflash --bootloader bootloader.bin --read 4 bootldr.img[/B] [I]Extract the bootloader on the gTab.[/I]
[G Tablet Q&A, Help & Troubleshooting] treepog:
Thanks very much for the reply. I just tried using Terminal Emulator for the past hour and I am really having a hard time figuring this out since I have never used terminal emulator before.

I tried typing:

gTablet$ dmesg | fgrep VmaxIndex

It says "permission denied"

I also typed:

dmesg | fgrep VmaxIndex

It says "permission denied"

How exactly do I do this??? Thanks very much.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
That's a very strange error for something so simple--BTW, that is the correct command to use; the "gTablet$" is just a prompt to tell you that it should be executed on the gTab.

1. Did you type the command inside the Terminal Emulator window on the gTablet?

2. Is your CyanogenMod working correctly?

3. What's the output of this command (again, type only the stuff in bold) on the gTablet:

gTablet$ [B]ls -l /system/bin/dmesg /system/xbin/dmesg /system/bin/fgrep /system/xbin/fgrep[/B]
[G Tablet Q&A, Help & Troubleshooting] treepog:
Yes, I typed exactly that:

dmesg | fgrep VmaxIndex

Into Terminal Emulator. :(

The Cyanogenmod was running "fine"...I was able to do the things that I wanted with the tablet which was play the few games that my daughter loves to play (diversion, angry birds, etc), watch movies through the netflix app, and browse the internet. Even when I would overclock I always noticed that it felt kind of sluggish though and i tried several browsers and none of them really ran great.

Back when I first modded this Gtablet (it was my very first Android device to mod). I remember having some issues when I went from Vegan to CM7. I am pretty sure I was not as thorough on cleaning up the tablet as i should have been before flashing.

Yesterday, after doing quite a bit of reading I decided to NVflash and totally clean up everything. I went back to 1.2-4349 and then followed the option 2 istallation instructions EXACTLY for Flashback 7.2. Wow, was I missing out I had always just thought the Gtablet was supposed to run like it was for me (not thinking that my botched install would have such an affect)...the Gtablet is running AMAZING now.

In any case I finished late last night and did not get a chance to update this thread.

Rather than just try to flash with what I think may have been 1.1 bootloader. I started from scratch and I am now running 1.2 bootloader on a Super clean machine with Honeycomb and VERY happy overall.

Thanks very much for your help!!!!
[Windows Phone 7 Q&A, Help & Troubleshooting] hedpe:
Hi all,

I have tried following these two methods to try and get to 7220, but I always get stuck on firmware 7304->7112 (first, second). Thereby, never actually getting to 7112.

Every time I go through the update procedure to 7112, it progresses half way, then it stops and reboots my phone with the error 80004005. I have tried:

clean NoDo install, and re-trying

removing the SD card

doing a hard reset on the phone

No matter what I try, the same thing happens when trying to get to 7112. How did other Samsung Focus users get to 7112?
[Windows Phone 7 Q&A, Help & Troubleshooting] baritoneguy:
This could be related to your version of Zune. The support tools and Zune must be on the same version.

You may have to reinstall the beta version of Zune 4.8 to make this work.

I can't remember the error code I received, but this is how I sorted it.

There is a post somewhere else that explains how to do it.
[Windows Phone 7 Q&A, Help & Troubleshooting] creamy:
Give the guide in this thread a go http://xdaforums.com/showthread.php?t=1101344 also if you have any issues read through this thread as all issues encountered have been addressed with relevant resolutions http://xdaforums.com/showthread.php?t=1215501

Hope this helps,

Creamy
[Windows Phone 7 Q&A, Help & Troubleshooting] hedpe:
thanks for your response. It seems like I need to unlock my phone first. What is the current defacto unlock method? Is it still Chevron?
[Windows Phone 7 Q&A, Help & Troubleshooting] day2die:
Flash you Samsung Focus with this ROM and try the update again.

http://xdaforums.com/showthread.php?t=1131022
[Windows Phone 7 Q&A, Help & Troubleshooting] hedpe:
thanks for the suggestion. I thought of doing this, but having trouble flashing the ROM:

http://xdaforums.com/showpost.php?p=17315234&postcount=107
[HTC Sensation] JettyLife:
Hey everyone, I'm looking into a Sensation 4G and was wondering if the two phones are interchangeable as far as roms and kernels go.

The only reason I ask is because I am currently running a Samsung Vibrant (Galaxy S 3G) and I know there is a difference between that and the Galaxy S 4G...

I mean, they do have different forums after all.

=)

Thanks!
[HTC Sensation] Towle:
Yes, every ROM and kernel is interchangeable between the two. The Vibrant and Galaxy S 4G were completely different phones whereas the Sensation and Sensation 4G are not.
[HTC Sensation] sromer:
Only difference is the Sensation 4G obviously has 4G.
[HTC Sensation] gugi_sat:
and how to tell the difference between Sensation and Sensation 4G?
[HTC Sensation] lianw:
Can't tell if serious.