Hello guys,
I got a new ota update, 7.0 android but im root, bootloader unlocked and im S-ON.
Can i get the OTA without any trouble or i have to flash it from twrp? Will i lose my root access if i accept the update?
Thanks for your time
To accept the ota update your phone must have a stock system and the only way to get that is to flash the stock firmware then update via ota.
S-on/off and bootloader unlocked/locked/relocked "do not" affect firmware flash ability. "do not" change the status of these to flash a stock firmware.
Get the firmware you currently have as a zip file, rename it to 0PJAIMG.ZIP and copy it to the external sd card. Connect a charger and boot into download mode. You should see a prompt in yellow at the bottom of the screen "press vol up to flash".
When done it will auto boot to os. You can then download and flash the ota. When you have flashed the ota you will have to root again.
Sneakyghost's flashable firmware packs don't contain a system image. Therefore, flashing one won't restore the ability to install OTAs. He wrote an article that described the difference between the system/rom and the firmware of HTC devices, some years ago. Unfortunately, it was hosted on the Team venom Website and that site got shut down when the Team retired. Edit: I could find it on archive.org.
You need to either flash a RUU (which is not the same as a firmware pack) or restore an untouched TWRP backup. Instructions and downloads can be found in the ReadMe thread. Be aware that a RUU will delete all personal data/settings.
Sidenote: Sneakyghost's firmware packs require S-OFF since they are custom made and not signed by HTC. And even RUUs require S-OFF in case you want to downgrade your phone's firmware.
Sent from my Moto X Style using XDA Labs
Related
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
I have an HTC One M9 (Telus Canadian phone) Unlocked with S-OFF.
Rooted with SuperSU and TWRP v2.8.7.0.
I really wanna update my ROM to Android 6.0 but my current firmware version (which I believe is 3.10) is stopping me from doing so. I tried to upgrade my firmware by following the steps on HTC's website but it didn't work.
How do I go about upgrading my firmware?
Hello, You have to be stock to have OTA working
As you're S-off, best way is to flash a RUU.
After OTA you have to install Twrp and SuperSu again to be root...
You are s-off, you should be able to flash an unsigned zip and be done with it.
Sent from my HTC One M9 using Tapatalk
I'm a little bit confused about the steps I actually need to take. If I flash the right RUU, it will replace my Boot, ROM and Recovery? So the phone will be completely stock? If so, where do I find the right RUU for my phone?
Oh... I wasn't aware that I flash the firmware manually. But where do I find the firmware file? Would you be able to send me a link?
Hi. I'm now on unlocked htc 10 with s-on. How can I back to clean, stock, oryginal condition? I tried to flash stock via ruu.exe and adb but it is failed. Relocking bootloader nothing helped. I tried some things but i got lost in this many theards. I will be very grateful if somebody help me and show me instructions. Actually i'm on m firmware.
boot into fastboot & paste the command below
copy the results & post here (remove imei from the post)
PHP:
fastboot getvar all
As you mentioned flashing the leaked nougat ruu ill assume you're on 401.x FW with the lastest ruu being 1.90.401.5
1. install twrp, restored untouched system & boot image, flash stock recovery
2. s-off downgrade to 1.90.401.5 , relock bootloader & run ruu
i see you edited your post
1. Rename zip to 2PS6IMG.zip
2. Copy zip onto sd card
3. Boot into download mode (download mode should detect the 2PS6IMG.zip)
4. Press volup to flash
Also flashing this will wipe your data , and it may render your phone *impossible* to receive future ota updates as it's an unofficial release from htc.
For example: lets say htc released a new nougat ota which updates you phone to 2.3x.401.x , that ota may only update phones on FW 1.95.401.4 & not 2.28.401.9
You would still be able to flash a 2.3x.401.x or above ruu (if available) or you could s-off & downgrade to 1.95.401.4 then accept ota
Personally i wouldn't flash it as yet as the official OTA is only around the corner (HTC said Q4)
@Diz so the 2.28.x is for unofficial/developers? Can I do it on unlocked bootloader?
Ps. i want to do it without s-off
So I've been trying the past couple weeks to root and flash my M9 (AT&T) to no avail. I have ADB, fastboot, sdk and the htc drivers installed on my computer. Thing is, moonshine keeps giving me an error after checking for updates, sunshine is unable to gain temproot, adb won't flash twrp because I have s-on, RUU updates keep failing and I can't get OTA updates to install. I'm on android 5.0.2 with firmware version 1.32.502.9 and did the HTC DEV process to unlock the bootloader. Any help will be much appreciated.
re-lock your bootloader with "fastboot oem lock" then you can run RUU and update it to latest firmware.
After that write a message and I'll help you with root, twrp, etc..
Thanks for the response. I'll get on it sometime this evening. All I'm concerned about is getting twrp installed so I can use it to flash a custom rom with su already installed and all the bloat are removed.
Donnie267 said:
Thanks for the response. I'll get on it sometime this evening. All I'm concerned about is getting twrp installed so I can use it to flash a custom rom with su already installed and all the bloat are removed.
Click to expand...
Click to collapse
Yeah, but first you need to update the firmware to latest(nougat) because with 5.0.2 firmware you can flash only lollipop and maybe some marshmallow roms and I don't think you want an old rom.
Also you don't need S-OFF for root, twrp, custom roms, so don't buy it if you really don't need it.
That's the thing. Every time I've tried flashing twrp, adb spat an error saying that it couldn't because I have S-on.
Donnie267 said:
That's the thing. Every time I've tried flashing twrp, adb spat an error saying that it couldn't because I have S-on.
Click to expand...
Click to collapse
Hmm that's weird, maybe you did something wrong.
You need to boot in download mode(download not bootloader) and do this command "fastboot flash recovery path/to/recovery.img" but first you need unlocked bootloader with htcdev.
Two important information:
A) The bootloader doesn't need to be locked or relocked for flashing a RUU on the M9. (Due to FRP I actually highly discourage everyone from relocking if you tinkered with this phone and don't know whether the RUU you want to flash is actually flashable on your phone. In other words, everytime you haven't already flashed the RUU successfully on your phone, before.)
B) You can't flash Nougat RUUs on a M9 with a non-Nougat firmware due to the different encryption keys.
Please take a look at the ReadMe thread if you need/are interested in more details.
Edit: And yes, that error always appears if you try to flash TWRP while the phone is booted to the bootloader.
Sent from my HTC One M9 using XDA Labs
1: I did some poking around on other threads here and found that I need to go to marshmallow to be able to go to nougat. Only ruu I've been able to find is the Verizon version and I need the one for AT&T if any of you have a link to one.
2: all I need is to get twrp on my phone and I'll he gravy. If any of you know how or where to find the process of flashing twrp WITHOUT rooting. That would be great.
Have you read the ReadMe thread? It contains a huge collection of RUUs and instructions for flashing TWRP. BTW, rooting is never needed for flashing TWRP. It's the other way round. You need TWRP for being able to flash SuperSU or Magisk.
Sent from my HTC One M9 using XDA Labs
Of course I have. Every last one of them says to use adb to flash twrp which 100% of the time says it failed because I have S-on as stated in my original post.
As mentioned before, that error occurs if you booted your phone to the bootloader instead of the download mode. Follow the instructions in the ReadMe thread and flash TWRP while your phone is booted to the download mode.
Sent from my HTC One M9 using XDA Labs
Finally got twrp installed and flashed the rooted developer edition running lollipop. Problem now is when I try a ton running marshmallow or nougat, my phone boots directly to bootloader. Any ideas why?
Android M roms require firmware 3.x and Android N can be used on at least firmware 3.x but are recommended to be used on firmware 4.x.
If you use older firmware versions the roms won't boot as @lucyr03 explained in one of the first replies in this thread.
Sent from my HTC One M9 using XDA Labs
Right. Now, would I be able to just jump right to the latest firmware, or do incremental updates and where can I get the necessary files?
The files are in the ReadMe thread.
You can jump to the latest 3.x firmware via a RUU. Due to the new encryption keys you can't use 4.x RUUs, though. You'll need to update from 3.x to 4.x via the software update function of the phone settings. Be aware that AT&T only let's you download updates for their branded phones if you own an AT&T sim card.
Sent from my HTC One M9 using XDA Labs
I'm using rooted developer edition Ron and every time I try updating, I get a message saying that my phone has been modified and can't update and the only ruu files on the HTC site are for nougat.
You can't update that custom rom you're using because its rom base doesn't match your phone's firmware. That's why you face that error message.
As written before, read the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
I'm using rooted developer edition Ron and every time I try updating, I get a message saying that my phone has been modified and can't update and the only ruu files on the HTC site are for nougat.
Can you comment the link to the Readme?
ATT One M9. Currently on Version 3.38.502.31, S-ON, Rooted, TWRP. I'm trying to get it back to stock so it can accept the Nougat OTA. I read that I could just run the RRU from HTC to restore it. Finally had the time today to do it however I get a 132 signature error. I relocked the bootloader but still got the error. As I read up on it it turns out for some reason the encryption was changed between the 3.xx and 4.xx versions so the update won't work. I don't want to pay to get S-OFF so the only other option I can find is to get an older RRU for either my current version or the one after it (3.38.502.31 or 3.38.502.41) and then allow the phone to OTA. I can't find one. I can find the 3.38.502.41 .ZIP but from what I understand i NEED the .EXE version. Does anyone have one of these older .EXE RRU files or another method to get my phone to accept the Nougat OTA?
There is no difference between the *.zip and the *.exe. (Well, aside from the fancy installer that gets used by the *.exe. It's not needed, though.) Besides, re-locking isn't just unnecessary it's actually highly not recommended unless you have a working RUU at hand due to the FRP that Google introduced with android 5.1.
Where did you read that you need an *.exe and/or that you need to re-lock your phone?
Sent from my HTC One M9 using XDA Labs
I figured that I needed the .exe because if you try to flash an official update .zip but the phone system is modded it will fail. So you are telling me that I can flash the RRU .zip with TWRP and it will work?
Please take the time to carefully read the ReadMe thread. You're mixing up a lot of things.
OTAs fail if your phone is modified. RUUs don't check whether you tinkered with your phone. They simply overwrite everything. As said before, there's no real difference between a RUU.zip and a RUU.exe for the same firmware version. If one can be flashed then so can be the other.
And no, you can't flash a RUU.zip via TWRP. RUUs get made by HTC and TWRP is a custom made recovery. They're not compatible with each other. (In other words, you can't flash RUUs via TWRP.)
Sent from my HTC One M9 using XDA Labs
I recommend that you unlock your bootloader as there is no reason for it to be relocked. Especially if you plan on rooting it again.
For the zip method:
Find the FIRMWARE zip that matches your current version on the phone. x.xx.xxx.yy where yy can be any number, xx MUST MATCH.
Check the md5 matches before you mess with the firmware file.
Rename the firmware zip file to 0PJAIMG.ZIP and copy it to the external sd card.
Reboot phone to download mode and in yellow writing at the bottom of the screen it should say to press vol up to flash. Make sure the phone is plugged into a charger and press vol up.
That flashes it back to stock stock and wipes root priveliges, flashes a stock recovery, flashes a stock system.
Once back to stock you can accept the ota updates. Bootloader and s-on/s-off have no influence at all. As flippy states, if you leave it as relocked you may encounter issues with google's frp (factory reset protection).
shivadow said:
I recommend that you unlock your bootloader as there is no reason for it to be relocked. Especially if you plan on rooting it again.
For the zip method:
Find the FIRMWARE zip that matches your current version on the phone. x.xx.xxx.yy where yy can be any number, xx MUST MATCH.
Check the md5 matches before you mess with the firmware file.
Rename the firmware zip file to 0PJAIMG.ZIP and copy it to the external sd card.
Reboot phone to download mode and in yellow writing at the bottom of the screen it should say to press vol up to flash. Make sure the phone is plugged into a charger and press vol up.
That flashes it back to stock stock and wipes root priveliges, flashes a stock recovery, flashes a stock system.
Once back to stock you can accept the ota updates. Bootloader and s-on/s-off have no influence at all. As flippy states, if you leave it as relocked you may encounter issues with google's frp (factory reset protection).
Click to expand...
Click to collapse
A little late but I wanted to thank you for your advice, I tried it today and it worked perfectly.