Develop Bugs

Error going back to stock.

I'm trying to get back to stock so I can flash the HTC OTA. When I try and get my main version it's blank, there's nothing there. I'm S-Off.

EchoX860 said:
I'm trying to get back to stock so I can flash the HTC OTA. When I try and get my main version it's blank, there's nothing there. I'm S-Off.
Click to expand...
Click to collapse
That's most likely due to the bug that was in earlier versions of TWRP. What device do you have i.e Verizon, T-Mobile, International WWE. More specifically perhaps, what's your CID?

BerndM14 said:
That's most likely due to the bug that was in earlier versions of TWRP. What device do you have i.e Verizon, T-Mobile, International WWE. More specifically perhaps, what's your CID?
Click to expand...
Click to collapse
My recovery is PhilZ, I also had the same issue with TWRP. My CID is 11111111

EchoX860 said:
My recovery is PhilZ, I also had the same issue with TWRP. My CID is 11111111
Click to expand...
Click to collapse
Yeah being SuperCID isn't going to help much with going back to stock. Don't you know what CID you had before you changed to SuperCID? Or what device you had? AT&T branded phone, T-Mobile, International WWE, if it's some of the big "names" then perhaps we can still refer to some backups etc, if its something like TIM Italy then
Unless you want to convert to International WWE seeing as you're S-OFF?

BerndM14 said:
Yeah being SuperCID isn't going to help much with going back to stock. Don't you know what CID you had before you changed to SuperCID? Or what device you had? AT&T branded phone, T-Mobile, International WWE, if it's some of the big "names" then perhaps we can still refer to some backups etc, if its something like TIM Italy then
Unless you want to convert to International WWE seeing as you're S-OFF?
Click to expand...
Click to collapse
VZW_001 was my CID.

EchoX860 said:
VZW_001 was my CID.
Click to expand...
Click to collapse
That clears things up a bit :good:
http://forum.xda-developers.com/showpost.php?p=55639805&postcount=2060
There I have some links to Verizon stuff. Including a link to the stock recovery and backups.
[GUIDE] RETURN TO STOCK(Mostly)
Also for Verizon. I'm pretty sure there's an RUU for Verizon as well, you could always run that and return to stock on your device.

[Q] Changing from unlocked (617) to international (401) with s-off

Hey guys,
I own an original unlocked M9 (1.32.617.30) and want to convert it to the international model for the quicker updates.
Just got it S-OFF and wanted to make sure I got the rest of the steps right:
1. Change MID to 0PJA10000
2. Change CID to 11111111 (or to HTC__001? which is better?)
3. Run 1.32.401.17 RUU (is it possible to run 1.40.401.8 RUU instead? or do I need to flash a 1.32 base first?)
Cheers! Trying to avoid a bricked phone :angel:

