Okay, so my phone is stuck in a boot loop after flashing a new ROM. I tried wiping the cache before and after and doing factory reset. I have tried different ROMs and the same thing always happens, it boots up and opmimizes apps then tells me "Unfortunately gapps or google play services or system ui or phone or something failed" and then restarts. Could someone please help me out.
korbs710 said:
Okay, so my phone is stuck in a boot loop after flashing a new ROM. I tried wiping the cache before and after and doing factory reset. I have tried different ROMs and the same thing always happens, it boots up and opmimizes apps then tells me "Unfortunately gapps or google play services or system ui or phone or something failed" and then restarts. Could someone please help me out.
Click to expand...
Click to collapse
What ROM, what recovery version, what firmware version, what model version, are you S-ON or S-OFF, did you do a clean flash or dirty flash? and the wipe is preferably before the ROM installation in my experience.
I started with CM 12.1 but it had a reboot loop issue when the screen would be put to sleep so I changed to Venom 3.50. I am using TWRP 2.8.7.0. Not sure what firmware, can I check that from recovery? It is a North American version on Rogers, can't find model version in bootloader or recovery. S-ON, what'e the difference between dirty and clean? I do a factory rest on recovery and then click install and flash the ROM and then reboot.
korbs710 said:
I started with CM 12.1 but it had a reboot loop issue when the screen would be put to sleep so I changed to Venom 3.50. I am using TWRP 2.8.7.0. Not sure what firmware, can I check that from recovery? It is a North American version on Rogers, can't find model version in bootloader or recovery. S-ON, what'e the difference between dirty and clean? I do a factory rest on recovery and then click install and flash the ROM and then reboot.
Click to expand...
Click to collapse
For clean in recovery click advanced wipe, check system, data , and both caches. Dirty install for example would be just flashing the ROM again if there was an update where you don't delete any of your data. Also the screen off reboot comes from not having the correct firmware for the ROM. Boot into download mode to see what firmware you are on. Then make sure you flash a ROM that is based off the firmware you are on.
BUBBA DUB'S said:
For clean in recovery click advanced wipe, check system, data , and both caches. Dirty install for example would be just flashing the ROM again if there was an update where you don't delete any of your data. Also the screen off reboot comes from not having the correct firmware for the ROM. Boot into download mode to see what firmware you are on. Then make sure you flash a ROM that is based off the firmware you are on.
Click to expand...
Click to collapse
I have been doing clean installs. I am on firmware 2.11 and I don't think any ROMs exist yet. The phone won't stay on long enough to use sunshine. Should I wait for a new ROM to come on based on my firmware? The phone just keeps rebooting and sometimes it won't even go to a homescreen. Is there anything else I should try? I am out of ideas at this point.
korbs710 said:
I have been doing clean installs. I am on firmware 2.11 and I don't think any ROMs exist yet. The phone won't stay on long enough to use sunshine. Should I wait for a new ROM to come on based on my firmware? The phone just keeps rebooting and sometimes it won't even go to a homescreen. Is there anything else I should try? I am out of ideas at this point.
Click to expand...
Click to collapse
Do you have the OEM lock disabled?
DeadPotato said:
Do you have the OEM lock disabled?
Click to expand...
Click to collapse
Says Unlocked on the Bootloader screen. Is that what you mean?
korbs710 said:
Says Unlocked on the Bootloader screen. Is that what you mean?
Click to expand...
Click to collapse
Go into settings, developer options , and then look for OEM lock setting.
BUBBA DUB'S said:
Go into settings, developer options , and then look for OEM lock setting.
Click to expand...
Click to collapse
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
korbs710 said:
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
Click to expand...
Click to collapse
If it boots up into anything it is not bricked. Can you hold power plus volume up and get into download mode? You could try fastboot flashing your RUU for your device to start over from scratch.
BUBBA DUB'S said:
If it boots up into anything it is not bricked. Can you hold power plus volume up and get into download mode? You could try fastboot flashing your RUU for your device to start over from scratch.
Click to expand...
Click to collapse
It will boot into TWRP 2.8.7.0 recovery mode and I downloaded the RUU for Rogers in Canada but it is based on a different firmware build. But do I have to lock my bootloader again with fastboot oem lock? I haven't tried that yet. Will the firmware matter in this case? I will try the relock and load RUU if you think firmware doesn't matter, I am on 2.11 and the RUU is based on 1.32.
korbs710 said:
It will boot into TWRP 2.8.7.0 recovery mode and I downloaded the RUU for Rogers in Canada but it is based on a different firmware build. But do I have to lock my bootloader again with fastboot oem lock? I haven't tried that yet. Will the firmware matter in this case? I will try the relock and load RUU if you think firmware doesn't matter, I am on 2.11 and the RUU is based on 1.32.
Click to expand...
Click to collapse
I am not sure @DeadPotato do you know if it's ok to go backwards with an RUU regarding firmware?
korbs710 said:
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
Click to expand...
Click to collapse
DO NOT RELOCK OR YOU MAY BRICK YOUR PHONE.
You probably can't run that ruu because you're not s-off and can't downgrade unless the aboot has not changed.
To confirm, you went into download mode and it says OS-2.11.x? What is your CID?
My suggestion would be to do another complete wipe (system, data, cache, dalvik) and then flash a different rom, preferably one of the stockish ones like ARHD or Maximus. If you can boot up most of the way, the problem is likely just getting your OS straightened out.
iElvis said:
DO NOT RELOCK OR YOU MAY BRICK YOUR PHONE.
You probably can't run that ruu because you're not s-off and can't downgrade unless the aboot has not changed.
To confirm, you went into download mode and it says OS-2.11.x? What is your CID?
My suggestion would be to do another complete wipe (system, data, cache, dalvik) and then flash a different rom, preferably one of the stockish ones like ARHD or Maximus. If you can boot up most of the way, the problem is likely just getting your OS straightened out.
Click to expand...
Click to collapse
Correct, I am not S-OFF as of now. Not sure if it is possible without being able to boot into an OS.
Yes I am OS-2.11.631.2. CID: ROGER001.
I have tried many ROMs, including ARHD 12.0 but the problem is all the ROMs are based on 1.32 and not 2.11. When I flash ARHD it will get to Optimizing apps once then it will reboot and be stuck on splash screen forever.
korbs710 said:
Correct, I am not S-OFF as of now. Not sure if it is possible without being able to boot into an OS.
Yes I am OS-2.11.631.2. CID: ROGER001.
I have tried many ROMs, including ARHD 12.0 but the problem is all the ROMs are based on 1.32 and not 2.11. When I flash ARHD it will get to Optimizing apps once then it will reboot and be stuck on splash screen forever.
Click to expand...
Click to collapse
There are many 2.x roms. If you're flashing 1.x roms, there's your problem. Download one of the latest 2.x-based roms.
iElvis said:
There are many 2.x roms. If you're flashing 1.x roms, there's your problem. Download one of the latest 2.x-based roms.
Click to expand...
Click to collapse
I have not been able to find one... ARHD 12.0 (the newst release is 1.x based I think). I could be wrong but even so, I have flashed that ROM and just have a boot loop error. How can I tell what the ROM is based on? I have tried many google searches and looked through many forums... At this point I just want the stupid phone to turn on. Sorry to be bothering you and I appreciate the help but I am just extremely frustrated at this point and I do realize it is all my fault.
korbs710 said:
I have not been able to find one... ARHD 12.0 (the newst release is 1.x based I think). I could be wrong but even so, I have flashed that ROM and just have a boot loop error. How can I tell what the ROM is based on? I have tried many google searches and looked through many forums... At this point I just want the stupid phone to turn on. Sorry to be bothering you and I appreciate the help but I am just extremely frustrated at this point and I do realize it is all my fault.
Click to expand...
Click to collapse
12.0 is based on 2.10.401. It's possible there is a conflict with the 2.11 Rogers firmware, though I have not seen anyone else post about this.
On the RUU, did you ever tick the "Allow OEM Unlocking" setting in Developer Options since you upgraded to 2.x? If you did not, you cannot relock in your current state because you won't be able to boot up (because of your custom recovery), and won't be able to unlock again, even through HTCdev, because this setting will block it. You would be stuck in bootloader until you could run a RUU, or flash a stock Rogers recovery.
The RUU might run if the aboot version has not changed since 1.32, but it's a risk. If it did not, you'd be stuck until there is a 2.11 Rogers RUU, if ever.
@iElvis , good looking out, if someone is s-on do they have to re lock the boot in order to flash RUU? I thought I saw somewhere you could could still flash via download being s-on.
@korbs710 hopefully you will get it all squared away. If you do I'd also recommend getting s-off via sunshine. It's totally worth the 25 bucks.
iElvis said:
12.0 is based on 2.10.401. It's possible there is a conflict with the 2.11 Rogers firmware, though I have not seen anyone else post about this.
On the RUU, did you ever tick the "Allow OEM Unlocking" setting in Developer Options since you upgraded to 2.x? If you did not, you cannot relock in your current state because you won't be able to boot up (because of your custom recovery), and won't be able to unlock again, even through HTCdev, because this setting will block it. You would be stuck in bootloader until you could run a RUU, or flash a stock Rogers recovery.
The RUU might run if the aboot version has not changed since 1.32, but it's a risk. If it did not, you'd be stuck until there is a 2.11 Rogers RUU, if ever.
Click to expand...
Click to collapse
No, I did not select Allow OEM Unlocking. So am I screwed then? I am trying to flash Maximus 6.0 but if it doesn't work I don't want to fully lock the device by trying the RUU.
BUBBA DUB'S said:
@iElvis , good looking out, if someone is s-on do they have to re lock the boot in order to flash RUU? I thought I saw somewhere you could could still flash via download being s-on.
@korbs710 hopefully you will get it all squared away. If you do I'd also recommend getting s-off via sunshine. It's totally worth the 25 bucks.
Click to expand...
Click to collapse
Ya I was going to gladly pay the 25 bucks if it meant being able to use my phone and supporting the devs is good.
Related
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
blankfile99 said:
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
Click to expand...
Click to collapse
you installed an OTA?
I'm using a Stock from a recovery Nandroid, not mine but the same CID 044... I guess I shold go back to RUU...but I've tried without any success
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
blankfile99 said:
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
Click to expand...
Click to collapse
you are on JB now and you can't run ICS RUUs, you can't downgrade...
matt95 said:
you are on JB now and you can't run ICS RUUs, you can't downgrade...
Click to expand...
Click to collapse
I'm not...I'm on 2.17 yet...JB update does not install...that's the main problem
and I have noticed that NO MATTER I CHANGE...IT WONT CHANGE THIS VERSION... OMG
tks man!
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Sentinel196 said:
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Click to expand...
Click to collapse
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Also, this may sound silly but did you reflash stock RECOVERY?
blankfile99 said:
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Click to expand...
Click to collapse
No worries, let us know how you go, and don't forget the Thanks button.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Well I am currently running Team Venom's Viper but I have HBOOT 1.31. My device's CID is HTC_J15.
I have checked the list of RUUs but unfortunately all of them are older than the version I need, which has to be 3+.
Does anybody know if there's an RUU available for my device? It is an ubranded WWE version, 401 if I remember correctly.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
I'm using the same as the NANDROID, taken from it...right?
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
That's all I need... I'll give my feedback later.
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
In my experience the 2.17.707.xx RUU Asia WWE does not work properly. It does its thing installing everything, relocks the bootloader but somehow it does not reflash the recovery. After 4 hours trying everything under the sun, I gave up and looked for a nandroid of 2.17 for CID_044 and restored from that, reflashed stock recovery and went to town with the OTA.
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Refer custom to stock thread posted earlier. Go through step by step procedure. It will help u to be on stock Rom. After that flash any Rom suitable to your CID only
http://forum.xda-developers.com/showthread.php?t=1859714
Hit Thanks if u like.
Sent from my HTC One X using xda app-developers app
Got It guys!!
What I did... NOTHING else...
Only Reboot the phone...wait to initialize completely, then reboot again, when came a little update about 1.25mb...installed and reboot...after that...JB update installed correctly.
If someone else needs...Someone like me who relocked the phone waiting for JB and Has problems
1. Unlock Phone
2. fastboot flash recovery recovery.img (from nandroid 2.17)
3. fastboot flash boot boot.img (from nandroid 2.17)
4. fastboot erase cache
5. restart bootloader (I like to do this way)
6. Install RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed on windows
7. Wait to boot completely, then restart phone.
8. Update Software ...a little update came before JB. (about 1.25mb)
9 Reboot phone.
10. Update Software... finally to JB.
Thanks guys!
Sentinel196 said:
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Click to expand...
Click to collapse
The RUU ran with no problem, and it relocked my bootloader, but it still did not receive any OTAs. So I had no choice but to do a nandroid restore instead (recommended anyway )
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'
Also, maybe try flashing the stock kernel as well?
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.
BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.
mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.
BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.
Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours
You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.
I originally had a stock sense M8 (bought it first day) but since October, I changed my phone to GPE (GPE Firmware and everything) and have been using 5.0 eversince using SkyDragon rom. Ran into issues a few weeks ago, and i've been waiting hard to go back to sense and use the newer 5.0 sense version.
However, today I ran into multiple issues, I thought installing the latest Sense Lollipop firmware and installing the latest ARHD 5.0 rom would do the trick, sadly that did not work.
I flashed the latest sense firmware and the ROM only for it to boot saying my Data is corrupt and i have to reset my phone, i say okay(was going to do that anyway) but then I access my recovery (TWRP) and my Internal storage/Cache/Data will not mount. I tried going back to GPE (atleast so my phone would work) but I cant do that either because even with the GPE firmware, the data partition wont mount and my internal storage shows 0 MB in TWRP, now im just stick in a bootloop/bricked device for hours. Any help would really be appreciated...thanks a lot.
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
redpoint73 said:
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
Click to expand...
Click to collapse
Thanks for your reply, to get this clear:
I should flash the Dev Edition RUU from (http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777) (3.28.1540.5) and then update the firmware to 4.16.1540.8 by just flashing that separate zip. However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery(Im terribly sorry if this sounds dumb, but my phone is soft bricked and I really need to get everything right this time), Is that the case if I flash the dev edition RUU? Thanks again.
Austin3161337 said:
However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery
Click to expand...
Click to collapse
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
redpoint73 said:
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
Click to expand...
Click to collapse
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all, is there anyway I can install the RUU by not really needing to connect the phone to the computer? (Put the file in the external SD and install it via the bootloader maybe?) Any tips on that? Thanks
Austin3161337 said:
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all
Click to expand...
Click to collapse
The phone doesn't need to boot into OS to run the RUU. It just needs to be able to get into bootloader/fastboot mode, which it can if the screen comes on.
If the device doesn't show on your PC, its a different issue. USB connectivity issue is almost always a driver issue. Install HTC Sync and HTC drivers, if you haven't already. Or uninstall and install them again.
I have a similiar issue. I had a tombile ruu.zip that a flashed as a 0P6Bimg.zip a kitkiat sense version for tmobile. Everything is cool and it runs fine. When I change cid and mid then flashed the sense lollipop firmware I lost my internal memory and twrp read storage as 0mb.
So idk
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Austin3161337 said:
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Click to expand...
Click to collapse
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
redpoint73 said:
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
Click to expand...
Click to collapse
I already had HTC Sync installed, had to boot into Fastboot USB for the thing to get recognized.
Hi guys,
I have an HTC One M9 Dev Edition. It is rooted, bootloader unlocked (since dev ed) and s-on. I had 2.8.617.4. I have been getting notifications to update it to 2.11.xxx.x, but since I was rooted, I couldn't update. So I thought of reverting back to stock to get the OTA. I booted to recovery (TWRP 2.8.7.0), tried restoring to the nandroid system that I had a backup of. That failed, with system is read only error or similar error message. So I followed step 5 from this guide - http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354.
After finishing the steps, my phone is now stuck on the htc logo. I'm not sure what is wrong. I can boot into recovery. One thing I notice is when I boot to download mode, I still see the OS as 2.8.617.4. I tried flashing system again, I still see the same thing and the same problem. I need your help fixing this. Thanks.
Step 5 in that guide says "Coming Soon"?
Are you on stock recovery or twrp?
I sincerely hope you did not lock your bootloader without ticking "allow oem unlock" in developer settings.
iElvis said:
Step 5 in that guide says "Coming Soon"?
Are you on stock recovery or twrp?
I sincerely hope you did not lock your bootloader without ticking "allow oem unlock" in developer settings.
Click to expand...
Click to collapse
Oh, I'm sorry, I meant Extra Section after step 5. No, I didn't lock my bootloader. I'm on dev edition, so my bootloader was unlocked right from the beginning.
I am on stock recovery. But I can flash twrp. My download mode is working, and I am able to flash different images, so I don't think my phone is bricked or anything.
At this point, I just need to get my phone back to a working condition. I'm sure someone can tell me how to do that.
Edit: Can it be because I tried to flash an older firmware (1.32.617.3) than what I currently have (2.8.617.4)?
slvrhwk said:
Edit: Can it be because I tried to flash an older firmware (1.32.617.3) than what I currently have (2.8.617.4)?
Click to expand...
Click to collapse
Good, don't relock.
That is almost certainly your problem. You just need to get back to current stock to take the ota. That thread is out of date IMO. You should look at one of the other back to stock threads, though ignore statements about relocking.
iElvis said:
Good, don't relock.
That is almost certainly your problem. You just need to get back to current stock to take the ota. That thread is out of date IMO. You should look at one of the other back to stock threads, though ignore statements about relocking.
Click to expand...
Click to collapse
I downloaded a system image of the current version of OS I am at. Do you think flashing that will work?
You probably have an bootloop because of the kernel.You are S-ON user so you probably have to flash the right (stock) kernel for the untouched system.img you have flashed.
If you try to make a wipe to data partition (even better a factory restore) could also help you but you are going to lose all your data.
If you want to flash a stock kernel (boot.img) just extract it from the same RUU you extracted system.img .
In order to flash it give the command
Code:
fastboot flash boot boot.img
After that give the command
Code:
fastboot getvar all
and copy-paste everything here (except your IMEI number).
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?
10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information
Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.