Develop Bugs

OTA Update on a rooted M8

hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks

I also am curious about this topic

snap213 said:
hello, i need to verify something with you guys.
Currently i'm using an HTC One M8 rooted and running on a stock rom, and TWRP as a recovery, can i still have OTA updates in my phone even if I'm on root and TWRP as a recovery. also one thing how can go remove TWRP recovery or revert to HTC recovery
many thanks
Click to expand...
Click to collapse
1. Download the stock recovery for your device from the recovery thread
2. Flash it through fastboot (as you did TWRP)
3. Apply the OTA
4. Reflash TWRP
5. Re-root the phone

guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7

snap213 said:
guess i'm stuck with my rooted phone then, i rooted my phone using Hansoon2000 All-In-One-Kit
and i can't find my stock rom, my software number is 1.54.707.7
Click to expand...
Click to collapse
Not stock rom...stock recovery

Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
spikeydoo2006 said:
Look at the bottom of the first post of mr_hofs thread in the general section here: http://forum.xda-developers.com/showthread.php?t=2701376 (under the nandroid backups section)
You'll find your stock recovery there ?
Hope that helps.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL

i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.

snap213 said:
i've browse mr.hofs thread and i've seen lots of stock recoveries. I don't know which stock recovery will I use.
I tried to match it using my software number 1.54.707.7 but there is none. or should i just try the closer to that version?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
thanks.
Click to expand...
Click to collapse
here is my recovery backup from 1.54.707.7. https://www.dropbox.com/s/p2ht9dxns3ggcyk/recovery.img
Can you backup your radio.img for me? I forgot to backup when i convert my phone to GPE.

to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.

snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Yes, you can! I did it exactly that way - and after OTA update reflashed TWRP and rerouted that way. Its a 4 minute job.

snap213 said:
to any Hasoons2000's users out there?
also another question? can i flash my stock recovery using Hasoon2000's AIO Toolkit? i see here on the left box it's says your own recovery.
---
or can anyone give me a much more detailed or step by step instructions, i know i' cant post in HTC development forum.
Click to expand...
Click to collapse
Learn to do it yourself, relying on toolkits is a false economy as if anything goes wrong you'll have no idea how to fix it...

EddyOS said:
Remember (as said a million times already in multiple threads) - to flash an OTA you CANNOT have changed anything in the original system (fonts, Xposed mods, removing system apps, ANYTHING) otherwise the OTA WILL FAIL
Click to expand...
Click to collapse
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.

anjaan said:
Yes, that has been mentioned quite a few times in various threads..However one question that pops up now is:
Lets says I did make changes to the system files by removing a system app or using xposed mods (but not flashing any custom roms). But these changes were made AFTER taking a backup of (unchanged) stock recovery. Will OTA still fail if i now flash stock recovery and then ota update? I am guessing it should work as i am bringing the phone back to stock status.
Also what if i do not flash any custom recovery, I just boot into it to take a backup and remain in stock rom. In that case, for an OTA update, do i still need to first flash stock recovery if I have not made changes to sys files?
Finally when you say OTA fail, does that mean there is a chance I will brick/soft brick my phone?or is it just an error message. I ask because in case i make changes to sys and then forget about it or do not realise its consequence for an OTA update, its better I know now what I am getting into.
Click to expand...
Click to collapse
The OTA requires a 100% stock running Android build, so if you have removed any system apps it will just fail and reboot to the ROM you're running at the moment (so you should be safe). Basically, if the /system partition on the phone is ANY way different from how it was when you first bought it the OTA will fail
For example, other than S-OFF my phone is exactly how I received it, therefore the new OTA update installed successfully. If I had removed one system app (e.g. Hangouts), it would fail as it's looking for it and if it can't find it it'll just reboot

i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?

snap213 said:
i still have my S-OFF here in my HTC, and i haven't removed any system apps. i'll try this later this week.
i just needed my root because of setCPU nothing else.
--- anyway, since we're all learning here.
we'll for example, OTA has been updated and all goes well. now that i have to reflash my recovery to TWRP.
big question again, how do i save my stock recovery using TWRP?
Click to expand...
Click to collapse
If you're now on 1.54.401.10, you can manually extract it from the firmware package I uploaded HERE

I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?