Jhonys said:
Hey guys,
I own an original unlocked M9 (1.32.617.30) and want to convert it to the international model for the quicker updates.
Just got it S-OFF and wanted to make sure I got the rest of the steps right:
1. Change MID to 0PJA10000
2. Change CID to 11111111 (or to HTC__001? which is better?)
3. Run 1.32.401.17 RUU (is it possible to run 1.40.401.8 RUU instead? or do I need to flash a 1.32 base first?)
Cheers! Trying to avoid a bricked phone :angel:
Click to expand...
Click to collapse
Who is your carrier?
You shouldn't need to change your mid. Just change to super cid and you can flash the latest firmware and any custom rom you want.
If you're AT&T, the 401 firmware should work seamlessly, you just probably will not get voLte. If you're tired mobile, 401 firmware should also work, but no Wi-Fi calling (you should confirm this because I'm really not sure). If you're Verizon or Sprint, I have no idea, but I think you're sol and have to wait until they release an update. .
Edit: nevermind about carrier stuff. Didn't see that you have dev edition. 401 firmware should all work.

jollywhitefoot said:
Who is your carrier?
You shouldn't need to change your mid. Just change to super cid and you can flash the latest firmware and any custom rom you want.
If you're AT&T, the 401 firmware should work seamlessly, you just probably will not get voLte. If you're tired mobile, 401 firmware should also work, but no Wi-Fi calling (you should confirm this because I'm really not sure). If you're Verizon or Sprint, I have no idea, but I think you're sol and have to wait until they release an update. .
Edit: nevermind about carrier stuff. Didn't see that you have dev edition. 401 firmware should all work.
Click to expand...
Click to collapse
I'm not in the US, but europe. I've bought the phone through HTC US and that's why i'm on 617.
Regarding the MID, it is only because it is listed as a step here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
And when you say "flash latest firmware" what do you mean exactly? should I install 1.40 RUU or 1.32.401.17 RUU first? I really want to know Im flashing the right file now that i'm S-OFF.

Jhonys said:
I'm not in the US, but europe. I've bought the phone through HTC US and that's why i'm on 617.
Regarding the MID, it is only because it is listed as a step here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
And when you say "flash latest firmware" what do you mean exactly? should I install 1.40 RUU or 1.32.401.17 RUU first? I really want to know Im flashing the right file now that i'm S-OFF.
Click to expand...
Click to collapse
Gotcha. I didn't understand your desires. I thought you were basically asking how to upgrade your firmware and flash a rom. Probably you should ask in that thread and maybe clsA or someone else in that thread can give you specific advise. I assume you're looking to convert to stock 401/0PJA10000 and receive official otas?

This might help you as well.. its an A,B, C ... guide
http://www.droidviews.com/how-to-restore-htc-one-m9-to-stock/
From what Im aware, I thought Sunshine 3.17 only supports 501... arent we on 502?

Thanks guys I followed the guide from clsA and it worked perfectly. :good:

Yup! If you have a GSM M-9 than it's easy as pie! S-OFF, Super CID, Flash Firmware, Flash Rom! BAM! DONE!

Can executable RUUs be used to downgrade?

There's something that I'm a bit unclear on when it comes to RUUs
Let's say that I'd like to try out the latest Marshmallow release without waiting for the OTA and use the HTC-provided RUU .exe (3.35.617.12)
I'm on a T-Mobile branded M9 and would like to keep WiFi Calling and Visual Voicemail. If I find that I am unable to use these features in the non-branded HTC MM release, will I simply be able to use the T-Mobile branded RUU .exe (2.11.531.19) to revert back or will I be unable to as it's an older version (Android 5.1)
I'm currently still locked and S-ON
I seem to remember downgrades not being possible on my M7 once the hboot was updated to a newer version, but am a bit confused about the specifics of the M9
Thank you, and my apologies if this is a dumb question -- I've done my best to find an answer through searching

You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.

But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)

asestar said:
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
Click to expand...
Click to collapse
Well, now I'm a bit confused as far as variants are concerned. This HTC release page states
This software upgrade comes in the form of two sequential updates. The first update will install software version 2.11.617.180 , which does not include the Android OS upgrades. The following update will install software version 3.35.617.12 , which includes the changes to the Android OS.
Click to expand...
Click to collapse
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Flippy498 said:
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
Click to expand...
Click to collapse
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 2.11.531.19
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50731G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
Click to expand...
Click to collapse

Miguel_Lancaster said:
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
Click to expand...
Click to collapse
Correct. 617 is the SKU for the unlocked/developer edition and 531 belongs to T-Mobile US.
Miguel_Lancaster said:
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Click to expand...
Click to collapse
1) Correct.
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Miguel_Lancaster said:
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
Click to expand...
Click to collapse
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)

