Develop Bugs

[Q] Can I re-lock my bootloader and S-ON without bricking?

I've converted my HTC One M8 (AT&T GSM) into a Google Play Edition device and changed the MID and CID so that they match those of a Google Play Edition HTC One M8 in order to receive OTA updates from Google. I used the method of flashing the Google Play Edition RUU file. I usually only flash custom ROMs for a purer Android experience such as Cyanogenmod; however, now that I'm running the purest version of any other version of Android, I would like to re-lock my bootloader and set my security back to S-ON because an unlocked bootloader and S-OFF opens up several security holes within the device which I take very seriously. My question is: can I re-lock my bootloader and turn S-ON without bricking my phone and still continue to receive OTA updates through Google?

Jephreyz said:
I've converted my HTC One M8 (AT&T GSM) into a Google Play Edition device and changed the MID and CID so that they match those of a Google Play Edition HTC One M8 in order to receive OTA updates from Google. I used the method of flashing the Google Play Edition RUU file. I usually only flash custom ROMs for a purer Android experience such as Cyanogenmod; however, now that I'm running the purest version of any other version of Android, I would like to re-lock my bootloader and set my security back to S-ON because an unlocked bootloader and S-OFF opens up several security holes within the device which I take very seriously. My question is: can I re-lock my bootloader and turn S-ON without bricking my phone and still continue to receive OTA updates through Google?
Click to expand...
Click to collapse
Yes you can, can you help me with something as well? I'm trying to change my mid but the changes never take effect. After I changed it I would type fastboot get var all & it's still the same mid as I had before. Help me out.

EternalAndroid said:
Yes you can, can you help me with something as well? I'm trying to change my mid but the changes never take effect. After I changed it I would type fastboot get var all & it's still the same mid as I had before. Help me out.
Click to expand...
Click to collapse
I used this thread: http://forum.xda-developers.com/showthread.php?t=2708581

Jephreyz said:
I used this thread: http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Tried but I can't get it to work. I'll try again.

EternalAndroid said:
Yes you can, can you help me with something as well? I'm trying to change my mid but the changes never take effect. After I changed it I would type fastboot get var all & it's still the same mid as I had before. Help me out.
Click to expand...
Click to collapse
Do you have any explanation for why you can or cannot?

Hmm not that I know of I just know it's possible without any harm.

EternalAndroid said:
Hmm not that I know of I just know it's possible without any harm.
Click to expand...
Click to collapse
Even in a converted circumstance?

Jephreyz said:
Even in a converted circumstance?
Click to expand...
Click to collapse
Correct.

[Q] Steps to convert to Dev Edition from AT&T?

I'm currently bone-stock AT&T, 4.4.2. I'm frustrated by the lack of OTAs from AT&T, especially given that the 4.4.4 was reportedly pulled. So I'm considering converting to Dev Edition to get timely updates and I'd like to make sure I have all of my ducks in a row before I begin.
Am I correct with these steps and order?
1. Unlock bootloader (htcdev key)
2. s-off
3. Change MID and CID as appropriate
4. Run the 5.0.1 RUU that HTC posted
5. ???
6. Profit
Thanks!

Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.

jshamlet said:
Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.
Click to expand...
Click to collapse
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?

OGhoul said:
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?
Click to expand...
Click to collapse
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.

jshamlet said:
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.
Click to expand...
Click to collapse
I've already got the tabs open for the adb steps for that on my home PC. Thanks a bunch; you've confirmed that I actually have learned something from lurking around here all this time.

I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.

vjaamm said:
I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.
Click to expand...
Click to collapse
Yes, except you *DO* have to change your MID.
http://forum.xda-developers.com/showthread.php?t=2708581

And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?

OGhoul said:
And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?
Click to expand...
Click to collapse
No you won't. The Developer edition has the latest firmware needed by the latest ROMs 4.x
So you'll be good to go.

I actually had to do some monkey business to get this to work.
I changed my CID to Super CID, then adb fastboot bootloader. Then ran the RUU .exe. This started to work, however it failed at I think step 5 telling me my CID was wrong, and the .exe told me to hold power for 10 seconds to reboot.
This then booted back into 4.4.2, and settings > about still said 4.4.2.
fastboot getvar all however, revealed all of the lollipop firmware settings.
So I rebooted to fastboot again, then changed my CID to the BS_US002.
Ran the RUU again. It took, and it's currently optimizing apps.

Big problem about S-off

