Related
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 would like to root my HTC One M9 without installing TWRP or another custom recovery so that I can easily unroot and then take OTA updates. I have a developer M9 so my bootloader is already unlocked. I will eventually flash custom ROMs but at the moment, the stock firmware with Sense 7 is more than sufficient for me. Can anyone shed some light? I did find this http://www.how-to-root.club/2015/03/htc-one-m9-6891.html but I'm not sure how reliable it is since there's only a few comments.
theloneranger08 said:
I would like to root my HTC One M9 without installing TWRP or another custom recovery so that I can easily unroot and then take OTA updates. I have a developer M9 so my bootloader is already unlocked. I will eventually flash custom ROMs but at the moment, the stock firmware with Sense 7 is more than sufficient for me. Can anyone shed some light? I did find this http://www.how-to-root.club/2015/03/htc-one-m9-6891.html but I'm not sure how reliable it is since there's only a few comments.
Click to expand...
Click to collapse
"I could be wrong here and let me know if I am" it doesn't work that way with the m9. That site is bogus anyways, could you not tell by the video? Anyhow, even if you where to root it, there is no way to "simply" unroot it and take ota. There is new security on the m9 dealing with updates. Ota will not work if your software is or has been modified in any way, or if you have super cid. The common way for people to get OTA with the m9 is flash twrp, make a backup BEFORE rooting, flash newest supersu beta inside twrp, profit. When ota comes, go back to twrp, restore non rooted backup, flash stock recovery, take ota. IMO this is all a waste of time with an htc, just bite the bullet and spend $25 on soff and you don't have to worry about ota, you can flash firmware all day long before htc even releases it. Just flash a stock rooted rom like maximus if you don't want a lot of tweaks.
Your boot loader will say modified after flashing twrp, and will still say modified after restoring back to your stock backup. The "modified" boot loader does not affect ota, but if it annoys you like it does me, the only way to get rid of it at this time is to have soff and flash stock RUU in exe or sdcard mode. fastboot oem rebootRUU will not remove boot loader modified
edit.. there is now a way to remove modified status without flashing rom
an0ther said:
"I could be wrong here and let me know if I am" it doesn't work that way with the m9. That site is bogus anyways, could you not tell by the video? Anyhow, even if you where to root it, there is no way to "simply" unroot it and take ota. There is new security on the m9 dealing with updates. Ota will not work if your software is or has been modified in any way, or if you have super cid. The common way for people to get OTA with the m9 is flash twrp, make a backup BEFORE rooting, flash newest supersu beta inside twrp, profit. When ota comes, go back to twrp, restore non rooted backup, flash stock recovery, take ota. IMO this is all a waste of time with an htc, just bite the bullet and spend $25 on soff and you don't have to worry about ota, you can flash firmware all day long before htc even releases it. Just flash a stock rooted rom like maximus if you don't want a lot of tweaks.
Your boot loader will say modified after flashing twrp, and will still say modified after restoring back to your stock backup. The "modified" boot loader does not affect ota, but if it annoys you like it does me, the only way to get rid of it at this time is to have soff and flash stock RUU in exe or sdcard mode. fastboot oem rebootRUU will not remove boot loader modified
edit.. there is now a way to remove modified status without flashing rom
Click to expand...
Click to collapse
Thanks for all of the info. I wish simply rooting your phone wasn't such a pain. I guess I'll just flash TWRP, make a backup of my phone, and then root it and then if I need to do an OTA I can just restore the backup and flash the stock recovery. I found this download site for the recovery. I'm assuming I'd pick developer and then recovery. Do I use the signed one? What happens if I flash the wrong recovery? https://www.androidfilehost.com/?w=files&flid=28830
Also, if I S OFF you said I can install OTA updates? So I can install them even if I have a custom recovery and root access?
theloneranger08 said:
Also, if I S OFF you said I can install OTA updates? So I can install them even if I have a custom recovery and root access?
Click to expand...
Click to collapse
Not ota, but you can flash firmware without doing anything. So you run a stockish rom like maximus and he releases his own OTA's, then you can flash official firmware to keep up with it, and if you get tired of that method, you can always ruu and go back to completely stock.
an0ther said:
Not ota, but you can flash firmware without doing anything. So you run a stockish rom like maximus and he releases his own OTA's, then you can flash official firmware to keep up with it, and if you get tired of that method, you can always ruu and go back to completely stock.
Click to expand...
Click to collapse
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
theloneranger08 said:
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
Click to expand...
Click to collapse
Correct. Roms do not upgrade firmware. In the future you will need to upgrade firmware when wifi/camera/touchscreen/etc improvements are implemented into firmware. Having soff, you can simply flash just the firmware and not worry about software. Without soff, you have to revert back to stock and take ota or use new firmware RUU. Soff is a must on HTC and is honestly the only reason I didn't buy an s6. Ive had the m7/m8/m9 and the flexibility of rooting and firmware etc is unlike any other.
an0ther said:
Correct. Roms do not upgrade firmware. In the future you will need to upgrade firmware when wifi/camera/touchscreen/etc improvements are implemented into firmware. Having soff, you can simply flash just the firmware and not worry about software. Without soff, you have to revert back to stock and take ota or use new firmware RUU. Soff is a must on HTC and is honestly the only reason I didn't buy an s6. Ive had the m7/m8/m9 and the flexibility of rooting and firmware etc is unlike any other.
Click to expand...
Click to collapse
Ok great and I can flash firmware regardless of what rom I'm running?
theloneranger08 said:
Ok great and I can flash firmware regardless of what rom I'm running?
Click to expand...
Click to collapse
Correct. It doesn't have to be a perfect match, just in the same base. Right now your current firmware is fine, but most people swap to the newest developer with no red text. If you are new to htc and flashing firmware read instructions carefully or ask me. You need super cid or matching cid to flash firmware that isn't supported by your carrier variant. Everyone has to learn and these phones are near impossible to hard brick as long as you can read. Never flash cdma firmware on gsm phone, never run ruu for your phone if MID doesn't match, never turn s-on back on, but if you have to make sure you are NOT super cid or have unsigned firmware "no red text firmware" Never ever ever unzip a signed firmware file and edit it and zip it back up to flash unless you decrypt it and know what you are doing. Get an 32 gig or less sd card. Feel free to ask me any questions.
an0ther said:
Correct. It doesn't have to be a perfect match, just in the same base. Right now your current firmware is fine, but most people swap to the newest developer with no red text. If you are new to htc and flashing firmware read instructions carefully or ask me. You need super cid or matching cid to flash firmware that isn't supported by your carrier variant. Everyone has to learn and these phones are near impossible to hard brick as long as you can read. Never flash cdma firmware on gsm phone, never run ruu for your phone if MID doesn't match, never turn s-on back on, but if you have to make sure you are NOT super cid or have unsigned firmware "no red text firmware" Never ever ever unzip a signed firmware file and edit it and zip it back up to flash unless you decrypt it and know what you are doing. Get an 32 gig or less sd card. Feel free to ask me any questions.
Click to expand...
Click to collapse
Awesome, thanks I really appreciate it. I'll definitely let you know if I have any questions.
theloneranger08 said:
So I bit the bullet and installed TWRP, did a Nandroid backup, and then rooted my phone. Now I'm trying to determine whether I want to S-Off my phone. I know that I'd need to RUU and return to stock to flash firmware if I'm S-On, but if I flash a rom that is continually updated, then will I miss any of the features of new firmware released by HTC? I guess my question is, if a dev. updates a rom to reflect the newest firmware from HTC, how does that actually work because from what I've read, it doesn't actually touch the firmware of the phone? So would there be things that HTC can improve that the rom cannot?
Click to expand...
Click to collapse
Check it out this http://www.bestandroidrootedapps.com/how-to-root-htc-one-m9-and-also-have-custom-recovery-installed-on-it/
Hi All,
I have a UK HTC One M8, rooted, S-off, and with ViperOne installed, an old version - 1.8.0
I have flashed a new firmware in order to update ViperOne, and I have lost root access. I used root checker app to verify.
I used this method to flash the firmware:http://forum.xda-developers.com/showthread.php?t=2696282
I obtained the firmware from here: http://android-revolution-hd.blogspot.co.uk/p/android-revolution-hd-mirror-site-var.html
I had changed the cid to supercid, as I am S-off, and i checked that the modelid was correct in "android-info.txt"
The flash went fine, no errors, phone turned on first time, but root access is lost.
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
I was wondering if somebody knowledgeable could reassure me that everything is fine, and perhaps point me to the most appropriate method for getting root access back. I am a little out of my depth here, I learned how to do most of this stuff a year ago when i first rooted, but I haven't been back to update since then, and have forgotten a lot of what I learned before.
Would appreciate any assistance you can offer
Cheers
Will
Willr01 said:
This thread I just found says that upgrading the firmware will always cause you to lose root. This is surprising as it wasn't mentioned in any of the guides I read to flashing firmware.
http://forum.xda-developers.com/showthread.php?t=2417442
Click to expand...
Click to collapse
Different device manufacturers do things in very different ways, so I wouldn't take that thread to mean anything, one way or another, regarding losing root when updating firmware. I also think in that thread, they may be talking about firmware = ROM (as opposed to something very different on HTC devices). In which case, yes, installing a stock ROM will in fact usually remove root on most Android devices.
In any case, see if you still have TWRP installed. That depends on whether the firmware package was modified or not to remove the stock recovery. If TWRP was replaced by stock recovery, simply install TWRP again using your method of choice (personally I prefer installing by fastboot). Then download the SuperSU zip to your phone from here and flash in TWRP.
In reality, I think you may not even have to download SuperSU. If you boot into TWRP and select reboot, I believe TWRP will automatically sense your ROM is not rooted, and ask you if you want it to do so. But I'm not 100% on that, and the SuperSU method is a sure thing.
Thanks a lot for your input. I don't have a recovery installed, so I have tried to flash twrp.
I tried flashing it twice, after reading it can be necessary to do that, and erasing the cache before attempting to boot to recovery. When I try and enter recovery, I get stuck on the startup htc screen with "Entering Recovery..." in pink.
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Thanks in advance
Willr01 said:
Snippets off other threads have suggested my hboot might not be compatible with the new version of twrp. Is it straightforward to update hboot?
Click to expand...
Click to collapse
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
redpoint73 said:
Updating your firmware updates the hboot. 3.19 is the current hboot, and you can check no the bootloader screen.
Make sure its a current version TWRP (2.8.7.0) and I think the opposite is also true (old versions of TWRP don't work with current hboot).
And to clarify, you want to fastboot erase cache, then flash TWRP; as this often clears up issues with TWRP not installing properly.
Click to expand...
Click to collapse
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Willr01 said:
So my hboot is 3.16, and the twrp was the latest version. I guess i need to find a more up to date firmware file. Any suggestions as to the best sources for firmware?
Click to expand...
Click to collapse
What exactly did you flash from the Android Revolution website (what you linked in the top post)?
That website has up-to-date firmware, but what you want is 4.xx version firmware, found under the "Firmware collection" link on that webpage.
Since your hboot number is 3.16, you either did not properly flash a firmware (flashed something else) or flashed a really old firmware (hboot 3.16 corresponds to firmware version 1.xx).
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
You have to be 100% stock to get OTAs successfully. Since you're s-off, just running an earlier RUU exe should do it, but you may need to relock.
Under no circumstances should you go back to s-on.
DroidShift79 said:
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
Click to expand...
Click to collapse
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
MAX 404 said:
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
DroidShift79 said:
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
Click to expand...
Click to collapse
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
MAX 404 said:
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
Click to expand...
Click to collapse
Thought of this,
just not sure if I need to relock bootloader to get official otas
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
THX kingvortex. I just do it and report back.
Thanks all of you.
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
kingvortex said:
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Well, what I did so far, was to use the 1.32.401.17 ruu.exe
Flash went fine, but no OTA did show up.
So I wanted to flash the 1.32.401.8 ruu zip.
But putting it on sdcard or using fastboot flash zip failed.
Wonder why!?
Later on I'll try Max 404 find.
MAX 404 said:
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Click to expand...
Click to collapse
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.