Develop Bugs

Error "main version is older" "Update Fail!" Truly RESOLVED!!

Do you have an HTC Evo and you want to truly get it rooted and have the NAND Unlocked? I've figured out how to get this done when the other methods out there today result in the error "main version is older - update fail!" when you try to downgrade your Evo from 1.47 to 1.32. I searched high and low and couldn't find a solution for this error. The more I searched the more I learned about the stage that was failing and walla, I figured out a solution. This should work for you too.
The instructions below will give you full root, NAND unlock, and Recovery from start to finish.
All files are attached in this archive. It's large but I think it's best to use the files/versions that I know will work. Feel free to post mirrors if you are able to host.
During the process below the phone can be connected to your PC via USB.
Files:
bit.ly/evonand
Large file but it has everything you need!
1) Revert your Evo to the stock setup using the file:
1=RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe
Follow the steps on the update program, allowing it to flash your phone to the stock 1.47 setup.
2) After the phone is ready to unlock the screen skip through the setup and get to the home screen. Enable USB debugging.
3) In the folder named: "2-Root+Recovery" from my archive, run the file: "reflash.exe"
4) When this application is launched it does it all automatically. The result will be a rooted EVO with a custom Recovery installed. Boot the phone back to the home screen again.
The HBOOT Drivers for your PC are in this folder as well, if you haven't already install them from one of the previous guides. You'll see what I mean during the reflash.exe process.
5) Once you're back to the home screen, enable the USB Drive option so you can browse your SD card on your PC.
6) Copy this file (Available in my archive) to the first level of the SD Card:
3-ROM_Supersonic_1.32.651.1_rooted.zip
7) When the copy is complete, power down the phone. Hold down the volume down key while powering back on the phone. After the initial check for update it does automatically, select "Recovery" from the options.
8) Using the recovery program that comes up, clear the user data and cache, then select the option to install .ZIP file from SD Card.
9) Proceed with installing the ROM you copied to the SD card in step 6. When this is complete, Recovery will say "Complete" Reboot the phone using the options on the Recovery program and skip through the setup options, getting to the home screen.
Here's your status at this point - Rooted, Custom Recovery, and downgraded to OS 1.32
10) Open the folder "4-NAND Unlock (1.32)" and run "Simple root.exe"
11) You're now on step 2 thanks to the above steps. Click on "Step 2" on this simple root program. Follow the instructions and then when that's complete, run "Step 3" to flash a newer Recovery program. The steps above have installed an older version.
12) And that's a wrap. In step 11 you'll notice the Update Fail error doesn't come up. You're able to flash the update needed to achieve NAND Unlock and you can, in my case, now install the super speedy and functional Froyo ROM from Cyanogen. And trust me, it's worth it. The ROM is fun and responds faster than ever before! Enjoy

so this is just using unrevoked3 to root and then downgrading you so you can use the original simpleroot correct?

yeah thats what kept happening to me. I used unrevoked at first, and then tried doing the toast root and it wouldnt let me because of "older version" so i had to do simpleroot and had no prob after that

why are you downgrading at all just root the latest 1.47 and flash CM6. no need to go back to 1.3

thanks, this worked for me, even went back to full unrooted stock and tried the simple root ota and kept getting that error. this worked, but how do i make sure nand is unlocked? I restored nandroid to the last backup i had when i was rooted with Unrevoked3, hopefully that does not screw things up.

N00dle said:
so this is just using unrevoked3 to root and then downgrading you so you can use the original simpleroot correct?
Click to expand...
Click to collapse
Yes and no - You do use the simpleroot in the end, but start on NAND unlock steps since the previous work gets you rooted and downgraded.

OneStepAhead said:
why are you downgrading at all just root the latest 1.47 and flash CM6. no need to go back to 1.3
Click to expand...
Click to collapse
Good point, but this thread is meant for those of us who had issues performing the simple root OTA 1.47 edition.