Black Antitoon said:
I installed the OTA yesterday and had a different experience. I am with the stock rooted ROM, but I installed Xposed with some modules and the swipe to sleep and no write protection kernel modules. Also, unlocking the bootloader also ate my calculator and torch apps, and I reinstalled them as user apps instead of system apps.
Well, after flashing the stock recovery, the OTA worked like a charm. I applied it manually from the stock recovery, but I don't think this makes a difference. I had to re-root afterwards, but all the rest was preserved.
I am S-OFF though. Is that the reason why it bypassed some security checks?
Click to expand...
Click to collapse
I can see the apps that were removed during unlocking still working if installed as user apps as they're still on the /data partition. If they weren't there at all then it'd probably fail. Surprised that it worked with Xposed installed, but that's also a user app so it could very well work - logically it makes sense.
As a rule of thumb I'd only apply an OTA on a 100% stock system, that way you know it'll all be fine

Help! Accidentally hit the OTA upgrade while runing TWRP (bootloop)

I hit the "OK" on the OTA box without thinking, and only realized my mistake when TWRP came up after it started it's process.
I can get all the way back into the Launcher, but after about 60 seconds is reboots.
I'm guessing all I need to to undo one thing, or maybe flash a new/stock bootloader, but I don't really know where to start. I am coming from Samsung phones, so the terminology is rather different with HTC.
I've already made a backup of boot, system, and data, from within TWRP and copied it off the phone. I also quickly moved the OTA zip off my phone as well in order to keep a copy of it. Lastly, I can boot into "Safe Mode" (which I discovered by accident) and it doesn't do the reboot thing.
Any help at all is appreciated.
Thank you.
EDIT: Success!
Turns out I needed to re-flash my SuperSU binary from TWRP. I re-flashed the version I had first which actually removed the SuperSU apk. I re-downloaded it from Play Store, then flashed the 2.01 update. Runs like a charm.
Thanks to everyone for the help.

Hi,if you already backup your ROM before OTA,just restore it

hdorius said:
Hi,if you already backup your ROM before OTA,just restore it
Click to expand...
Click to collapse
I only did the backup after I got into the reboot cycle.
I haven't tried restoring it, but I don't imagine that it will work.

Can u please post your cid?u can find the stock nandroid backup that linked at my signature

winnower said:
I only did the backup after I got into the reboot cycle.
I haven't tried restoring it, but I don't imagine that it will work.
Click to expand...
Click to collapse
No it will not work. Just delete the backup and save you the time and trouble messing with it. If you can grab a good backup from someone then you will be ok. Simply restore and all should be well. Then, make sure you remove your custom recovery prior to accepting the OTA.
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.

hdorius said:
Can u please post your cid?u can find the stock nandroid backup that linked at my signature
Click to expand...
Click to collapse
Ok, I need to do a bit of reading it seems.
I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.
Modding.MyMind said:
No it will not work. Just delete the backup and save you the time and trouble messing with it. If you can grab a good backup from someone then you will be ok. Simply restore and all should be well. Then, make sure you remove your custom recovery prior to accepting the OTA.
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.
Click to expand...
Click to collapse
Thanks, I kinda figured the backup wouldn't help.
I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?

winnower said:
Ok, I need to do a bit of reading it seems.
I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.
Thanks, I kinda figured the backup wouldn't help.
I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
Click to expand...
Click to collapse
Just use the command "fastboot getvar all" it will read your CID and find the backup at Stock Nandroid Backup that match your phone and restore it
Edit: oops the thread that i linked is closed and all the links are removed

winnower said:
Ok, I need to do a bit of reading it seems.
I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.
Thanks, I kinda figured the backup wouldn't help.
I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
Click to expand...
Click to collapse
The recovery image is based for the new OTA. Won't necessarily be the same as what your device currently used but it should still work. If by any chance it does not then it is because of the Bootloader version you are currently running which is causing the problem. Which at that point you will need to grab the other stock recovery.img prior to the update.
---------- Post added at 09:56 AM ---------- Previous post was at 09:55 AM ----------
I don't have your device so I can't really provide any links to assist even further but I ca build you a foundation to go off of. The logic with this stuff is relatively universal across common android devices for the most part.

winnower said:
I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
Click to expand...
Click to collapse
Since you have the OTA, can you put the details of android-info.txt that you have inside it ?? This will definitely help you to find the right recovery/backup.

Modding.MyMind said:
Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.
Click to expand...
Click to collapse
Have you actually seen this done? AFAIK stock recovery is required to install OTA; but perhaps I'm mistaken. In any case, its far easier to restore stock recovery if the intent is to install OTA. However, the current installed ROM must also have no system files altered, as this is also a requirement for OTA installation.
Another (probably easiest) way out of this loop would be to mount the memory, find the OTA file and delete it. The phone should then stop trying to find stock recovery to install the OTA (which is the cause of the bootloop).

@redpoint73, that is a valid question to ask. I have not seen any guides made available to the public however, I can vouch it works. I once did it myself many many many months ago once I did some extensive studies on how an OTA was applied. Though, I won't hesitate to mention that it's a tedious process and I wouldn't recommend it less it were your only absolute option since there are so many easier methods to use.

Modding.MyMind said:
@redpoint73, that is a valid question to ask. I have not seen any guides made available to the public however, I can vouch it works. I once did it myself many many many months ago once I did some extensive studies on how an OTA was applied. Though, I won't hesitate to mention that it's a tedious process and I wouldn't recommend it less it were your only absolute option since there are so many easier methods to use.
Click to expand...
Click to collapse
Good to know, thanks for the explanation. Interesting that custom recovery will actually work (technically) with an OTA, that its just security checks that keep if from happening.
As you mentioned, there are many much easier options to recovery; so what you mentioned is just a method of "last resort".

ckpv5 said:
Since you have the OTA, can you put the details of android-info.txt that you have inside it ?? This will definitely help you to find the right recovery/backup.
Click to expand...
Click to collapse
OTAfile/firmware.xip/android-info.txt:
modelid: 0P6B16000
cidnum: BM___001
cidnum: SASKT001
mainver: 2.23.666.2
btype:1
aareport:1
hbootpreupdate:12

hdorius said:
Just use the command "fastboot getvar all" it will read your CID and find the backup at Stock Nandroid Backup that match your phone and restore it
Edit: oops the thread that i linked is closed and all the links are removed
Click to expand...
Click to collapse
Ok, downloaded fastboot-win.zip from HTC's dev site.
C:\Android\m8>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
So, if those links are offline, do you have another source or just use the one I got with the OTA?

Did you try to just find the OTA file and delete it, as I previously suggested? This should get the bootloop to stop.

redpoint73 said:
Did you try to just find the OTA file and delete it, as I previously suggested? This should get the bootloop to stop.
Click to expand...
Click to collapse
Yes, the OTA is no longer on the phone.
It's not really "bootlooping", it boots normally into the Sense launcher, then after about a minute it restarts. It's not stuck on the HTC logo or anything; it's more like a restart-cycle.

Were you on a stock ROM, or custom before this OTA mess started? My recommendation would just be to pick a custom ROM of your choice on the phone (either via adb push or on the removable SD) and flash it in TWRP and forget this OTA business. Making it more complicated than it needs to be, and OTAs don't really have any business on modded phones anyway, for the most part.

redpoint73 said:
Were you on a stock ROM, or custom before this OTA mess started? My recommendation would just be to pick a custom ROM of your choice on the phone (either via adb push or on the removable SD) and flash it in TWRP and forget this OTA business. Making it more complicated than it needs to be, and OTAs don't really have any business on modded phones anyway, for the most part.
Click to expand...
Click to collapse
I was on stock Sense6. I had previously unlocked and loaded TWRP since I assumed I'd switch ROMs very shortly after getting the phone. I was coming from Samsung's world where running my own ROM was mandatory since TouchWiz was so awful.
The only thing keeping me from flashing a custom ROM right now is my data/apps. In my sleep deprived state, I didn't think to make a backup (or to not accept the OTA in the first place). If I can flash a customized Sense6 ROM and keep my apps/data then I will.

The phone isn't really working for more than a minute or so. So I'd just do a wipe and install a custom ROM. Something is broken now, so a clean slate is probably your best bet.

Yeah, I'm just trying a few last things.
I tried flashing the newest TWRP and the stock recovery.img I got with the OTA; no luck.
I still have the full OTA zip though... Is there any way for me to adb push that file on the /sdcard/ to force it to complete the update? That way I can just re-flash TWRP and SuperSu and keep my data.
Thanks for all the help.

HTC One M8 Root [HELP PLEASE]

So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?

Just restore your backup ... you should already make one before you tried to root it.
Post here fastboot getvar all result without serial & imei no then we'll see what you need.

ChiefMustardo said:
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Click to expand...
Click to collapse
When I helped you previously, I had to advise you to provide the proper details. So why are you repeating the same mistakes here? You need to help us help you, by posting the proper details.
In addition to the getvar output requested by ckpv5, what versions of SuperSU did you use? "Much newer version" doesn't really tell us anything (at least not specific enough for us to help you).
Your current firmware version greatly affects what version TWRP and SuperSU you need to use to avoid problems that you mentioned (no boot). So we can't begin to properly help, until you provide the proper info.
Additionally, you started another thread asking same/related questions. I won't respond to that thread, as making multiple threads (for related issues) is confusing and will only cause more problems (such as hopping back and forth between the threads). Bump your existing thread, if you have to (and asking subsequent questions in that existing thread is an acceptable way of doing that). But please don't make more threads. I have some input on the specific questions you asked in the other thread:
ChiefMustardo said:
Can someone please explain to me why when i use twrp or cwm no ROM installs and the md5 check fails as does the signature verification and it says that the zip file is corrupt. It isn't because i got it from the skydragon website.
Click to expand...
Click to collapse
Can't say for sure why TWRP is failing, until you provide the getvar info. It can be a mismatch between your current firmware and the TWRP version. But we have no way of telling, unless you provide the requested details.
And are you trying to use multiple TWRP versions, or just the one mentioned? And BTW, there is no TWRP 3.2.0, so I assume you mean 3.0.2, but please confirm.
Also, I would avoid CWM, as it hasn't been updated in a very long time, which can create a lot of issue in itself.
What is the exact file name, or Skydragon version of the ROM you are trying to install (also very important)?
Just because you downloaded from Skydragon website, does not exclude the possibility the file is corrupt. A perfectly working file can get corrupted during download to your phone/computer. Try downloading twice, to eliminate that as a possibility.
You should also turn off MD5 verification in TWRP; which is probably causing the MD5 error (as mentioned by dottat here). MD5 check typically not used for ROMs (particularly if there was no MD5 hash code supplied with the ROM).

Here is my fastboot getvar all
http://prntscr.com/bd24cj

ChiefMustardo said:
Here is my fastboot getvar all
http://prntscr.com/bd24cj
Click to expand...
Click to collapse
It was also the SuperSU 2.46

ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
Skydragon: SkyDragon+M8+v4.0.0+Sense+8+MM
TWRP: twrp-3.0.2-0-m8
Philz touch: philz_touch_6.26.6-m8

1. You used wrong TWRP recovery 2.7.x.x that make your version-main now empty.
2. You installed wrong SuperSU - 2.46 is NOT for Marshmallow.
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
I suggest you revert to stock first then redo the whole thing ... rooting or installing a custom ROM, these you can do later after you fix your phone.
Read this for the drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
And this for installing RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)

ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
That version is really old, released about Feb 2015!
SuperSU 2.65 is recommended. Anything older than 2.52 or so does not include the ability to root MM, and will fail with no boot/boot loop.
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
ckpv5 said:
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
Click to expand...
Click to collapse
That is true, its not clear what the OP is currently trying to accomplish. This thread started out asking about root (stock ROM?) than started another thread asking about custom ROMs.
Its one or the other, not both (root vs. custom ROM) since as you mention, custom ROMs are already rooted.

I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen

ChiefMustardo said:
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
Click to expand...
Click to collapse
Just kill the process, and start it again. This is a reported issue for some folks.
If the issue reoccurs, we may have to look at USB connection issues.
Are you using the RUU zip method that ckpv5 directed in Post #7 above?

The RUU method you have suggested seems like it isworking.

The RUU worked thank you so much. Now to install SkyDragon ROM.

I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked. It is on Optimizing 44 of 153

ChiefMustardo said:
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked.
Click to expand...
Click to collapse
The .exe is finicky. Anything but Windows 7 and USB 2.0 can cause problems with its USB connectivity. The zip method is more reliable (as you've seen).

It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?

ChiefMustardo said:
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
Click to expand...
Click to collapse
Read again : http://forum.xda-developers.com/showpost.php?p=67197327&postcount=7
Clearly stated :
ckpv5 said:
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
Click to expand...
Click to collapse

OK thanks. Do I not require s-off then?

Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.

ChiefMustardo said:
OK thanks. Do I not require s-off then?
Click to expand...
Click to collapse
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
ChiefMustardo said:
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
Click to expand...
Click to collapse
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?

redpoint73 said:
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
Click to expand...
Click to collapse
I am using the skydragon ROM (latest for Marshmallow) but in the zip the only file there is system. It also skips the MD5 check and has a progress bar for a bit and then comes up with the corrupt zip message.

Help – I'm lost. New to HTC and quite confused about flashing/rooting/...

Hey there,
I've got my first HTC device some days ago (-> HTC 10), but coming from a Nexus 5 where things are handled differently, I'm currently quite confused on how all of this works with my HTC 10.
I'd like to apologize in advance if the following questions seem to be stupid or unnecessary, but I'd like to use my device to the fullest and therefore I need your help.
My device is not branded (as far as I can tell) and I've already unlocked it via the steps on htcdev.com + I've installed TWRP + SuperSU (thanks to my previous knowledge with my N5 this was somewhat easy).
Now I got my first OTA update and this is when things got complicated. Several questions popped up and I tried to answer them myself while looking over here, but after reading all those threads I'm even more confused than before :/
My questions are the following:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4)
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them?
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty?
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data?
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though?
I'm completely fine with losing my current data if that means that I can set it up my device in such a way that I can avoid any further data wipes when flasing/updating.
I'd be absolutely grateful if someone would answer those questions and help me to understand all of this.
Greetings,
makit_

1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares

not an expert but here's my thoughts...
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data? Yes. see also #1
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though? I think you meant sim unlocking here?? Generally, "unlocking" mostly mentioned in xda refers to bootloader

Tarima said:
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
Click to expand...
Click to collapse
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
side_flip15 said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
Click to expand...
Click to collapse
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
side_flip15 said:
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
Click to expand...
Click to collapse
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
side_flip15 said:
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
Click to expand...
Click to collapse
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
side_flip15 said:
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
Click to expand...
Click to collapse
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
side_flip15 said:
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
Click to expand...
Click to collapse
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_

When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
Click to expand...
Click to collapse
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
Click to expand...
Click to collapse
Data partition can be backed up actually and can be restored.
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
Agree. there is no sense in reverting back to s-on unless if it's for warranty purposes.
Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Click to expand...
Click to collapse
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing
Click to expand...
Click to collapse
Take a look at this link. It provides you a complete explanation between ROM and Firmware.
Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Click to expand...
Click to collapse
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.

makit_ said:
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
Click to expand...
Click to collapse
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...

side_flip15 said:
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
Click to expand...
Click to collapse
I know that app by name, but never used it. Will take a look into it
side_flip15 said:
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
Click to expand...
Click to collapse
Do you mean like this? (found in another forum):
1. First step is to unlock bootloader:
a) If bootloader unlock is turned off on your phone, you need to turn it on first:
- Boot to Android OS and perform initial setup if necessary
- Go to Menu -> Developer settings and tick "Enable OEM unlock"
Run XTC 2 Tool and open "Bootloader unlock" tab, follow instructions to unlock your bootloader.
2. Reboot to download mode, open "HTC 10" tab and install twrp recovery, you can get it here:
[...]
or
[...]
3. Boot to Bootloader, and press "Reboot to recovery".
4. In "HTC 10" tab press "Do S-OFF button".
5. Wait for the process to finish. Done.
Click to expand...
Click to collapse
side_flip15 said:
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Click to expand...
Click to collapse
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
side_flip15 said:
Take a look at [... ]this link[/URL]. It provides you a complete explanation between ROM and Firmware.
Click to expand...
Click to collapse
Thanks, will look into it.
side_flip15 said:
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
Click to expand...
Click to collapse
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification, I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Is this correct or are there any mistakes?
And thanks a ton, you've helped me so much already!
Greetings,
makit_

makit_ said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
Click to expand...
Click to collapse
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc

yankee1390 said:
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
Click to expand...
Click to collapse
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that

makit_ said:
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
Click to expand...
Click to collapse
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification

yankee1390 said:
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
Click to expand...
Click to collapse
Will also look into this. I've used Xposed on my N5 but wasn't sure the HTC 10 is already fully supported (have read something about that, but those threads were already 3-4 months old). Thanks!

So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.

makit_ said:
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
Click to expand...
Click to collapse
Link didn't work on my app so can't confirm if that will work. However any TWRP stock backup that matches your current version should work. RUUs will wipe your data if you use them.
Definitely good idea to backup after each ota before modifying system partition to make next ota easier. Though usually someone on here can provide a backup if you don't get one.

I know that app by name, but never used it. Will take a look into it
Click to expand...
Click to collapse
i suggest you purchase a pro version. It's a really a must-have app
Do you mean like this? (found in another forum):
Click to expand...
Click to collapse
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
Click to expand...
Click to collapse
Yeah. They might not know we can s-off. lol
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification
Click to expand...
Click to collapse
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Click to expand...
Click to collapse
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
And thanks a ton, you've helped me so much already!
Click to expand...
Click to collapse
You are welcome.
---------- Post added at 02:22 AM ---------- Previous post was at 01:44 AM ----------
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.

side_flip15 said:
i suggest you purchase a pro version. It's a really a must-have app
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah. They might not know we can s-off. lol
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
You are welcome.
Click to expand...
Click to collapse
Thanks for all your help. I will look into it when I need it. For now I'll stick with stock (see below)
side_flip15 said:
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
Click to expand...
Click to collapse
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!

Piggybacking on this thread because my new-to-me HTC 10 is coming in the mail and I'm planning what to do with it. It is already bootloader unlocked and s-off. I would like to use Leedroid, ElementalX, Magisk, and Xposed.
I've never had an HTC device so I just want to make sure I'm doing this right. So I think this is what I need to do:
1) Flash TWRP via ADB
2) Flash SuperSU in TWRP
3) Flash everything else...Leedroid, ElementX, Xposed, Magisk. In that order? Can I flash them all at once (just keep adding zips to the TWRP list) or do I have to boot between each one?
Xposed is more important to me than a custom ROM, because I need to use Amplify and PowerNap to improve my battery life. Would it be better just to stay on stock instead of Leedroid?

@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10

I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Click to expand...
Click to collapse
When I said stock ROM, i meant stock HTC ROM and it's not stock Android. It's a skinned android called HTC sense. . If you want a stock android to run in your HTC 10 you can flash a AOSP based custom ROM.

Magnum_Enforcer said:
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
Click to expand...
Click to collapse
Ah yeah, sorry, fastboot is what I meant. Thank you! I haven't had an unlocked bootloader in quite a while (was using TWRP and Sony stock-based ROMs on a locked Z3c), so it will be interesting to flash kernels and such again.

d_Schizzo said:
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
Click to expand...
Click to collapse
not only bootloader, it contains everything. radio.img and any other thing. "low-lewel-stuff", kernel etc, recovery (if stock signed firmware, which is not modded/removed). there are many important things inside.
but firmware is meant for every device the same. it contains everything so that this device can run/work properly.

Root and update OTA?

Hello ,
I will have a ONE PLUS 5T.
I would like to root this one to have adblocker...
First question : How could root this?
Second question: If my phone is rooted, is it possible to have update OTA (or like samsung, impossible after)?
Thank you;

If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.

jim262 said:
If you replace the stock recovery with a custom recovery, like TWRP, OTAs will not work. However, if retain the stock recovery and simply boot TWRP in fastboot mode, you will be able to root your stock phone and receive OTAs. Just use the ADB command <fastboot boot twro_xxx.img> or simply flash back to a stock recovery image every time an OTA comes in.
Click to expand...
Click to collapse
it's chinese for me your answer... is there a tutorial for that?

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
Guide: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
You can't use OTAs after you root. You'll need to download the full update every time one is released and flash it in TWRP.

ilan78 said:
it's chinese for me your answer... is there a tutorial for that?
Click to expand...
Click to collapse
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.

jim262 said:
If that is a major issue for you, use the TWRP recovery from blu_spark, otherwise, simply go into your TWRP settings and set the language to English or... Either way the language has nothing to do with functionality and it operates the basically the same.
Click to expand...
Click to collapse
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.

shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
If we root our device.can we install ota manually via twrp ??
If yes, then how??

Amanpreetsingh said:
If we root our device.can we install ota manually via twrp ??
If yes, then how??
Click to expand...
Click to collapse
Let me clarify: OTA stands for Over-The-Air and implies that you're going to download the partial update from OnePlus and install it in stock recovery. Do NOT do this.
OnePlus usually publishes full zips of their updates when the OTA is released. Currently a mirror for them exists in the guides section. You can flash those (>1 GB) safely in TWRP to update OOS.

santor said:
Jim your answer wasn't Chinese to me and made perfect sense thank you. I have a doubt, if I just use "fastboot boot *TWRP*.IMG" and root and flash exposed too, will I be able to receive otas and update offically and redo boot TWRP and root and flash exposed again without problems?
Click to expand...
Click to collapse
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
shadeau said:
No. You should NEVER take an OTA if you have root. You can dirty flash the full update zip in TWRP when they're released though.
Click to expand...
Click to collapse
What's the difference? You still need to reroot.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
I apologize if I'm out of the loop. When I first read about OTAs with root I was on a Samsung device and everyone said that it would either brick the phone or upgrade the OS with no way to re-root the device. Looking through your answer it's obvious that that fear probably only applies to Samsung devices. Thanks for correcting me on this.

jim262 said:
Here is the reality. YES. You can still receive OTAs with root, However, the OTA will break the root and you will need to reroot your device. Those who are saying no are wrong. It is very simple. To process an OTA, your phone needs stock recovery. TWRP will not process an OTA. So if you have stock recovery in your recovery partition and you reboot your phone into fastboot mode and from your PC, run the ADB command, <fastboot boot twrp_xxx.img>, you will boot up the TWRP image and will be able to run it as one normally would, but you will still have stock recovery loaded in the recovery partition.[QRCODE][/QRCODE]
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
What's the difference? You still need to reroot.
Click to expand...
Click to collapse
Thanks Jim , I can confirm this works without problems on op5t. I had TWRP flashed and rooted with xposed installed.
I clean flashed the 4.7.1 stock ROM and got stock recovery and fresh os.
Just booted to TWRP using fastboot boot and rooted / installed xposed.
I got OTA updated to 4.7.2 and rerooted using fastboot boot TWRP and now rooted with xposed on stock ROM and stock recovery. ?

I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?

ilan78 said:
I have a question :
I would like to root without lost everything.
Is it possible? if yes , how?
Click to expand...
Click to collapse
Exactly like I said. Rooting, by itself, does not wipe your storage. The only time your storage is wiped is when you unlock your (bootloader) phone, when you manually choose to wipe storage in TWRP or when you do a factory reset. If you do not have an unlocked bootlader, you must make a backup of your files first, as once you unlock it does a factory reset. You can then run TWRP and restore your files. You are now rooted with your files and ability to take OTAs. There are plenty of tutorials here on XDA describing the process step by step. May I suggest you do a search first. You are very likely to get all the answers to these questions as they have been asked many, many times.

Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Look through the Magisk forum. They have a method of rooting that doesn't require a custom recovery.
I use helium backup for my non-root app backup needs. Settings are trickier and I typically do them over every time. Super backup & restore is good for call logs, texts, and contacts.

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Did you read my post? The answers are all there. SEARCH! This question has been asked several times a day. You need to back up your data to another site, such as cloud, other device or PC. Then unlock bootloader, run TWRP and root file, then restore data. Tutorials are online. Now SEARCH!

ilan78 said:
Thank you.
so my question is FOR ROOTING, i HAVE TO UNLOCK BOOTLOADER?
And how Back up my data, my apps, all my settings without root or TWRP?
Click to expand...
Click to collapse
Man seriously! You got your answers and still you keep asking. Makes me wonder if you are just trolling

Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?

Tefzors said:
Non-trolling question - I am experienced when it comes to flashing/rooting. So if I want to stay with TWRP, I have to sacrifice OTA's, but it will be possible to flash the new updated zips and still keep my data via dirty flashing? Any negatives to doing this?
Click to expand...
Click to collapse
Yes, as far as I know, if on stock OOS, you download the full zip (over 1GB in size), flash that in TWRP, and then flash root solution right after (before leaving TWRP) to prevent it being overwritten by the stock recovery.
I don't think dirty flashing has any downsides, but if you do end up running into issues, a clean flash usually solves them