Develop Bugs

[Q] How do I change my CID (and get EU RUU)

I have gotten myself a s-offed HTC One X from a local carrier with their firmware on it so I have no real hope of fast updates...
CIDgetter says in the top left I have CID of 11111111, yet going down to ro.aa.maincid says TELENZ001 - the carrier
Obviously I am s-offed and can get into the bootloader, how do I go about changing my CID and flashing a European RUU?

Have you tried just plugging in when in fastboot and running the RUU? If you really do have Super CID it'll just work

Sorry to ask this but have you contacted the guys in the s-off thread? They may be interested in hearing from you.
http://forum.xda-developers.com/showthread.php?t=1604300
Sent from my HTC One X using xda premium

Mind giving me a walk through guide Eddy? With a $600 toy I don't wanna mess anything up...
Will post in that thread badger and see if I can be of any use

Can you make a picture of the bootloader. To see what version HBOOT and radio you have. Maybe this is causing the issue.

P1n3apqlExpr3ss said:
Mind giving me a walk through guide Eddy? With a $600 toy I don't wanna mess anything up...
Will post in that thread badger and see if I can be of any use
Click to expand...
Click to collapse
Boot phone into fastboot, connect to PC, run RUU - not a lot else to do!
It'll either work or give you an error and reboot, with no changes made

Cid-11111111
hboot-0.43.0000
radio-1.1204.90.13

P1n3apqlExpr3ss said:
I have gotten myself a s-offed HTC One X from a local carrier with their firmware on it so I have no real hope of fast updates...
CIDgetter says in the top left I have CID of 11111111, yet going down to ro.aa.maincid says TELENZ001 - the carrier
Obviously I am s-offed and can get into the bootloader, how do I go about changing my CID and flashing a European RUU?
Click to expand...
Click to collapse
wawawawa!
Don't change your CID! a CID of 11111111 should be able to flash anything. SuperCID!
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
Doombadger said:
Sorry to ask this but have you contacted the guys in the s-off thread? They may be interested in hearing from you.
http://forum.xda-developers.com/showthread.php?t=1604300
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Please!

Supaiku said:
wawawawa!
Don't change your CID! a CID of 11111111 should be able to flash anything. SuperCID!
Click to expand...
Click to collapse
I realise that ofcourse, its the maincid I want changing. I assume flashing the EU RUU will change that maincid?
On that note can anyone link me to the RUU I would want?
Oh and I did post in the s-off thread, skimmed through the pages since my post and no one seemed to say anything in regards to my post

P1n3apqlExpr3ss said:
I realise that ofcourse, its the maincid I want changing. I assume flashing the EU RUU will change that maincid?
On that note can anyone link me to the RUU I would want?
Oh and I did post in the s-off thread, skimmed through the pages since my post and no one seemed to say anything in regards to my post
Click to expand...
Click to collapse
Bump

P1n3apqlExpr3ss said:
Bump
Click to expand...
Click to collapse
If you have superCID then choose whatever RUU you want from HERE. It will not change your CID if you flash a particular RUU.

May I hook on to this.
My CID is O2__001. So I want to change it into 111111.
When I boot into fastboot and give 'fastboot oem writecid 11111111' it says:
FAILED (status read failed (Too many links).
I've tried different usb-ports, different usb-cables
Or is there another way to change the CID?
Bootloader is unlocked (HTCDev)
HBoot: 0.43.0000
Softwareversion is still 1.26.206.2, no updates available
Someone can help me?
Thanks in advance

almanbrother said:
May I hook on to this.
My CID is O2__001. So I want to change it into 111111.
When I boot into fastboot and give 'fastboot oem writecid 11111111' it says:
FAILED (status read failed (Too many links).
I've tried different usb-ports, different usb-cables
Or is there another way to change the CID?
Bootloader is unlocked (HTCDev)
HBoot: 0.43.0000
Softwareversion is still 1.26.206.2, no updates available
Someone can help me?
Thanks in advance
Click to expand...
Click to collapse
You can't without S-OFF, so you will only get updates from o2 or you can go custom

EddyOS said:
You can't without S-OFF, so you will only get updates from o2 or you can go custom
Click to expand...
Click to collapse
Thanks for your fast replay!
How do I change S-ON to S-OFF

You can't, and this is why the OP has a rare phone...
Go do some reading and you'll see why we can't get it

You're really fast! Thanks, I will search.

shadowboy23 said:
If you have superCID then choose whatever RUU you want from HERE. It will not change your CID if you flash a particular RUU.
Click to expand...
Click to collapse
Sorry for not just going ahead and flashing it but...
a) Do I need root/htcdev to flash? (im assuming not)
b) If I flash the EU RUU will I get OTA updates as theyre pushed out (im assuming so)
EddyOS said:
You can't, and this is why the OP has a rare phone..
Click to expand...
Click to collapse
Straight from HTC, that's why review phones sent out to media (at least in New Zealand) are also s-offd