Hello
I have bootloader unlocked, rooted HTC one M8. I want to use android revolution hd and to do that I need to flash a new firmware. I need to do "s-off". However I tried I failed that with "runrummer". I get this fail : (I dont wanna pay 25$ for sunshine)
Pouring (1) ......................
Pouring (2)
WTF: what are you doing.
Press Enter to exit.
I want to do s-off so badly and I can give more info. about the phone.
Thanks a lot

Runrunner doesn't work with the M8. Sunshine is the only working method

EddyOS said:
Runrunner doesn't work with the M8. Sunshine is the only working method
Click to expand...
Click to collapse
So you say There is no other way execpt sunshine ?

tugratolunay said:
So you say There is no other way execpt sunshine ?
Click to expand...
Click to collapse
Yep man. I use s-on for its ok all good

leos0000 said:
Yep man. I use s-on for its ok all good
Click to expand...
Click to collapse
That's nice, but you need to be S-Off to do certain things, like manually flashing firmware without reverting to stock, or using firmware meant for carriers other than yours when they update before your carrier.
There are other advantages as well, but these are the ones that S-Off is most used for.

tugratolunay said:
So you say there is no other way except Sunshine ?
Click to expand...
Click to collapse
That's exactly what I'm saying

tugratolunay said:
WTF: what are you doing.
Click to expand...
Click to collapse
"WTF what are you doing" indeed. Rumrunner never worked for this phone. It was for the M7. Firewater (related, but different from rumrunner) was for earlier M8 versions. It was an online service, and will no longer work now that the dev has stopped supporting it (so don't even bother asking).
For many variants, s-off is not needed to update firmware (as long as Lollipop has been released for your variant). You can just return to stock ROM and stock recovery, and OTA to Lollipop in order to update your firmware.

redpoint73 said:
"WTF what are you doing" indeed. Rumrunner never worked for this phone. It was for the M7. Firewater (related, but different from rumrunner) was for earlier M8 versions. It was an online service, and will no longer work now that the dev has stopped supporting it (so don't even bother asking).
For many variants, s-off is not needed to update firmware (as long as Lollipop has been released for your variant). You can just return to stock ROM and stock recovery, and OTA to Lollipop in order to update your firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2694994
I have used this rom (Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9) and I still cant use wifi or I cant restart the phone it stucks at HTC logo. Could you please help me about finding correct stock rom ? or is there only 1 stock rom I really dont know what to do so far or how do I return back..

tugratolunay said:
http://forum.xda-developers.com/showthread.php?t=2694994
I have used this rom (Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9) and I still cant use wifi or I cant restart the phone it stucks at HTC logo. Could you please help me about finding correct stock rom ? or is there only 1 stock rom I really dont know what to do so far or how do I return back..
Click to expand...
Click to collapse
There are different stock ROMs for different CIDs. Plus, if you have no WiFi, and extreme long boot times, its due to your firmware not being supported by the ROM. You need to find the stock ROM for your current firmware and CID. Then you also need to flash the corresponding stock recovery. After that, you can OTA to the latest firmware.
What is your CID, hboot number, and radio number?

redpoint73 said:
There are different stock ROMs for different CIDs. Plus, if you have no WiFi, and extreme long boot times, its due to your firmware not being supported by the ROM. You need to find the stock ROM for your current firmware and CID. Then you also need to flash the corresponding stock recovery. After that, you can OTA to the latest firmware.
What is your CID, hboot number, and radio number?
Click to expand...
Click to collapse
HBoot 3.16.0.0000
Radio-1.16.21331931.LA11G
Cid : CWS_001
by the way I bought this phone when I was in USA and I bought it from AT&T I dont know if it makes difference. I have a custom rom (4.4.2) its the only rom that I can use the phone and this rom is sux :'(

tugratolunay said:
HBoot 3.16.0.0000
Radio-1.16.21331931.LA11G
Cid : CWS_001
by the way I bought this phone when I was in USA and I bought it from AT&T I dont know if it makes difference.
Click to expand...
Click to collapse
Not only is that make a difference, it makes it easy to update your firmware. Just relock the bootloader and run the new Lollipop RUU: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Backup any important personal data before RUU, as RUU will wipe the phone.

redpoint73 said:
Not only is that make a difference, it makes it easy to update your firmware. Just relock the bootloader and run the new Lollipop RUU: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Backup any important personal data before RUU, as RUU will wipe the phone.
Click to expand...
Click to collapse
Would you mind I want you to explain the process how to do it or can you please give me link to follow the process?

tugratolunay said:
Would you mind I want you to explain the process how to do it or can you please give me link to follow the process?
Click to expand...
Click to collapse
1) To lock bootloader: Connect phone to PC (PC required for RUU). Boot phone into bootloader-fastboot mode. Open command prompt on computer, and type command: fastboot oem lock
2) Download RUU onto PC. With phone connected, run the RUU exectuble program on the PC and follow the instructions given.
3) Done, drink beer
A little more detail is given here under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
But seriously, the RUU is a self-explanatory program. It will tell you to confirm a couple dialogue boxes. But aside from that, the program will install a completely clean factory Lollipop software image.
Option Step) Unlock the bootloader again via HTCDev.com, then flash TWRP if you want to root or flash a custom ROM.

