Update Stuck - One (M7) Q&A, Help & Troubleshooting

Hi everyone,
I'm having an issue updating my wife's rooted and unlocked HTC One.
I flashed stock recovery for the process to go smoothly but the update is always stuck at roughly 25%. I switch off the phone, it tries again and gets stuck again at 25% with a red mark.
I tried deleting the update and downloading it again through the GUI without luck.
I suspected 3rd party mods like the battery percentage hack, but it still didn't work after reverting it.
P.S. I also have an HTC One, had an issue updating because I had CWM, but the update worked like a charm when I flashed stock recovery.

Any clues?

Bump

1. where are you flashing the update from? - is it a zip file or is it the one the pone received OTA?
2. Which recovery are you using?
3. Which Rom are you on?

Related

[Q] Booting PAST recovery...cannot apparently root.

Been flashing ROMs for months.Going back to stock then update..
With this last flash to Stock and after applying Update through recovery the phone will not root.
After reinstall packages after Update was applied the phone just boots and does not go into second recovery screen.
SU was never installed.
Any ideas what mucked up the Stock flash tp where One click or update root does not work?
Found the solution
New Update file

Stuck on Boot Screen (HTC Quietly Brilliant)

Hi,
I got my brother's old HTC One M7 and tried to flash the ROM.
I have experience with Samsung Devices so I figured it worked the same way.
I install cyanogenmod using their installer. It worked, but dreadfully slow (slower than the stock rom).
So I downloaded Android Revolution 53.0, put in the /Downloads folder and went into recover and tried to install from zip.
It appeared as if the installation went through, and now the phone is stuck on the HTC quietly brilliant screen.
I can go into HBOOT, FASTBOOT, RECOVERY.. But I can't seem to get past it.
Just went into recovery and see "No OS installed! Are you sure you wish to reboot?"
Please help!
Thanks.
First question....what version recovery are you using
Sent from my HTC One using XDA Premium 4 mobile app
To revive this thread.
So, I was able to figure out the original problem or at least get around it.
For whatever reason Android Revolution HD wouldn't install despite trying to flash the ROM using TWRP or CWM recovery.
I was able to get CyanogenMod and LiquidSmooth to work without issues.
I later used a Nandroid backup of a Bell Mobility (CID BM____001) and return it to "stock" JB.
I'm trying to get KIT KAT on it, I get the OTA update notification, but after it initiates the installation, device reboots into my custom recovery.
So, I tried to flash the stock BM recovery, and BM Stock KitKat install starts, but then I get a teal and pink screen back to back and get stuck on the HTC / Beats screen.
Any help is appreciated.
OK, your first problem sounds like you didnt flash the Boot.img first through fastboot, before trying to install the ARHD Rom, extract it from the zip file you downloaded and flash it through fastboot, then flash the rom, I believe Sense Roms (ARHD) will not work on non sense rom boots like CyanogenMod.
Post 3 problem is you need to install the stock recovery first.
Thanks for the quick response.
I've gotten further than where I was about an hour ago.
I realized when I flashed the stock recovery for BM_001, it was an older version (mismatched my ROM).
I flashed the the stock recovery version of my stock ROM, and I was able to get KIT KAT.
Now, it's doing a 2nd OTA update to get SENSE 6.
Will post update as soon as it's done. Hopefully it's successful.

Need help Reinstalling stock recovery HTC One m7

Hey everyone,
I need some help, a while ago I attempted to install a custom ROM for my HTC One m7. Anyway I never actually installed the custom rom so I still have my carriers version or rom still installed (Optus australia) which is the good news! The bad news is I still have TWRP recovery installed instead of the stock recovery. Now my problem is I want to install the latest update from my carrier but it keeps going into TWRP when the phone restarts to install the update. Is there away to remove TWRP and install stock recovery that comes with the phone? If so do I have to install RUU file? The problem is I cant find the RUU file for optus australia anywhere, except the nandroid file, but i think ill have problems with the touch screen if use that? So Is there a way to install stock recovery without using ruu, rom or nandroid file?
Thanks!
This might help
http://forum.xda-developers.com/showthread.php?t=2463387
Hey thanks for the link. That was help full. But iv got another problem I installed the stock recovery for htc one and everything seemed ok except when i went to install the latest update from my carrier (optus AU) the phone restarted it went in to update mode and got about half way and then i got error it was a red triangle with the explanation mark.
I then hit the power button and volume up to get into its loader screen (not really sure what its called) and I restored the phone to factory settings and then rebooted the phone. I then download the update again and restarted the phone to get the red triangle and explanation mark again.
I did notice when I got into the bootloader that my device is still TAMPERED ,***UNLOCKED** and the s-on is active. Could any of these be the reason why its not installing the latest update? sorry im pretty bad at this!

