Related
Update: Well, I took the plunge on my own, and everything worked fine. Flashed firmware.zip, went to stock recovery and flashed OTA, and voila, all good.
So I've bought an HTC device for the first time. I did S-Off and unlocked bootloader and rooted as well. Now, there's an OTA available (I have the Asia_India variant), and I wanted to ask just how would I go about updating.
Here's what I've surmised till now:
1. Revert changes to system partition or it will fail to update (I moved some system APKs, but I saved them for such a scenario.)
2. Flash Firmware.zip to get stock recovery back.
3. Install OTA normally from the notification.
However, I'm still not sure what else I'd need to do (unroot, using the option in SuperSU?), so was wondering if someone could help me out. I've made backups in Philz and TWRP recovery both just to be sure.
P.S.: I extracted the firmware.zip file from the OTA, and tried to open it, but it doesn't open in apps like WinRAR. Is that normal, with the file only flashable via fastboot?
Personally, I'd say remove root just incase it stops the OTA but others will say it doesn't matter so long as the rest of the system is 100% stock as HTC intended it
For OTA updates after having a custom recovery, just flash your ROM stock recovery (search XDA all are available) then run OTA as you normally would and then flash your custom recovery again (if you like to get root again). However personally I would not do this with S-ON device, probably it's better if you're S-OFF while doing this to avoid any problem.
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Black Antitoon said:
I am also interested in this. What would be the risk if I do this with S-ON? Assume I flash the wrong stock recovery or do some other mistake, won't I still be able to flash my custom recovery back from fastboot and get everything back up and running?
Thanks to whom will answer. :good:
Click to expand...
Click to collapse
So long as the phone still boots to fastboot, yes (although unlocking the boot loader will delete any backups so make sure you backup the backup to your PC before doing anything else!)
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Black Antitoon said:
Thank you for your answer. As far as you know, being S-ON, is there really any kind of mistake one can do to brick the phone so that it doesn't even boot to fastboot?
Also, if my bootloader is already unlocked, no data wipe is going to happen again flashing a firmware/OTA in any predictable case, right?
Once again, thank you or anybody else who knows the answer.
By the way, are there any FAQs answering these questions? There are some FAQs here and there, but none seems to be very clear on these matters.
Click to expand...
Click to collapse
If you're S-ON there's not a lot you can do to brick the phone. You could wipe the ROM and have it not boot but you should always be able to get back to fastboot. This is where S-OFF is only handy to have if RUUs are about (it's the ONLY reason I am S-OFF, it's purely for a 'going back to stock' standpoint)
Yes, if the bootloader is already unlocked then you're good to go
Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
mcgrathpatj said:
Listen guys, sorry I've screwed this up so badly. I got a developer edition from swappa, and it came rooted with the stock sense ui. It was rooted, twrp installed. S-on, NOT, s-off was enabled.
I switched to gpe edition seamlessly through twrp. Now, looking to go back to stock sense ui and cannot.
Here's what I've done attempting to go back.
Attempted RUU for developer edition software. No luck because of error in software, error 155.
Tried to flash the RUU zip and that too errored out on me.
I then figured it was because of S-on, so tried to figure that out... Unsuccessfully.
Then thought I needed stock recovery, flashed that with error and now stuck with no recovery at all. Fastboot flash recovery recovery. IMG didn't work. Yeah, so no recovery.
Then I thought RUU wouldn't work because I'm unlocked bootloader. So, I locked the boot loader via fastboot OEM lock.... Probably not good
Fastboot menu days tampered, relocked.
Oh, Wi-Fi doesn't work either.... I forgot to mention that before I attempted to flash a stock sense ROM with no root.
Sow now what? Any advice?
Click to expand...
Click to collapse
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
xunholyx said:
The command is fastbooot flash recovery.img. No caps on the img and no space after the period, if that helps. Plus recovery only once, not twice.
You are placing the recovery.img into your fastboot folder, correct?
EDIT: fastboot oem unlock to unlock your bootloader again.
Click to expand...
Click to collapse
It's fastboot flash recovery recovery.img
The first recovery tells the device the location to which you want to flash it, in this case "recovery" for the recovery partition and the second one is the file you wish to flash in this case "recovery.img".
---------- Post added at 07:26 PM ---------- Previous post was at 07:04 PM ----------
mcgrathpatj said:
fastboot flash recovery xxxxxxx.img is the command i used. probably looked conufsing as i didn't use a proper variable for the image file but rather recovery.img
Click to expand...
Click to collapse
Do you know what software version you were on?
Just try the Developer Edition RUU again. If you're S-ON which you are, then bootloader needs to be relocked. I can't think of a reason why it shouldn't work, even if recovery is gone it completely returns device to stock(Including recovery).
You don't have to do the CID/MID part seeing as you're S-ON and you need S-OFF to do that. I don't think you used the converted GPE but instead a GPE ROM
I donwloaded the RUU for the Develoer Edition and it errored out at 155. I must have tried this 5-6 times.
I think I finally figured this out, so it may be useful for someone else. Who knows.
1) I downloaded another users NANDROID backup from the Dev Edition from this thread: http://forum.xda-developers.com/showthread.php?t=2701376
2) I flashed TWRP, restored the NANDROID from the above thread using TWRP.
3) Then, I flashed the original STOCK corresponding recovery from the same thread.
4) I was able to reboot and wifi FINALLY worked properly on a sense rom. I downloaded the OTA and it updated successfully, upon reboot through, wifi was broken again.
5) Re-locked the bootloader via fastboot oem lock, then performed the RUU for the Dev Edition from this thread here: http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
The RUU just completed successfully, so I think I'm out of the woods. But man oh man that was painful.
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735
I cant do that because i am not s-off
marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result
marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then
I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse
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.
I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...
arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.
Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?
arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.
Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.
Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....
arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.
iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?
arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.
iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.