[Q] Stuck in bootloop, unable to restore PG32IMG - Verizon Droid Incredible 2

Let me preface this by saying I am not super familiar with this system, I rooted this for my sister.
I am stuck in a bootloop, I am S-Off
I have tried to restore to stock. I placed the stock image on my SD card and it was recognized and it attempted to update. The file is good and the MD5 checked out.
The results are below, and I have also included 2 screen shots.
[1] TP -OK
[2] Recovery - OK
[3] Bootloader - Bypassed
[4] Splash1 - OK
[5] Boot - OK
[6] Userdata - OK
[7] TP - Bypassed
[8] System - OK
[9] Radio - OK
It said during the update that it could not roll back hboot version.
I'm assuming this is related to being S-Off
What is my next move to fix this?

I haven't looked too much into this, but does this guide help? http://forum.xda-developers.com/showthread.php?t=1466295
Sent from my ViperDinc

I am hesitant to follow that because the first step is exactly what I have been doing except with a different RUU file... would the fact that this is froyo change that the bootloader is being bypassed?

For anyone with a similar issue, i fixed this by downloading and installing the android developers kit
http://developer.android.com/sdk/index.html
you have to make sure you install java within the correct folder. ( I believe it is the eclipse folder but the program will tell you when you try to run it the first time)
I then installed htc drivers again just to make sure they were good.
then i downloaded this file
http://www.filefactory.com/file/ccf....01.0622_NV_VZW1.92_release_199487_signed.exe
ran the program from my computer and followed the instructions. I had to run it twice since it froze halfway through the first time and i needed to do a battery pull.
After this i was still in boot loops, but i booted into the recovery and did a factory reset after which point the phone was working...

Related

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..

[Q] HTC EVO Not functioning

I have messed up my phone, and not sure exactly how.
When I first got my evo in august, it came with Froyo. I tried to root it using the procedures for 2.1, not knowing that it was for 2.2. My mistake. I went through the procedures, and it never worked. Then when the rooting for 2.2 came out, i tried to do that, but it didn't work. I followed the instructions from here and followed allong with the video on youtube. When I was pushing those files using the command prompts, they all worked, but that biggest file never came through.
On Tuesday, i was able to use unrevoked 3.2 to root my evo. I know it was successful because unrevoked said done when i finished. I was able to do the wifi tether on it, plus the screen shots, and superuser was asking for permisions, so I know it was fully rooted.
Today I tried to do a rom, and I was unsuccessful from the start. The phone wont start the recovery mode.
This is what it says:
SD Checking....
Loading... [PC36DIAG.zip]
No image!
Loading... [PC36DIAG.nbh]
No image or wrong image!
Loading... [PC36IMG.zip]
And then it will go to the next screen, which says:
Parsing...[SD ZIP]
[1] BOOT
[2] BOOTLOADER
[3] MICROP
[4]RADIO_VZ
[5] RECOVERY
[6] SPLASH1
[7] SYSTEM
[8] TP
[9] TP
[10] USERDATA
[11] WIMAX
Do you want to start update?
So I've pressed yes once before. However, my phone will not move past these screens. I can select all the options, like clear storage, power down, etc. I can't go into recovery. When I do, it shows a black screen with a phone and a red triangle with an exclamation point.
I won't say that it is bricked, but I know something isn't right. Have I messed up my phone beyond repair? And if this is in the wrong place, I am starting a thread in the Q and A general forum with the exact same message.
You trying to flash a rom from the bootloader? Try doing it from recovery...
You probably never deleted/renamed the PC36IMG.zip after rooting.
Also, delete the PC36IMG.zip from your sd card. You dont need it anymore. Just download Quickboot from the market and you can boot directly into recovery instead of selecting it from the bootloader.
Looks like you forgot to delete that pc36img zip from the root of your sd card and you're just updating that same image every time. Try deleting that first or select no for the update next time you boot into recovery.
Sent from my PC36100 using Tapatalk
m4rk0358 said:
You probably never deleted/renamed the PC36IMG.zip after rooting.
Click to expand...
Click to collapse
+1
Also sounds like you may not have flashed a custom recovery yet.
Sent from my PC36100 using XDA App
No, I have not deleted the pc36img.zip file. i can't get it to cut on so i can connect it to the computer to use as a (usb) disk drive to delete it.
When I select no, i don't want to update it, it takes me back to that screen that says hboot at the top.
I also haven't flashed a custom recovery because it gets stuff on that black screen when I select recovery.
I can't use quickboot because I can't get to the phone and apps part of the phone.
If you moved past the bootloader screen and into the black screen with that cool wittle triangle then you may be able to ABD into recovery. Wipe and then flash from there. You can also remove your micro sd card and put into a sd card reader on your pc. Find and delete that pc 32 zip!
Sent from my PC36100 using XDA App
This has happened to me a couple of times, just run the PC36IMG again, let it update again, then reboot. This worked everytime
Sent from my PC36100 using XDA App

[Q] Boot Partition Failure for Sprint Lovers ROM

I am sure this has come up before, but I cant seem to find any thing that matches my description. I am new to these forums and it seems like everyone is incredibly helpful. I rooted my Evo using the method described here
hxxp://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/54844-guide-rooting-3-7-hboot2-02-w-screen-shots-1-27-2011-a.html
Everything went smoothly until I tried installing the rom. I am trying to install Sprint Lover 2.2 and every thing installs correctly until the boot partition. My screen looks like this:
[1] RADIO_V2 - OK
[2] RADIO_CUST - OK
[3] SYSTEM - OK
[4] USERDATA - OK
[5] WIMAX - OK
[6] BOOT - Fail-PU
Partition update fail!
Update Fail
My phone works when i reboot it, but I just want to make sure that I didn't do anything incorrectly. Is there anything I can do to fix this? I might just being anal, this is my first time rooting.
Thanks in advance for your help!

"error [152]: Image update error

Hi,
could any one help me please,
since I bought my phone I can not flash any rom other than CM7.
the problem, I thought the best solution is to go back to stock>
thats why I tried to flash the following rom and I forgot that my hone is still s-off:
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed
and I ended up by the following issue:
"ERROR [152]: IMAGE UPDATE ERROR
When I unplug the usb cable from my phone this is what my phone reads
RUU
Parsing...[downloaded ZIP]
[1] BOOT - Fail-PU
[2] RECOVERY - OK
[3] SYSTEM - OK
[4] USERDATA - OK
[5] SPLASH1 - OK
[6] WIMAX -OK
Partition update fail!
Update Fail!"
After I pull the battery and turn my phone back on it just has a black screen. Says HTC in the middle and there are four Exclamation Points in triangles in each corner.
Can someone please help meby solving this issue? I dont mind to reinstall CM7 but how??? I cant open the recovery or the bootloader????

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.

Categories

Resources