Installed Xposed Framework zip, soft-bricked phone :(

Hey guys,
I know I know, I was stupid to try to get this working but I tried and failed. Now I'm just looking to get my old phone back and just leave it at being rooted (with custom recovery installed) and a custom rom. All 3 of these I had successfully done before I installed the framework zip which is where the problems arose.
I'll give you as much information as possible:
Phone: SM-G935F (UK version and on EE network)
Rooted with: CF-Auto-Root-hero2lte-hero2ltexx-smg935f
Custom Recovery flashed: twrp-3.0.2-2-hero2lte.img.tar
Other things flashed: UPDATE-SuperSU-v2.76-20160630161323.zip
no-verity-opt-encrypt.zip
Custom Rom flashed: KryxxOS-R1.3-G935F.zip
All of these were working and I should have stopped here but with the new Pokemon craze I really wanted Xposed installed to use the modules for it however massively regret it. I wish to get back to this point.
Zip used for Xposed: xposed-v86-sdk23-arm64.zip
Phone initially wouldn't do anything apart from show a battery (not charging (grey icon with lightening in it)) icon when connected to power. And it would ONLY do something when booting into download mode allowing me to go into it. It seemed the custom recovery was no longer working. I then tried everything, flashing back all Stock firmware for my model using ODIN and correct files for my phone (G935FXXU1APF2_G935FEVR1APE2_EVR), that didn't work. Even when installing only AP, all 4 using first HOME_CSC in the CSC and then using all 4 using the CSC file in the CSC. Then I tried using Smart Switch's recovery system, this failed also. Then I remembered hmmm, I can try to reflash my custom recovery using Odin. That WORKED. I thought great now I can do something and sure enough I could wipe my phone and access my files on my phone again when rebooted. After the reboot I tried just re-flashing the SU, the no-verify and the custom ROM thinking it would take me back. It still didn't boot. Black screen nothing. The last thing I attempted was to flash the Xposed Framework uninstaller and used this zip : xposed-uninstaller-20150831-arm64. I didn't know what this asci files were so I didn't flash them? After flashing the uninstaller, I again flashed SU, no-verify and the custom ROM. Nothing. Still nothing. However...whilst I was typing this, because my phone was connected to my PC and not stuck in DL mode or anything, it's now randomly come up with a battery charge. 3% so far but I want to wait until its higher before I risk trying to turn it on. Could it have been a dead battery all along whilst trying to fix?
I'd appreciate your help even if its to clarify that the battery seems to be the problem. I'll keep you posted with it throughout the night but if it gets sorted tonight it means I don't have to go into the city tomorrow to buy a fix. Thanks to all who post. Ask if you need anymore information.
Chris
hey, how did things go now, is it back to normal... rooted with TWRP and your custom ROM of choice ?
nexiros said:
Hey guys,
Chris
Click to expand...
Click to collapse
lol i know this is an old post but damn what a mess you are. you did just everything wrong. :laugh::laugh: hope everything is back working now

i can't update my phone after unrooting

ok so basically i rooted my phone some time ago and it went kinda fine, after some time i realized i didn't really need it and i unrooted it just now with superSU, when doing so, superSU asked me if i wanted to return to the stock ROM, and i said yes, since i had an update to do, and you can't do those via OTA with a custom rom i think, anyways i said yes and unrooted my phone, the i proceded to delete lucky patcher, twrp, and everything root related, even after all this, after downloading the update my phone gets stuck in a bootloop and i have to press power+volumeup+volumedown to go into recovery mode (i think that's recovery mode?) and here it starts the update, after 5%, it says it failed and i have to reboot, how do i even check if i have my stock rom back?
Rurouni_ said:
ok so basically i rooted my phone some time ago and it went kinda fine, after some time i realized i didn't really need it and i unrooted it just now with superSU, when doing so, superSU asked me if i wanted to return to the stock ROM, and i said yes, since i had an update to do, and you can't do those via OTA with a custom rom i think, anyways i said yes and unrooted my phone, the i proceded to delete lucky patcher, twrp, and everything root related, even after all this, after downloading the update my phone gets stuck in a bootloop and i have to press power+volumeup+volumedown to go into recovery mode (i think that's recovery mode?) and here it starts the update, after 5%, it says it failed and i have to reboot, how do i even check if i have my stock rom back?
Click to expand...
Click to collapse
Because you have not flashed the stock boot. Use dload method to boot to stock rom now. You may flash the same build number or the one with ota.

Categories

Resources