Related
Hi,
I have become really stuck with this issue
ROM - 2.29.405.2
I origonally had a rooted phone with clockworkmod installed. I subsequently wanted to put it back to stock. Which i ran the latest RUU with the goldcard. I now am getting a continuous white HTC screen then vibrates and keeps doing this. No matter what i do i cannot get the phone into the recovery menu it just starts the reboot loop again.
I can get on fastboot and resend the same RUU to the phone. This installs without any issue and says that it is going to reboot the phone and going straight back to the rebooting loop.
I somehow need to get clockworkmod reinstalled so i can resolve this problem as it seems that the recovery partition is damaged somehow. I have s=on so i cannot force the restore of the recovery console with the colckworkmod as i get signature failure.
Is there an origional HTC recovery file i can use which gets past the signature failure??
"Clear storage" from HBOOT.
And give a try to the other way - download this zip , rename it "PB99IMG.zip" put it in the root of your SD card (not in a folder) , pull battery , plug it back , enter HBOOT (power+volume down) and apply it.
Edit: use goldcard if you are branded. If I understand you correctly, you say this "I subsequently wanted to put it back to stock. Which i ran the latest RUU with the goldcard" - if you flashed your original stock ROM, then you didn't need a gold card.
Branded
Yes i am branded.
Sure i tried this last time where it showed a blue meter on the right hand side. Went all the way and rebooted to the same if i rememeber.
But i will give it another go see if it works. Cheers.
I managed to get it to run the PB99IMG in the end which updated all parts without an issue. On rebooting of the phone it still does it boot loop.
I really done know what is causing this.
It all goes like this - I wanted to root my WPS to solve space problem, although, there was a solution for it without rooting, I figured I will be wanting to use some apps that need root access and some roms sooner or later.
So I did a search and found few ways to root my phone. Being a lazy ass I decided to use "the simple" one click solutions - gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) or Root Unlocker (http://www.unlockroot.com/) This was no success. Gingerbreak kept rooting when I launched the app, but Root Unlocker displayed " FAIL TO GET SHELL ROOT". I figured that problem with Gingerbeak might be that I updated the software to the latest version -
Then I went on and tried another tutorial(http://forum.xda-developers.com/showthread.php?t=1195275). Everything was fine till I selected Recovery from bootloader. It got stuck with white HTC logo. Took out the battery tried to use newer version of ClockworkMod Recovery, but still was a no-go. I also can't do a factory restart. I can't do it from bootloader or settings > SD & phone storage > Factory data reset. (But could do it at first. Before trying to root my device I did a factory reset once.)
Is there a way to use another Recovery (not CMR) or force Recovery from fastboot? As I found there are some other people that got stuck with similar problem.
Other problems:
My phone doesn't show up in HTC Sync. Althought, when I tipe adb devices in cmd, it shows up. I did turn my AntiVirus off when I installed HTC Sync, but it still didn't display my phone.
I also found that I can't boot when I connect powered off phone to my pc. I have to take off my batery.
Here are my specs:
Model HTC Wildfire S A510e
It shows Marvel in bootloader.
Phone was S-OFF when I bought it.
Android 2.3.5
HTC Sence 2.1
Software number 2.26.401.3
I bought my phone without a contract from a local internet shop. I am from Baltics.
The phone might be somewhere from Europe.
My bet would be Poland. (guessing that manual language is Polish, but I might be wrong)
Thanks in advance.
UPDATE!
I took the original recovery img from http://forum.xda-developers.com/showthread.php?t=1426611 and flashed it. All went well. I did a restart (after doing this I was able to boot power my device while connected to pc) and had another try with CMR recovery, but it didn't work. I also I tried http://forum.xda-developers.com/showthread.php?t=1406321 recovery img, but it didn't help, I still can't get into.
How to root Wildfire S S-OFF the easy way
First download this
Put it in your memory card
then press and hold voldown+Power
It will load the bootloader follow the instructions on the screen and update accordingly
Then Turn off
Remove that PG76IMG from sdcard
After that download this and put in your memorycard and update same way, it will flash the CMR5.0.2.8 (after flashing dont forget to remove this PG76IMG from sdcard as well).
Now download this put it in your mmc and flash this from recovery.
Done.. U have successfully rooted Ur S-OFF device Now In CWM do factory reset install new custom rom according to the way devs say. I can assure U that this process will even remove Ur white screen
im stuck too on the recovery s-on btw and bootloader unlocked
ME TOO
but i m s-on
Same problem here, unlock by htc-dev worked. Recovery flashed but device stays stuck on the HTC logo. So my daughter's phone is unlocked but that's it.
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Let me know
7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
I dont understand. If ur splash screen changed means u have installed cwm. Just select recovery and install a rom. Like this one
Download the rom. Put in ur sdcard.
remove battery
press vol down+power
press vol down
press power to select recovery
In recovery to move press vol up/down, to select press power
Wipe data/factory reset
Wipe cache partition
Advanced>> Wipe Dalvik cache then also wipe battery stats
Go back
Install zip from sdcard
Select the romname.zip put in sdcard
that should be it instructions are also found in that rom. thread so simple!!
7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
Here is a flash file you can try since you are S-Off. It should flash the default splash image, CWM 5.0.2.8, hboot 1.03 and re-calibrate the touch panel.
Hope it works for you.
Deleted
Problems persist
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?
Return back to Normal after BOOT-LOOP !
muckz said:
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?
Click to expand...
Click to collapse
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......
Senthamil said:
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......
Click to expand...
Click to collapse
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html
For those who want more info, here's another thread:
http://forum.xda-developers.com/showthread.php?t=1725398
It appears that the latest Wildfire S has a slightly different firmware, possibly for the video chip, which causes the CWM Recovery not to work. Perhaps there'll be a fix released eventually, but for now you can follow the thread above for some possible workarounds and more info.
Try mg all in one tool. Here: http://forum.xda-developers.com/showthread.php?t=1697985
It should sort out you guys problems.
muckz said:
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html
Click to expand...
Click to collapse
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:
7axew3ku said:
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:
Click to expand...
Click to collapse
It appears that CWM 5.0.2.8 actually works, but it doesn't provide any output to the screen. With ROM Manager, you can automate starting into CWM Recovery and installing a custom ROM, so it doesn't matter if the screen is blank.
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.
Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.
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.
I really hope someone can help me.
I tried to root my HTC One X a few days ago but it failed (don't know why) halfway through. It now continually reboots. I've gone into recovery and hit restore, wiped caches and factory reset but it's still doing it. I only have Jelly Bean on my OS card because I was trying to install that too. That just sits on the boot screen though. I even tried opening the phone to manually put the SD card in my computer to put a different update on it but there didn't seem to be an obvious SD card. It's a brick at the moment, can anyone help, please?
Hold the power button and the volume - button together as long as it takes to get into the bootloader. Once there you flash the boot.img from the new rom with fastboot commands
After that you enter the recovery and make a FULL wipe and install the rom
Ow and you can mount the sdcard as an usb diskdrive inside the recovery !