some quastion about this phone - One (M8) Q&A, Help & Troubleshooting

hi all
after reading too much about this phone im really confused about some of things that i need to ask them from you guys
1-can s-off be blocked by htc?
2-what is hboot? is it down gradable ?
3-what are the most awful things about this phone ?
thank all of you guys

1) HTC could only block S-OFF by releasing a firmware update that patches the exploit used to gain S-OFF. Anyone who is not S-OFF already and updates, would not be able to use whatever method existed previously to S-OFF.
2) Hboot is technically just one file out of the firmware file package that makes up the bootloader screen and reports the firmware version number or hboot version number. This can get confusing because technically one could just flash or update an hboot, without updating the rest of the device firmware so, while the hboot version will show to be one version, the rest of the firmware files to match that hboot version may not actually be those pertaining to the hboot version projected. Hence, it is usually within best practice to update your hboot along with the rest of the firmware files that have been updated with that hboot version. It is common practice on XDA to refer to the entire group of firmware files from an hboot version as simply the hboot.
Typically updating one's hboot is done by flashing an HTC signed RUU or OTA. But can also be done by flashing the firmware.zip file contained within them respectively. It is important to note, if just flashing the firmware.zip files, they must be done sequentially or altered properly to contain all sequential updates otherwise one will brick and probably require JTAG.
3) After unlocking and modding my phone to my liking, I have not one complaint. This phone is everything I wanted in a phone when setting out to upgrade.
Sent from my HTC One_M8 using xda app-developers app

i have 3 more quastions
1-what happens if i receive the phone after s-off is blocked. can devs make s-off again? can i downgrade and s-off my phone? (im going to buy a unlocked version)
2-can i s-off my phone again after flashing ruu and s-on?
3-will i lose s-off if htc fixes the bug and i update my phone?

pedyvirus said:
i have 3 more quastions
1-what happens if i receive the phone after s-off is blocked. can devs make s-off again? can i downgrade and s-off my phone? (im going to buy a unlocked version)
2-can i s-off my phone again after flashing ruu and s-on?
3-will i lose s-off if htc fixes the bug and i update my phone?
Click to expand...
Click to collapse
1) There is a good chance your phone will not come with any updated firmware if you order it in the near future. That being said, I am not a fortune teller..I have no idea if future updates will be able to achieve S-OFF should they be released.
2) Once you achieve S-OFF, it remains so until you manually force S-ON. If you force S-ON after updating to a firmware that cannot be exploited, you will not be able to get S-OFF until an exploit is found if one is found, however there is never any real good reason to S-ON unless you're trying to trick HTC into honoring the warranty you knew you were forgoing upon unlocking your bootloader.
3) see answer to 2.
*****EDIT*****
I felt I should add that money and or money and knowledge can get your phone S-OFF in just about any state assuming your hardware is working fine. A riff box and some knowhow or a JTAGG service if you don't have the knowhow can always put your phone in an S-OFF state.
Sent from my HTC One_M8 using xda app-developers app

Related

[Q] Strange CID and Stock update help please?