Where is the archive!?

Worked for me.
Someone who has been fighting this probably already has most of what is in your archive already. All they would probably need beyond that is the older rooted stock ROM and maybe the RUU.

Uhm...OP. Your post fails in same place many others do...you do not have CLEAR instructions on when to be USB attached, when mounted when charging, where to put the files...what system you were running all this on...etc. (When you do mention USB you call it 'usb drive option'...not heard that term before.)
I am a training developer and instructor for many many years. It is so very common to see someone write instructions and miss the bits they 'just know'. If you are aiming at noobs with this...you might want to put in all the minutia.
Good try though and great job sharing your experiences and what worked for you. Sorry for picking on you.

I can confirm this actually does work I discovered this method a week ago and have been helping members use it. I've also been working on a tut just not that great at writing it which is very important as the user above pointed out. I'm also working on a automated method to get this going easier for users. if anyone really needs help getting this done send me a pm as I put in many other threads I will walk you thru it in english laymans terms. Thanks op great work where did you find it?

Im having the same issues as the OP had and I tried doing the first step of reverting but i get Error: 170 which states can't connect to device. And says make sure USB is plugged in blah blah.. Yet it is. Whats the deal

tlxxxsracer said:
Im having the same issues as the OP had and I tried doing the first step of reverting but i get Error: 170 which states can't connect to device. And says make sure USB is plugged in blah blah.. Yet it is. Whats the deal
Click to expand...
Click to collapse
Did you make sure Debug is checked?

Still can't get past the main version is older message
Rooting the EVO
On friday a friedn tried to root my EVO and was using simple root, and he couldn't get it to work. I'm not sure how far he got but here is what I know so far, and what i've tried to get it to root. Please offer instructions on what I should do to get rooted and get a good ROM loaded to the phone. Though I am not technologically ignorant, I have never rooted a phone, and I am not a programmer. Please dumb down your instruction for a noob.
Firmware Version
2.1-update1
Baseband Version
2.05.00.06.10
Kernel version
2.6.29-789bf291 [email protected] # 1
Build Number
1.47.651.1 CL195459 release-keys
Software number
1.47.651.1
Browser version
webkit 3.1
PRI Version
1.40_003
PRL Version
60668
Desktop Operating System
WinXP Pro SP3, 32 bit
These are the versions I see in hboot
SUPERSONIV EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-014F
TOUCHPANEL-ATMEL224_16AB
RADIO-2.05.00.06.10
Apr 14 2010, 15:41:34
Steps I have attempted
1 - Tried the method here...
ht tp : // forum. ppcgeeks. com / showthread.php ? t = 123714
(remove spaces to activate link, i'm new so i can't post links in messages)
and got stuck at step 1F because the phone never asked if I wanted to start the update, just got the “main version is older” error
2 - Tried Simplerootfull.2
Had error with .net framework v4. Something or other, downloaded newest version and then I was able to install the program. However, on step1 I got the “Main Version Older” error.
3 – Tried This
ht tp : // forum. xda- developers . com / showthread . php ? t = 739321
(remove spaces to activate link, i'm new so i can't post links in messages)
Which is specifically suppsed to address the “Main Version is Older” error
Step 1 – Im pretty suyre I already had this ROM installed, because it installed 1.47.651.1, Radio 2.05.00.06.10 and CL195459, which I already had installed, as you can see above. I did the update anyway, and it completed with a picture of the phone and a green circle with several arrows, then I got the white HTC Evo Screen and sprint boot sounds etc.
Step 2 – Completed Succesfully
Step 3 – running reflash.exe automatically starts unrevoked3, which reboots the phone to the HBOOT screen, and it tries to load the pcimg file that I already had on the card, gives me the Main Version is Older Message, I then select, Vol Down, to tell it not to reboot. Then I follow the onscreen instruction in unrevoked3, which tells me to “Press Volume down to choose “HBOOT USB” and then press power. Make Sure driver is installed!” I can only guess it's talking about the driver to communicate with the PC, but whatever the intent, I still get the “Main Version is Older!” error.
I guess I don't understand something fundamental to this process, because i've now tried three different methods to root this phone, one that was SPECIFICALLY supposed to address the “Main Version is Older!” error message, and i'm still stuck at square one. I appreciate all the help I can get.
While i'm waiting for a reply for this, i'm going to delete all the files i've copied to the root of the sdcard and try again. Stop me if im about to screw something up....
Thanks
Chris