redpoint73 said:
1) To lock bootloader: Connect phone to PC (PC required for RUU). Boot phone into bootloader-fastboot mode. Open command prompt on computer, and type command: fastboot oem lock
2) Download RUU onto PC. With phone connected, run the RUU exectuble program on the PC and follow the instructions given.
3) Done, drink beer
A little more detail is given here under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
But seriously, the RUU is a self-explanatory program. It will tell you to confirm a couple dialogue boxes. But aside from that, the program will install a completely clean factory Lollipop software image.
Option Step) Unlock the bootloader again via HTCDev.com, then flash TWRP if you want to root or flash a custom ROM.
Click to expand...
Click to collapse
Cant I use the same unlock_code.bin ? and Will the at&t app be back? and will my SD card will be safe? Should I be in fastboot while doing RUU? or just homescreen?
Sorry for bothering you too much :/
***Tampered***
***relocked***
***security Warning**
M8_ul_ca
.
.
.
I cant open my phone, it always comes at this screen (bootloader). Is that normal?

tugratolunay said:
Cant I use the same unlock_code.bin ?
Click to expand...
Click to collapse
You can try it. It certainly doesn't hurts, as it only takes a single fastboot command, and would be faster than going through the whole HTCDev.com process (although that really doesn't take that much time, either).
I know using the same token has worked on past HTC devices. But I haven't seen much (if any) success on the M8. Most (or all?) folks have had to get a new token in order to unlock.
tugratolunay said:
Will the at&t app be back?
Click to expand...
Click to collapse
Yes, whatever AT&T apps are present on the stock Lollipop AT&T image will be on your phone. Simply root and delete/freeze, or install a custom ROM to be rid of the AT&T bloat.
tugratolunay said:
will my SD card will be safe?
Click to expand...
Click to collapse
You mean the removable SD? It should be safe. But you can always take it out before RUU to be sure it doesn't get touched by RUU.
Any other data on the phone (including the "virtual SD" AKA internal storage) should be backed up, if you want to keep it. Internal storage "might" be okay, but I'd back up anything you want to keep, just in case.
tugratolunay said:
Should I be in fastboot while doing RUU? or just homescreen?
Click to expand...
Click to collapse
Usually booted into OS works. But some folks have had to put the phone in fastboot mode.
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
tugratolunay said:
Sorry for bothering you too much :/
Click to expand...
Click to collapse
Its no bother. I enjoy helping others.
I only ask in return you click the "Thanks" button for any posts you found helpful.
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
tugratolunay said:
***Tampered***
***relocked***
***security Warning**
M8_ul_ca
.
.
.
I cant open my phone, it always comes at this screen (bootloader). Is that normal?
Click to expand...
Click to collapse
Yes, that is normal. Its expected that RUU will be run once you relock, so it makes the phone this way.
I always forget this, since I s-off my devices (no relocking necessary to RUU with s-off)

redpoint73 said:
I always forget this, since I s-off my devices (no relocking necessary to RUU with s-off)
Click to expand...
Click to collapse
After installing this RUU I will have original At&t rom and unroot, relocked bootloader phone. and it will be 5.0.1 lollipop. Am I right? and so firmware will be upgraded tho? That means I can Unlock it, root it and install that android revolution HD rom without having problems.

tugratolunay said:
After installing this RUU I will have original At&t rom and unroot, relocked bootloader phone. and it will be 5.0.1 lollipop. Am I right? and so firmware will be upgraded tho? That means I can Unlock it, root it and install that android revolution HD rom without having problems.
Click to expand...
Click to collapse
Yes, yes, and yes.
The only thing above that isn't completely correct, if that after you unlock the bootloader again, just install custom recovery and flash ARHD. No need to root before flashing a custom ROM. Installing a ROM wipes whatever you did with root anyway, and custom ROMs are always pre-rooted. So rooting manually is an unnecessary step. You only need to root "manually" if you are keeping the stock ROM.

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