Hi there.
I'm new to the forum but have lurked and used some of the great information and tools that are available here.
So firstly, thank you.
Now.
I bought my One X in China (Where I live), in around August. It seems as though the one I got isn't a regular One X and because of that I'm having some problems.
A month and a half or so ago I installed an AOKP Rom which I've had some pretty intense bugs with, such as the the phone restarting whenever I toggle WiFi on or off. Because of that, I finally attempted to return to stock today. After a while, I found some success. I restored my nandroid backup, reflashed the stock recovery and relocked the bootloader. Happy that I was back to normal, I went to download the Jelly Bean OTA update, but kept having errors when doing so. (The green bar would reach about 1/3 of the way and then a red triangle showed up.) I've tried to troubleshoot and in doing so have found out that my CID is "11111111", so I have no idea what to make of it. All i could find was that this is some kind of superCID, but if it's preventing me from installing an OTA update then how do I go around this?
Is it possible to change my CID to something more accessible? This is the international Tegra 3 model by the way.
Additionally, the HBOOT screen shows that my phone is "ENDEAVORU PVT SHIP S-OFF RL". Is this normal?
Any answers would be extremely appreciated. Thank you.
You're really lucky actually, because a lot of people want exactly your phone - SuperCID and S-OFF. You cannot flash OTAs on a SuperCID phone iirc, but you can unlock the bootloader and flash something else
Hi, there are fastboot commands to change your cid if you are s-off but I am not sure why you would want to.
With s-off you can just go and flash the 1.39 hboot from mikes thread (link from his arhd thread OP)
I have same setup as you and have been wondering what actually is stock for me if I ever needed it. I don't have a nandroid from when I got the phone and I guess that s-off and super cid means I could pick any one ? But which.
Sent from my HTC One X
Thanks for the replies. I guess i have a better understanding now of what these things all mean.
So I gather if I want to get the stock Jellybean ROM I have to flash it myself?
Eh, that's kind of a pain but I guess it's not too bad. Do I go about it in the same way that anyone else would or will there be a variation based on the situation of my phone?
Thanks
I reckon someone with an s-on would gladly swop with you if its a pain you have the most flexibility as it is.
Flash whichever update you like without worrying about the cid matching. That's the magic of super cid. Then because you are s-off you also have the option to downgrade if that ever took your fancy.
There are many guides on how to do this written far better than I could so just search the forum.
Enjoy
Sent from my HTC One X
I see.
I've had a look around and I'm still a little confused to be honest.
Because I'm S-Off and have SuperCID, does that mean I can just choose a Jellybean OTA Update, download it, install it and upgrade the HBOOT?
Everything will be the same as if I upgraded OTA?
Sorry for being so useless.
Don't hang me for this info, see it more as a pointer to more info to search on
What i have read before is that you can write yourself a CID and update the hboot with a firmware from that CID. then you can run any software out there......
Do not run a ruu, it might mess up your s-off to s-on
When I get to my pc I will write up what I did with a link.
I did as Mr Hofs said but I did not need to change my cid from super to do it.
I have never tried an ruu.
Sent from my HTC One X
Ok so first i read this and watched his youtube vid http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html
Check video here http://www.youtube.com/watch?v=AQasxRPopSM he works with an S-Off
I started on HBoot 1.12 i believe
Then I got my unlock token handy (one from htcdev) and made sure fastboot working etc
Then did a nandroid (which i subsequently deleted but hey i tried to do the right thing )
Then I got the latest firmware for HBoot 1.39 from here http://forum.xda-developers.com/showthread.php?t=1957376 I downloaded the first 1.39 for WWE (x.xx.401.x - World Wide English (WWE))
No need to change your CID. Super CID works with any of them.
Now I just followed the usual steps explained many times here to flash the firmware.
You need to put the stock recovery back on. I got mine from here http://forum.xda-developers.com/showthread.php?t=1546970&highlight=htc+one+x+*stock* EDIT: dont think you need this step actually -will let one of the pro's confirm.
Then relock bootloader and reboot in RUU and flash the firmware.
When done unlock bootloader again, flash custom recovery and flash a ROM. You can skip the extra step of flashing the boot.img as with S-Off your custom recovery can do it.
As mentioned by Mr Hofs I have no idea what an RUU would do to S-Off, Ive never tried.
Good luck.

Ex nexus user brain frazzled with amount of work involved