P1n3apqlExpr3ss said:
Sorry for not just going ahead and flashing it but...
a) Do I need root/htcdev to flash? (im assuming not)
b) If I flash the EU RUU will I get OTA updates as theyre pushed out (im assuming so)
Straight from HTC, that's why review phones sent out to media (at least in New Zealand) are also s-offd
Click to expand...
Click to collapse
If you have S-OFF you don't have any need for HTCdev. Being superCID your phone can get OTA updates as long as you have stock recovery.

shadowboy23 said:
If you have S-OFF you don't have any need for HTCdev. Being superCID your phone can get OTA updates as long as you have stock recovery.
Click to expand...
Click to collapse
Thought that might be the case, as for flashing the RUU, is it the standard CWM way or with the fastboot files you mentioned in the video in your sig? Do the same instructions apply from it for me?

P1n3apqlExpr3ss said:
Thought that might be the case, as for flashing the RUU, is it the standard CWM way or with the fastboot files you mentioned in the video in your sig? Do the same instructions apply from it for me?
Click to expand...
Click to collapse
bump

HTC One M8 Update problem !

Hi Friends ! I have problem with my New M8. the phone is used for 3 weeks and I bougth it. there is update to lolitop but whenI press to install button the phone enters recovery mode (twrp) and thats all. doesnt update even manually I could not it. its unlock and s-on. thanks a lot. sorry my english

dj_muncher said:
Hi Friends ! I have problem with my New M8. the phone is used for 3 weeks and I bougth it. there is update to lolitop but whenI press to install button the phone enters recovery mode (twrp) and thats all. doesnt update even manually I could not it. its unlock and s-on. thanks a lot. sorry my english
Click to expand...
Click to collapse
TWRP is custom recovery. You need stock recovery to install an OTA. Find the right stock recovery for your CID and stock software number here: http://forum.xda-developers.com/showthread.php?t=2701376

redpoint73 said:
TWRP is custom recovery. You need stock recovery to install an OTA. Find the right stock recovery for your CID and stock software number here: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
thank you got it but how can I learn my cid number ?

dj_muncher said:
thank you got it but how can I learn my cid number ?
Click to expand...
Click to collapse
Seriously....READ that thread mate ! It's all described there.

In this shot taken from the OP of that specific thread ..... I read something and there i also read something as CIDNUM.....you think that command will lead you to your CID ?

Mr Hofs said:
In this shot taken from the OP of that specific thread ..... I read something and there i also read something as CIDNUM.....you think that command will lead you to your CID ?
Click to expand...
Click to collapse
still the same problem. even install stock recovery but it suddenly stopped when updating. and red triangle exclamation point than the phone restarted. so how can I update do you have any idea ?

dj_muncher said:
still the same problem. even install stock recovery but it suddenly stopped when updating. and red triangle exclamation point than the phone restarted. so how can I update do you have any idea ?
Click to expand...
Click to collapse
Yeah your system is not stock. Make backups of what you need in the future and do exactly as the thread tells you in order to return to stock via a new stock backup which is probably available there (or a ruu in some cases)

Mr Hofs said:
Yeah your system is not stock. Make backups of what you need in the future and do exactly as the thread tells you in order to return to stock via a new stock backup which is probably available there (or a ruu in some cases)
Click to expand...
Click to collapse
I dont need any thing so just install a stock rom ?

