Develop Bugs

red triangle while trying to update OTA lollipop while on TWRP...

Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376

jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.

flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.

jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!

jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.

If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).

redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.

flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.

redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.

flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.

redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.

flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.

So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2

New to M8, first HTC device since Hero, some newbie help

Reading some scary things that I want confirmed and also want some advice
Getting S off costs $25? Rooted and unlocked countless phones across Moto, Samsung. etc and never had to pay a dime. If there is a paywall, what can one do with a locked boot?
also. can band 2 really not be unlocked?
2. Marshmallow GPE. Do I need root or can I flash via stock recovery or PC app?
3. General recommended ROM. Stay stock or is there a true MM stable 100% ROM of choice?
Other than that I am happy with the device. Mind blown by what $100 got me

againareku said:
Reading some scary things that I want confirmed and also want some advice
Getting S off costs $25? Rooted and unlocked countless phones across Moto, Samsung. etc and never had to pay a dime. If there is a paywall, what can one do with a locked boot?
also. can band 2 really not be unlocked?
2. Marshmallow GPE. Do I need root or can I flash via stock recovery or PC app?
3. General recommended ROM. Stay stock or is there a true MM stable 100% ROM of choice?
Other than that I am happy with the device. Mind blown by what $100 got me
Click to expand...
Click to collapse
1. No need for S-off if you want to flash roms/kernels. What band 2 can't be unlocked?
2. You can flash GPE rom or you can convert ur device to GPE(needs S-off)
3. Plenty of them, we have few sense 8 roms out there, Srom is 100% port of the HTC 10 and bunch of cmte/aosp roms as well.

Imotep95 said:
1. No need for S-off if you want to flash roms/kernels. What band 2 can't be unlocked?
2. You can flash GPE rom or you can convert ur device to GPE(needs S-off)
3. Plenty of them, we have few sense 8 roms out there, Srom is 100% port of the HTC 10 and bunch of cmte/aosp roms as well.
Click to expand...
Click to collapse
Band 2 lte apparently can't be enabled on tmo variant, won't stick by changing nv values according to the thread here
thanks for the help though, got a fun night ahead of me

