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.
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.
(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
WutUpCuuuz said:
(My Download Mode screen while stuck in boot-loop)
*** UNLOCKED ***
htc_pmewh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.42.651.6
Jan 18 2017, 11:10:08(857212)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security checking failed GT_CONNECT_FAIL
Security Warning
Bla bla bla
SD MOUNTED
OTG NOT MOUNTED
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
FILE /mnt/media_rw/ext-sd/2PS6IMG.zip
So, I had Viper10 5.9 with TWRP, Magisk, and SuperSu but somehow messed with one of my color settings and just couldn't figure out how to fix it, this went on for weeks... so I decided to restore it and reflash the ROM. Somewhere in that process S-OFF went to S-ON, I believe, not sure if it makes a difference but from all the searching I've done trying to figure this out it seems like a big deal. Anyway, I can tell you this...
1) When I tried to format data through TWRP before it said something like "failed to mount bla bla bla device is busy or in use" (maybe something to do with encryption? or root? maybe not having root anymore since I had uninstalled SuperSu?
2) Now when I try to format data through TWRP it acts as if everything is fine and then I reboot and I'm stuck in a never-ending boot loop again
3) When I try to flash my firmware zip (which I got from here) in Download Mode I get
"22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
4) When I try to ADB sideload through TWRP it says the zip file is corrupt
5) When I try the HTC RUU (while in Download Mode) it never gets past the first screen where InstallShield or whatever is setting up
6) I just flashed Viper10 5.9 through TWRP and it worked all of a sudden (wasn't working before, while stuck in the loop)... I went with Magisk and MagiskSu this time to avoid a future conflict (not that I now what I'm doing or anything)
So I'm wondering if I'm okay... I'm still S-ON (I thought it went S-OFF when rooted?) and everything seems to be working fine... My Download Mode screen is exactly the same, including the "Security checking failed GT_CONNECT_FAIL"
Although I have this tiny itch to format my data through TWRP at some point and do a "fresh" install/ROM flash to be sure there isn't a hidden issue. Am I good? Seems like it's not quite perfect yet.
Thanks for your help.
Click to expand...
Click to collapse
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Sent from my 2PS64 using Tapatalk
WutUpCuuuz said:
Update: Since re-flashing Viper I haven't had any issues, although I haven't tried anything in depth. I still wonder about it not wanting to format data in TWRP before (remembering that it said it couldn't do something with /data).
Is there a way I can still format my device and get it back to stock, S-OFF and locked so I can start from scratch? The /data thing and the GT_CONNECT_FAIL are bothering me. Or, if there's a better route I should go I'm definitely open to suggestions.
Click to expand...
Click to collapse
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Tarima said:
Put an ruu on an SD card and run that. Will take you back to complete stock and remove everything from the phone.
Also, regarding s-off, it's not clear if you ever had s-off to begin with. You had previously paid for it via sunshine??
Click to expand...
Click to collapse
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Sent from my 2PS64 using Tapatalk
WutUpCuuuz said:
I'm not exactly sure either... maybe I'm just imagining it. Looked into Sunshine but have yet to pump the trigger on it.
At one point I had found an RUU zip, put it on the SD, and renamed it to 2PS6IMG.zip, but it wouldn't run. I'll try again. Think I could use one of HTC's RUU executables? (that might be a dumb question [emoji6])
Thanks for your help
Click to expand...
Click to collapse
If you're not sure you ever had s-off, then you didn't have it. S-off is a separate procedure, not be confused with bootloader unlocking or rooting.
If the ruu didn't run, most likely you tried one made for another mid/cid, or the software version was older than what you had already on your phone. Make sure both of these are corrected and report back if it works. And yes the ruu.exe would work, but the two points I just mentioned need to be taken into account.
Double checked that it was the correct RUU... still correct as far as I can tell. Rebooted to download mode, didn't see it on the SD. Renamed the RUU to 2PS6IMG.exe, still didn't see it. ??? I'm stuck, my PC isn't here with me so I can't try it that way.
Greetings.
I had issues updating my Honor. Every time I would try the update, after downloading it, it would boot into TWRP with the message failed to unmount /system: device or resource busy.. Then, if I rebooted, the update simply didn't work (I was stuck in an older version of EMUI 8.0, I don't quite recall the precise number). Actually, the same error message would come every time I simply booted into TWRP.
At this point, after a backup, I thought I could just wipe the /system partition and then flash a zip, containing a new ROM, from the TWRP; I wiped the partition and rebooted, and of course the phone started into TWRP, because there wasn't a system anymore. The problem is: TWRP is stuck at splashscreen, and I can't access it anymore.
I tried going into fastboot, but only to find myself with the message Phone Unlocked, FRP Locked, and I was unable to boot another version of the TWRP.
Another thing I did was to boot into the e-Recovery, and from there if I tried restore to factory settings, it would boot again into the stuck TWRP; and if I tried to download latest version and restore, the download would fail because I couldn't retrieve package info.
I then tried a solution I've seen in this forum, namely , with a Windows 10 machine that I used as an hotspot (actually I wasn't able to use the same IP from primary and secondary DNS, only for primary).
I understand that the only thing left to do is to pay some amount of money to some company that would give me the FRP unlock key based on my IMEI, and I actually tried that, with HCU-Client, but after buying 12 credits, they reimbursed them for no appareantly no reasons. Did somebody use this method, perhaps with another company? And did it work?
tl; dr: honor 7x bricked: stuck into fastboot with FRP lock, can't open twrp, don't have system, need help to know if I can actually pay a company to give me the key for the FRP unlock.