Related
Hi Guys
I have a uk HTC One X which was originally on the 02 network. I have been flashing custom roms and now want to revert back to stock but cant seem to find the proper RUU....please help!!
3.14.206.27
Many thanks in advance.
http://forum.xda-developers.com/showthread.php?t=1975140
Check here !
Thats great thank you...do I need a boot image and recovery as well or will they come with the rom?
robs1971 said:
Thats great thank you...do I need a boot image and recovery as well or will they come with the rom?
Click to expand...
Click to collapse
Boot.img and recovery from the nand, flash them both.....make a full wipe then restore the nand. Then flash this stock HTC recovery and perform ota
https://www.dropbox.com/s/q3wiubr92cbkrid/stock recovery 2.17.img
Mr Hofs said:
Boot.img and recovery from the nand, flash them both.....make a full wipe then restore the nand. Then flash this stock HTC recovery and perform ota
https://www.dropbox.com/s/q3wiubr92cbkrid/stock recovery 2.17.img
Click to expand...
Click to collapse
Would there be a detailed set of instructions I could follow or a guide you can recommend?
robs1971 said:
Would there be a detailed set of instructions I could follow or a guide you can recommend?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=33728099&postcount=1
I tried a few guides on this, my advice would be that you take the utmost care when attempting this, I almost blew it and couldn't install any rom until I tried viperx
Sent from my HTC One X using Tapatalk
karluag said:
http://forum.xda-developers.com/showpost.php?p=33728099&postcount=1
Click to expand...
Click to collapse
Just got round to doing this now and it worked perfectly thanks again for your help
Right guys I'm in trouble again So after returning to stock as per above my phone wanted to update but every time it tried it just rebooted into the boot loader. So....I relocked the boot loader thinking this would cure the problem...I was wrong. The boot loader is now relocked but the phone wont boot the rom it just back into the locked boot loader...please help.
Thanks in advance.
Hi Everyone,
As mentioned in the title, its a very simple yet important question.
Will rooting my international and unlocked HTC One M8 prevent me from receiving OTA updates on stock rom?
Thanks
mahdibassam said:
Hi Everyone,
As mentioned in the title, its a very simple yet important question.
Will rooting my international and unlocked HTC One M8 prevent me from receiving OTA updates on stock rom?
Thanks
Click to expand...
Click to collapse
You will receive OTA updates so long as you are on the stock rom with stock recovery (with stock CID or S-OFF) though I recommend having S-OFF if you intend to do so as an extra precaution.
exad said:
You will receive OTA updates so long as you are on the stock rom with stock recovery.
Click to expand...
Click to collapse
And as easy as that this thread is closed
Thank you
mahdibassam said:
And as easy as that this thread is closed
Thank you
Click to expand...
Click to collapse
Be sure to check my edit. HTC OTA/RUU's have bricked phones with a modified CID and S-ON on previous phone(s) so I recommend having S-OFF just in case.
You might lose some standard apps, but since they are on the data partition, which unlocking wipes, it shouldn't cause a problem.
exad said:
You will receive OTA updates so long as you are on the stock rom with stock recovery (with stock CID or S-OFF) though I recommend having S-OFF if you intend to do so as an extra precaution.
Click to expand...
Click to collapse
Ok I'm on the TWRP recovery, how do I restore the phone back to stock recovery so I can do the Verizon OTA update?
BTW its a Verizon M8
I have been searching for this but haven't found anything about it.
Thanks
fastboot flash recovery stock_recovery.zip
Make sure you get the correct recovery, Verizon versions are odd, aren't they?
how do we check our cid?
BenPope said:
fastboot flash recovery stock_recovery.zip
Make sure you get the correct recovery, Verizon versions are odd, aren't they?
Click to expand...
Click to collapse
Recoveries are flashed in fastboot as images not zips.
ashyx said:
Recoveries are flashed in fastboot as images not zips.
Click to expand...
Click to collapse
Mea Culpa
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
yasha.sinitski said:
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
Click to expand...
Click to collapse
The Bootloader 3.18. tells you, you have 2.x firmware
So what is stopping me from flashing new firmware each time?
yasha.sinitski said:
So what is stopping me from flashing new firmware each time?
Click to expand...
Click to collapse
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
xunholyx said:
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
Click to expand...
Click to collapse
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
yasha.sinitski said:
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
Click to expand...
Click to collapse
It might be because you have a modified /system partition. Do you use Xposed?
xunholyx said:
It might be because you have a modified /system partition. Do you use Xposed?
Click to expand...
Click to collapse
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
yasha.sinitski said:
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
Click to expand...
Click to collapse
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
EDIT: I'm mistaken here. You need them unzipped. PM sent.
For others with the same issue of returning to Canadian stock, go to this thread for links and a guide on how to do so.
xunholyx said:
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
Click to expand...
Click to collapse
Are you going to post links? No matter what you do, I cant thank you enough for your help.
yasha.sinitski said:
Are you going to post links? No matter what you do, I cant thank you enough for your help.
Click to expand...
Click to collapse
Whoops!
Here ya go.
xunholyx said:
Whoops!
Here ya go.
Click to expand...
Click to collapse
Doing all that right now. I'll update how it goes.
yasha.sinitski said:
Doing all that right now. I'll update how it goes.
Click to expand...
Click to collapse
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Otherwise you brick your phone.
That the firmware number is not showing is not critical i think. Its a symtom of some roms.
I flashed the newest firmware to my m7, number was showing. Then i flash Viper 7.0.1 and after that, my number is hidden.
But everything works, so i think its not critical.
Roma80 said:
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Click to expand...
Click to collapse
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
BerndM14 said:
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
Click to expand...
Click to collapse
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Roma80 said:
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Click to expand...
Click to collapse
Yeah, Mike's guide has some good info. A lot of misinformation out there about some stuff.
He also has an excellent blog with plenty of info/resources if you're bored and what to read up on some stuff. Great site.
Android Revolution HD :good:
Hi everyone ,
Here is my problem, I bought a french htc one m8 with orange carrier, I unlocked my bootloader and installed phil's touch recovery and then I flashed skydragon rom 4.4.2 with htc sense 6 but now I would like to flash the last skydragon lollipop but here's my problem , I can't go s-off with this rom so I can't update my firmware or change my CID, so I can't install lollipop rom without wifi's problem. I would like to know how can I do to update my firmware to 4.4.4 cause I tried to s-off with firewater but doesn't work too.
Anyone have a solution would be a god to me ^^
Thanks in advance.
blop135 said:
Hi everyone ,
Here is my problem, I bought a french htc one m8 with orange carrier, I unlocked my bootloader and installed phil's touch recovery and then I flashed skydragon rom 4.4.2 with htc sense 6 but now I would like to flash the last skydragon lollipop but here's my problem , I can't go s-off with this rom so I can't update my firmware or change my CID, so I can't install lollipop rom without wifi's problem. I would like to know how can I do to update my firmware to 4.4.4 cause I tried to s-off with firewater but doesn't work too.
Anyone have a solution would be a god to me ^^
Thanks in advance.
Click to expand...
Click to collapse
Firewater doesn't work anymore. HTC patched the exploit.
You'll have to use SunShine S-Off. It costs $25, but is guaranteed to work or you don't pay.
Having S-Off is totally worth $25 IMO.
Here's a link to their website.
xunholyx said:
Firewater doesn't work anymore. HTC patched the exploit.
You'll have to use SunShine S-Off. It costs $25, but is guaranteed to work or you don't pay.
Having S-Off is totally worth $25 IMO.
Here's a link to their website.
Click to expand...
Click to collapse
I tried but it didn't work , it told me I've got to be on a stock rom :/
blop135 said:
I tried but it didn't work , it told me I've got to be on a stock rom :/
Click to expand...
Click to collapse
Go to this thread. It has a collection of stock backups you can falsh to get back your stock ROM.
It also has a collection of stock recoveries to flash with ADB if you need that.
All the instructions are there.
xunholyx said:
Go to this thread. It has a collection of stock backups you can falsh to get back your stock ROM.
It also has a collection of stock recoveries to flash with ADB if you need that.
All the instructions are there.
Click to expand...
Click to collapse
OK thanks a lot , the number before every rom is my firmware right? So I've got to download the one with my number on it ?
blop135 said:
OK thanks a lot , the number before every rom is my firmware right? So I've got to download the one with my number on it ?
Click to expand...
Click to collapse
Firmware is something separate. That link will get you back to stock ROM. Then use Sunshine to s off. After that, you can update your firmware.
xunholyx said:
Firmware is something separate. That link will get you back to stock ROM. Then use Sunshine to s off. After that, you can update your firmware.
Click to expand...
Click to collapse
Ok I'll try this but I need to find the good stock recovery ? Sorry for my noob questions ^^
blop135 said:
Ok I'll try this but I need to find the good stock recovery ? Sorry for my noob questions ^^
Click to expand...
Click to collapse
The stock recoveries or in that link too. I'm not sure if you need them for sunshine though. Try with custom recovery, if that doesn't work, get a stock recovery.
Or get both ROM and recovery stock, then reflash a custom recovery and ROM.
If you get both to stock, you shouldn't have any issues.
xunholyx said:
Firewater doesn't work anymore. HTC patched the exploit.
You'll have to use SunShine S-Off. It costs $25, but is guaranteed to work or you don't pay.
Having S-Off is totally worth $25 IMO.
Here's a link to their website.
Click to expand...
Click to collapse
How did HTC patch the exploit?
xunholyx said:
The stock recoveries or in that link too. I'm not sure if you need them for sunshine though. Try with custom recovery, if that doesn't work, get a stock recovery.
Or get both ROM and recovery stock, then reflash a custom recovery and ROM.
If you get both to stock, you shouldn't have any issues.
Click to expand...
Click to collapse
OK I'll try this, Thanks you very much
passion4tech said:
How did HTC patch the exploit?
Click to expand...
Click to collapse
Firmware updates. If you have one fresh out of the box, Firewater would probably still work. And still does for some.
xunholyx said:
The stock recoveries or in that link too. I'm not sure if you need them for sunshine though. Try with custom recovery, if that doesn't work, get a stock recovery.
Or get both ROM and recovery stock, then reflash a custom recovery and ROM.
If you get both to stock, you shouldn't have any issues.
Click to expand...
Click to collapse
Ok so now when I try to flash the offical carrier rom with phil's touch recovery , there is an android on the back with a red triangle and it says installation aborted
blop135 said:
Ok so now when I try to flash the offical carrier rom with phil's touch recovery , there is an android on the back with a red triangle and it says installation aborted
Click to expand...
Click to collapse
First, I misunderstood your earlier question. Yes the number in front of the backups are for firmware.
To help you more, I'll need some information. Hook up your phone to your computer and start ADB. Then issue these commands:
adb reboot fastboot (wait till your phone boots into fastboot)
fastboot getvar all
Then post what the readout says here, but edit out your serial number (serialno) and IMEI for your own safety.
Then I'll be able to give you a little more guidance.
xunholyx said:
First, I misunderstood your earlier question. Yes the number in front of the backups are for firmware.
To help you more, I'll need some information. Hook up your phone to your computer and start ADB. Then issue these commands:
adb reboot fastboot (wait till your phone boots into fastboot)
fastboot getvar all
Then post what the readout says here, but edit out your serial number (serialno) and IMEI for your own safety.
Then I'll be able to give you a little more guidance.
Click to expand...
Click to collapse
Here it is
http://imageshack.com/a/img537/3226/6mu7TC.png
blop135 said:
Here it is
http://imageshack.com/a/img537/3226/6mu7TC.png
Click to expand...
Click to collapse
Your CID is ORANG202 and your firmware is 1.54.73.5, so you will need the backup that corresponds with that.
The backup available was made with TWRP recovery. So you'll need that. (In my opinion, TWRP is a better recovery, less issues)
You could go to their website to download it and get instructions on how to flash it, but there is a much easier way.
Go to the Play Store and install an app called TWRP Manager. Hit the three line menu thingy on the top left, and pick "Install TWRP".
After that go back to the stock backup thread and flash the backup that matches your CID and firmware.
xunholyx said:
Your CID is ORANG202 and your firmware is 1.54.73.5, so you will need the backup that corresponds with that.
The backup available was made with TWRP recovery. So you'll need that. (In my opinion, TWRP is a better recovery, less issues)
You could go to their website to download it and get instructions on how to flash it, but there is a much easier way.
Go to the Play Store and install an app called TWRP Manager. Hit the three line menu thingy on the top left, and pick "Install TWRP".
After that go back to the stock backup thread and flash the backup that matches your CID and firmware.
Click to expand...
Click to collapse
Ok thanks I'll try that
xunholyx said:
Your CID is ORANG202 and your firmware is 1.54.73.5, so you will need the backup that corresponds with that.
The backup available was made with TWRP recovery. So you'll need that. (In my opinion, TWRP is a better recovery, less issues)
You could go to their website to download it and get instructions on how to flash it, but there is a much easier way.
Go to the Play Store and install an app called TWRP Manager. Hit the three line menu thingy on the top left, and pick "Install TWRP".
After that go back to the stock backup thread and flash the backup that matches your CID and firmware.
Click to expand...
Click to collapse
Okay so I could finally go s-off by flashing an 4.4.3 android revolution , can you tell me how I should do to flash this rom with wi-fi working ? :
http://forum.xda-developers.com/showthread.php?t=2706391
You would be the best
Thanks a lot
xunholyx said:
Firmware updates. If you have one fresh out of the box, Firewater would probably still work. And still does for some.
Click to expand...
Click to collapse
What firmware version works best with firewater? My firmware is 1.54.651.10
blop135 said:
Okay so I could finally go s-off by flashing an 4.4.3 android revolution , can you tell me how I should do to flash this rom with wi-fi working ? :
http://forum.xda-developers.com/showthread.php?t=2706391
You would be the best
Thanks a lot
Click to expand...
Click to collapse
My friend has made a comprehensive guide on firmware and firmware flashing, complete with downloads. Make sure to read the whole opening post so you understand everything. It looks like it might be hard because of his full explanation of the whole process, but it's actually very easy. And very informative.
xunholyx said:
My friend has made a comprehensive guide on firmware and firmware flashing, complete with downloads. Make sure to read the whole opening post so you understand everything. It looks like it might be hard because of his full explanation of the whole process, but it's actually very easy. And very informative.
Click to expand...
Click to collapse
Ok but I'm french so I'm not that good in english but I will try anyway Thanks
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.