dj_muncher said:
I dont need any thing so just install a stock rom ?
Click to expand...
Click to collapse
All explained in there, i don't want to sound rude or such but if you study that thread to get to stock you will find all answers

Mr Hofs said:
All explained in there, i don't want to sound rude or such but if you study that thread to get to stock you will find all answers
Click to expand...
Click to collapse
Ok thank you

Mr Hofs said:
All explained in there, i don't want to sound rude or such but if you study that thread to get to stock you will find all answers
Click to expand...
Click to collapse
I am sorry to trouble you but is there any way to get s-off ?

dj_muncher said:
I am sorry to trouble you but is there any way to get s-off ?
Click to expand...
Click to collapse
SunShine for modern Motorola & HTC devices
That's the only way.

BerndM14 said:
SunShine for modern Motorola & HTC devices
That's the only way.
Click to expand...
Click to collapse
thank you !

BerndM14 said:
SunShine for modern Motorola & HTC devices
That's the only way.
Click to expand...
Click to collapse
I have solved the problem and I got the updates thank you very much but I have 4.4.4 and when i check for new updates it says you have the last updates. do you have any idea ?

dj_muncher said:
I have solved the problem and I got the updates thank you very much but I have 4.4.4 and when i check for new updates it says you have the last updates. do you have any idea ?
Click to expand...
Click to collapse
I won't know.... What CID do you have? Mr Hofs asked this previously and I'm yet to see anything from your side. If you're on International WWE then the update is not yet out for your device. If you have Asian WWE then the update *might* be out for your device, either way we won't know. Share some info on what device you have.
In the first post you mentioned you received the OTA for your device... If you don't get it now then try to do a factory reset and see if you can get it afterwards. Though it would still help a lot to know what device you have. So get adb on your PC and in bootloader mode use the command: fastboot getvar all and share the info, just delete the IMEI and Serial number.

BerndM14 said:
I won't know.... What CID do you have? Mr Hofs asked this previously and I'm yet to see anything from your side. If you're on International WWE then the update is not yet out for your device. If you have Asian WWE then the update *might* be out for your device, either way we won't know. Share some info on what device you have.
In the first post you mentioned you received the OTA for your device... If you don't get it now then try to do a factory reset and see if you can get it afterwards. Though it would still help a lot to know what device you have. So get adb on your PC and in bootloader mode use the command: fastboot getvar all and share the info, just delete the IMEI and Serial number.
Click to expand...
Click to collapse
Thank you very much !
My CID is spcs_001 and model is 831C.
software status : Official
relock
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
There was new updates and i installed it. after this I got 4.4.4 and now there are no updates avaible for your phone.

dj_muncher said:
Thank you very much !
My CID is spcs_001 and model is 831C.
software status : Official
relock
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
There was new updates and i installed it. after this I got 4.4.4 and now there are no updates avaible for your phone.
Click to expand...
Click to collapse
Sprint device? Didn't think you'd have a Sprint one, thought you were from the Ukraine going by your flag choice etc.
Either way, 4.4.4 is the latest for Sprint devices, the Lollipop update is still in 2(Integration) stage so it has some ways to go still before lollipop.

BerndM14 said:
Sprint device? Didn't think you'd have a Sprint one, thought you were from the Ukraine going by your flag choice etc.
Either way, 4.4.4 is the latest for Sprint devices, the Lollipop update is still in 2(Integration) stage so it has some ways to go still before lollipop.
Click to expand...
Click to collapse
Actually i am from Turkey but I live in Ukraine so my situation - its a little complicated Yes sprint device but what is the difference between the other devices M8 and sprint M8 ? And the seller told me the device from USA.
So my device never will get the lollipop ? Or I have to be patience

dj_muncher said:
Actually i am from Turkey but I live in Ukraine so my situation - its a little complicated Yes sprint device but what is the difference between the other devices M8 and sprint M8 ? And the seller told me the device from USA.
So my device never will get the lollipop ? Or I have to be patience
Click to expand...
Click to collapse
Well it looks like you've been getting OTA updates so far, so you should be able to get it when Lollipop is released, whenever that is.
Sprint - CDMA device (Verizon as well).
Other M8s - GSM Devices.
You can look up the main differences between the two with a quick google search.
It's American device yes. It would perhaps have been better if they had the Developer Edition or Unlocked Edition from the US instead of a carrier specific(Sprint) device which runs on different technologies(Radios) for their networks. Generally you won't be able to us a CDMA device "just anywhere" where as GSM is Global. Like I said though, you can get the whole explanation with a simple Google search though.