asestar said:
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Click to expand...
Click to collapse
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
asestar said:
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
Click to expand...
Click to collapse
Phone was just purchased used, so if there's any warranty period left it probably isn't for very much longer. In the past I've gone S-OFF for all my HTC devices (Incredible, then One S, then One M7) but they've always seemed to have their own unique quirks and this M9 appears to be no different.
My main reasoning for staying S-ON/Stock at the moment is just in case I find a reason to return the device to the seller. After a few days when I'm sure everything is alright with it, I'm sure I'll be less reluctant to tweak.
Is a bootloop easily fixable?
So, to clarify (again!) --
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Thanks a bunch for your responses. I'm sure this stuff gets answered all the time, but it can sometimes be difficult to find a specific answer in the depths of these boards. Plus, I find it hard to keep 100% on all development when I only buy a new device every couple of years.
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.

Miguel_Lancaster said:
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
Click to expand...
Click to collapse
The difference between rom and firmware.
Miguel_Lancaster said:
Is a bootloop easily fixable?
Click to expand...
Click to collapse
Just reflash a RUU. The problem for most non-US firmwares is that HTC doesn't provide RUUs so sometimes there is no freely accessible RUU for a specific firmware version. (The only other method besides flashing a RUU is restoring a TWRP backup or re-/flashing a custom rom which needs an unlocked bootloader and TWRP.) If someone decides to re-S-ON and to lock/relock and the rom doesn't boot then that person might not be able to fix that bootloop without this RUU service. (The same applies to S-ON users who decide to relock if the rom doesn't boot.) HTC introduced a new security feature with Android 5.1 (firmware 2.x and higher). It prevents the bootloader unlock if the option OEM Unlock isn't activated in developer options. That's why I recommend everyone staying S-OFF and unlocked unless you need to send your phone back to HTC for a warranty claim since even OTAs can be installed with an unlocked bootloader. Well, RUU.exe deny to flash with S-ON and an unlocked bootloader but there are not many RUU.exe for non-US firmware versions and you can always extract the RUU.zip from a RUU.exe. (RUU.zip files can be flashed via an external SD card even if the bootloader is unlocked.)
Miguel_Lancaster said:
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
Click to expand...
Click to collapse
Correct if you're talking about Sense roms.
Miguel_Lancaster said:
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
Click to expand...
Click to collapse
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem writemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BS_US002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Miguel_Lancaster said:
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Click to expand...
Click to collapse
Correct.
Miguel_Lancaster said:
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Click to expand...
Click to collapse
Don't know about ARHD but Viper has that feature.
Btw: Getting S-OFF is quite easy but it costs 25 USD. You simply need to use the Sunshine App. (Or you look for someone who has a java card.)

Thank you for taking the time to answer all of my questions.

No problem. Maybe those detailed answers might help other users as well. (That's at least what I hope. )

Flippy498 said:
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem changemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BSUS_002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Click to expand...
Click to collapse
**** --
I changed my MID to the Developer edition, but I accidentally used the letter O and not the number 0 -- so OPJA11000
Then I attempted an RUU and now my phone is stuck in the RUU screen and I can't even turn it off. Is there any way to recover this? I don't even think I can use ADB anymore.
edit: I got it to reboot by holding BOTH volume buttons and POWER. What a stupid mistake. I'll leave this here though so hopefully no one else does anything so stupid.
Yikes :silly:
edit 2: Hmm, changed MID to the correct value but I'm still getting ERROR 131 CUSTOMER ID ERROR during RUU. Will have to investigate this further. Maybe I need to relock the bootloader.
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
edit 3: Relocking the bootloader still gives the same error RUU. Now I'm stumped.
edit 4: Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
edit 5: Yup, fixing the CID solved the problem

Miguel_Lancaster said:
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
Click to expand...
Click to collapse
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Miguel_Lancaster said:
Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
Click to expand...
Click to collapse
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.

Flippy498 said:
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Click to expand...
Click to collapse
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.

Miguel_Lancaster said:
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Click to expand...
Click to collapse
That whole "0" or "O" bull**** ...
Cost me 3 days of heartache getting errors...
Yeah....that structure is a horrible idea....g

Can I safely revert to Android 6.x? (From 7) using RUU?

I updated my HTC 10 to the brand new 7.0. It seems either Google or HTC has totally broken the long pause conference call pin feature in android. (This is where you dial a number and a conference pin separated by a semi-colon like XXXXXXXXXX;XXXXX) The popup asking me if I want to send the Pin number disappears after about 3 or 4 seconds way before the "Beep" when i need to send the pin.
Total deal breaker for me, since I make conference calls ALL day and I'm not going to revert to writing pin numbers on my hand while i'm in the car so I can dial them at the beep.
I desperately need to go back to Android 6.0.
I have lots of flashing, unlocking, and custom rom experience, but this device has some strange quirks like breaking the radio if you decrypt the file system...
Do I just need to use an android 6.0 RUU?
Will there be any issues due to encryption, 7.0 firmware, or anything else I need to be careful of when downgrading?

I am wondering too about downgrading procedure...
I want to know if it is safe using ruu.
I want to convert my international Htc 10 to developer unlocked and flash ruu so I can receive the nougat it's just to try it out.
Can I reverse this?
Looking forward to that answer.

If you're s-off it should be ok I think. But without s-off, downgrading firmware using an official RUU is not possible

sardelisp said:
I am wondering too about downgrading procedure...
I want to know if it is safe using ruu.
I want to convert my international Htc 10 to developer unlocked and flash ruu so I can receive the nougat it's just to try it out.
Can I reverse this?
Looking forward to that answer.
Click to expand...
Click to collapse
I was on Viper 3,5. I converted my cid-mid to us unlocked and installed latest US UNLOCKED MM RUU.exe successfuly. Then I checked the firmware and took the official OTA,upgraded to Nougat successfuly. So I guess you can have Nougat,too.
Now I am on Nougat US Unlocked S-off cid BS_US001 mid 2PS650000 . I am wondering if I could revert to MM with the RUU.exe I have. Do I have to change to Supercid or do anything else,or just the RUU.exe would do the trick?

ordeniz said:
I was on Viper 3,5. I converted my cid-mid to us unlocked and installed latest US UNLOCKED MM RUU.exe successfuly. Then I checked the firmware and took the official OTA,upgraded to Nougat successfuly. So I guess you can have Nougat,too.
Now I am on Nougat US Unlocked S-off cid BS_US001 mid 2PS650000 . I am wondering if I could revert to MM with the RUU.exe I have. Do I have to change to Supercid or do anything else,or just the RUU.exe would do the trick?
Click to expand...
Click to collapse
I downgraded back to 6 from 7 with no issues

gillim74 said:
I downgraded back to 6 from 7 with no issues
Click to expand...
Click to collapse
You were like me?

ordeniz said:
You were like me?
Click to expand...
Click to collapse
Yeah

gillim74 said:
I downgraded back to 6 from 7 with no issues
Click to expand...
Click to collapse
And when you say you downgraded..
Were you S-Off? (I'm not and since you said you were like ordeniz, I assume you were?)
Were you on the official 7 OTA (with firmware upgraded) or a custom rom built on 7 but without the firmware upgrade? (Again, if you were like ordeniz then you had the official OTA.)
I just wanted to be clear, and not make any assumptions.

x51 said:
And when you say you downgraded..
Were you S-Off? (I'm not and since you said you were like ordeniz, I assume you were?)
Were you on the official 7 OTA (with firmware upgraded) or a custom rom built on 7 but without the firmware upgrade? (Again, if you were like ordeniz then you had the official OTA.)
I just wanted to be clear, and not make any assumptions.
Click to expand...
Click to collapse
I am s-off converted my htc 10 to us unlocked as its the verizon variant upgraded to nougat didnt reallly like it so i downgrade back to 1.96

Tarima said:
If you're s-off it should be ok I think. But without s-off, downgrading firmware using an official RUU is not possible
Click to expand...
Click to collapse
gillim74 said:
I am s-off converted my htc 10 to us unlocked as its the verizon variant upgraded to nougat didnt reallly like it so i downgrade back to 1.96
Click to expand...
Click to collapse
OK. Thanks to all.
Guess I need to S-Off. (I hope sunshine works on 7.0) or I'm pretty well screwed.

x51 said:
OK. Thanks to all.
Guess I need to S-Off. (I hope sunshine works on 7.0) or I'm pretty well screwed.
Click to expand...
Click to collapse
As of now i dont think sunshine does

The sure thing I know is that you need to be rooted to be s-off. If sunshine will succeed you will know it when the sunshine app check your system. Download the app and before in app purchase a licence will tell you if you have successfull s off.

incallui.apk
Would someone be so kind as to upload a copy of InCallUI.apk from a 6.x Rom.
It's located in
/system/priv-app/InCallUI

HTC 10 T-Mobile Oreo firmware

I've been looking everywhere for an Oreo firmware on the web. Is there one out there?

mcarden2006 said:
I've been looking everywhere for an Oreo firmware on the web. Is there one out there?
Click to expand...
Click to collapse
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126

yldlj said:
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
Click to expand...
Click to collapse
Sorry I should have been more specific. I found the link you sent me but I wasn't too sure if the t-mobile firmware De and pl will work with USA variants. The one I have is T-mob010.

mcarden2006 said:
Sorry I should have been more specific. I found the link you sent me but I wasn't too sure if the t-mobile firmware De and pl will work with USA variants. The one I have is T-mob010.
Click to expand...
Click to collapse
Tmob010 is there. Not sure if it's the same but it matches your cid. Usually you can tell from the 3rd set of numbers in the firmware. x.xx.111.xx

Alonso2019.2019 said:
hello check here link removed
Click to expand...
Click to collapse
Please stop spamming this forum with links to easy-firmware where you have to pay for them. There are downloads linked on XDA that are free
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
mcarden2006 said:
Sorry I should have been more specific. I found the link you sent me but I wasn't too sure if the t-mobile firmware De and pl will work with USA variants. The one I have is T-mob010.
Click to expand...
Click to collapse
The thread he linked you to has that firmware, but you can only flash them (full wipe and no wipe are both linked there) if you are S-Off. They aren't signed so if you're S-On you can't flash them.
EDIT: You can flash the RUU for your version if you are S-On as well as S-Off. Download it from here

Alonso2019.2019 said:
hello check here https://easy-firmware.com/home/browse/category/id/5/
Click to expand...
Click to collapse
Reported for spam......

Mr Hofs said:
Reported for spam......
Click to expand...
Click to collapse
I think I beat you to it

xunholyx said:
Please stop spamming this forum with links to easy-firmware where you have to pay for them. There are downloads linked on XDA that are free
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
The thread he linked you to has that firmware, but you can only flash them (full wipe and no wipe are both linked there) if you are S-Off. They aren't signed so if you're S-On you can't flash them.
EDIT: You can flash the RUU for your version if you are S-On as well as S-Off. Download it from here
Click to expand...
Click to collapse
I took a look at what do and pl are and they are both European. Would it work for USA variant? I am s-off, bootloader unlocked, and rooted.

mcarden2006 said:
I took a look at what do and pl are and they are both European. Would it work for USA variant? I am s-off, bootloader unlocked, and rooted.
Click to expand...
Click to collapse
I'm sorry. I should have looked at the posts better. I saw the links and mention of T-Mo Germany and just went with that. The CID for T-Mo US is T-MOB010 and for Germany it's T-MOB101, so I didn't notice.
I don't think T-Mo has updated to Oreo for the US yet. I do know there were issues with the one for US Unlocked, and the RUU has been pulled from their website for download. That's the second time they removed it (or maybe the third?). You can find it here on XDA, but I haven't flashed it yet because of the issues with it that have been reported (I'm US Unlocked).
The WWE version I think has less problems, but there isn't an RUU for it. Flashing the 2.41.401.41 RUU (WWE) then checking for updates in settings brings up the one for Oreo via OTA, so maybe that hasn't been pulled for a reason?
Since you are S-Off, you could change your CID and MID and flash the 2.41.401.41. RUU and update that way. The WWE firmware works fine in the US (except for on Sprint and maybe Verizon) so you wouldn't have to worry about much except for maybe some T-Mo specific things (like VoWIFI)
If you need instructions on how to do this, just reply to this and I'll do that for you.

xunholyx said:
I'm sorry. I should have looked at the posts better. I saw the links and mention of T-Mo Germany and just went with that. The CID for T-Mo US is T-MOB010 and for Germany it's T-MOB101, so I didn't notice.
I don't think T-Mo has updated to Oreo for the US yet. I do know there were issues with the one for US Unlocked, and the RUU has been pulled from their website for download. That's the second time they removed it (or maybe the third?). You can find it here on XDA, but I haven't flashed it yet because of the issues with it that have been reported (I'm US Unlocked).
The WWE version I think has less problems, but there isn't an RUU for it. Flashing the 2.41.401.41 RUU (WWE) then checking for updates in settings brings up the one for Oreo via OTA, so maybe that hasn't been pulled for a reason?
Since you are S-Off, you could change your CID and MID and flash the 2.41.401.41. RUU and update that way. The WWE firmware works fine in the US (except for on Sprint and maybe Verizon) so you wouldn't have to worry about much except for maybe some T-Mo specific things (like VoWIFI)
If you need instructions on how to do this, just reply to this and I'll do that for you.
Click to expand...
Click to collapse
Thank you so much for the info. Would you be able to post a link or a walk through to change from T-Mobile to USA unlocked? That would be so awesome in more ways. I also have an HTC U11 Life T-Mobile and unfortunately sunshine hasn't updated the s-off yet. T-Mobile stated I have to use the service for 40 days or an equivalent of $100 to unlock. Bootloader, tarp, and root with a new flash and unlocked it.

mcarden2006 said:
Thank you so much for the info. Would you be able to post a link or a walk through to change from T-Mobile to USA unlocked? That would be so awesome in more ways. I also have an HTC U11 Life T-Mobile and unfortunately sunshine hasn't updated the s-off yet. T-Mobile stated I have to use the service for 40 days or an equivalent of $100 to unlock. Bootloader, tarp, and root with a new flash and unlocked it.
Click to expand...
Click to collapse
You just need to change the CID. The MID will already be correct.
In bootloader mode:
fastboot oem writecid BS_US001
Then you'll be able to flash the US Unlocked stuff.
For the U11 Life, I'm assuming you mean unlock the bootloader and not SIM unlock?
You can unlock it via htcdev.com just like most HTCs. T-Mo reps (and reps from pretty much any carrier) don't know F all. You need to elevate your requests to someone who knows somwthing. The people who answer you calls aren't technicians. They know squat. Same goes for salesmen at the stores.
At https://www.htcdev.com just choose "all other supported models" at the bottom of "select your device" and follow the instructions given on the website

xunholyx said:
You just need to change the CID. The MID will already be correct.
In bootloader mode:
fastboot oem writecid BS_US001
Then you'll be able to flash the US Unlocked stuff.
For the U11 Life, I'm assuming you mean unlock the bootloader and not SIM unlock?
You can unlock it via htcdev.com just like most HTCs. T-Mo reps (and reps from pretty much any carrier) don't know F all. You need to elevate your requests to someone who knows somwthing. The people who answer you calls aren't technicians. They know squat. Same goes for salesmen at the stores.
At https://www.htcdev.com just choose "all other supported models" at the bottom of "select your device" and follow the instructions given on the website
Click to expand...
Click to collapse
Thank you for the info. I'm going to rework the cid and get Oreo installed. You've been very helpful and thank you so much for your time and patience with me.