Tried a new ROM but it froze on me. Then tried my back up and it would reboot after like a minute. So decided to do a full wipe but it deleted everything. I can get into the bootloader screen and TWRP but Windows can't read the phone and when it tries to install the drivers some of them fail. I have a copy of my recovery but need to know how to push it back to my phone and get the drivers installed right so that my PC can read my phone. Help.
TWRP seems to now act funny too where it'll like go to sleep and I have to press the home button or power button for a while before it turns the screen back on. Sometimes though I have to do the button combo to get back into recovery.
RUU
So I RUU'd the phone and it's working now, thanks. But it still shows unlocked and with S-OFF. So at this point can I just proceed with rooting it or do I have to lock it and put it back to S-ON before trying to re-root it? Or can I just try rooting it and putting a recovery image on it? It's been a while since I rooted it and obviously there was no 4.3 out at that time.
No need to re-lock or s-on just flash recovery and flash a rooted rom
bigdaddy619 said:
No need to re-lock or s-on just flash recovery and flash a rooted rom
Click to expand...
Click to collapse
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
QuiQNeZZ said:
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
Click to expand...
Click to collapse
You should be able to flash right over the older version make sure you download a fresh version of 2.6.3.0 from here http://techerrata.com/browse/twrp2/m7wls
Also remember after flashing the recovery.img type fastboot erase cache
The other thing is go into settings/screen and disable screen timeout that should take care of the "freezing" problem
RESOLVED: So of course, taking 10+ minutes to type this out magically fixed the issue, huh? :silly:
What I did was I restored my backup, installed TWRP 2.7.0.1 from a download on this forum, and tried it again. Made sure to factory reset both times, etc.
I'm booted into ViperOne 5.8.0 now! Sorry for wasting anybody's time...
So, I've searched around the forums, and I haven't found anything that quite sounds like what's going on with my phone. My issue is that I get put in a boot loop after flashing ViperOne 5.8.0.
First, some info about my phone:
Unlocked (S-OFF)
CID: VZW__001
HBOOT: 1.56.0000
OS: 3.11.605.1
Steps leading to the issue:
Used rumrunner to s-off and root phone back when it came out for VZW in August.
Had CWM recovery for the longest time. Didn't update the phone since then.
The other day, I backed up my phone with CWM and then later decided to switch to TWRP (got the newest version I could find - 2.7.0.0).
I put TWRP on my phone and then tried flashing ViperOne 5.8.0 from it.
It seemed to have put me in a bootloop, so I tried a few factory resets and cache clearing, etc.
Then, I went into ViperOne's installer and installed the older version of TWRP.
At that point, I couldn't even get back into recovery, so I used fastboot to put the latest TWRP back on.
I threw out my old backup and used a RUU to get back to stock 1.10.605.1 (RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted) from here.
At this point, my phone was working again. I installed all of the updates through the phone to get to KitKat 4.4.2.
From here, I installed a bunch of apps I used, reacquired root (my phone still said S-OFF/Unlocked from the first ever time I did it) and performed a TWRP backup.
I decided to give ViperOne a shot again since my phone had been updated and I wasn't sure if the newer hboot or stuff like that would help.
I followed the instructions on some site that said to fastboot flash the boot.img in the zip first and then flash the zip from TWRP.
Everything seemed fine again. I factory reset BEFORE and AFTER flashing ViperOne. However, it's giving me the same issues; I'm stuck in a boot loop.
I got ViperOne from here. The ViperOne Verizon page seemed to just link there (I couldn't find a download specific to Verizon) so I'm assuming that's the right one.
If anyone could offer any suggestions on what to do? The next think I'll try is downgrading my version of TWRP I guess?
If more details are needed, please let me know. Also, sorry if this is in the wrong section?
I believe the root problem of this may be using TWRP manager to update recovery, because it happens after I attempt to do that. It asks if /dev/block/mmcblk0p43 is the correct partition, which i believe it is, and attempts to flash it. Once it attempts, it says it is failed, but when I reboot into recovery it is the updated version of TWRP. I think it may be messing up my partitions somehow.
The problem is, I RUU'd last night with the official Sprint exe, and all was fine. Rooted, installed recovery and flashed the latest of CM12. Get it up and running, go about re installing all my apps, and use TWRP manager to update the recovery. Today the new nightly has some M8 specific updates to it, so I decided to flash it. I flash in recovery, get no errors, but once I reboot it stays stuck at the white HTC screen where they threaten to send you into poverty for misusing their software.
Does anyone have any input on how to correct this issue, outside of RUU'ing again?
Krunk_Kracker said:
I believe the root problem of this may be using TWRP manager to update recovery, because it happens after I attempt to do that. It asks if /dev/block/mmcblk0p43 is the correct partition, which i believe it is, and attempts to flash it. Once it attempts, it says it is failed, but when I reboot into recovery it is the updated version of TWRP. I think it may be messing up my partitions somehow.
The problem is, I RUU'd last night with the official Sprint exe, and all was fine. Rooted, installed recovery and flashed the latest of CM12. Get it up and running, go about re installing all my apps, and use TWRP manager to update the recovery. Today the new nightly has some M8 specific updates to it, so I decided to flash it. I flash in recovery, get no errors, but once I reboot it stays stuck at the white HTC screen where they threaten to send you into poverty for misusing their software.
Does anyone have any input on how to correct this issue, outside of RUU'ing again?
Click to expand...
Click to collapse
S-on or S-off? If S-on you have to flash the kernel separately from the ROM.
Magnum_Enforcer said:
S-on or S-off? If S-on you have to flash the kernel separately from the ROM.
Click to expand...
Click to collapse
I've been s-off'd since day one, and I just booted into bootloader and double checked, still s-off.
I did however this morning flash the Blissful kernel and it booted, and noticed your comment when I came to update. It's very strange that it needed the kernel flashed.
Hello,
I just installed latest OTA with security fixes and after reboots it's stuck at the white HTC screen.
I'm s-off, relocked and have custom recovery.
How to get into android without losing data?
Thanks in advance
mderksen said:
Hello,
I just installed latest OTA with security fixes and after reboots it's stuck at the white HTC screen.
I'm s-off, relocked and have custom recovery.
How to get into android without losing data?
Thanks in advance
Click to expand...
Click to collapse
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
help plz
donkeykong1 said:
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
Click to expand...
Click to collapse
i am facing the same problem.. i downloaded it frm settings>about>software update..
i was running teamwin recovery.. it failed to install..
thn i flashed stock recovery..
thn installed the ota frm software updates...
btw now my phn is stuck on the boot screen... plz hlp...
HTC M7UL
ROOTED
i was running 7.19.401.22
I'm facing the same problem: Stuck on white HTC screen.
1. Saw the notice for the OTA update for 7.19.401.30.
2. Since I was running Teamwin, reflashed 7.19.401.22 stock firmware.
3. Installed OTA 7.19.401.30.
4. Stuck on black screen (nothing on it, but illuminated)
5. Factory Reset.
6. Stuck on white HTC screen.
donkeykong1 said:
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
Click to expand...
Click to collapse
The normal way. I got a new update message on Android. I downloaded it and let it install. It rebooted twice or three times and now after boot it's stuck at the HTC white screen.
The only thing i could imagine is the custom recovery (twrp teamwin) which should be replaced by stock before i ran the update.
Now i see reflashing stock recovery in the replies here is not helping people either...
Same here.
Unlocked, S-Off, Stock 7.19.401.22 Rom and recovery . White Screen after applying the update.
Any hints?
Same problem here.
1. Running stock ROM, downloaded OTA.
2. Flashed stock recovery 7.19.401.22 via fastboot.
3. Installed OTA (default software update tool).
4. Device rebooted into recovery, installed, rebooted.
5. Stuck at htc one logo (white screen).
Is rooted, S-ON.
khfaisal994 said:
i am facing the same problem.. i downloaded it frm settings>about>software update..
i was running teamwin recovery.. it failed to install..
thn i flashed stock recovery..
thn installed the ota frm software updates...
btw now my phn is stuck on the boot screen... plz hlp...
HTC M7UL
ROOTED
i was running 7.19.401.22
Click to expand...
Click to collapse
muschi.muscholini said:
I'm facing the same problem: Stuck on white HTC screen.
1. Saw the notice for the OTA update for 7.19.401.30.
2. Since I was running Teamwin, reflashed 7.19.401.22 stock firmware.
3. Installed OTA 7.19.401.30.
4. Stuck on black screen (nothing on it, but illuminated)
5. Factory Reset.
6. Stuck on white HTC screen.
Click to expand...
Click to collapse
Jorgo-Bo said:
Same here.
Unlocked, S-Off, Stock 7.19.401.22 Rom and recovery . White Screen after applying the update.
Any hints?
Click to expand...
Click to collapse
An3skmbi said:
Same problem here.
1. Running stock ROM, downloaded OTA.
2. Flashed stock recovery 7.19.401.22 via fastboot.
3. Installed OTA (default software update tool).
4. Device rebooted into recovery, installed, rebooted.
5. Stuck at htc one logo (white screen).
Is rooted, S-ON.
Click to expand...
Click to collapse
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Thanks for your explanation. I did a RUU reset with 7.19.401.22 signed zip. After that i installed the update. All fine now. Phone is up and running again.
alray said:
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Click to expand...
Click to collapse
thanks dear dev... i was thinking of doing so.. but i have something important on my phone storage... now am backing up those files using adb... thn am going for it....
many many thanks...
alray said:
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Click to expand...
Click to collapse
weird, i just looked at the updater-script, and everything looks normal, first it checks all the files then performs the patches if everything matches.... did you ever figure out what the culprit was?
nkk71 said:
weird, i just looked at the updater-script, and everything looks normal, first it checks all the files then performs the patches if everything matches.... did you ever figure out what the culprit was?
Click to expand...
Click to collapse
No I did not looked at it yet. I just remember it was the same scenario with the previous ota:
Unlocked BL + custom recovery + stock rooted rom
restored stock recovery
downloaded and installed the ota update, no error during the update process
reboot and stuck at htc boot screen
I remember many ppl were having the same issue early June in the update thread, I have also experienced the same issue from 7.17.1540.7 to .21
(stock rooted, flashed back stock recovery, installed the update and phone stuck at HTC boot screen. Waited a lot thinking it was only the cache being rebuilt but after an hour, still not booted).
Very strange
Same here. I´ve installed the patch via OTA, all was running fine but the boot at the end stops at the white HTC screen.
OS 7.19.401.30, no root
I´ve tried start with power butten, out of the recovery the boot, even today a factory reset was without success. And the phone isn´t recognized by pc.
What should I do to get a working phone again?
Greetings mammaonecat
mammaonecat said:
Same here. I´ve installed the patch via OTA, all was running fine but the boot at the end stops at the white HTC screen.
OS 7.19.401.30, no root
I´ve tried start with power butten, out of the recovery the boot, even today a factory reset was without success. And the phone isn´t recognized by pc.
What should I do to get a working phone again?
Greetings mammaonecat
Click to expand...
Click to collapse
How long did you waited, first boot after an ota update can take longer (10 mins) than usual. Is your booloader unlocked/locked/re-locked?
Could someone provide me with a Nandroid backup of 7.19.401.30?
alray said:
How long did you waited, first boot after an ota update can take longer (10 mins) than usual. Is your booloader unlocked/locked/re-locked?
Click to expand...
Click to collapse
More than 30 minutes. The bootloader is locked. S-Off.
I´ve found also this: Android system recovery <3e>
LRX22G release-keys
E: missing bitmap oem_unlock_bg (Code -1)
E: missing bitmap oem_unlock_bg_yes
E: missing bitmap oem_unlock_bg_no
E: missing bitmap icon ruu (Code-1).
Greetings mammaonecat
I could not recover my data in any way... Tried whole saturday.
Just flashed RUU again and OTA's. The last OTA went fine now. After last OTA i rooted the phone again.
please give me the full stock rom of htc one m7 7.19.401.30 because i fail to flash the new update 186 mb patches... i do evry thing but i when the phone reboot to recovery mode he abrot the instalation of the update notes i m s-on i instal aroma stuck recovery and i relock the bootloader because unloking bootloader give nothing plz help
Hello everyone,
I'm having the same problem. I have an international HTC One M7. My OTA half worked (I put the stock recovery before flash), and now my phone says "7.19.401.30" when I'm in the bootloader. I am S-ON with unlocked.
Can I flash a RUU (zip format) with an older version (7.19.401.22) ? Is it possible ?
Other information, when I go into the stock recovery, I have lines of errors. Something like this :
E:missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bg_no
PS : I tried a usual .exe RUU but it failed.
Thanks for your help.
Loweack said:
Hello everyone,
I'm having the same problem. I have an international HTC One M7. My OTA half worked (I put the stock recovery before flash), and now my phone says "7.19.401.30" when I'm in the bootloader. I am S-ON with unlocked.
Can I flash a RUU (zip format) with an older version (7.19.401.22) ? Is it possible ?
Other information, when I go into the stock recovery, I have lines of errors. Something like this :
E:missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bg_no
PS : I tried a usual .exe RUU but it failed.
Thanks for your help.
Click to expand...
Click to collapse
I had the same problem. I installed the 7.19.401.22 zip from a connected USB-stick with CWM recovery and my phone booted again with all my settings and apps as they were before the update (apart from supersu)