1. S-off isn't needed for many folks. As mentioned above, you can root, flash ROMs, kernels, and lots of other mods just by unlocking the bootloader on HTCDev.com, which is a free and pretty easy process.
You'll need s-off if you want to flash a modified hboot, manually flash radios, change to another version (change CID and MID), and a few other things.
2. You can't flash anything with stock recovery, that isn't intended for your version. But with an unlocked bootloader (and that is the key, you can't mod anything with the bootloader locked), you can flash custom recovery, and flash a GPE based ROM from the Development section.
againareku said:
Band 2 lte apparently can't be enabled on tmo variant, won't stick by changing nv values according to the thread here
thanks for the help though, got a fun night ahead of me
Click to expand...
Click to collapse
LTE Band 2? You need to be specific when talking about bands (3G or LTE). I'll assume LTE Band 2. The nv value mod only works on the Sprint and Verizon (CDMA) variants. To change band support (if you need Band 2 on your carrier), you'll need to flash a radio baseband for a version that supports the desired band. And to do that you'll need s-off.
---------- Post added at 09:38 AM ---------- Previous post was at 09:30 AM ----------
Imotep95 said:
2. You can flash GPE rom or you can convert ur device to GPE(needs S-off)
Click to expand...
Click to collapse
To clarify this statement, s-off is only needed if you want to "fully convert" to the GPE version by RUU (makes it essentially a fully stock GPE phone in terms of software). The only advantage to this, is if you want the GPE partition scheme (smaller system partition, which results in more user storage) and official GPE updates. The downside, is that you can no longer install Sense ROMs (system partition is too small) unless you convert back. Plus, it will also give you the band support of the GPE version (which does not include LTE band 2 that you are apparently looking for).
In any case, as mentioned, you don't need to "fully convert" to run a GPE ROM. Just flash a GPE based ROM (after unlocking bootloader and installing custom recovery).

Change rom?

Is it possible to flash a unlocked rom to a Tmobile version of the HTC 10? I've seen this done with SAmsung S7edge carrier to unlocked anf it worked. Guy said he hasnt had issues and this was on XDA.

BlackKnight23 said:
Is it possible to flash a unlocked rom to a Tmobile version of the HTC 10? I've seen this done with SAmsung S7edge carrier to unlocked anf it worked. Guy said he hasnt had issues and this was on XDA.
Click to expand...
Click to collapse
Sure can, just pick a ROM that support multi-carrier, such as Viper, Leedroid, ICE.
When you flash the ROM, in aroma you will be presented with an option to choose carrier, pick Tmobile and good to go. :good:

I actually meant flashing a stock us unlocked rom

BlackKnight23 said:
I actually meant flashing a stock us unlocked rom
Click to expand...
Click to collapse
Link?

http://forum.xda-developers.com/att-s7-edge/how-to/samsung-sm-935u-firmware-install-guide-t3411451
Again this is Samsung but I couldn't see it not working with HTC as well

BlackKnight23 said:
I actually meant flashing a stock us unlocked rom
Click to expand...
Click to collapse
To fully convert your device to us unlocked, you will need to s-off, using the paid sunshine app ($25). This is the only way you will be able to flash the US unlocked firmware. If you want to try keeping your tmo firmware and just try to use the US unlocked ROM, your best bet is to download a US unlocked backup and restore it with TWRP.
Stock backups are in this thread: http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
There isn't a 1.91 backup available yet, though. 1.80 is the best you can do.

So after I do this will it think my phone has beem untouched and allow for OTA? The person I spoke with about his Galaxy S7 he flashed the unlocked rom to from carrier says everything works as it was factory unlocked phone even samsung pay. I am hoping to do the same for my HTC

For instance direct firmware from HTC
http://www.htc.com/us/support/htc-10/news/
Hopefully it displays right but it has the direct download for the 1.91.617.1 or whatever the Unlocked one is. How would I flash this do my device amd make it think it's all factory to receive OTA updates still?

BlackKnight23 said:
For instance direct firmware from HTC
http://www.htc.com/us/support/htc-10/news/
Hopefully it displays right but it has the direct download for the 1.91.617.1 or whatever the Unlocked one is. How would I flash this do my device amd make it think it's all factory to receive OTA updates still?
Click to expand...
Click to collapse
To use that file, you need to fully convert, which means using sunshine to s-off, then changing your cid and mid to match the us unlocked. Then you will have a fully functioning us unlocked device.
If you just want the US unlocked rom, then just restore a stock us unlocked backup in twrp. This will be mostly fully functioning, but you will still be in T-Mobile firmware (shouldn't be a problem as long as your on the newest T-Mobile firmware already) and you won't be able to get ota.

Is that the way i can flash the htcs website firmware?

BlackKnight23 said:
Is that the way i can flash the htcs website firmware?
Click to expand...
Click to collapse
To use an RUU (ROM Update Utility) from HTC's website, you either have to use the one for your specific device OR you have to convert your device by using sunshine to s-off ($25) and changing your model id (probably not necessary as I'm 99% sure that TMO and US Unlocked use the same mid) and carrier id (definitely necessary) to match the RUU you want to flash.
Also, just for your education, I know Samsung people call everything firmware, but technically that's incorrect and in the HTC world, firmware refers to the actual firmware (like bootloader, modem, radio, etc) and ROM, or system, refers to the system files (like android framework, apps, system ui, etc).
There is a thread in the Guide section that details using Sunshine to S-Off.
And see post #3 in this thread about converting a device to WWE (World Wide Edition) using RUU. The steps to convert to US Unlocked are identical EXCEPT for the following:
Step 7:
CID for US Unlocked is BS_US001
MID for US Unlocked is 2PS650000
Step 8:
Get the US Unlocked RUU.zip from here
Once you do that, you will have a 100% fully functioning US Unlocked device. The only difference from a factory provided US Unlocked device will be the text on the rear housing.

Thank you all for helping I've only flased a few times and it still is complicated to me.

BlackKnight23 said:
Thank you all for helping I've only flased a few times and it still is complicated to me.
Click to expand...
Click to collapse
No problem. Can I ask what you would like to accomplish with the US Unlocked rom as opposed to T-Mobile? Just debloat?

I'm worried Tmobile has abandoned the 10. They don't list it online, most stores do not have stock anymore, and the ones that do have few left due to initial shipment. New roms have been out and Tmobile has yet to keep it updated, software only has a few added apps other than that unlocked vs Tmobile roms are the same. Both Roms support VoLTE, Band 12, and Wi-Fi calling. I want faster updates. I love my HTC 10 except it has a few bugs in radios i.e. wifi and LTE. I have no clue if Tmobile will continue to support it, they claim they will but have yet to update the device.

BlackKnight23 said:
I'm worried Tmobile has abandoned the 10. They don't list it online, most stores do not have stock anymore, and the ones that do have few left due to initial shipment. New roms have been out and Tmobile has yet to keep it updated, software only has a few added apps other than that unlocked vs Tmobile roms are the same. Both Roms support VoLTE, Band 12, and Wi-Fi calling. I want faster updates. I love my HTC 10 except it has a few bugs in radios i.e. wifi and LTE. I have no clue if Tmobile will continue to support it, they claim they will but have yet to update the device.
Click to expand...
Click to collapse
I hear you. Then you need to do the full conversion to accomplish that. Just follow the guide I linked to exactly and if you don't understand something, just ask before doing anything. It's not really novice level, but it's hardly rocket science and everything is pretty well laid out in writing. Good luck

I followed the s-off step, changed my cid, used HTCs RUU and flashed it. It's starting up now.

What does this mean? Cause I'm S-off? How do I S-on? I flashed by being s-off but locked should i have been unlocked?

Is this a good sign?

BlackKnight23 said:
What does this mean? Cause I'm S-off? How do I S-on? I flashed by being s-off but locked should i have been unlocked?
Click to expand...
Click to collapse
BlackKnight23 said:
Is this a good sign?
Click to expand...
Click to collapse
That's normal. Looks good. The Sunshine guys suggest locked is preferred.
Don't play around with going s-on until you need to return the phone or sell it. It's not necessary and if you don't do something right can brick the phone.

Anyone with a unlocked US HTC 10 is it typical for it to ask which carrier after inserting sum. Restarting?

What is the best rom to update to?

HI, Im just wondering what the best rom to update to is for my HTC 10.
Im currently on UK EE network.
I have unlocked the bootloader (via HTCdev), I have S-off (via sunshine) and i am still running stock recovery and official rom on android 6.0.1.
I am hoping to update to nougat.
My plan is to hopefully lock the bootloader again after once i have updated so i can use Android pay again. Their damn safetynet app stops me from running it having an unlocked bootloader.
Answering my own question though, would android pay still work with a custom rom? or can I use an official Nougat rom then lock the bootloader to fool it?

with magisk and phh su safety net currently also passes on rooted custom roms.

j to the 4n said:
with magisk and phh su safety net currently also passes on rooted custom roms.
Click to expand...
Click to collapse
I never used Android pay before my HTC10. the last phone I rooted was an old Galaxy S4, I had installed TWRP, SU, and used resurrection remix for it. it seemed to work perfectly fine. until I loaned it to someone an now its dead, (suspect water damage).
I'm currently at the stage of whether to install TWRP & SU to root it then go on to install a custom ROM, or leave as is.
I was tempted to go S-off,/Locked to allow it to work via sunshine but I would need to reset to S-on first.
Not entirtely sure of which route to take at the mo

What did you end up doing here, I'm on EE 1.95.91 and want to get onto N and a custom ROM - any suggestions?

SailorJerry01 said:
What did you end up doing here, I'm on EE 1.95.91 and want to get onto N and a custom ROM - any suggestions?
Click to expand...
Click to collapse
Ive ended up using Leedroid. But I have lost the WiFi calling option. Im presuming that this is because of My HTC10 being locked to EE and having the EE branded firmware on. Lee an me have been trying to figure this out as I seem to be the only one
The latest Leedroid can be found on his website.

aceniz said:
Ive ended up using Leedroid. But I have lost the WiFi calling option. Im presuming that this is because of My HTC10 being locked to EE and having the EE branded firmware on. Lee an me have been trying to figure this out as I seem to be the only one
The latest Leedroid can be found on his website.
Click to expand...
Click to collapse
Youre s-off so update the firmware and install either viper or leedroid.. Both work fine. I'm in ee too although I don't care about wifi calling and android pay.. Magisk may allow them to work.

dladz said:
Youre s-off so update the firmware and install either viper or leedroid.. Both work fine. I'm in ee too although I don't care about wifi calling and android pay.. Magisk may allow them to work.
Click to expand...
Click to collapse
Yeh Im S-off but I cant seem to update the Firmware for some reason. Or I havent been trying the right ones. I tried an update from HTCdev to update me to 2.41 but it failed.

aceniz said:
Yeh Im S-off but I cant seem to update the Firmware for some reason. Or I havent been trying the right ones. I tried an update from HTCdev to update me to 2.41 but it failed.
Click to expand...
Click to collapse
ensure you supercid, then flash the WWE (401) firmware from the thread of @Sneakyghost

j to the 4n said:
ensure you supercid, then flash the WWE (401) firmware from the thread of @Sneakyghost
Click to expand...
Click to collapse
Thanks, SuperCID done, had to mess about a little as bloody Powershell has took over cmd despite disabling it.
The latest fw on htc for unlocked/developer HTC10 is 2.41.617.3, I presume this would be the same thing done via RUU and Sneakyghost's has no particular changes to it?

aceniz said:
Thanks, SuperCID done, had to mess about a little as bloody Powershell has took over cmd despite disabling it.
The latest fw on htc for unlocked/developer HTC10 is 2.41.617.3, I presume this would be the same thing done via RUU and Sneakyghost's has no particular changes to it?
Click to expand...
Click to collapse
correct, just that it won't wipe your data..
You have a Dev Edition device? If not, you would need the 2.41.401.3 firmware.

j to the 4n said:
correct, just that it won't wipe your data..
You have a Dev Edition device? If not, you would need the 2.41.401.3 firmware.
Click to expand...
Click to collapse
Right Ill use Sneaky's version then.
My HTC is direct from EE, but now as I've rooted it etc it says its a dev for the obvious security check.
My problem has always been as it had original EE based firmware on it. a little googling shows a lot of network features dont work unless you use it. I know currently my VoLTE doesnt work as it drops to 3G when i make a call.

How to convert/change HTC One M8 Verizon ROM to Unbranded Official Stock ROM?

Hi,
I recently purchased a HTC One M8 Verizon here in Brazil and want to know how to change/convert/remove completely the Verizon ROM to a Unbranded Official Stock ROM?! I searched all over Google/xda and found absolutely nothing concrete about this.
I only want the Stock Official ROM, not interested in any Custom ROM due to the difficulty to install and also instability.
Anyone help me?
Thanks and sorry for my bad english.

I can tell you concrete that you should not attempt to "fully convert" to any other version by flashing another version's RUU or firmware. Other firmware/RUUs are not compatible with the Verizon version, it won't work, and it can possibly result in a permanent radio brick!
So that pretty much excludes any fully "official" ROM/RUU.
Your only option then is to s-off the phone by sunshine ($25 US) since the Verizon version can not be bootloader unlocked via HTCDev.com. Then you can unlock the bootloader, flash custom recovery TWRP, and flash a stock-ish ROM that meets your needs and preferences. You will also need to make sure you use a ROM that supports the Verizon variant, since it uses a different kernel from most other M8 vesions.
In short, the Verizon version (along with Sprint) are the worst M8 version for any folks outside of customers on those actual carriers (Verizon and Sprint) in the US. The Verizon version is especially bad, since unlocking the bootloader by HTCDev.com is blocked.
---------- Post added at 10:53 AM ---------- Previous post was at 10:48 AM ----------
Heavyweight_inc said:
I only want the Stock Official ROM, not interested in any Custom ROM due to the difficulty to install and also instability.
Click to expand...
Click to collapse
You won't be able to install another M8 version's stock RUU, as already mentioned. So a TWRP-flashable ROM is your only choice (besides staying stock Verizon).
Also, your misgivings about the instability of custom ROMs is incorrect, and not based on any reason evidence. There are plenty of stable custom ROMs, which also make the phone more functional by removing useless carrier bloat, and remove carrier restrictions like the tethering block.

redpoint73 said:
I can tell you concrete that you should not attempt to "fully convert" to any other version by flashing another version's RUU or firmware. Other firmware/RUUs are not compatible with the Verizon version, it won't work, and it can possibly result in a permanent radio brick!
So that pretty much excludes any fully "official" ROM/RUU.
Your only option then is to s-off the phone by sunshine ($25 US) since the Verizon version can not be bootloader unlocked via HTCDev.com. Then you can unlock the bootloader, flash custom recovery TWRP, and flash a stock-ish ROM that meets your needs and preferences. You will also need to make sure you use a ROM that supports the Verizon variant, since it uses a different kernel from most other M8 vesions.
In short, the Verizon version (along with Sprint) are the worst M8 version for any folks outside of customers on those actual carriers (Verizon and Sprint) in the US. The Verizon version is especially bad, since unlocking the bootloader by HTCDev.com is blocked.
---------- Post added at 10:53 AM ---------- Previous post was at 10:48 AM ----------
You won't be able to install another M8 version's stock RUU, as already mentioned. So a TWRP-flashable ROM is your only choice (besides staying stock Verizon).
Also, your misgivings about the instability of custom ROMs is incorrect, and not based on any reason evidence. There are plenty of stable custom ROMs, which also make the phone more functional by removing useless carrier bloat, and remove carrier restrictions like the tethering block.
Click to expand...
Click to collapse
Thanks for repply!
I totally regretted buying this smartphone!!!
Now, what's the best thing to do? Where do I start?
The issue of not wanting a "Custom ROM" is that I hate the tweaks that have to be done to get install and stable and also do not want to lose the look and functions of HTC Sense. What ROM most clean, simple to install and sense visual based do u recommend for me?
Anyway, any rom I install will have to pay the $ 25.00 to unlock via Sunshine? Why dont have this for Free?
Thanks!

Heavyweight_inc said:
Now, what's the best thing to do? Where do I start?
Click to expand...
Click to collapse
You should start by reading, researching, and learning. It's apparent that you are missing a lot of knowledge about this device, in particular the Verizon version.
In fact, such research would have prevented the mistake of buying the Verizon version M8, in the first place.
From there (after reading and learning) you will need to do kingroot to get root, then sunshine s-off, unlock bootloader. Then you can install TWRP and flash a custom ROM.
Heavyweight_inc said:
The issue of not wanting a "ROM Stock" is that I hate the tweaks that have to be done to get install and stable and also do not want to lose the look and functions of HTC Sense. What ROM most clean, simple to install and sense visual based do u recommend for me?
Click to expand...
Click to collapse
Your "hate" of the tweaks is misplaced. Even on a non-Verizon device, in order to install another version's official ROM, you would need s-off (which requires root) and to change CID. So even to change to a stock ROM, takes significant modifications. But again, do not attempt to do this on your Verizon device; as doing so is dangerous.
You are also not understanding the concept of custom ROMs properly. A custom ROM can still be Sense based. It's only the AOSP ROMs (Lineage, Resurrection Remix, etc.) and the Google Play Edition (GPE) ROMs which do not contain the Sense features and look.
There are a number of Verizon-compatible Sense custom ROMs, which are stable and quite good, including Viper, S.ROM, Wolla, and others.
Heavyweight_inc said:
Anyway, any rom I install will have to pay the $ 25.00 to unlock via Sunshine? Why dont have this for Free?
Click to expand...
Click to collapse
Unfortunately, for the Verizon version (and only the Verizon version) you need s-off in order to unlock the bootloader (which is required in order to flash custom recovery TWRP and flash ROMs). And sunshine is the only currently working method for s-off.
On most all other versions of the M8 (except Verizon) you can unlock the bootloader through HTCDev.com, which costs no money. You can thank Verizon for having this feature blocked.
As to why sunshine costs money, they developers have contributed lots of work to XDA, previously only working for donations. But they spent hundreds of hours working on sunshine, and bricked several devices in the process. Charging for s-off is simply so they can recoup there loses. If you ask "why isn't it free" then I ask you, would you do all that for free?
You may not like it, but it is what it is. You can search and read if you want to learn more about this topic. But it has literally been argued on both sides for dozens and dozens of forum pages. There is no complaint you can make about this, that hasn't already been made before.

HELP!
I think I have the same problem, Can any one guide me or give me somewhere to learn and help my self??

Ahmedyasssen said:
I think I have the same problem, Can any one guide me or give me somewhere to learn and help my self??
Click to expand...
Click to collapse
You should explain your problem in detail, not just say you have the "same problem".
I already explained to the OP, that trying to "fully convert" with stock RUU will brick the phone.