So I deleted all the files I copied to the sdcard myself, and then ran reflash again. This time there was no pcimg to attempt to load, so I was able to do what it required, and it looks like it tried to run hboot using the android drivers through the USB cable. I had to install the android drivers in the middle of this step but it appeared to work.
Step 4 – Appears to have worked, but unrevoked is still “Waiting for reboot...” so i'm not sure if it got it all done or not...
Step 5 – Enabled USB Drive.
Step 6 – File Copied Succesfully
Step 7 – When I select recovery from the options, I get the regular green headers across the top of the HBOOT screen, and then highlighted red I see
FASTBOOT USB
but I dont see any option that says “clear user data and cache” or the option to install a .ZIP file from the SD Card. I'm going to try and do reflash again.

Yes, i know usb debug is checked.
I tried to use simpleroot, and it goes smoothly up until the last step when it says wait till it goes to the white screen with the skateboarding android. It never goes there and when I try to do it manualy it still does main version is older.

i think I'm making progress
Ok this time I got past the waiting for reboot message in unrevoked, and got the
“Waiting 5 seconds because windows sucks”
then got
“Communications with Phone unexpectedly interrupted. Try Again”
both in the unrevoked windows in, well, Windows
on the phone however, I see the Clockwork Recovery v2.5.0.1 and I now see some of the options that I did not before. However the wording is slightly different. I've got
wipe data/factory reset (instead of clear the user data)
wipe cache ( instead of clear cache)
Install zip from sdcard.
So I guess now i'll go back to Step 8, and do those steps.
Step 8 – since I didn't have “clear the user data” I selected “wipe data/factory reset”
It formatted my sdcard, I'm gonna be really unhappy if that wiped my backups of my SMS messges and Call Log. I needed that info in there, that's why I backed it up.
I selected “wipe cache partition”, even though it said it was formatting the cache in the previous step.
Nothing noteworthy after that action.
Step 9 – since the instruction are a little unclear as to exactly how to do this I just selected “install zip from sdcard”, followed by “choose zip from sdcard”
I did see that it did not remove the calllogbackup folder or smsbackup folders, so I hope that those contents are still intact. It also found the 3-ROM_Supersonic_1.32.651.1_rooted.zip file that I copied to the sdcard before I did the wiping operations, so i'm assuming my concerns, at this point, are unwarranted. I still feel better when I can see my sms and call logs in the phone though.
Ok it appears like i've got a “Install from from sdcard complete.” message with no errors that I can see...
So “reboot the phone from the options on the Recovery Program” doesn't appear to be a available selection, so i'll pick “Go Back” and then “Reboot Now”
I have confirmed at this point that I have the following changes in Software Information
Kernel Version
2.6.29-a2443432
[email protected] # 1
Build Number
1.32.651.1 CL171253 release-keys
Software Number
1.32.651.1
So it appears that i've done the following
1 – rooted the EVO
2 - Installed the custom recovery “Clockworkrecovery”
3 – Downgraded to OS 1.32.651.1
Yay!
On to step 10...