yes i have been getting OTA update. Patience or custom rom .
I can wait for it I think .
And i dont know my device is unlocked edition or developer edition but i use my phone normally i put a nano sim and the network works very well.
I have searched it and get the main idea thank your very much

firmware ota update not working

Recently bought a htc one m8 off of eBay. It is running 4.4.2 and I want to upgrade to the latest firmware. When I go into setting's about phone software update it says network connection failed even though I am connected to wifi? If anyone could shed any light in this would be greatly appreciated.
Cheers

1. Is your phone rooted?
2. Is your bootloader unlocked?
3. Can you access the adb and fastboot function?
4. Are you on the stock rom or custom rom?
5. Are you on stock or custom recovery?
Check those out and go from there

kullum79 said:
1. Is your phone rooted?
2. Is your bootloader unlocked?
3. Can you access the adb and fastboot function?
4. Are you on the stock rom or custom rom?
5. Are you on stock or custom recovery?
Check those out and go from there
Click to expand...
Click to collapse
1. Phone is not rooted
2. Bootloader is locked
3. Can you explain how you access adb and fastboot?
And not sure about 4 or 5
Cheers

snowy20792 said:
1. Phone is not rooted
2. Bootloader is locked
3. Can you explain how you access adb and fastboot?
And not sure about 4 or 5
Cheers
Click to expand...
Click to collapse
I also forgot to ask which carrier are you with?

kullum79 said:
I also forgot to ask which carrier are you with?
Click to expand...
Click to collapse
Additionally, need to know what CID (carrier version) of the phone.

kullum79 said:
I also forgot to ask which carrier are you with?
Click to expand...
Click to collapse
redpoint73 said:
Additionally, need to know what CID (carrier version) of the phone.
Click to expand...
Click to collapse
Not rooted, bootloader locked.
Build number in Settings > About > Software Information > More should be enough info with your setup @snowy20792

hmmm
xunholyx said:
Not rooted, bootloader locked.
Build number in Settings > About > Software Information > More should be enough info with your setup @snowy20792
Click to expand...
Click to collapse
Since my last post I have found out that my phone is actually a german phone. So it won't update because it's on a UK network trying to download a german update which is why I get the network connection failed error. I have downloaded the tool kit to try and root it but when I go to get token ID some of the code is protected so I can't see the CID number or the mid number.

snowy20792 said:
Since my last post I have found out that my phone is actually a german phone. So it won't update because it's on a UK network trying to download a german update which is why I get the network connection failed error. I have downloaded the tool kit to try and root it but when I go to get token ID some of the code is protected so I can't see the CID number or the mid number.
Click to expand...
Click to collapse
Why didn't you provide the information I asked for? If you did, I could probably find an RUU for you to run to update.

xunholyx said:
Why didn't you provide the information I asked for? If you did, I could probably find an RUU for you to run to update.
Click to expand...
Click to collapse
Sorry I didn't have the handset on me. The build number is
1.60.1400.3 CL341824 release-keys

just ran a cid getter app and it is coming up with HTCEN701

snowy20792 said:
Sorry I didn't have the handset on me. The build number is
1.60.1400.3 CL341824 release-keys
Click to expand...
Click to collapse
snowy20792 said:
just ran a cid getter app and it is coming up with HTCEN701
Click to expand...
Click to collapse
Nothing much that we can help ... you have a China HTC set .. HTC M8w
View attachment 3581922

ckpv5 said:
Nothing much that we can help ... you have a China HTC set .. HTC M8w
View attachment 3581922
Click to expand...
Click to collapse
Ok so where do I go from here?

