Hi all,
Any help I can get would be greatly appreciated. I have a Sprint HTC One M7 that was previously rooted. Currently it is relocked with S-On, but at some point an OTA update was downloaded and now my phone keeps restarting itself and boots to this "android is upgrading..." screen. It keeps doing this loop over and over. It restarts itself, and then goes to this "android is upgrading..." I've spent hours in the forum this afternoon and I've tried numerous things and nothing seems to be working. Everything I've tried keeps giving me errors. At this point I would simply like to go back to the stock ROM and have a working phone. Can anyone help?
FYI...
I've tried using the .exe method from an RUU, but that isn't working because when it reboots to bootloader at the very beginning of the process my phone boots to android and I get the "android is upgrading..." message.
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
I've tried a factory reset and that fails. Again, I get the "android is upgrading..." loop.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader, and everything I've tried to work around that problem fails.
I'm currently running 6.23.651.7 and I'm trying to flash 6.23.651.10.
Again, any help would be massively appreciated. I'm desperate...
johnnycr said:
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
Click to expand...
Click to collapse
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader
Click to expand...
Click to collapse
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
alray said:
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
Click to expand...
Click to collapse
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
johnnycr said:
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
Click to expand...
Click to collapse
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Is your bootloader still relocked? If it is, you can't flash custom recovery. The only thing you can do is run RUU in that state
alray said:
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Click to expand...
Click to collapse
Well, I was just going to try and do this again, but now my PC can't even find it when I run "fastboot devices." I have the SDK and ADB driver installed, so I don't know why it can't find it all of a sudden.
I can't install the RUU by running the .exe, because when I do and it gets to the "waiting for bootloader..." screen my phone reboots and loads android and goes to the "android is upgrading" screen. So I need to flash the RUU via fastboot, but now my PC isn't recognizing my device in CMD...
Okay... so I finally got adb and fastboot working again. When I run "fastboot oem rebootRUU" the phone reboots to Android and goes to the "android is upgrading..." screen.
Update: So... I was able to successfully use adb and fastboot to unlock my HTC One again. I then tried to flash a custom recovery via fastboot, but I kept getting "FAILED (remote: signature verify fail)". I tried flashing TWRP, CWM, and stock HTC recovery and got the same failed message for each one. I'm just trying to find a way to break this stupid boot loop... HELP!
Update: So, my phone even restarts itself when I boot into safe mode... not good. Can anyone help me out?
Related
Some basic info about my phone-
HBOOT 1.47.0000
Radio 2.42.01.04.23
Carrier- iWireless (Kroger, Sprint subsidary)
S-ON
Alright, so I was just using my phone as normal. Running CM7.2 and ClockWorkMod Recovery. I turned off my phone, everything was fine. When I went to turn it on again, it showed the green HTC logo, as per normal, then it suddenly rebooted. There, it showed the green HTC logo again, and it'll just stay there. So I tried to boot into recovery (pulled the battery, put it back in, held the red end call button + volume down, got into hboot, then pressed home to go to recovery).
The thing is- it did the same thing. Reboot before it gets to recovery, and then stuck at the HTC Logo. I tried using the Sprint RUU, didn't work- it told me to download the right RUU for this phone, and gives me an error 131. I used the flashable RUU found in this thread (found here), in conjunction with this tutorial (found here). It gave me an error that looked like this when I ran "fastboot flash zip *flashable RUU zip path*"
Code:
FAILED (remote: 42 custom id check fail)
I believe it has something to do with the fact that it is NOT a Sprint branded phone. It doesn't even have a Google logo on the back.
Since it's not S-OFF, I can't flash a recovery via fastboot. I'm stuck. Help?
*TO CLARIFY*
I can't get into Recovery, or the actual system. I also can't access adb. The only part I can access is the bootloader and fastboot.
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
laie1472 said:
How much battery did you have left before you turned your phone off ?? Also what was the reason you turned your phone off ??? Also you linked to the use fastboot thread did you already type the "fastboot reboot reboot RUU" command ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
About 75% if I remember correctly. Only light usage. And I just turned it off in school, we were taking a test. Nothing abnormal about turning it off. And yes, several times. Tried flashing recovery/system/boot in every way possible, using that command and not using that command. I noticed something else- it seems like the NAND memory is completely wiped. There is NOTHING on the phone, other than the bootloader.
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
laie1472 said:
After you ran that command you tried to flash a zip or no ??? And more info on when you say the bootloader is the only thing on the phone would be appreciated. Also when you plug your phone into your pc does it recognize in its current state ??? Also when you boot into the bootloader what info is now displayed ???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Yes, I tried flashing multiple times. As I said, it fails with a CID check failure. And it doesn't seem that there's anything on the NAND anymore, as it doesn't even get to the boot logo, and recovery will just restart the phone.
My PC recognizes my phone, only in fastboot. And just normal bootloader info- model number, baseband, etc.
Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.
I had unlocked HTC One with Sense, which I had done 4.3 RUU install to convert it to GPe. Fast forward to now... I thought I'd sideload the 4.4 update, and during that process I got
set_metadata_recursive: some changes failed
installation aborted
I thought, great. No problem, I'll just do the traditional RUU again, I'll be fine.
BUT...
Now I can't boot into old OS. The phone keeps rebooting to the recovery. I tried to wipe-data from recovery, which didn't help. I also tried factory reset from HBOOT, and that didn't do anything either.
I am able to get into HBOOT and Stock recovery, so I know the phone is not bricked. I guess, I never had to deal with this situation before so I'm not sure how to get out of this loop. Is there a way I can get my phone to recognize on my computer, so that I can do the ADB / Fastboot commands?
Help!
PS: It might help to know what my device situation is atm. I have Unlocked bootloader with HBOOT 1.54, S-OFF
Have you tried to run the 4.3 or 4.4 RUU file from http://forum.xda-developers.com/showthread.php?t=2358781 ?
you have fastboot on your pc?
khhhhris said:
you have fastboot on your pc?
Click to expand...
Click to collapse
Yes.
SaHiLzZ said:
Have you tried to run the 4.3 or 4.4 RUU file from http://forum.xda-developers.com/showthread.php?t=2358781 ?
Click to expand...
Click to collapse
To do that, my phone would have to be recognized by the pc first, right? If I plug in via USB, and run adb devices I don't get any devices listed.
At what point should my phone be recognized by my laptop? The phone never goes to the main OS, so is there some way to get it to be recognized on my laptop USB while in HBOOT or Recovery? I have the stock recovery. The top of the recovery screen say s"Android system recovery <3e>"
I'm following along in http://forum.xda-developers.com/showthread.php?t=2544199 thread for now. A few things are similar. If I see anything different, I'll comment here again to see if anyone can help.
As you are S-Off, you can put the phone in fastboot mode, connect to computer and run the fastboot flash ruu twice.. either 4.3 or 4.4 RUU.
Update your covery twrp to v2.6.3.3 I updated after the looping problem and it worked, it installed with out the boot loops
Fastboot Flash the 4.3 boot.img
Then
Fastboot erase cache
Boot recovery
Wipe data
Flash 4.3 rom
SaHiLzZ said:
As you are S-Off, you can put the phone in fastboot mode, connect to computer and run the fastboot flash ruu twice.. either 4.3 or 4.4 RUU.
Click to expand...
Click to collapse
I got as far as flashing the RUU. I ran fastboot oem rebootRUU and then fastboot flash zip RUU-<more-stuff>.zip. The progress on my console shows the process completed successfully, but the phone is stuck at almost 99% on the progress bar. I'll wait for a while and see if it finishes. How long would be too long to wait?
drec70 said:
Update your covery twrp to v2.6.3.3 I updated after the looping problem and it worked, it installed with out the boot loops
Click to expand...
Click to collapse
I suppose I can go that route later on.
pull the plug and reboot manually..
backfromthestorm said:
Fastboot Flash the 4.3 boot.img
Then
Fastboot erase cache
Boot recovery
Wipe data
Flash 4.3 rom
Click to expand...
Click to collapse
Thanks for the help, but I guess I don't have to do this now. I'll keep this in mind in case I'm stuck again.
SaHiLzZ said:
pull the plug and reboot manually..
Click to expand...
Click to collapse
Haah! I should've followed through the complete instructions... I ended up giving the fastboot reboot and it started the boot. I couldn't reply sooner due to new-member 5-minute restriction.
Learned something good, something new today. And the phone WORKS! Thanks for your help.
Great news. Hit the thanks button if you dont mind! and keep the S-Off. that is your savior!
Cheers.
SaHiLzZ said:
Great news. Hit the thanks button if you dont mind! and keep the S-Off. that is your savior!
Cheers.
Click to expand...
Click to collapse
Aha! S-OFF shall stay intact Thanks.
Hi everyone
Since I restarted my phone last night, my phone has been in a endless bootloop and I can't even enter recovery, without it rebooting again and going into the same endless bootloop again, around 2 seconds after showing the "Teamwin" logo.
I'm using ARHD, and if I remember correctly it's version 71.1. TWRP is "openrecovery-twrp-2.6.3.3-m7" and running ElementalX kernel.
I expect my partition is somehow corrupted, but I'm at a loss of ideas as to how I can recover my phone again. I would apreciate if I could somehow manage to make a backup of my data, but it that's totaly hopeless, I'm thinking of going for the ArtMOD ROM instead and starting fresh.
Is there a helpfull soul out there, that could maybe give me some insights as to what I can do from here? Thanks in advance!
I was hoping I could install a stock ROM and start from scratch again, but I somehow suspect having used a modified ROM has gotten me in trouble now and the ROM Upgrade utility sees this as a downgrade. I've not been able to find a newer ROM for the .401. series than "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". Although the updater believes I'm updating from 4.19.401.11 (the ARHD ROM).
I can get into FASTBOOT USB and the phone goes to the black HTC logo screen when trying to update, but quickly fails on the PC during the process at "Updating 1/5". When unplugging the USB cable the phone shows:"
RUU
Security fail!
Update Fail!
I've attached two screenshots, to better explain
Can some kind soul out there please help me getting a working phone again? What ROM I'll end up with doesn't really matter
Since you're using unlocked bootloader, why don't you try RUU to get back on Stock ROM.
Here is the collection of ROMS
Download your ROM.
from Windows Command prompt
adb reboot bootloader #
If it didn't work, Press and Hold Power button along with Volume down of your phone,
When you reach to bootloader, get into fastboot mode.
Now follow the following commands to restore the STOCK Rom. (make sure your downloaded ROM are in the same directory where you have fastboot.exe, abd, and abdwin.api etc)
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip RUU.zip (RUU.zip is of course your downloaded Stock ROM). If it says Failed, try again.
4) fastboot erase cache
5) fastboot reboot-bootloader
6) fastboot reboot
Good Luck
Hope that helps.
Thank you so much for helping out!
After several tries, tries and retries, I finally managed to get the phone back up and running with the stock ROM. I believe what finaly did the trick, was to use "fastboot oem lock" to get the stock ROM installed. From here, I'm now able to unlock it again and install a custom recovery (TWRP) and ROM (I went for ARTMOD). Thanks again!!!
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".
It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img
Rename file
Did you rename the file? You need to rename it before flashing.
IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.
cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.
Try the last TWRP release, should work!
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.
Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...
cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...
adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers