Develop Bugs

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

[Q] another bricked phone thread; help needed

I've looked around for solutions as much as I could before posting
I've outlined everything I've done so far, not sure how much is relevant
Was running LeeDrOiD HD V3.3.1 before the phone became bricked
I rebooted the phone at one point, and the battery fell out during a reboot
Next time I rebooted it got to the ascii art android logo, onto a part with text on, and got stuck in a boot loop, the text had a progress part "so&so out of 2703kb" or something to that effect
(can't remember the text exactly)
After a few tries at rebooting it went to the home screen, however nothing loaded onto the home screen for 20 minutes, and the only function that worked was locking the screen, I couldn't turn it off or anything.
After this, everytime I booted it got stuck in a boot-loop on a splash screen of
"ANDROID" in silver writing
This is what I currently get when I boot my phone
When booted into recovery mode (hboot) I first get the message;
SD Checking...
Loading...[PC36DIAG.zip]
No image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36.IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
After I get this message I am free to go into fastboot and recovery menu
The PC recognises the phone in fastboot (I'm running windows 7)
I tried reflashing the leedroid rom straight from the recovery menu, didn't affect anything at all.
Went on to reformat sd card entirely.
Tried updating to the latest ruu, as there was no ruu that was exactly the same as mine, my phone was originally on virgin mobile and there were no ruu's with the same baseband
RUU used; RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
But the update fails part way through (after it reboots the phone) and gives
ERROR 131: CID ERROR
Rom update utility cannot update your phone at this time
Please get the correct rom update utility and try again
Click to expand...
Click to collapse
Current information that hboot gives me;
Bravo PVT1 SHIP S-ON
HBOOT-0.80.0000
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Click to expand...
Click to collapse
Can anyone help?

if you can go into recovery, try reflash the zip file again and let it do its job. your hboot is not screwed so it shall restart with a new flash. recommending you download oxygen and save it on your sdcard. due to its fastest to load and most stable.

Just FYI: bootloop is not any kind of brick, and you're not bricked either.
Just do full wipe and reflash the ROM.
If you want to go back stock, you will need goldcard when running RUU.
SD Checking...
Loading...[PC36DIAG.zip]
No image!
Loading...[PC36DIAG.nbh]
No image or wrong image!
Loading...[PC36IMG.zip]
No image!
Loading...[PC36.IMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
Everyone is getting this upon entering bootloader...

Flashed oxygen, rebooted, left for 5 minutes
I'm still stuck in a boot loop, however the 'ANDROID' text splashscreen is now the 'OXYGEN' splashscreen

Did you do Full Wipe/Factory reset & dalvik cache wipe before flashing new ROM?
Do you have any partitions on SD card?

k3lcior said:
Did you do Full Wipe/Factory reset & dalvik cache wipe before flashing new ROM?
Do you have any partitions on SD card?
Click to expand...
Click to collapse
I wiped both
Yes, I partitioned it as instructed in the stickied noob guide
4GB partioned to 1GB of Ext3, the rest is FAT32. The partition is still there.

Probably something went wrong when you was creating ext partition, what i suggest is downloading this recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519 (md5sum zip: 170785457774834c7ae58e331d6f4ab4)
Put it onto your sdcard (root of SD, not in any folders), rename it to "PB99IMG.zip" and boot into bootloader.
It should ask if you want to update, choose yes.
Partition your SD in new recovery, it will also perfectly align it, try to flash with this should be good.

k3lcior said:
Probably something went wrong when you was creating ext partition, what i suggest is downloading this recovery:
http://forum.xda-developers.com/attachment.php?attachmentid=661317&stc=1&d=1311251519 (md5sum zip: 170785457774834c7ae58e331d6f4ab4)
Put it onto your sdcard (root of SD, not in any folders), rename it to "PB99IMG.zip" and boot into bootloader.
It should ask if you want to update, choose yes.
Partition your SD in new recovery, it will also perfectly align it, try to flash with this should be good.
Click to expand...
Click to collapse
Didn't ask if it wanted to update
Text said loading image, A progress bar automatically appeared on the right, after it was done loading, it said 'checking image' then just went straight back into the bootloader

Are you sure you renamed file to PB99IMG.zip ? You can also try to rename it to PB99IMG (without extension)

k3lcior said:
Are you sure you renamed file to PB99IMG.zip ? You can also try to rename it to PB99IMG (without extension)
Click to expand...
Click to collapse
Yep, just double checked and tried a few more times, redownloaded and tried again just to be sure.
When renamed without extension the phone didn't find it, renamed with .zip extension the phone seemed to recognise it, but stopped after saying "checking image"

If you are branded try to put in you gold card and then try...
btw.
What did you used to partition your SD card?

k3lcior said:
If you are branded try to put in you gold card and then try...
btw.
What did you used to partition your SD card?
Click to expand...
Click to collapse
I'm just trying to create a gold card now (didn't know about them until after I flashed)
I used Gparted

You can also try to repartition in the recovery you have right now, might help who knows.

I'm crossing my fingers for the repartitioning from current recovery mode to work
because I'm not entirely sure on how to create a goldcard without being able to boot my phone normally
*edit*
Yes, that did indeed work
seems the file structure got fudged up when the battery fell out for a reboot
such a simple solution that I overlooked at the beginning sorry
Thanks for all your help

Create goldcard and bring your phone back to stock with the ruu you already wanted to use. With three goldcard you won't get the cid error.
Run unrevoked again, but this time you use a custom recovery:
http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
I can highly recommend rmd recovery:
http://forum.xda-developers.com/showthread.php?t=1137763
Download the zip, extract it and check the md5 of the image.
Standard amonra recovery:
www.android-hilfe.de/attachments/ro...-0-0-14-11-2010-recovery-ra-desire-v2.0.1.zip
Configure your phone correctly for using unrevoked.
Start unrevoked>file>custom recovery>choose the downloaded recovery image.
Run unrevoked.
If successfully done, go into recovery and flash custom rom.
The one k3lcior provided cannot be used as long as one is not s-on. So you cannot use it.
@k3lcior: Take care of this when you tell people to flash this recovery.
Swyped from Oxygen with Transparent XDA App

[Q] HBOOT Image and Update Script Errors

What I did:
Rooted Evo 4G Gingerbread using Revolutionary
Flahsed su-2.3.6.3-efgh-signed.exe and PC36IMG.EXE
Worked great, got excited flashed:
SOS_v1.9.0.2-swag.exe, navbar_rednblack.exe, remap_camera.exe, and ChopSuey-v.9.2.6-UNIVERSAL-signed.exe
Whats going on:
SOS, navbar, and remap flash fine; all other flash attempts give the error, E: Can’t Find Update Script
At HBoot
SD Checking
Loading (PC36IMG.img)
No Image
Loading (PC36IMG.img)
No Image or Wrong Image
Loading (PC36IMG.img)
No Image
Loading (PC36IMG.img)
No Image or Wrong Image
(With PC36IMG.EXE on the SD root) Also
Parsing (SD ZIP)
(1) Recovery
So how do I get rid of the errors so I can flash another ROM or whatever? Thanks for helping a noob

If you're already rooted, you need to boot into recovery. Then navigate to where the .zip (ROM) is located. The instructions to flash should be provided on the first page of the dev's post.

Thank you but, I don't undeerstand. I can find the zip files that I put on the SD card, and go into the recovery screen but when I try and flash any ROM/add on/bootanimation/ I get the eror, E: Can’t Find Update Script" so where is the script? Also, any ieas on the no/wrong image issue?

What recovery r u using? R u flashing chopsuey thru hboot or recovery?
Sent From My Pocket

I flashed the Kernal throu recovery.

HBoot> scroll to Recovery>hit power key> Brings up android systems recovery screen> scroll to "Flash sip from SDcard> Select the zip file. That is when I get the E: Can not find update script error.
I am not running the PC36IMG ROM, I am running the SOS_v1.9.0.2-swag but in HBOOT, its looking for the PC36IMG image, are't these issues related?

Google "evo amon-ra xda forums".
Download the PC36IMG.zip.
Copy and paste it in the root of your SD card.
Press volume up to install in hboot.
Once complete, boot into recovery and try to flash the ROM zip file.
Be sure to delete the amon-ra zip file or else it'll just ask if you want to flash when hboot loads.
Sent from my PC36100

Thanks, trie your suggestion but the file still aborted with the can find update script error.

Sounds like you got a bad zip file
Sent From My Pocket

i also have this problem now (different phone tho). but now it keeps telling me "No image!" "loading....[pj75diag.zip] No image!"

alltoEZ said:
i also have this problem now (different phone tho). but now it keeps telling me "No image!" "loading....[pj75diag.zip] No image!"
Click to expand...
Click to collapse
Go to the correct forum for your device. I'm sure someone over there will be able to help you do whatever it is you're trying to do.
If you're looking for a bootloader-flashable recovery file, I posted one in the TWRP thread for the LTE.

[Q] Help - stuck at HBOOT/Recovery and can't run RUU on HTC Desire

Hi guys, wonder if you can help me. I have a HTC Desire (GSM) and rooted it, removed UK O2 branding and putting Froyo (2.2) on it and a new radio and Clockwork Mod Recovery. I messed around - thought I’d bricked it following a dodgy flash, as couldn't boot, get into recovery or anything, with the phone looping at the HTC logo and powering on until I took the battery out.
Thought I’d look at it today and made progress, but still can’t get a RUU to install on it. I can get into Recovery menu via bootloader and I think the SDcard is a goldcard. Issues I have are:
• I can’t flash a RUU onto the phone from running the file through Windows, as I constantly get an Error 170 USB Connection error. I’ve tried reinstalling HTC Sync, trying different versions, tried a different USB cable and port. I’ve tried running HTC Sync as Admin, and in compatibility mode under XP SP 2 and updated the driver in Control Panel and it displays as “My HTC”, nothing works. I am running Windows 7 64 Bit.
• I tried putting the RUU onto the phone as a PB99IMG.zip file and running it through Recovery, but I get a message saying “bad file”
• As soon as I put a file onto the SD card, Ext3 then won’t mount with an error message and I have to repartition the SD card in Windows (Using Mini-tool Partition Wizard). The error I get is "can't mount /dev/block/mmcblk0p2 (File exists) error mounting /sd-ext/!” I can fix it, but soon after it is fixed it reverts back to error it I add any files to root of the SD card to run through Recovery.
I just want to get the phone back working, whether it is branded or unbranded, and whatever RUU I can get working on it. Can anyone advise the steps I can take from here please?
My stats/versions are:
HBoot 0.93.0001
Radio 5.09.00.08
ClockworkMod Recovery v2.5.0.7
S=On
Thanks,
Stewart

Tried downloading the RUU again? I recommend to check md5sum afterwards.
Sent from Sandvold's ICS using Transparent XDA App

Thanks MatDroid, I've managed to get past the 171 error and now getting a 131 error, saying it is the incorrect ROM. Is there somewhere I can get confirmation of the correct ROM for my device and check MD5sum before loading?

I would look at putting on another recovery, something like 4ext touch. Google it, your current clockwork recovery is pretty dated. Look at a program called android flasher, and you will be able to flash a new recovery through that.
Once you get the new recovery working, there is an option to toggle USB storage in which you can put your custom from on the SD card. Once the custom from is on your SD card, flash it through recovery. Hopefully it should work
Sent from my HTC Desire using XDA App

you should really look at my guide, you don't flash RUU zip files through recovery.

just realised you are s- on so android flasher won't work. Therefore until you s-off your phone, as mattdroid said you may have a bad download for the ruu. Try downloading ruu again nd running the exe file
Sent from my HTC Desire using XDA App

bortak said:
you should really look at my guide, you don't flash RUU zip files through recovery.[/QUOTE
Yeah just realised that too sorry for the wrong information. he is only wanting a ruu which of course is not done through recovery with the exe file. Custom rom is a different story.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse

Thanks guys I've figured it out and have now succesfully got the phone working.
Issues were:
I was trying to flash the wrong RUU (a 2.09 instead of 2.10) so when flashing it was rejecting as a lower version. Using the right RUU worked
My SDcard wasn't a goldcard - I thought it was but apparently not. I re-created the goldcard and it worked
I was trying to flash from the wrong place - instead of through FastBoot USB I was going into Clockwork Mod and loading files, mucking around with the mountings and things like that
All great now, so thanks again.
Stewart

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.