Hi Guys,
I have a very similar problem, maybe you have an idea how to fix it. I bought an Austrian HTC M8 and since Lollipop I couldn't OTA update it. I had it for a long time, but never had the time to figure out why it can't update. Turns out, the previous owner had the bootloader opened (I have talked with HTC support and they checked).
I've written down all sorts of information needed, but long story short, I run full stock software (haven't even rooted it). Can you give me any suggestion how to get it to update?
Thank you in advance, I would really appreciate any help.
(Btw, I've been a long forum follower [like Samsung Omina with cooked Froyo old], but I have successfully outlocked myself from my old account - deleted my email account, to which it was linked to.)
1. Non rooted 4.4.4
2. Unlocked bootloader
3. Power+vol up can go into fastboot menu
4. Stock rom
5. Sotck recovery (with the 3 little androids on skateboards )
Settings menu:
Code:
Kernel version: 3.4.0-g222defb [email protected] #1 SMP PREEMPT
Baseline version: 1.22.21331147A1.29G_20.67.4196.01_F
Bulid number: 3.28.401.9 CL389838 release-keys
Power+vol up at startup:
Code:
***software status: modified***
*** unlocked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.22.21331147A1.29G
OpenDSP-v.46.2.2-00564-M8974_F0.0811
OS-3.28.401.9
eMMC-boot 2048MB
Oct 27 2014, 18:44:38.0

snowy20792 said:
Ok so where do I go from here?
Click to expand...
Click to collapse
I have no idea as I know nothing about China Set. You have to wait for the expert to advise.
If possible, return the device to seller.

ampersandroid said:
Hi Guys,
I have a very similar problem
Click to expand...
Click to collapse
Your case is totally different and very easy to fix.
Please post in HELP THREAD (the no. 1 listed in Q&A) if you can't find a similar case or you can create a new thread.

ckpv5 said:
Your case is totally different and very easy to fix.
Please post in HELP THREAD (the no. 1 listed in Q&A) if you can't find a similar case or you can create a new thread.
Click to expand...
Click to collapse
Thank you very much, will do that.

Is it possible to flash the m8w to an english firmware? and is so how?

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't flash anything and phone goes into random reboots

I'm currently at loss for what to do now, heres what happened which I think started all these problems
-Was running ICE 5.5.1 stable
-Phone randomly reboots into HTC's white startup screen
-went into TWRP and wiped everything including internal storage
-flashed a new rom hoping it'll stop the reboots, and halfway during the flash the phone reboots itself even before completing
-now stuck with no OS and cant get into recovery
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 3.42.708.3
boot-mode: download
version-baseband: 01.01_U11440801_97.04.60111G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__044
download mode shows "FILE /mnt/media_rw/ext_sd/0PJAIMG.zip; FILE NOT FOUND"
Anybody got any suggestions? Hopefully someone here knows something about this

digged around and found that I might need to flash 0PJAIMG.ZIP. Any kind helpful souls out there able to post the image for 3.42.708.3? Tried finding everywhere but couldn't find the relevant file in this forum

You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Beamed in by telepathy.

shivadow said:
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Beamed in by telepathy.
Click to expand...
Click to collapse
aw shucks, is there any other way to get out of this problem?

12021656627z said:
aw shucks, is there any other way to get out of this problem?
Click to expand...
Click to collapse
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.

computerslayer said:
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
Click to expand...
Click to collapse
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?

computerslayer said:
Flashing an RUU is definitely the way to go, and will work just fine as long as your SKU and OS version match with the RUU you're attempting to flash.
Being rooted and/or having an unlocked bootloader will not affect the success/failure of flashing an RUU. Follow the instructions on the readme page and you should be golden.
Click to expand...
Click to collapse
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
too old. You can't downgrade.
12021656627z said:
aw shucks, is there any other way to get out of this problem?
Click to expand...
Click to collapse
Probably not. Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Beamed in by telepathy.

12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
You've read correctly. You need a 3.xx.708.xx RUU (EDITED: See Flippy498's correction below). It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
While HTC can almost assuredly help you (for a fee), it may be worthwhile to look into the paid service mentioned in the readme thread to see if that is more cost-effective.

