Related
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.
Hi all,
I bought an AT&T HTC One (M8) set a year back and there is no Lollipop update till now. I have tried to reset the phone to factory setting as well. FYI, I'm living in Malaysia and i did not buy the phone directly from AT&T. Whenever i "check for updates" the message will be "No update is available for your device at this time. Your device will automatically check for an update within the next 48 hours." I always get this message from 1 year back till now.
Versions:
Android version: 4.4.2
HTC Sense version: 6.0
Software number: 1.58.502.1
HTC SDK API Level: 6.17
Kernel version: 3.4.0-gaabcaed [email protected] # 1 SMP PREEMPT (IS IT ROOTED?)
Baseband: 1.16.21331931.LA1 1G_20.31A.4145.02L
Build Number: 1.58.502.1 CL335549 release-keys
Maybe because you're not connected to their network.
You can run AT&T RUU to manually update it to lollipop.
Read this : http://forum.xda-developers.com/showthread.php?t=2751432
Use that RUU 5.0.2
If you are willing to shell out the $25, you can also S-off, install the Developer Edition, and essentially have the same thing, except debloated and easily rootable. The developer edition phones are AT&T phones (same MID) with an unlocked bootloader and no SIM lock.
jshamlet said:
If you are willing to shell out the $25, you can also S-off, install the Developer Edition, and essentially have the same thing, except debloated and easily rootable. The developer edition phones are AT&T phones (same MID) with an unlocked bootloader and no SIM lock.
Click to expand...
Click to collapse
What do you mean by 'shell out the $25'?
ckpv5 said:
Maybe because you're not connected to their network.
You can run AT&T RUU to manually update it to lollipop.
Read this : http://forum.xda-developers.com/showthread.php?t=2751432
Use that RUU 5.0.2
Click to expand...
Click to collapse
How to know whether my phone is S-on or S-off? (idk what this is).
Can i use the RUU directly?
hustlerism said:
How to know whether my phone is S-on or S-off? (idk what this is).
Can i use the RUU directly?
Click to expand...
Click to collapse
1. Boot to bootloader you will see it's written there either S-On or S-Off.
But not to worry so much on this as I believe you have a stock device. You need to see whether it is written "LOCKED" or "RELOCKED" or "UNLOCKED" there.
2. If it is "LOCKED" or "RELOCKED" - just run the RUU directly and follow the instructions.
Note : this will wipe everything in your internal storage ... make a backup of your important files like musics, photos & etc to PC before you proceed RUUing your device.
hustlerism said:
What do you mean by 'shell out the $25'?
Click to expand...
Click to collapse
That is the cost to go S-off with Sunshine, which is required to change the CID. Theoretically, you could skip that, just unlock the bootloader, and restore a nandroid backup. However, if you change the CID you can use an official RUU and get OTA updates.
jshamlet said:
If you are willing to shell out the $25, you can also S-off, install the Developer Edition, and essentially have the same thing, except debloated and easily rootable. The developer edition phones are AT&T phones (same MID) with an unlocked bootloader and no SIM lock.
Click to expand...
Click to collapse
I'm not getting any of this. Should i just follow ckpv5 instructions?
hustlerism said:
I'm not getting any of this. Should i just follow ckpv5 instructions?
Click to expand...
Click to collapse
If you aren't clear on how to do the conversion, then yes - just get the AT&T RUU and be done with it.
jshamlet said:
If you aren't clear on how to do the conversion, then yes - just get the AT&T RUU and be done with it.
Click to expand...
Click to collapse
Alright thanks.:good:
How long?
ckpv5 said:
Maybe because you're not connected to their network.
You can run AT&T RUU to manually update it to lollipop.
Read this : http://forum.xda-developers.com/showthread.php?t=2751432
Use that RUU 5.0.2
Click to expand...
Click to collapse
How long does it take? Mines been "Updating..(0/6) Sending" for over an hour even though it says it only takes 10 minutes.
Update: Ok, it was taking so long because it wasn't doing anything. Not sure if its my port but apparently updating your M8 through the RUU won't work with USB 3.0. I would recommend to use a USB 2.0 port and if possible the original USB cable that came with the phone.
ShibeInus said:
How long does it take? Mines been "Updating..(0/6) Sending" for over an hour even though it says it only takes 10 minutes.
Update: Ok, it was taking so long because it wasn't doing anything. Not sure if its my port but apparently updating your M8 through the RUU won't work with USB 3.0. I would recommend to use a USB 2.0 port and if possible the original USB cable that came with the phone.
Click to expand...
Click to collapse
Do i need to connect to the internet as well?
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
Hi guys, I got the HTC 10 bell variant at a good price and since is my back up phone I'm trying to put it to the test to change it from bell variant to the US variant, I was reading a lot of threads but im confused, , I unlocked the bootloader, I instaled the twrp, now how do i change the CID ??mine shows 666, and I want to change it to 617 , do I have to have S-OFF?? or I can do that with S-ON since the Bootloader is unlocked , will I get the OTA updates for the 617 after i change it?? (btw i dont want to chage it to 401 international because im afraid i will loose the band 4 LTE )
I'm with bell and changed to us unlocked. There might be a way to do it without s-off like maybe super cid. But to install ruu.exe you need s-off. You will get ota but to apply all you need is to reinstall stock recovery.
Sent from my HTC 10 using Tapatalk
You can't change your CID and flash the Unlocked version without S-OFF.
Thanks guys for your replays ,btw nitramus can u pls add a step by step how I did it??I'm new with the HTC
Since you're at the cid part just look for the thread for changing cid and flash ruu. And look at the thread with all the backups for all the versions or stock rom. You will have all you need, latest available rom with ota. To prevent any problems as soon as your phone is ready to use after ruu and you logged in to you account apply ota right away, then flash supersu and have fun.
Sent from my HTC 10 using XDA-Developers mobile app
But first do I have to take s-off??I mean to change from s-on to s-off
nutzuTo said:
But first do I have to take s-off??I mean to change from s-on to s-off
Click to expand...
Click to collapse
Yes to convert your phone to U.S Unlocked you'd have to S-off to be able to change your CID. You gotta pony up the 25 USD, which is worth it in my opinion if you're gonna use the 10 as your main phone and tinker with it for a year or two.
Basically follow the steps from this guide, and when it comes to flashing an RUU use the Unlocked one you can download directly from HTC.com
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
BTW it's very fitting that Bell's CID is 666
Tarima said:
Yes to convert your phone to U.S Unlocked you'd have to S-off to be able to change your CID. You gotta pony up the 25 USD, which is worth it in my opinion if you're gonna use the 10 as your main phone and tinker with it for a year or two.
Basically follow the steps from this guide, and when it comes to flashing an RUU use the Unlocked one you can download directly from HTC.com
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-drand-convert-htc-10-to-t3374593
BTW it's very fitting that Bell's CID is 666
Click to expand...
Click to collapse
OK did that so I have S-off, I changed the CID on the cmd , and than I flashed with RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5 than update to the latest ones that they pop up to update, nice Thank you ,btw if i want to change S-on will impact the updates or should i keep it S-off??
Personally I don't bother to change back but if security is important for you then maybe. Later depending if you want to change things again depending on what you do you might still need s-off.
Sent from my HTC 10 using XDA-Developers mobile app
nutzuTo said:
OK did that so I have S-off, I changed the CID on the cmd , and than I flashed with RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5 than update to the latest ones that they pop up to update, nice Thank you ,btw if i want to change S-on will impact the updates or should i keep it S-off??
Click to expand...
Click to collapse
If you are rooted and/or have a custom recovery, you can't use the official OTAs. You'll need the stock and never rooted ROM (it has to have an unmodified system partition), and also the stock recovery to flash it.
The easiest (and often quicker way than waiting for an official OTA) is to just flash a firmware.zip package in either fastboot or by the rename/SD card method.
I recommend the ones on this thread. You can find both Full Stock .zips there, that will wipe your phone (because they contain the boot.img), and No-Wipe .zips that won't wipe your phone (obviously) as they have the boot.img (kernel and ramdisk) removed, and also contain the latest TWRP recovery versions instead of the stock recovery.
nutzuTo said:
OK did that so I have S-off, I changed the CID on the cmd , and than I flashed with RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5 than update to the latest ones that they pop up to update, nice Thank you ,btw if i want to change S-on will impact the updates or should i keep it S-off??
Click to expand...
Click to collapse
To add regarding future OTA updates, if you want them directly from HTC you'll also have to remove SuperCID, if you have it. Just having a stock/unmodified system and recovery isn't enough.
And I agree, just keep S-off unless you're making a warranty claim.
Tarima said:
To add regarding future OTA updates, if you want them directly from HTC you'll also have to remove SuperCID, if you have it. Just having a stock/unmodified system and recovery isn't enough.
And I agree, just keep S-off unless you're making a warranty claim.
Click to expand...
Click to collapse
I was hoping someone might have the official stock firmware including recovery, from bell? I have to send my phone in for warranty repair. I have my stock system backed up and am on firmware 121.666... I have s-off and boot loader locked status. I have super cid 11111111. Any help will be reciprocated. Thank you for any help.
Salem's galaxy said:
I was hoping someone might have the official stock firmware including recovery, from bell? I have to send my phone in for warranty repair. I have my stock system backed up and am on firmware 121.666... I have s-off and boot loader locked status. I have super cid 11111111. Any help will be reciprocated. Thank you for any help.
Click to expand...
Click to collapse
Hey, did you get this figured out?
I have a stock backup in my recovery, might work. Might not lol..
Was thinking of going US since Bell still has not pushed an update out..
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