Related
Phone replaced, came w/ 1.54 Bootloader & 2.24.401 OS-Version How restore Backups?
Hey,
I am pretty frustrated right now
I had to get my HTC One replaced and got a Version in return that obviously has the 1.54.0000 Bootloader and the OS-Version is 2.24.401.1.
For years I am using TitaniumBackup and regular nandroid backups as my backup routine.
That's what I did before I sent the phone in, due to an hardware issue.
I don't want to unlock using htcdev, I see no point.
An as I can tell right now there seems to be no option to unlock the bootloader, flash a custom recovery and root with one of the other methods, such as revone or moonshine.
Okay, I can probably wait a bit and hope for an Exploit...
But how can I restore the app data of my daily driver apps from either the TitaniumBackup or the nandroid, without root in the meantime.
To be honest...not having root is the worst.
Is there any option that I missed?
Thanks
You can root but you can't do s-off
Sent from my HTC One using xda app-developers app
I wouldn't care much about S-OFF (don't want to change my CID or anything), but with my bootloader locked, I can't flash a custom recovery and by that I can't flash root.
Well then it seems like there is indeed a point to unlocking the bootloader
You're only options are to wait or to use htcdev.
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3
Is there no option to temporarily root? (That I maybe lose after reboot?)
Just to at least restore backups of my daily driver apps?
There is indeed a way to unlock the bootloader and flash a custom recovery. Go look for the many toolkits in the htc one dev sections and you'll be able to do what you're looking for with not too much trouble.
Kraize said:
There is indeed a way to unlock the bootloader and flash a custom recovery. Go look for the many toolkits in the htc one dev sections and you'll be able to do what you're looking for with not too much trouble.
Click to expand...
Click to collapse
spaboleo said:
[...]
I don't want to unlock using htcdev, I see no point.
An as I can tell right now there seems to be no option to unlock the bootloader, flash a custom recovery and root with one of the other methods, such as revone or moonshine.
[...]
Click to expand...
Click to collapse
Well then, i'll have to agree with everyone else. You'll have to unlock the bootloader via htcdev in order to install a custom recovery. That should be point enough in order for you to do so if you would like a custom recovery. Not like there are any disadvantages to having S-OFF.
Kraize said:
Well then, i'll have to agree with everyone else. You'll have to unlock the bootloader via htcdev in order to install a custom recovery. That should be point enough in order for you to do so if you would like a custom recovery. Not like there are any disadvantages to having S-OFF.
Click to expand...
Click to collapse
*sigh...I guess it's late (Don't get me wrong...I totally appreciate that you take the time to help, but it's just slightly off topic :angel
I would do that without hesitation if I could, as described above
there is not yet an exploit (nothing else do revone and moonshine use) that allows to unlock the bootloader with HBOOT 1.54.0000, which came with the latest updated, which obviously no gets shipped with replacement devices as well...
So yeah...I am actually at this point where I decided to stock with the Stock-Sense Rom and just wait, but still I need some way to restore my apps. At least conversations, logs, stats etc. from certain ones from my previous backups.
But I couldn't find any option to root it temporarily.
Can't you downgrade using the same method done to go back to stock and then do s-off?
Kraize said:
Can't you downgrade using the same method done to go back to stock and then do s-off?
Click to expand...
Click to collapse
As far as I know I would need clockwork or twrp to flash any stock image.
Or do you know of any downgrade method?
Thanks :good:
spaboleo said:
As far as I know I would need clockwork or twrp to flash any stock image.
Or do you know of any downgrade method?
Thanks :good:
Click to expand...
Click to collapse
You can flash via fastboot?
Sent from my HTC One using Tapatalk 4
Do you mean the custom recovery? If so, then I can't, as this "modification" is blocked by the bootloader.
Or do you mean the stock image with another bootloader?
To be honest, I don't know. And couldn't find something about "downgrading" to HBOOT 1.44.000 :/
Fastboot can be accessed via computer and having your phone in bootloader mode and clicking fastboot. I'm thinking that installing a custom recovery would be blocked, but maybe you should be able to install another rom that has root? I'm just throwing ideas. I haven't encountered this problem. I do know that you can't s-off with 1.54 though.
Hehe yeah...it's blocked in fastboot
i've never heard of flashing roms via fastboot...doesn't it "only" have access to the bootloader and the recovery?
So I guess you'll need s-off to downgrade the hboot.
You need s-off to downgrade.
You need a custom recovery to root.
You need an unlocked bootloader to flash a custom recovery.
The ONLY way to unlock 1.54 is htcdev.
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3
Yes, thanks for the summary of what has been stated above.
---
Is there no way without root to restore backups of Apps, by restoring them from a TitaniumBackup or nandroid Backup?
I once used "AppExtractor", but it requires root as well.
spaboleo said:
Yes, thanks for the summary of what has been stated above.
---
Is there no way without root to restore backups of Apps, by restoring them from a TitaniumBackup or nandroid Backup?
I once used "AppExtractor", but it requires root as well.
Click to expand...
Click to collapse
I appreciate the sarcasm. And the answer is no, which is what I was trying to tell you. The apps require root because to do what you're trying to do you need root access. Nandroid backups are specific to custom recoveries, and even if you pulled the files from the nandroid, you couldn't push them to the rom because you'd need a root explorer.
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3
Okay...flashing recovery obviously is possible from fastboot.
http://forum.xda-developers.com/showpost.php?p=44623360&postcount=4716
By that:
--> Recovery --> Root with S-ON?
What are the potential risks or problems that one might run into using this method?
i will lose the stock recovery
if something goes wrong and i want to revert back to the stock image, flashing of the update.zip via fastboot to do so, will be blocked, due to S-ON (and of course the current version's image is not yet available)
hmmm....
Hi.im planning to buy htc one which i dont want to use with stock rom,so if i get the phone with hboot1,54 would i be able to root phone,install custom recovery and flash roms,kernels? Or i need s off for all this stuff? As i read someware on xda that both rooting methods for htc one are not working with a hboot 1.54 thanx in advance
vigorito said:
Hi.im planning to buy htc one which i dont want to use with stock rom,so if i get the phone with hboot1,54 would i be able to root phone,install custom recovery and flash roms,kernels? Or i need s off for all this stuff? As i read someware on xda that both rooting methods for htc one are not working with a hboot 1.54 thanx in advance
Click to expand...
Click to collapse
you can Root, install custom recovery and flash roms
S-Off means you can install RUU from different country, regardless of the Carrier and Region
you dont even need S-Off if you want to Root, Recovery, and flash ROMs
Aha, so 100% i can root phone with both metods methods? Revone and forgot the name of second one?
vigorito said:
Aha, so 100% i can root phone with both metods methods? Revone and forgot the name of second one?
Click to expand...
Click to collapse
Those are not rooting methods but s-off methods.
No root exploit is needed for this phone. Just unlock via htcdev, flash custom recovery, flash rooted rom.
Story:
So I have been using this device with call recording, because it's a feature I really wanted. That's the main reason I went with Android.
The feature always worked only 50%. My voice is loud and clear, other party is quite quiet.
It was worse in my previous One X, so no complaints here.
But, if I check a Samsung phone, or an LG, the recording is crystal clear over there. It works there, it's loud, it's perfect.
My big question here is:
- Should I root with sunshine? (with skvalex recorder -CAF + ALSA, it is said to be working.)
- Should I wait for L? Will it change anything? Anyone have a leaked image to test?
h8Aramex said:
My big question here is:
- Should I root with sunshine?
Click to expand...
Click to collapse
Sunshine is not needed to root your M7, its mainly a S-OFF exploit. All you need to do to root is to unlock your bootloader, flash TWRP and the latest supersu.
Don't think lollipop will change anything in the sound quality but if you want to give it a try, the latest MaximusHD rom is based on lollipop.
alray said:
...
Click to expand...
Click to collapse
All you need to do to root is to unlock your bootloader, flash TWRP and the latest supersu
Click to expand...
Click to collapse
Warranty is the only thing that concerns me. And the available root methods.
I had to return my One X several times, and people in the M7 forum complain about several issues plaguing the M7 as well.
Do you know a good reversible / simple root method?
(TWRP is the second thing, how am I supposed to revert it to stock state after flashing TWRP?
Do I have to flash back the original stock fw? And will the device forget about the root? - I read that HTC also have a "tampered with" warning message.)
And the phone is also "mission critical", so the smoothest way to root would be the best.
Don't think lollipop will change anything in the sound quality but if you want to give it a try, the latest MaximusHD rom is based on lollipop.
Click to expand...
Click to collapse
Yeah, I was hoping that users of MaximusHD will reply and tell me if it fixed it on their device.
I was thinking if the new API fixed recording - magically.
Ps.: Thanks for your quick reply!
h8Aramex said:
Warranty is the only thing that concerns me. And the available root methods.
Click to expand...
Click to collapse
Rooting the M7 is always done by unlocking the bootloader, flashing a custom recovery and then either flashing a pre-rooted rom or flashing supersu. SO I don't get what you mean by "root methods", there is only one method to root. For your warranty to be valid, your bootloader must be locked (not re-locked) and no "Tampered" flag showing. Removing the Tampered flag from the bootloader and setting it back to locked instead of re-locked require S-OFF. S-OFF is achieved with different exploits depending your bootloader version. You also need your software and firmware to be 100% stock for your warranty to be valid which might require to flash a RUU if any available for your version.
I had to return my One X several times, and people in the M7 forum complain about several issues plaguing the M7 as well.
Click to expand...
Click to collapse
I also had the One X (endeavor variant) before the M7 and believe me, you can't compare these 2 phones. The X was pure garbage compared to the M7. Don't know what issues you are talking about for the M7, the only common issue is the camera purple hue.
Do you know a good reversible / simple root method?
Click to expand...
Click to collapse
Like said there is 1 method to root --> Unlock BL, flash custom recovery ---> flash a rooted rom or flash supersu on your stock rom. Unrooting for warranty purpose will require S-OFF and possibly a RUU
alray said:
... Like said there is 1 method to root --> Unlock BL, flash custom recovery ---> flash a rooted rom or flash supersu on your stock rom. Unrooting for warranty purpose will require S-OFF and possibly a RUU
Click to expand...
Click to collapse
Thanks for the lenghty post and explanation.
So capping that up (real short):
- I need S-OFF after all, to revert if needed.
- So I need Sunshine or any other method - that is compatible with my bootloader - which gives me S-OFF.
One last q: Sunshine now features a supersu installer as well.
Can I just use that (implying it will work)?
SunshineDownloads said:
Download SunShine SUInstaller
SUInstaller is our free application for installing su (aka "perm rooting") devices that have already been unlocked. SUInstaller is the "lazy man's route", and is not entirely reliable. To use SUInstaller run it, once the phone reboots install SuperSU from the market, run SuperSU and allow it to update the su binaries with the "normal" option. If SUInstaller fails, you will need to install su through a custom recovery, or another route. SUInstaller is provided with no warranty, nor guarantee, no nothing, but it is free.
Click to expand...
Click to collapse
To be honest I don't really want to pay, but heck, if it works...
Let's not get into the whole debate that millions of others have about sunshine.
Anyway, I have seen conflicting information, and am somewhat confused. Many say you can still install custom roms with S-On and even install custom recoveries, while others say you can't install some roms unless you are S-Off.
Now, I know I can't flash a custom radio while S-On, or "convert" it into a play or dev or whatever edition.
I am fine with that (I assume I can still flash official radios released for it?), I don't want to convert it into a different type of M8 or switch carriers or anything. I just want to have rooted custom roms.
In that regard, just what would I be limited to exactly? Again, half the posts say you can still flash custom and rooted roms with S-On, and others say you need S-Off for custom roms, do they mean custom roms that are for dev/play/etc editions would require S-Off? Or are there custom roms designed for a regular Sprint M8 that would still need S-Off? Or am I even limited to only stock versions/mods of the Sprint rom? What about installing recoveries?
S-off isn't required to flash a ROM, but in some cases you have to flash the kernel separately from the ROM.
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Cyber Akuma said:
Do you mean that I won't be able to flash a kernel separately with S-on? I don't get that, won't roms flash the kernel and other key files to the system partition (which I assume you need to format first before flashing the rom) anyway?
Click to expand...
Click to collapse
Hit the second link in my sig and read the section pertaining to S-on kernel flashing.
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Cyber Akuma said:
I don't understand, what do you mean that you can't write to the /system partition permanently if you are S-On? Wouldn't you need to be able to write to the system partition in order to flash a custom rom your phone?
Click to expand...
Click to collapse
Meaning any changes that you make are only temporary and won't survive a reboot.
Though again, changes like installing a custom ROM? Or do you not need access to /system to install a custom rom?
It certainly helps to have S-OFF, but I haven't found it all that necessary. I'm currently on the ViperOneM8 3.2.1 with S-ON, and I'm not having any issues. Nothing that cannot be fixed anyway. At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it. The trouble was with Venom Tweaks, it just wouldn't run. Thankfully I had a back-up, loaded it up, and it's all good. Other than that, no problem. And I'm not even sure if S-ON was the problem, but I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
But yeah, I would give ViperOneM8 a try, though be careful. Make sure you have all the right firmware installed BEFORE you start doing any rooting. It will save you a lot of headache.
Amer28 said:
At one point, I had ran into some trouble when I installed Sense 6 Toolbox (Xposed Mod), played with some settings and then uninstalled it.
Click to expand...
Click to collapse
Amer28 said:
I'm assuming that the reason why Venom couldn't boot up was because it had no permission to overwrite some stuff that the xmod sense 6 toolbox left behind. I'm just guessing of course, I'm probably wrong.
Click to expand...
Click to collapse
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Cyber Akuma said:
Sorry to keep going on about this, but I am still confused. If you can't permanently write to the /system partition, how were you able to install tools that modify system files? You mentioned that you think the reason was that the Toolbox software you installed left some modified files behind, if S-On means you can't permanently modify those files then how did they survive a reboot?
Would I be able to install a security application like avira onto the system partition with S-On? It has an option to install itself, and it's settings, into a rooted phone so the application (and it's settings) cannot just be wiped from a factory reset. Wouldn't it need to write to the system partition in order to do that?
Come to think of it, I know you can install another bootloader and/or recovery once you are rooted, but wouldn't you also need to be able to access the system partition in order to be able to do that?
I don't get what this unable to permanently write to the system partition while S-On entails since it seems like many things do permanently write to it still.
Click to expand...
Click to collapse
I'm not hundred percent sure on this. I don't do any modding or anything myself, but it is my understanding that you actually 'can' write to the system partition. Just not 'some' stuff. It's essentially like having safe mode on, it just ensures that you don't completely brick the phone.
Again, please do not quote me on any on this. I'm merely humoring the subject, not an expert in any sense of the word.
You can flash virtually any custom ROM with S-On as long as you unlock your Bootloader at HtcDev... I can explain details later on, I am just busy atm...
---------- Post added at 11:09 PM ---------- Previous post was at 10:19 PM ----------
Some more details:
Basically you have 2 options to enable Custom Roms on the HTC One M8
1. Unlock bootloader at http://www.htcdev.com/bootloader/
2. Gain S-Off
For 99% of the ROMs it makes no difference which way you go. You can flash a custom recovery with both ways and you can flash custom ROMs with both ways. There is no such thing as a limitation during writing /system.
The difference is that with S-Off you can change your device IDs (e.g. CID) and in consequence you can flash firmware (like radio firmware, adsp firmware, etc.) that is not meant for your device. So playing with S-Off is quite "risky" you can "easily" achive a brick.
With S-On, you can only flash firmware which is signed for your device.
I would give the recommendation as follows: If you decide to go with S-On (which I would do if you have no specific reason for S-Off) then after flashing a custom recovery, take a backup of your stock ROM. Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
elandroido said:
Then, when you need a update of the firmware components, you can restore that backup, flash stock recovery, relock bootloader and use stock OTA to update all firmware components consistently.
Click to expand...
Click to collapse
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Well you can flash a radio which is signed for your device. But the safer way imho is to go the OTA way, because that really dates up everything. There might be other firmware components that can receive an update and when you go OTA everything stays consistent. But oft course you can also take the manual way, if you find a proper firmware zip.
Cyber Akuma said:
Wait, so I can't flash an updated radio if I am on a custom rom even if that radio was officially released for my device? I thought even with S-On you would still be able to flash a radio if it was officially released and signed for your device?
Click to expand...
Click to collapse
You can flash the full, signed firmware such as what OMJ provides in his RUU thread, but you cannot flash unsigned firmware to your device while S-on. You can still update your radios, you just have to jump through a few more hoops to do so, unlike those who have S-off.
You might want to take a look at the first post in the thread linked below for more info:
http://forum.xda-developers.com/showthread.php?t=1680928
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
tw39515 said:
Just got a new m9 been away from htc and rooting for a long time. just upgraded from my trusty galaxy s3. Is there any thing i should be aware of before unlocking boot loader and rooting. the phone is bone stock on 5.0.2 Should i let it update before unlocking boot loader and rooting. To my understanding i should unlock boot loader install twrp and don't mount the system before making a back up. Then install supersu and root or use sunshine to get root and do both.
Click to expand...
Click to collapse
Welcome back to HTC
It really depends on what you plan to do with your M9.
If you plan on using custom roms then yes unlock and install TWRP. Root is not required to flash roms.
Sunshine does not root or unlock but removes secure write (S-Off) which allows you to install different firmware's etc.
With S-on you can only move forward with firmware's. Lots of people complain about the 25.00, But its well worth it.
If you are not concerned about the cost, then unlock, twrp, flash superSu, and install sunshine and S-off then your free to do anything.
backup if you like but there is a thread with stock backups etc...
hope this helps
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
will do viperone had issues on initial firmware so i flashed the latest ruu, sunshine is next. thanks for the advice.
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
umangilu said:
Hi everyone,
I need some help if you may please. I bought an HTC One M9 phone and for a while it's been telling me to update to the newest android version. However, this was impossible because even when I downloaded de update from TMobile, when restarting, TWRP would kick in and wouldn't let me go through the whole setup. So, I got to some tutorials and I found some guidance but it's all so confusing and I've gotten to a point where I have no idea what to do next.
Phone is from:
-TMobile
What I did:
-Got rid of TWRP
-Got it back to unroot
Phone status as of now:
It works fine, but it's still not updated.
When going into the HTC Download mode screen, i get the following info:
-UNLOCKED
-htc_himaul PVT S-ON
-OS-1.32.531.24
-Warning: Security checking failed NOT_FIND_SMARTIO
FILE /mnt/media_rw/ext_sd/0PJAIMG.zip
File NOT FOUND
ADB is not reading my device when in download mode, I was trying to install stock recovery by following a tutorian in android soul: how to install stock recovery on htc one m9 (sorry but the forum won't let me post the link.
What do I need to do? There are so many tutorials out ther with so many different instructions that I'm totally confused now as to what to install or not to install . I'd like to install the Developer version but if I have to deal with the Tmobile one, that's ok.
Thanks in advance
Umang jain
[email protected]
Click to expand...
Click to collapse
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
tw39515 said:
My main concern was if i want to use the phone first with out unlocking and it receives the tmobile update that i can unlock and root later.
Click to expand...
Click to collapse
kc6wke said:
Yes you can still unlock and root and S-off on the current OS 5.1 - 2.11.531.19, but I would do it before MM comes out for this device.
Click to expand...
Click to collapse
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Miguel_Lancaster said:
Wait. I just picked up an M9 myself, and my current plan is to wait until the official T-Mobile Marshmallow OTA is released before I unlock bootloader and S-OFF. My logic being that I could create then create a backup point in TWRP if I can't find a custom ROM that suitably handles T-Mobile specific features (WiFi calling, etc.) and just restore to the stock T-Mobile image.
Are you saying that updating OTA to Marshmallow could limit my ability to use Sunshine for S-OFF?
I suppose I could just S-OFF now and then RUU back to Stock T-Mobile Marshmallow once released?
edit: I'm already on Lollipop 5.1 on my M9. Am I already ****-out-of-luck for Sunshine?
Click to expand...
Click to collapse
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
kc6wke said:
Sunshine will work on the current version. We never know what will come when a new OTA's come out.
An OTA wont relock the bootloader or return it to S-ON. That is why I would recommend to do the S-off before an OTA.
Click to expand...
Click to collapse
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Miguel_Lancaster said:
Makes sense.
But won't unlocking the bootloader, flashing TWRP, then going S-OFF with Sunshine make it so that the newest OTA won't be accepted as an actual over-the-air update due to the altered filesystem? I know that I can still RUU, but will RUU not revert my S-OFF back to S-ON and re-lock the bootloader? Or are those things unaffected by RUU, even as an executable RUU?
Click to expand...
Click to collapse
The RUU will not relock bootloader or rewrite S-On. To accept OTA, you need to have stock unmodified device.
You could run the RUU again or just unroot and flash stock recovery. The OTA will not wipe the device but the RUU will.
Hope this helps.
kc6wke said:
You say you got rid of twrp and tried to flash the stock recovery but adb is not working, so what recovery is currently on the phone?
I think the simplest solution would be to run the latest RUU from your sd card since you have adb issues (most likely a driver).
This will bring you to current stock 2.11.531.19. This will wipe the device and you must use a 4-32GB sd card.
Place it on the root of the sd card and boot into download mode, vol up to update and let it run.
you can get the RUU here
Click to expand...
Click to collapse
Thanks for this! Im having trouble with my computer and have been looking for a ruu zip all day lol. Will give this a shot on my TMOUS S-Off M9 tomorrow so I can jump to my next device.