I have an AT&T m7. It has S-off and an unlocked bootloader. Once Android 5 came out, I flashed the phone to GPE so I could get the OTA updates. I also prefer stock Android to Sense.
The phone is able to download the latest update: LMY47O.H6 (281.3MB) but fails to install. The phone reboots and I get the Android animation with a progress bar, but hits an error when it reaches about 25%. This has happened 4-5 times over the past couple of weeks.
Epos7 said:
but hits an error when it reaches about 25%.
Click to expand...
Click to collapse
And what is the error exactly?
alray said:
And what is the error exactly?
Click to expand...
Click to collapse
I have the same issue with my M7 (s-off, root, gpe). The error is that phone stops installing update, there's green android on its back with red triangle with exclamation mark in stomach It lasts for a minute and the phone restarts itself.
PatriotPL said:
I have the same issue with my M7 (s-off, root, gpe). The error is that phone stops installing update, there's green android on its back with red triangle with exclamation mark in stomach It lasts for a minute and the phone restarts itself.
Click to expand...
Click to collapse
To see what the error is exactly, you must hold volume up and hit power when in recovery so you can see the recovery menu and the error at the bottom of the screen when it is failing.
"Red triangle" can be caused by many things:
Not using the correct recovery
Corrupted system files
Missing system files
Rom fingerprint mismatch
and more
We need to know what is the error exactly.
I've been trying other methods to get the update and I think the error is this: a message about some fingerprints that should be "htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys" or "htc/m7_google/m7:5.1/LMY470.H6/536258:user/release-keys" and mine is "htc/cm_m7/m7:4.4.2/KVT49L/3f6e6e21ab:eng/test-keys". What can I do to install the update?
PatriotPL said:
I've been trying other methods to get the update and I think the error is this: a message about some fingerprints that should be "htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys" or "htc/m7_google/m7:5.1/LMY470.H6/536258:user/release-keys" and mine is "htc/cm_m7/m7:4.4.2/KVT49L/3f6e6e21ab:eng/test-keys". What can I do to install the update?
Click to expand...
Click to collapse
looks like you don't have to correct recovery installed, try to flash 5.0.1 or the 5.1 GPE stock recovery posted here
5.11.1700.3
or
6.04.1700.6
Hm, that's strange... In Settings > Phone Info I have "Compilation Number" that says "LRX22C.H3 release-keys" (which is one of two mentioned above necessery to install update). In fastboot i have this:
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.....
OS-5.11.1700.3
So it seems that I have the version you mentioned...
PatriotPL said:
Hm, that's strange... In Settings > Phone Info I have "Compilation Number" that says "LRX22C.H3 release-keys" (which is one of two mentioned above necessery to install update). In fastboot i have this:
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.....
OS-5.11.1700.3
So it seems that I have the version you mentioned...
Click to expand...
Click to collapse
so flash the 5.11.1700.3 stock recovery and try again
Ok, I flashed it and tried to go to recovery - and again there's the green bot with red triangle (I used both adb "adb reboot recovery" and power+volDown). Before I flashed that recovery you sent I had TWRP and it worked just fine (besides it didn't let me update to 5.1). Maybe you have another idea?
PatriotPL said:
Ok, I flashed it and tried to go to recovery - and again there's the green bot with red triangle (I used both adb "adb reboot recovery" and power+volDown). Before I flashed that recovery you sent I had TWRP and it worked just fine (besides it didn't let me update to 5.1). Maybe you have another idea?
Click to expand...
Click to collapse
You can't update when a custom recovery is installed. You can't neither initiate the update process yourself by booting in stock recovery. Now that the stock recovery is installed just boot in the OS, search for updates and let the phone reboot to recovery itself to install the update.
Stock recovery is installed, but why I can't boot into it? Anyway, I tried to search for the update through Settings but now it says that I am up-to-date (but I'm not - I still have 5.0.1). Is there any way to install the update manually?
Ok, I tried to install update with adb sideload, but I got this error: Installing update L50QCT.00.001.001; Verifying current system ; "/system/bin/app_process32" has unexpected contents. E:Error in sideload/package.zip (Status 7) And it stops. Any idea what can I do?
PatriotPL said:
I have the same issue with my M7 (s-off, root, gpe). The error is that phone stops installing update, there's green android on its back with red triangle with exclamation mark in stomach It lasts for a minute and the phone restarts itself.
Click to expand...
Click to collapse
This is the error I have. I also can't load recovery, getting the same error.
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.
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
cburch85 said:
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
Click to expand...
Click to collapse
donwload the all in one toolkit use it to erase cache then install recovery. after that either mount usb otg and copy rom to sd or sideload a rom. all in one toolkit automates everything you need to do:good::good:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
cburch85 said:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
Click to expand...
Click to collapse
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
skinsfanbdh said:
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
Click to expand...
Click to collapse
Thanks for getting me this far. Mounting didn't work, so I sideloaded rom. it is showing up on the phone as "sideload.zip" i try to run and it fails. Any ideas?
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Guich said:
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Click to expand...
Click to collapse
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
im guessing your using twrp but just select no dont root the rom is already rooted and it should boot. may take getting through a few aroma freezes but it will boot
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Guich said:
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Click to expand...
Click to collapse
OK, so I didn't say yes to the question this time after sideloading android revolution. same thing. goes blank then reboots to bootloader menu. So I tried sideloading viperrom 1.04. This time after it finished sideloading it randomly installed instelfl, and now viperrom is installed, its booting up to the phone now finally, yet before anything can initialize, it just reboots again. It's been caught in this boot loop about ten minutes now. No end in sight. Any ideas?
ViperRom from Sprint or AT&T one forum?
Your phone is branded or no-brand?
However, boot into recovery, and use this command:
Code:
adb push name_of_rom.zip /sdcard
, then flash it
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
cburch85 said:
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
Click to expand...
Click to collapse
Have you tried to flash the boot.img from fastboot?
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
cburch85 said:
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
Click to expand...
Click to collapse
Where did you find the RUU for sprint? I cant seem to find one that works with my CID: SPCS_001.
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
zach832 said:
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
Click to expand...
Click to collapse
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Can't detect SD Card
Guich said:
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Click to expand...
Click to collapse
Hi, I'm having sort of the same problem. My phone is stuck on a bootloop, I flashed a new recovery because the previous TWRP stopped working. When I try to wipe data/factory reset, It says that it can't detect E:\ or the SD Card. I can't even mount it. Any ideas? Please help. Thanks
Hello friends, I'm new here. The name's Jay. I hope to make good acquaintances here
Now for my problem: my One is stuck on a boot loop. It boots fine into the bootloader and recovery. I tried using the 1.29 RUU and the latest RUU (version 3.x) but still after a few mintues of booting into the OS it would restart. I've tried factory reseting and wiping the caches but no cigar.
Some back story: I originally had the phone rooted but with stock ROM and bootloader (using CWM recovery). All was good until one day my phone was not getting any service (there was an x on the signal indicator). I tried restarting my phone and thats when the boot loop started. I, ofcourse, backed everything up via adb (so no problem there) then tried resseting, changing ROMs (cyannagem) and it still rebooted a few minutes after the OS loads. On the sprint ROM, it always says system is unresponsive and it crashes.
Is my phone dead for good?
auto44e said:
Hello friends, I'm new here. The name's Jay. I hope to make good acquaintances here
Now for my problem: my One is stuck on a boot loop. It boots fine into the bootloader and recovery. I tried using the 1.29 RUU and the latest RUU (version 3.x) but still after a few mintues of booting into the OS it would restart. I've tried factory reseting and wiping the caches but no cigar.
Some back story: I originally had the phone rooted but with stock ROM and bootloader (using CWM recovery). All was good until one day my phone was not getting any service (there was an x on the signal indicator). I tried restarting my phone and thats when the boot loop started. I, ofcourse, backed everything up via adb (so no problem there) then tried resseting, changing ROMs (cyannagem) and it still rebooted a few minutes after the OS loads. On the sprint ROM, it always says system is unresponsive and it crashes.
Is my phone dead for good?
Click to expand...
Click to collapse
Phone is not dead for sure.
Which os were you on? Did your father get 4.3 update?
Hboot version?
Does ruu go through completely. If not check drivers
aashishbhargav said:
Phone is not dead for sure.
Which os were you on? Did your father get 4.3 update?
Hboot version?
Does ruu go through completely. If not check drivers
Click to expand...
Click to collapse
IWhen i brought the phone (July 2013) HBOOT was on 1.4x (something close) and i think 4.2.2 android. That rooted fine, until i had the boot problem. After trying the latest RUU 3.x (and it did go through all the way both the 1.29 ruu and 3.x) HBOOT is now at 1.5x and android is (i think) at 4.3 (it doesn't stay on lopng enough for me to check the andoid version).
auto44e said:
IWhen i brought the phone (July 2013) HBOOT was on 1.4x (something close) and i think 4.2.2 android. That rooted fine, until i had the boot problem. After trying the latest RUU 3.x (and it did go through all the way both the 1.29 ruu and 3.x) HBOOT is now at 1.5x and android is (i think) at 4.3 (it doesn't stay on lopng enough for me to check the andoid version).
Click to expand...
Click to collapse
Boot into Bootloader mode by using power button and volume down key.
Install drivers for HTC one on a different computer. HTC should show as MyHTC in device manager.
Then close all other programs on the computer and run 3.04.651.2 RUU from here
Good Luck.
---------- Post added at 12:07 PM ---------- Previous post was at 11:57 AM ----------
aashishbhargav said:
Boot into Bootloader mode by using power button and volume down key.
Good Luck.
Click to expand...
Click to collapse
at this point lock your bootloader again to run RUU.
Command to check if fastboot recognizes your device:
fastboot devices
fastboot oem lock
Read this http://forum.xda-developers.com/showthread.php?t=2424287
The same thing happened to me. read that post and applied fixed it right up!
aashishbhargav said:
Phone is not dead for sure.
Which os were you on? Did your father get 4.3 update?
Hboot version?
Does ruu go through completely. If not check drivers
Click to expand...
Click to collapse
aashishbhargav said:
Boot into Bootloader mode by using power button and volume down key.
Install drivers for HTC one on a different computer. HTC should show as MyHTC in device manager.
Then close all other programs on the computer and run 3.04.651.2 RUU from here
Good Luck.
---------- Post added at 12:07 PM ---------- Previous post was at 11:57 AM ----------
at this point lock your bootloader again to run RUU.
Command to check if fastboot recognizes your device:
fastboot devices
fastboot oem lock
Click to expand...
Click to collapse
finally got around to trying it, even at 3.04, i still have a boot loop, and now I can't even flash a custom recovery for some reason (it always says signature check fail)
are you s-off?
auto44e said:
finally got around to trying it, even at 3.04, i still have a boot loop, and now I can't even flash a custom recovery for some reason (it always says signature check fail)
Click to expand...
Click to collapse
Hi guys,
I am feeling quite panicked right now since I flash the wrong firmware (lower version) which leads me to failed RUU "Too many links" and then when i reboot to bootloader it constantly boot into four triangles and unable to fastboot oem rebootRUU at all to reflash and my bootloader are in a messed.
I have the same exact problem as this guy http://forum.xda-developers.com/showthread.php?t=2459221 but i don't really understand to solve the problem as i'm not an expertise in this type of problem.
I can still access my phone by manually using "Fastboot oem boot" but other than that i can't power up my phone or boot into bootloader as i have four triangles in each edge of my phone and orange-colored "RUU". I cant flash any rom or firmware or going into my TWRP.
My Phone is S-OFF and Unlocked bootloader.
Here's My partition 19 if needed to solve this issue.
Help me please !
ander427 said:
Hi guys,
I am feeling quite panicked right now since I flash the wrong firmware (lower version) which leads me to failed RUU "Too many links" and then when i reboot to bootloader it constantly boot into four triangles and unable to fastboot oem rebootRUU at all to reflash and my bootloader are in a messed.
I have the same exact problem as this guy http://forum.xda-developers.com/showthread.php?t=2459221 but i don't really understand to solve the problem as i'm not an expertise in this type of problem.
I can still access my phone by manually using "Fastboot oem boot" but other than that i can't power up my phone or boot into bootloader as i have four triangles in each edge of my phone and orange-colored "RUU". I cant flash any rom or firmware or going into my TWRP.
My Phone is S-OFF and Unlocked bootloader.
Here's My partition 19 if needed to solve this issue.
Help me please !
Click to expand...
Click to collapse
First before sending you the modified misc partition, can you please tell us what you have flashed exactly (provide link) and more info about your devices (fastboot getvar all) or at least your CID, MID, Version number you was on before flashing?
I see in your misc partition that the RUU flag is indeed active.
---------- Post added at 04:39 PM ---------- Previous post was at 04:24 PM ----------
however here it is: https://dl.dropboxusercontent.com/u/77459918/p19noRUUflag.img
Code:
fastboot oem boot
then copy the file to the root of your sdcard or you can push it using
Code:
adb push p19noRUUflag.img /sdcard
then to restore it to your misc partition
Code:
adb shell
su
dd if=/sdcard/p19noRUUflag.img of=/dev/block/mmcblk0p19
exit
adb reboot-bootloader
and then flash your RUU.zip and make sure to flash it correctly.
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
Don't know what ruu you need, if you need help choosing one then post your "fasboot getvar all".
And be very very careful with the "dd" command. If you make a typo, you can brick your phone foor good (writing to the wrong parititon)
IT WORKED !! My Bootloader went back to normal !!! You are a savior and making my day better
Thanks !! Your explanations are really clear and very easy to understand that i able to follow all the steps correctly with ease : )
Well I was using ARHD 71.1 and planning to dirty flash to ARHD 90.0 if possible. Then I was using 5.x.401.x firmware that was used in ARHD 71.1. I have seen that the new ARHD 90.0 are using the latest 7.15.401.1 so i flash to that firmware directly before I plan to install the ROM. And I forgot to place the ROM to the SDCard which then requries me to boot to the O.S in order to access the storage. Then suddenly when i restart my phone, My Phone soft bricked where the phone is stuck at black screen constantly while usually the phone should properly goes to the "HTC One" Phrase and then goes to the O.S but in my case, It first boot into the htc green logo and after a while the screen goes black screen.
I thought the firmware is incompatible with my arhd 71.1 so i downgrade it again 5.x.401.x and then while updating the RUU, I receive "Failed : Too many Links" which quite made my worried so I restart the phone to try if downgrading to the older firmware would fix the issue. But then, the "Four Triangle" issue rise.
I am grateful that you have solve my issue regarding this matter and I cannot be more happier than this that everything went back to normal. Thank You So Much! :good: You are the best !
ander427 said:
IT WORKED !! My Bootloader went back to normal !!! You are a savior and making my day better
Thanks !! Your explanations are really clear and very easy to understand that i able to follow all the steps correctly with ease : )
Well I was using ARHD 71.1 and planning to dirty flash to ARHD 90.0 if possible. Then I was using 5.x.401.x firmware that was used in ARHD 71.1. I have seen that the new ARHD 90.0 are using the latest 7.15.401.1 so i flash to that firmware directly before I plan to install the ROM. And I forgot to place the ROM to the SDCard which then requries me to boot to the O.S in order to access the storage. Then suddenly when i restart my phone, My Phone soft bricked where the phone is stuck at black screen constantly while usually the phone should properly goes to the "HTC One" Phrase and then goes to the O.S but in my case, It first boot into the "Quietly Brilliant" htc green logo and after a while the screen goes black screen.
I thought the firmware is incompatible with my arhd 71.1 so i downgrade it again 5.x.401.x and then while updating the RUU, I receive "Failed : Too many Links" which quite made my worried so I restart the phone to try if downgrading to the older firmware would fix the issue. But then, the "Four Triangle" issue rise.
I am grateful that you have solve my issue regarding this matter and I cannot be more happier than this that everything went back to normal. Thank You So Much! :good: You are the best !
Click to expand...
Click to collapse
you're welcome!
alray said:
you're welcome!
Click to expand...
Click to collapse
damn.. I create another mistake.. I flash the RUU into 7.15.401.1 and I wanted to flash the ARHD 90.0 ROM but suddenly its still in stock recovery, forgot to flash the TWRP.. Now I restart the phone wanting to boot into bootloader fastboot and now i unable to get into the bootlaoder and constantly forced to go into the HTC Green logo screen. And Now It stays on the "Red Triangle Exclamation Mark". What did i do wrong ??
ander427 said:
damn.. I create another mistake.. I flash the RUU into 7.15.401.1 and I wanted to flash the ARHD 90.0 ROM but suddenly its still in stock recovery, forgot to flash the TWRP.. Now I restart the phone wanting to boot into bootloader fastboot and now i unable to get into the bootlaoder and constantly forced to go into the HTC Green logo screen. And Now It stays on the "Red Triangle Exclamation Mark". What did i do wrong ??
Click to expand...
Click to collapse
hold power and volume down until you are in bootloader mode then reflash your custom recovery and after arhd 90
alray said:
hold power and volume down until you are in bootloader mode then reflash your custom recovery and after arhd 90
Click to expand...
Click to collapse
I have tried doing that countinously and the phone wont boot into the bootloader mode in fact it keep restarting normally somehow goes to the HTC Green Logo. Now after continous restart, I able to boot the phone normally into the O.S with Safe Mode. Which Step should I do? to be able to boot into the bootloader.
ander427 said:
I have tried doing that countinously and the phone wont boot into the bootloader mode in fact it keep restarting normally somehow goes to the HTC Green Logo. Now after continous restart, I able to boot the phone normally into the O.S with Safe Mode. Which Step should I do? to be able to boot into the bootloader.
Click to expand...
Click to collapse
when booted in safe mode, open a command prompt and type
Code:
adb reboot bootloader
alray said:
when booted in safe mode, open a command prompt and type
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Thanks For Reminding the way, I forgot that part haha
Thanks now my phone is back to normal !! ThankYou once again Sir !
ander427 said:
Thanks For Reminding the way, I forgot that part haha
Thanks now my phone is back to normal !! ThankYou once again Sir !
Click to expand...
Click to collapse
So your firmware is 7.15.401.1 and you have flashed arhd 90 and everything works fine now?
alray said:
So your firmware is 7.15.401.1 and you have flashed arhd 90 and everything works fine now?
Click to expand...
Click to collapse
Yes! Everything works fine the way it should now
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?