Step 10 - Running Simpleroot, and it is giving me lots of “Good!” messages, I'll take that as a good sign. It's loading the PC36IMG.zip like it did before, crossedfingers hoping for no “Main Version is Older Error”
…...
Sweet! I Got the “Do you want to start Update?” so I guess that means I am progressing in the right directino
TP (it looks like it skipped this one altogether, there is no message to the right of it...)
TP “Bypassed”
Update Complete do you want to reboot the device?
Yes I do, and it booted just fine, and then I was able to Flash to the updated ClockworkMod Recovery v1.8.2.2. Success!!!
Thanks for the help with this OP, i hope my extra notes help anyone who got stuck where i did!
Now i just need to decide what custom rom i want to run.

Thank you SO MUCH!!!! I was beating my head against the wall all night trying to use the OTA 1.47 SimpleRoot. This worked like a charm!!

Im still not even able to get past Step 1 by using the .exe to factory restore..

EVO Bricked? Please Help

I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….

Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk

What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw

did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.

@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted

Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com

Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.

Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse

Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...

Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse

Yes your just not rooted anymore. Run whatever process worked for you the first time

Try whitslack's method.
EDIT: Nevermind, no can do.

What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse

xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first

Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse

I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse

latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!

Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!

Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse

I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse

Need Help Unrooting. S-ON already done but now Says Aborted?

Quick Back story I went to Florida on vacation and while at movies It fell 2 feet from the cup holder and the touch screen wasnt fully functional only parts of the screen so I knew I have to take it to sprint to get it repaired. So I backed up my contacts and apps/data.
Then I tried taking out the battery a couple of times but nothing it would just stay loading on the HTC Evo Screen I left it, 1 hr later came back still the same. Loading.
I cleared the dalvik cache and cache. then clear storage on the device still nothing So came online read how to turn on the S-ON did so by flashing the "unrevoked-forever-son.zip" It rebooted but never came fully on so after 5 mins took out battery checked it and was now with S-ON.
Now I have to remove the clockwork mod Ive tried flashing the "PC36IMG.zip" through the choose zip option it says aborted and it is in the main directory of my sd card.
Any help would be appreciated.
R.Soul

RhythmaticSoul said:
Quick Back story I went to Florida on vacation and while at movies It fell 2 feet from the cup holder and the touch screen wasnt fully functional only parts of the screen so I knew I have to take it to sprint to get it repaired. So I backed up my contacts and apps/data.
Then I tried taking out the battery a couple of times but nothing it would just stay loading on the HTC Evo Screen I left it, 1 hr later came back still the same. Loading.
I cleared the dalvik cache and cache. then clear storage on the device still nothing So came online read how to turn on the S-ON did so by flashing the "unrevoked-forever-son.zip" It rebooted but never came fully on so after 5 mins took out battery checked it and was now with S-ON.
Now I have to remove the clockwork mod Ive tried flashing the "PC36IMG.zip" through the choose zip option it says aborted and it is in the main directory of my sd card.
Any help would be appreciated.
R.Soul
Click to expand...
Click to collapse
If your flashing a PC36IMG.zip file you have to flash it through.the bootloader not via recovery
Sent from my PC36100 using XDA App

Download the newest 4.54 pc36img. Boot into bootloader and apply.
Support TrevE !!

I havent done much flashing of roms for about 7 months since I found Synergy and loved it. So I need a little refreshing on what you mean by using the bootloader.
____________
The way Im trying to do this is by:
--> Volume Down + Power
--> Recovery
Loads ClockworkMod Recovery v3.0.0.5
--> Instal zip from sdcard
--> Choose zip from sdcard
I then select
--> PC36IMG.zip
--> YES
It then reads:
-- Installing: /sdcard/PC36IMG.zip
Finding update package...
Opening update package...
Installing update...
Installation Aborted.
____________
I tried also doing this:
--> Volume Down + Power
--> Fastboot
--> Bootloader
Nothing, I also tried
--> Volume Down + Power
--> Fastboot
--> Reboot Bootloader
As you can tell Ive been out of the loop for a bit.
If you can post up a link or youtube video to get me back uptodate with the bootloader that be nice.
@{ParanoiA} do you have a link to that rom/backup?
Thank You again fellas

Rename to PC36IMG.zip power button+ volume down make sure the PC36IMG.zip is not in any folders it will scan for it accept. Also you flash RUUs through the bootloader also
Sent from my PC36100 using XDA App

First of all, if you're s-on then you can only flash official PC36IMG files, no recoveries or anything.
Here are the steps that should get you to where you need to be in order to take it into Sprint.
1) Download this file. Do not rename it, just put it on the root of your SD card.
2) Hold volume down and power simultaneously. This will take you to the bootloader (hboot). Hboot will scan for the file, find it, and ask you to update.
3) Accept the update by following the on-screen instructions. Let it flash, don't pull the battery or anything. When it finishes you can accept the prompt to reboot, if you decline it will take you back to the bootloader.
4) You can check to see if you have the stock recovery by selecting recovery from the hboot menu. If you have the stock recovery, you'll see a red triangle with an exclamation point. This means that you're fully unrooted, s-on, stock.
Notes: If you have ClockworkMod, you may want to make a nandroid backup first. Though you shouldn't restore backups across phones, Titanium Backup Pro can restore apps from backups made with CWM or TWRP. If you decide to go that route, don't restore system apps.
You will possibly get a device other than the Evo, like the 3D. If so, be careful restoring apps across different phones.
If the file is not detected by the bootloader, then there's probably a problem with your SD card. You can double check the file name as well, but don't add a zip extension if you don't see one. If you continue to have problems flashing the RUU, you can download one as exe and run it from a PC.
Good luck!
Supersonic Evo 4G | MIUI | Tapatalk

plainjane said:
First of all, if you're s-on then you can only flash official PC36IMG files, no recoveries or anything.
Here are the steps that should get you to where you need to be in order to take it into Sprint.
1) Download Do not rename it, just put it on the root of your SD card.
2) Hold volume down and power simultaneously. This will take you to the bootloader (hboot). Hboot will scan for the file, find it, and ask you to update.
3) Accept the update by following the on-screen instructions. Let it flash, don't pull the battery or anything. When it finishes you can accept the prompt to reboot, if you decline it will take you back to the bootloader.
4) You can check to see if you have the stock recovery by selecting recovery from the hboot menu. If you have the stock recovery, you'll see a red triangle with an exclamation point. This means that you're fully unrooted, s-on, stock.
Notes: If you have ClockworkMod, you may want to make a nandroid backup first. Though you shouldn't restore backups across phones, Titanium Backup Pro can restore apps from backups made with CWM or TWRP. If you decide to go that route, don't restore system apps.
You will possibly get a device other than the Evo, like the 3D. If so, be careful restoring apps across different phones.
If the file is not detected by the bootloader, then there's probably a problem with your SD card. You can double check the file name as well, but don't add a zip extension if you don't see one. If you continue to have problems flashing the RUU, you can download one as exe and run it from a PC.
Good luck!
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
Perfect! Thank You PlainJane that got it fixed.
My phone has finally turned on completely and working only issue is parts of the touchscreen is non responsive so I'm planning on calling sprint get an eticket created and stop by a local store and have it either repaired or replaced.
If they say they are out of stock what replacement phone would you recommend?
Weird this is my original Evo I got on launch day (1 year and 6 months) and its been through so much, Dropped it so many times highest was around 5 feet. Its gotten soaked with water and screen is scratched, but still worked
The most heavy duty phone I have ever had.
Just to think a small drop from those movie theater cup holders would mess up my phone. Crazy!
Again thank you all for the help!

Can get to HBOOT, but dead end from there...

Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!

BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.

cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?

BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.

cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?

BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?

BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...

BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.

cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )

Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!

So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app

nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?

BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.

cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )

There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off

eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...

I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app

eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.

BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243

eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!

Bootloop After Trying to Unroot

Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.

That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.

Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!

So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?

double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...

I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?

double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.

Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.

double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe

Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.