shivadow said:
You can flash any 3.xx.708.xx firmware. Only the first and third set of numbers really matter. The second set is incremental version, forth set is times to push to devices.
Click to expand...
Click to collapse
computerslayer said:
You've read correctly. You need a 3.xx.708.xx RUU.
Click to expand...
Click to collapse
No, not only the first and the third number of the firmware version matter for S-ON phones. The X and the SKU in X.XX.SKU.YY need to match between the RUU and the phones current firmware. Only Y is allowed to differ if the phone is S-ON.
And a RUU actually flashes everything back to stock. So this
shivadow said:
Bear in mind that your device is rooted and unlocked bootloader so flashing stock isn't an option.
Click to expand...
Click to collapse
isn't true at all.
shivadow said:
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
Click to expand...
Click to collapse
There is a sticky with all needed information for RUUs: The ReadMe thread. (But as always, if you call something "ReadMe" you can rest assured that no one really reads it...) Flashing RUU.exe files can be a pain (just like using htc_fastboot)*. It's easier to use the SD card method. The ReadMe thread even explains how to get the *.zip out of the *.exe.
* I actually never had issues with them but I faced enough users here on XDA and on Handy-FAQ who just couldn't get them to work.
12021656627z said:
I've tried and the only RUU that matches the SKU 708 is 1.32.708.15, is it possible to flash that on my current firmware? I've read that it's not compatible... or is it?
Click to expand...
Click to collapse
As mentioned before by the others, that RUU is too old.
shivadow said:
Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Click to expand...
Click to collapse
computerslayer said:
It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
Click to expand...
Click to collapse
How about Llabtoofer's RUU service as suggested in the ReadMe thread? Or Easy-Firmware if you prefer to own the RUU? (If you choose the latter make sure not to download a RUU with "combined_signed" in its naming. Those are custom made and only flashable with S-OFF. And don't forget to make it available for others, afterwards. )

Flippy498 said:
How about Llabtoofer's RUU service as suggested in the ReadMe thread? Or Easy-Firmware if you prefer to own the RUU? (If you choose the latter make sure not to download a RUU with "combined_signed" in its naming. Those are custom made and only flashable with S-OFF. And don't forget to make it available for others, afterwards. )
Click to expand...
Click to collapse
Thanks for the suggestions! Sad to know that Easy-Firmware is only available for S-OFF users, it could've been great if its flashable on S-ON. Looks like the only way out of is Llabtoofer's RUU service

12021656627z said:
Thanks for the suggestions! Sad to know that Easy-Firmware is only available for S-OFF users, it could've been great if its flashable on S-ON. Looks like the only way out of is Llabtoofer's RUU service
Click to expand...
Click to collapse
Easy-Firmware is usable for S-ON users. You just need to make sure that you don't download a "combined_signed" RUU. The ones with only "signed" should be just fine (e.g. "0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_HK_3.42.708.3_Radio_01.01_U11440801_97.04.60111G_F_release_471142_signed_2_4_2.zip" or "0PJAIMG_HIMA_UHL_M60_SENSE70_MR_hTC_Asia_HK_3.42.708.3_Radio_01.01_U11440801_97.04.60111G_F_release_471142_signed_2_4.zip").

computerslayer said:
You've read correctly. You need a 3.xx.708.xx RUU. It may be possible to get on from a paid repository of firmwares, but I don't have any recommendations there.
While HTC can almost assuredly help you (for a fee), it may be worthwhile to look into the paid service mentioned in the readme thread to see if that is more cost-effective.
Click to expand...
Click to collapse
shivadow said:
ruu.exe only?. These htc rules are confusing. There needs to be a sticky with the requirements for each state of the phone.
too old. You can't downgrade.
Probably not. Only HTC can fix it afaik. I reckon your attempts to flash will fail.
Beamed in by telepathy.
Click to expand...
Click to collapse
Any rough estimates on how much will the repair by HTC cost?

Flippy498 said:
Easy-Firmware is usable for S-ON users. You just need to make sure that you don't download a "combined_signed" RUU. The ones with only "signed" are just fine.
Click to expand...
Click to collapse
Oh! Sorry I must've misread your post then. I'll consider giving it a shot!

Flippy498 said:
No, not only the first and the third number of the firmware version matter for S-ON phones. The X and the SKU in X.XX.SKU.YY need to match between the RUU and the phones current firmware. Only Y is allowed to differ if the phone is S-ON.
Click to expand...
Click to collapse
I'm sorry for spreading bad information. Thanks for the correction.