Hi there.
So In short I'm a Nexus 5 user and as you can imagine unlocking that phone is literally 2 minutes at most using fastboot.
I got myself a brand spanking new HTC One m8 on Vodafone UK, however I hate Sense UI and would love to "transform" my phone to GPE edition.
I have few questions hopefully easy to answer. reading through the forums gives me a headache.
1. Do I need a S-Off if I want to convert my GSM to GPE? Thought its just a matter of flashing a rom? (I do know the answer to this but just cant believe it)
2. My phone is network locked, should I unlock it first and than run sunshine or the other way around (I've heard people having problems when they try to unlock after sunshine)
3. Do I need to backup my stock Vodafone Image if I want to return to stock at some point? I had HTC Desire/HD and returning back to stock was matter of flashing RUU back in the days (these seem to be provided on HTCDev now). But it looks like a lot has changed since then.
4. What order of operations? Please correct me if I'm wrong: Unlock Bootloader (Any other way than HTC Dev?) --> TWRP-->Root-->Sunshine-->Backup Image-->Convert to GPE
I'm absolutely fine with using fastboot etc (no toolkits for the wicked ) although most guides involve Windows and im on Mac... Anyone had any issues ?
Appreciate any help
Thanks
Nexus phones are designed to be developer phones, so they make it as easy as possible. (Though, and this is an important note, they still keep secure boot enabled...) The HTC One, like most consumer oriented devices, isn't quite the same.
First off, yes, you will need to S-off your phone to do a complete version change. You will also need to change your CID/MID if you want OTA updates. None of this has anything to do with SIM locking, though there is a thread you might consult once you are S-off. It may or may not work with HBOOT 3.19, but once you are S-off, you can downgrade to an older HBOOT that does fully support SIM unlocking.
If you want to ever go back, you will also need to install TWRP or CWM like always and make a nandroid backup. You don't have to be S-off to do this, but Sunshine unlocks your bootloader in the process, which you WILL need to do.
If your device is supported (because some newer firmware versions aren't) I would suggest using Sunshine S-off to unlock your bootloader and S-off your phone. At that point, flash over a custom recovery and backup your current install. Then, use the instructions here to switch your CID/MID and install the appropriate GPE version. Note! You *CAN* use a GPE RUU, but that will change the partitioning on the device making it very hard to go back.. I would strongly recommending using using a GPE backup and leaving the partition tables alone, but that's just me.
jshamlet said:
Nexus phones are designed to be developer phones, so they make it as easy as possible. (Though, and this is an important note, they still keep secure boot enabled...) The HTC One, like most consumer oriented devices, isn't quite the same.
First off, yes, you will need to S-off your phone to do a complete version change. You will also need to change your CID/MID if you want OTA updates. None of this has anything to do with SIM locking, though there is a thread you might consult once you are S-off. It may or may not work with HBOOT 3.19, but once you are S-off, you can downgrade to an older HBOOT that does fully support SIM unlocking.
If you want to ever go back, you will also need to install TWRP or CWM like always and make a nandroid backup. You don't have to be S-off to do this, but Sunshine unlocks your bootloader in the process, which you WILL need to do.
If your device is supported (because some newer firmware versions aren't) I would suggest using Sunshine S-off to unlock your bootloader and S-off your phone. At that point, flash over a custom recovery and backup your current install. Then, use the instructions here to switch your CID/MID and install the appropriate GPE version. Note! You *CAN* use a GPE RUU, but that will change the partitioning on the device making it very hard to go back.. I would strongly recommending using using a GPE backup and leaving the partition tables alone, but that's just me.
Click to expand...
Click to collapse
Thanks a lot for that.
Could your please clarify your last 2 sentences. This is first I hear about. If I use GPE backup will I be able to get OTA updates? Where can I find GPE backup rather than RUU. I think most here are RUU's.
Or do you mean GPE ROM vs GPE RUU?
MattSkeet said:
Thanks a lot for that.
Could your please clarify your last 2 sentences. This is first I hear about. If I use GPE backup will I be able to get OTA updates? Where can I find GPE backup rather than RUU. I think most here are RUU's.
Click to expand...
Click to collapse
The partition sizes are different between GPE and Sense, with Sense having a much larger /system partition than GPE. If you convert from Sense to GPE fully (using an RUU), then you will have to use an RUU to go back to Sense or the /system partition won't be large enough. If you just restore a nandroid backup of GPE to a Sense partitioned device, it will still work fine and you can revert back without any special effort.
S-off yes carrier unlocking yes and I'm an ex nexus 5 user as well
Sent from my HTC One_M8 using XDA Free mobile app
MattSkeet said:
3. Do I need to backup my stock Vodafone Image if I want to return to stock at some point? I had HTC Desire/HD and returning back to stock was matter of flashing RUU back in the days (these seem to be provided on HTCDev now). But it looks like a lot has changed since then.
Click to expand...
Click to collapse
I don't believe HTC posts RUUs to HTCDev.com any longer. There is a RUU floating around for the "generic" WWE version, but for Vodaphone or other carrier branded versions outside the US, you probably won't find any RUUs.
Therefore, its always good to at least make a nandroid before making any other changes. Or you can find the stock nandroid for your CID here:
http://forum.xda-developers.com/showthread.php?t=2701376
MattSkeet said:
4. What order of operations? Please correct me if I'm wrong: Unlock Bootloader (Any other way than HTC Dev?) --> TWRP-->Root-->Sunshine-->Backup Image-->Convert to GPE
Click to expand...
Click to collapse
I believe you can temp root, sunshine s-off and use sunshine to unlock the bootloader and bypass HTCDev.com. But I haven't done it that way personally, so I'm not 100% on that.
redpoint73 said:
I don't believe HTC posts RUUs to HTCDev.com any longer. There is a RUU floating around for the "generic" WWE version, but for Vodaphone or other carrier branded versions outside the US, you probably won't find any RUUs.
Therefore, its always good to at least make a nandroid before making any other changes. Or you can find the stock nandroid for your CID here:
http://forum.xda-developers.com/showthread.php?t=2701376
I believe you can temp root, sunshine s-off and use sunshine to unlock the bootloader and bypass HTCDev.com. But I haven't done it that way personally, so I'm not 100% on that.
Click to expand...
Click to collapse
http://www.htcdev.com/devcenter/downloads/P00 there are RUU's here which is very strange and makes it confusing in regards to backing everything up if its there
MattSkeet said:
http://www.htcdev.com/devcenter/downloads/P00 there are RUU's here which is very strange and makes it confusing in regards to backing everything up if its there
Click to expand...
Click to collapse
The only RUU there is T-Mobile US. All the rest are kernel source (and a couple framework support) files. Keep in mind, the RUU is something like 1.6 GB.
Note that there are other RUUs, they just aren't posted there. The Developer Edition has an RUU, and there is an older one for AT&T floating around somewhere as well.
I really don't understand why HTC doesn't make these more available, as they are a great way to reset a phone short of warranty service. I would think they would want people to have these as an option.
jshamlet said:
Note that there are other RUUs, they just aren't posted there. The Developer Edition has an RUU, and there is an older one for AT&T floating around somewhere as well.
Click to expand...
Click to collapse
Yes, in fact AT&T has RUUs for every major OTA build its released so far. Sprint and T-Mobile US also have RUUs. Of the major US carriers, only Verizon does not have RUUs.
I haven't seen any official RUU releases outside the US. I know there is a WWE 3.28.401 RUU think is being linked lately, but I don't know if that is a leak, or something more official. But otherwise, RUUs don't exist outside the US (or only as leaks). What makes the US so special, I don't know.
jshamlet said:
I really don't understand why HTC doesn't make these more available, as they are a great way to reset a phone short of warranty service. I would think they would want people to have these as an option.
Click to expand...
Click to collapse
I don't get it either. On past devices, I've seen specific reports of HTC support directing folks to RUU when they have software issues (after the "usual" solutions like factory reset didn't help).

HTC 10 Bell

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..

A few questions about the bootloader and S-off-ing

Hi!
I've spent a few hours researching these topics but I still feel a bit unstable. If I get it right, you can use the HTCdev method to unlock your bootloader safely, but doing so will make you unable to relock it flawlessly. Using the Sunshine method gives you an opportunity to S-off while keeping the bootloader locked.
1.) Using the Sunshine S-off LOCKED method, can you "re-S-on" to make your device look factory new? (In other words: can you revert the changes completely?)
2.) I've read that S-off-ing is only required to install firmwares and for other "high-level" purposes. Could you please tell me a few situations / examples where S-off-ing would come handy (and an unlocked bootloader wouldn't be enough)?
3.) How can you install software updates while being in "S-off LOCKED" or just simply bootloader unlocked mode?
4.) Do you think Nougat will make any differences regarding the Sunshine method?
I'm planning to do one of the 2 methods after the official EU release of Android N.
Thank you in advance!
1-Yes. But s-on is not recommended unless you really really need it.
2-For example,I'm s-off unlocked.Changed my Europe device's Cid and Mid to US Unlocked version,flashed latest Nougat RUU.exe.Wanted to go back to Viper 3.5 MM,Flashed US unlocked MM RUU.exe,Changed mid cid,Flashed a stock MM European MM 1.90 rom,flashed Viper,upgraded firmware to 1.95 through fastboot.And that's it.I was back in the beginning.2 days later,saw the root came out,changed mid-cid,flashed RUU.exe just like that,and stock N again.Then applied root,here I am.If I wasn't s-off,in some place on this process,I believe I would be bricked,hard or soft,but bricked.
3-You can get the updates normally when s-off locked/unlocked through the OTA.
4-You should s-off while you're still on MM,because afaik sunshine isn't compatible with N yet.
ordeniz said:
1-Yes. But s-on is not recommended unless you really really need it.
2-For example,I'm s-off unlocked.Changed my Europe device's Cid and Mid to US Unlocked version,flashed latest Nougat RUU.exe.Wanted to go back to Viper 3.5 MM,Flashed US unlocked MM RUU.exe,Changed mid cid,Flashed a stock MM European MM 1.90 rom,flashed Viper,upgraded firmware to 1.95 through fastboot.And that's it.I was back in the beginning.2 days later,saw the root came out,changed mid-cid,flashed RUU.exe just like that,and stock N again.Then applied root,here I am.If I wasn't s-off,in some place on this process,I believe I would be bricked,hard or soft,but biricked.
3-You can get the updates normally when s-off locked/onlocked through the OTA.
4-You should s-off while you're still on MM,because afaik sunshine isn't compatible with N yet.
Click to expand...
Click to collapse
Thanks for the fast anwser!
So the software updates only cause trouble when the bootloader is unlocked, regardless of being in s-off or s-on mode?
If I S-off now, will I be able to upgrade to N and keep the "S-off LOCKED" state?
bence.szij said:
Thanks for the fast anwser!
So the software updates only cause trouble when the bootloader is unlocked, regardless of being in s-off or s-on mode?
If I S-off now, will I be able to upgrade to N and keep the "S-off LOCKED" state?
Click to expand...
Click to collapse
No,not updates.Downgrades may cause serious problems if you are not s-off.
Yes,you keep the s-off locked.
ordeniz said:
No,not updates.Downgrades may cause serious problems if you are not s-off.
Yes,you keep the s-off locked.
Click to expand...
Click to collapse
Thank you very much!
ordeniz said:
1-Yes. But s-on is not recommended unless you really really need it.
2-For example,I'm s-off unlocked.Changed my Europe device's Cid and Mid to US Unlocked version,flashed latest Nougat RUU.exe.Wanted to go back to Viper 3.5 MM,Flashed US unlocked MM RUU.exe,Changed mid cid,Flashed a stock MM European MM 1.90 rom,flashed Viper,upgraded firmware to 1.95 through fastboot.And that's it.I was back in the beginning.2 days later,saw the root came out,changed mid-cid,flashed RUU.exe just like that,and stock N again.Then applied root,here I am.If I wasn't s-off,in some place on this process,I believe I would be bricked,hard or soft,but bricked.
3-You can get the updates normally when s-off locked/unlocked through the OTA.
4-You should s-off while you're still on MM,because afaik sunshine isn't compatible with N yet.
Click to expand...
Click to collapse
I've been curious about this, does the MID matter? Europe is 2PS62000 and US is 2PS65000. I didnt know if there were hardware differences beyond radio ones, and whether or not that would create problems for European models outside of US?
Well,I read on the forum (don't remember which thread) someone having a problem because he forgot to type 1 zero in the mid.I mean it would be same if you change cid but not mid.And since it is really easy to change ,I changed them both.

Cant update from: 3.35.617.31, Getting errors with RUU, Cant OTA

Hello,
I have bought HTC One M9 off Aliexpress.
I bought it as developer version. When it came I started OTA upgrade. It downloads and then it says update cannot be performed because of modified system.
I cant even use RUU to get it working, I receive error 132. While chatting to HTC support their run my IMEI by their system. It came back as T-Mobile (US) version. Even though on back of my phone is engraved -
Model: OPJA110 which should mean it is developer version.
On my download mode it states: S-on, official system and locked bootloader.
Can anyone give me some tips how to get the newest system installed?
I have been trying for past 2 days without any luck to figure it out.
Any help is appreciate.
EDIT: Forgot CID:11111111 MID: 0PJA11000
Thank you very much.
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Thanks for your time.
Flippy498 said:
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have read ReadMe.
So that means I need to S-OFF my phone using SunShine (other oprions?)
Then changing CID to BS_US001 (because Im running .617. system)
Then I can flash RUU (3.35.617.31)
And after that I can use OTA updates?
Do I need to unlock bootloader through HTCdev or is enough to check OEM Unlocking under developer options?
Thank you again for your time.
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.) The alternatives to Sunshine are a Java card, an XTC clip or similar tools which are way more expensive.
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Flippy498 said:
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.)
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Click to expand...
Click to collapse
Ok, Im gona pay that 25 bucks, it doesnt really matter.
So, I should start with unlocking bootloader via HTCdev.
After that I need to use SunShine.
Changing CID.
Flashing 3.x RUU.
And then doing OTA.
Is that all correct?
And should I install TWRP or stay on stock recovery after unlocking bootloader?
Really appreciate your time.
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Flippy498 said:
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Click to expand...
Click to collapse
Thanks,
is there a point in TWRP backup? Wont it stop OTA updates? On my other phone (Ulefone Metal) It is not possible to get OTA with custom recovery.
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you, I did as I said.
After flashing 3.x RUU OTA was successful.
That updated my system to: 4.16.617.6.
After that I continued by flashing latest RUU (4.30.617.12).
Everything went well. Until this point. When I booted the device I got to choose language. But there are just few (20 or so) available.
Unfortunately no Czech which I want. On previous version (4.16.617.6) there was huge list to choose from, including Czech.
Im still using 617 edition.
Where is the problem? Is here a way to get Czech lang. working again?
One again thank you for your time and effort
HTC probably removed the languages from the selection. Don't ask me why. I have no clue.
You could try setting up the phone in English and then switching to Czech via the app MoreLocal2. There's a thread about the app somewhere hidden on xda (sorry, I don't have a direct link at hand). You should be able to find it via google.
Sent from my HTC One M9 using XDA Labs

Categories

Resources