Database Develop

[Q]I need some help about RUU, CID, and OTAs.

Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app

tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
This one has got me, i dont know what is holding you up. We've been talking in PM's trying to get to the bottom of this but havent had any luck. He has the same ATT device as me, followed the exact procedure i did but keeps getting the error. Has anyone else had issue doing OTA's when all pre requisites are met? The ATT and Dev are the same MID so that's not it. Which s-off method did u use? revolutionary most likley.. it's the easiest. I used moonshine method. Anyone using the revolutionary method that has been successful doing what we're trying to do here? I know it probably doesnt matter which s-off method was used but i'm grasping at the moment.. cant figure this one out, it should be working. Did you change your ro.cid to BS_us001 via hex edit or was it like that? I never hex edited mine and it worked with the ATT cid. If you did change it, Maybe push your original mmcblkop19 back that had the original cid and retry.. The one that hasnt been edited. Again grasping here, but trying to duplicate my setup exactly.
Edit: i just noticed you said you cant even run the ruu now, are you talking about the same ruu you already ran successfully? 1.29.1504.3? Did you check the md5? How about changing back to supercid to install the ruu? I always initiate the ruu install when my phone is on fastboot screen.

tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What I would do is start completely over, Restore to a stock ATT RUU, then run moonshine, then change to CID with the fastboot command, then do the hexedit procedure for changing the CID within your ro.prop. Then flash a DEV RUU. it should return CID 11111111 if its all done correctly.

tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which region RUU are you trying to install?

tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did this to my AT&T One yesterday and was successful. There are 3 things that I did differently and it worked for me...
- I never bothered with the SuperCID, I changed my cid to BS_US001 and then flashed the ruu, no problems. That is the correct cid for the dev edition, so might as well keep it that way.
- I did not relock the bootloader, it's completely unnecessary as the dev edition ships unlocked out of the box. That's the way it's meant to be.
- I flashed the 1.28 ruu as I wanted to be sure that I'd be able to receive ota's. I was then successfully able to download and install the latest 1.29 ota.
So I essentially have a dev edition One now, maybe something that I did can help you (and others).

nugzo said:
This one has got me, i dont know what is holding you up. We've been talking in PM's trying to get to the bottom of this but havent had any luck. He has the same ATT device as me, followed the exact procedure i did but keeps getting the error. Has anyone else had issue doing OTA's when all pre requisites are met? The ATT and Dev are the same MID so that's not it. Which s-off method did u use? revolutionary most likley.. it's the easiest. I used moonshine method. Anyone using the revolutionary method that has been successful doing what we're trying to do here? I know it probably doesnt matter which s-off method was used but i'm grasping at the moment.. cant figure this one out, it should be working. Did you change your ro.cid to BS_us001 via hex edit or was it like that? I never hex edited mine and it worked with the ATT cid. If you did change it, Maybe push your original mmcblkop19 back that had the original cid and retry.. The one that hasnt been edited. Again grasping here, but trying to duplicate my setup exactly.
Edit: i just noticed you said you cant even run the ruu now, are you talking about the same ruu you already ran successfully? 1.29.1504.3? Did you check the md5? How about changing back to supercid to install the ruu? I always initiate the ruu install when my phone is on fastboot screen.
Click to expand...
Click to collapse
Thank you my friend, I really appreciate everything u taught me =))
I already checked the md5, it's correct. And it's the same RUU which is I flashed success before.
And I never try to hex edit.
Maybe I can run RUU with supercid, but basically I could run with BS_US001 too.
I will try what u said.
I hope we can figure it out.
Sent from my HTC One using xda app-developers app

x017in said:
Which region RUU are you trying to install?
Click to expand...
Click to collapse
I don't want run any RUU, I just want to become Dev edition.
Sent from my HTC One using xda app-developers app

tommy0411 said:
I don't want run any RUU, I just want to become Dev edition.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You do know the Dev edition isn't any better than an unbranded handset from another region, right?

EddyOS said:
You do know the Dev edition isn't any better than an unbranded handset from another region, right?
Click to expand...
Click to collapse
AFAIK, the software, from HTC, is the same. I just don't want use at&t version cuz its update is really late, and I want to keep absolutely stock cuz it's the gift for my mom =b
By the way, the AT&T and Dev edition have same MID, that's why I choose Developer version =))
It I am wrong, correct me plz.
Sent from my HTC One using xda app-developers app

aimfire72 said:
I did this to my AT&T One yesterday and was successful. There are 3 things that I did differently and it worked for me...
- I never bothered with the SuperCID, I changed my cid to BS_US001 and then flashed the ruu, no problems. That is the correct cid for the dev edition, so might as well keep it that way.
- I did not relock the bootloader, it's completely unnecessary as the dev edition ships unlocked out of the box. That's the way it's meant to be.
- I flashed the 1.28 ruu as I wanted to be sure that I'd be able to receive ota's. I was then successfully able to download and install the latest 1.29 ota.
So I essentially have a dev edition One now, maybe something that I did can help you (and others).
Click to expand...
Click to collapse
Thanks for your idea, I will try it.
Sent from my HTC One using xda app-developers app

Good news and bad news.
Good news is I finally can update by OTAs.
Bad news is I still don't know why I can't do that before. All I did this morning is that I changed CID from BS_US001 to 11111111, reboot, then changed CID from 11111111 to BS_US001, reboot and everything works perfect.
By the way, I found one thing. If I changed to Supercid, the ro.cid will show CWS_001. However, if I changed to BS_US001, the ro.cid shows BS_US001. Even I have never touched hex edit.
Anyway, thanks @nugzo. U made my day =b
Sent from my HTC One using xda app-developers app

Yeah, all we need now is a 4.2.2 OTA! Hope it comes soon!

4.2.2
can i update 4.2.2 with OTA?
my cid is 401.

djkinetic said:
What I would do is start completely over, Restore to a stock ATT RUU, then run moonshine, then change to CID with the fastboot command, then do the hexedit procedure for changing the CID within your ro.prop. Then flash a DEV RUU. it should return CID 11111111 if its all done correctly.
Click to expand...
Click to collapse
Hex edit is strictly cosmetic, You can do everything you need to do with fastboot oem writecid. Like OP said, his ro.prop cid changes with different fastboot CIDs. The ro.prop cid also changes with certain roms, aosp for example. IMO it's a little dangerous to hex edit for strictly cosmetic results..
---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------
mehrzadkh said:
can i update 4.2.2 with OTA?
my cid is 401.
Click to expand...
Click to collapse
wont know till it gets here. Also dont update as soon as its available. It could lock you out let the devs get a hold of it first.

nugzo said:
Hex edit is strictly cosmetic, You can do everything you need to do with fastboot oem writecid. Like OP said, his ro.prop cid changes with different fastboot CIDs. The ro.prop cid also changes with certain roms, aosp for example. IMO it's a little dangerous to hex edit for strictly cosmetic results..
---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------
wont know till it gets here. Also dont update as soon as its available. It could lock you out let the devs get a hold of it first.
Click to expand...
Click to collapse
Not exactly, my phone's prop.ro cid didnt match fastboot changed cid till i hex edited. the hex edit changes the value within the mm block, the HTC one cid is stored in two places hence why u still see the original CID when u do the fastboot command to read from ro.prop, there are some instances where users have experienced being unable to flash a particular ruu even after changing their cid via fastboot only..Hex editing the prop value allowed them to flash whatever ruu they were trying to provided its the right region for the phone...if you want to change the phones region then you would need to also change the mid.
Sent from my One using Tapatalk 4 Beta

djkinetic said:
Not exactly, my phone's prop.ro cid didnt match fastboot changed cid till i hex edited. the hex edit changes the value within the mm block, the HTC one cid is stored in two places hence why u still see the original CID when u do the fastboot command to read from ro.prop, there are some instances where users have experienced being unable to flash a particular ruu even after changing their cid via fastboot only..Hex editing the prop value allowed them to flash whatever ruu they were trying to provided its the right region for the phone...if you want to change the phones region then you would need to also change the mid.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
The MID absolutely, but the getprop cid is cosmetic, it does not matter. It is not the tru cid location. I've been through all of these supercid threads as well as s-off 7 or 8 Ones and i cant find any evidence of this being needed. Please link me to one if you know any. My phone and 7 others that i updated never touched get prop cid in mmcblk019. only changed fastboot cid and was able to switch from ATT to Dev edition, Install RUU and get the OTA installed all while still having the ATT CID in mmcblk019. CID has always been modified the same way, fastboot oem writecid, There has always been different partitions that stored CID information, just cos they are stored there doesnt mean its the location that counts. Its just super dangerous and i personally haven't needed it for a total of 8 phones that i touched, and 2 more here at XDA the i helped with. Not 1 needed to hex edit to achieve the goal.

nugzo said:
The MID absolutely, but the getprop cid is cosmetic, it does not matter. It is not the tru cid location. I've been through all of these supercid threads as well as s-off 7 or 8 Ones and i cant find any evidence of this being needed. Please link me to one if you know any. My phone and 7 others that i updated never touched get prop cid in mmcblk019. only changed fastboot cid and was able to switch from ATT and tmobile to Dev edition, Install RUU and get the OTA installed all while still having the ATT or tmobile CID in mmcblk019. CID has always been modified the same way, fastboot oem writecid, There has always been different partitions that stored CID information, just cos they are stored there doesnt mean its the location that counts. Its just super dangerous and i personally haven't needed it for a total of 8 phones that i touched, and 2 more here at XDA the i helped with. Not 1 needed to hex edit to achieve the goal.
Click to expand...
Click to collapse
I haven't had issues flashing personally but I have seen reports by some being able to flash a ruu cause of cid mismatch even tho a phone has been fast boot written... might be a rare occurrence or it could just be user error.. Also I don't recommend that anyone just go hex editing without good reason... It is though one other step someone can take to ensure everything is what it should be.

djkinetic said:
I haven't had issues flashing personally but I have seen reports by some being able to flash a ruu cause of cid mismatch even tho a phone has been fast boot written... might be a rare occurrence or it could just be user error.. Also I don't recommend that anyone just go hex editing without good reason... It is though one other step someone can take to ensure everything is what it should be.
Click to expand...
Click to collapse
The only issues i've seen are with people having the wrong MID. They can do the RUU but cant get OTA;s/

Reverting Back from Google Edition !

So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.

details
Bloodrave said:
So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.
Click to expand...
Click to collapse
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC

cc999 said:
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC
Click to expand...
Click to collapse
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.

hboot
Bloodrave said:
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.
Click to expand...
Click to collapse
Then your Hboot 1.44 may not be the correct one. PM me with your email and I will give
you the correct one.
CC

I have tried once again with the 1.44 Hboot and the zip from htc official website , the developer edition one.
Still no luck.

With the help of cc999 i managed to revert back to 4.3 Developer Edition.
Apparently there was a mess in my adb and usb drivers.
So i managed to install the 4.3 Developer Edition on another laptop and it worked just fine.
Thank you again cc999 for the support.

You should use the stock recovery to flash the ruu.exe. Makes life so much easier!
Sent from my HTC One using Tapatalk 4

[Q] which ruu to use

i want to Unroot my HTC One, and Relock the Bootloader what ruu to use
version-main: 1.36.599.1

seanpx said:
i want to Unroot my HTC One, and Relock the Bootloader what ruu to use
version-main: 1.36.599.1
Click to expand...
Click to collapse
there is no ruu for .599

So can I use a next ruu and or is there a next way to get back to stock or do I have to wait till one comes out
Sent from my HTC One using xda app-developers app

seanpx said:
So can I use a next ruu and or is there a next way to get back to stock or do I have to wait till one comes out
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
1- Why do you want to unroot and relock it? Send it for repair under warranty?
2- what is your CID and MID?
3- Is your device s-off?

alray said:
1- Why do you want to unroot and relock it? Send it for repair under warranty?
2- what is your CID and MID?
3- Is your device s-off?
Click to expand...
Click to collapse
i just want to know in the event i do need to unroot it.
cid: HTC__332
mid: PN0711000
it is s-on

seanpx said:
i just want to know in the event i do need to unroot it.
cid: HTC__332
mid: PN0711000
it is s-on
Click to expand...
Click to collapse
There is no RUU for this one. I really doubt it will comes out. I was in the same boat couple week ago when I bought mine from ebay. Received this HTC One M7_U CID HTC__332 MID PN0711000. This is a mexican/american latina version missing some features and not received any ota update yet except a small one for camera.
If you want to play with your phone (install custom rom, recovery etc...) there is no way to go back to your .599 stock software locked and unrooted.
But if you s-off it you will be able to return to ''stock'' but not the same software region. i.e. you can return to stock .401 but not .599.
btw .599 sucks
The best thing you can do imo is to unlock bootloader, install twrp recovery, install root, s-off, change cid to HTC__001 and mid to PN0710000, run a .401 ruu and update it ota to android 4.3 (3.62.401.1) this will make your device an international one and will be much easier to play with after.

K thanks alot
Sent from my HTC One using xda app-developers app

Can you send me a link to the ruu
Sent from my HTC One using xda app-developers app

seanpx said:
Can you send me a link to the ruu
Click to expand...
Click to collapse
RUU download page:
http://forum.xda-developers.com/showthread.php?t=2428276
and should also read this:
http://forum.xda-developers.com/showthread.php?t=2358738

Thanks
Sent from my HTC One using xda app-developers app

seanpx said:
Thanks
Click to expand...
Click to collapse
just hit ''thanks'' button if i helped

Which ruu u recommend
Sent from my HTC One using xda app-developers app

seanpx said:
Which ruu u recommend
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
.401

K
Sent from my HTC One using xda app-developers app

seanpx said:
K
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe

alray said:
There is no RUU for this one. I really doubt it will comes out. I was in the same boat couple week ago when I bought mine from ebay. Received this HTC One M7_U CID HTC__332 MID PN0711000. This is a mexican/american latina version missing some features and not received any ota update yet except a small one for camera.
If you want to play with your phone (install custom rom, recovery etc...) there is no way to go back to your .599 stock software locked and unrooted.
But if you s-off it you will be able to return to ''stock'' but not the same software region. i.e. you can return to stock .401 but not .599.
btw .599 sucks
The best thing you can do imo is to unlock bootloader, install twrp recovery, install root, s-off, change cid to HTC__001 and mid to PN0710000, run a .401 ruu and update it ota to android 4.3 (3.62.401.1) this will make your device an international one and will be much easier to play with after.
Click to expand...
Click to collapse
BEST solution I've read. Thanks a lot! Been "fighting" with my phone endlessly during the last week, but for sure this is the best option for us with that sucky 599 version. Thanks!

jsoltero said:
BEST solution I've read. Thanks a lot! Been "fighting" with my phone endlessly during the last week, but for sure this is the best option for us with that sucky 599 version. Thanks!
Click to expand...
Click to collapse
No prob, just be sure to read carefully before proceeding. Changing MID can be a little tricky and scary when you flash the eng hboot, but it worth it. I'm still runing my HTC One on 3.62.401 and everything still working fine. If you need more assistance regarding all those steps pm me or just quote me in this thread.

the same to me
alray said:
There is no RUU for this one. I really doubt it will comes out. I was in the same boat couple week ago when I bought mine from ebay. Received this HTC One M7_U CID HTC__332 MID PN0711000. This is a mexican/american latina version missing some features and not received any ota update yet except a small one for camera.
If you want to play with your phone (install custom rom, recovery etc...) there is no way to go back to your .599 stock software locked and unrooted.
But if you s-off it you will be able to return to ''stock'' but not the same software region. i.e. you can return to stock .401 but not .599.
btw .599 sucks
The best thing you can do imo is to unlock bootloader, install twrp recovery, install root, s-off, change cid to HTC__001 and mid to PN0710000, run a .401 ruu and update it ota to android 4.3 (3.62.401.1) this will make your device an international one and will be much easier to play with after.
Click to expand...
Click to collapse
hi guys, i got the same version i'm sad for this but i want to say something, i have this version too but i received via ota android 4.3 but with sense 5.0, now i see u said is best change my cid and mid, how can i do this in this version, i read something about revone but this not support h1.55 thanks by the way for ur help

edulaffont said:
hi guys, i got the same version i'm sad for this but i want to say something, i have this version too but i received via ota android 4.3 but with sense 5.0, now i see u said is best change my cid and mid, how can i do this in this version, i read something about revone but this not support h1.55 thanks by the way for ur help
Click to expand...
Click to collapse
Yep, probably you received ota to 4.3 this is a 10 months old thread lol.
You cant s-off with revone on hboot 1.55. You need to use rumrunner tool to s-off
Sent from my HTC One using xda app-developers app

maybe
alray said:
Yep, probably you received ota to 4.3 this is a 10 months old thread lol.
You cant s-off with revone on hboot 1.55. You need to use rumrunner tool to s-off
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yes, i note that, but i buy my ONE 1 week ago! xD, than what do u recommend to me?, i must wait to 4.4 or do s-off?. i'm reading a lot and believe me my english is not so good but i'll try at least, is better a custom rom or a official rom like i just have installed right now? thanks a lot again

A noob question, what do MID / CID mean and what are their the significance ?

I used to have Nexus devices, and this is my first HTC device ever. I just bought HTC One 32GB international from Amazon. So I'm learning the basics here. I've been hearing a lot terms like MID/CID, what do these mean? What do these stand for? What are their significance or rule? Where to find those? Thanks in advance!

M_Shaaban said:
I used to have Nexus devices, and this is my first HTC device ever. I just bought HTC One 32GB international from Amazon. So I'm learning the basics here. I've been hearing a lot terms like MID/CID, what do these mean? What do these stand for? What are their significance or rule? Where to find those? Thanks in advance!
Click to expand...
Click to collapse
MID = Model ID
CID = Carrier ID
you can find them using "fasbtoot getvar all" in bootloader/FASTBOOT USB.

nkk71 said:
MID = Model ID
CID = Carrier ID
you can find them using "fasbtoot getvar all" in bootloader/FASTBOOT USB.
Click to expand...
Click to collapse
What's the significance? Is there something to be understood or to be categorized accordingly? Thanks in advance!

M_Shaaban said:
What's the significance? Is there something to be understood or to be categorized accordingly? Thanks in advance!
Click to expand...
Click to collapse
Don't know exactly how to put it, but here goes:
MID = Model ID = Hardware
you can check this, for the differences: http://forum.xda-developers.com/showthread.php?t=2223236
CID = Carrier ID = origin of your phone (manufactured by HTC, but sold by a specific company), for example HTC__001 is an unbranded international version, H3G__001 is a UK Three version, CWS__001 is a US AT&T version. a simple search would show you this: http://forum.xda-developers.com/showthread.php?t=2445289
As to the significance, it really depends what you mean, if you're just asking which one gets updates, which doesnt, then the simple answer is usually the unbranded first, then the carrier specific ones. Reason: HTC releases the unbranded updates, whereas the carrier specific ones, need to go through the carrier first (in case they want to add or remove something), and then get's released.
EDIT: so far the trend for updates has been: Taiwan first (HTC), then US Developer edition, then unbranded, then carrier specific.
With S-Off, you can change both MID and CID.
Hope that helped a little, if it did hit the thanks button.

nkk71 said:
Don't know exactly how to put it, but here goes:
MID = Model ID = Hardware
you can check this, for the differences: http://forum.xda-developers.com/showthread.php?t=2223236
CID = Carrier ID = origin of your phone (manufactured by HTC, but sold by a specific company), for example HTC__001 is an unbranded international version, H3G__001 is a UK Three version, CWS__001 is a US AT&T version. a simple search would show you this: http://forum.xda-developers.com/showthread.php?t=2445289
As to the significance, it really depends what you mean, if you're just asking which one gets updates, which doesnt, then the simple answer is usually the unbranded first, then the carrier specific ones. Reason: HTC releases the unbranded updates, whereas the carrier specific ones, need to go through the carrier first (in case they want to add or remove something), and then get's released.
EDIT: so far the trend for updates has been: Taiwan first (HTC), then US Developer edition, then unbranded, then carrier specific.
With S-Off, you can change both MID and CID.
Hope that helped a little, if it did hit the thanks button.
Click to expand...
Click to collapse
I have bought the unlocked international version from Amazon. I want to convert to the developer edition to receive updates faster, would that be possible and ensure the future OTA updates, or I'd have to flash the updates manually every time after conversion?
Sent from my HTC One using XDA Premium 4 mobile app

M_Shaaban said:
I have bought the unlocked international version from Amazon. I want to convert to the developer edition to receive updates faster, would that be possible and ensure the future OTA updates, or I'd have to flash the updates manually every time after conversion?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're s-off and set the correct MID (fasboot oem writemid PN07xxxxx) and CID (fasboot oem writecid xxxxxxxx), and have stock rom + stock recovery, etc.
you'll receive OTAs without problems; now and in the future.
PS: xxxx are just placeholders you'll have to fill them what you want them to be.

nkk71 said:
If you're s-off and set the correct MID (fasboot oem writemid PN07xxxxx) and CID (fasboot oem writecid xxxxxxxx), and have stock rom + stock recovery, etc.
you'll receive OTAs without problems; now and in the future.
PS: xxxx are just placeholders you'll have to fill them what you want them to be.
Click to expand...
Click to collapse
Can I unlock, s-off, root, correct MID and CID without installing custom recovery -while keeping the stock recovery?
Sent from my HTC One using XDA Premium 4 mobile app

M_Shaaban said:
Can I unlock, s-off, root, correct MID and CID without installing custom recovery -while keeping the stock recovery?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
why bother trying? if you are going for the developer edition, then s-off, change MID and CID, and when you run the RUU.EXE:
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
everything will be 100% Developer Edition (stock rom, recovery, hboot, etc) and you can receive all the OTAs
KEEP S-OFF.

nkk71 said:
why bother trying? if you are going for the developer edition, then s-off, change MID and CID, and when you run the RUU.EXE:
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
everything will be 100% Developer Edition (stock rom, recovery, hboot, etc) and you can receive all the OTAs
KEEP S-OFF.
Click to expand...
Click to collapse
Thanks
Can I root without having to install a custom recovery?
Sent from my HTC One using XDA Premium 4 mobile app

No, you can not. You can however root using custom recovery, and then install stock recovery to overwrite the custom recovery. Why do you want stock recovery however?

SaHiLzZ said:
No, you can not. You can however root using custom recovery, and then install stock recovery to overwrite the custom recovery. Why do you want stock recovery however?
Click to expand...
Click to collapse
Good to know it's possible to install stock recovery to overwrite the custom one. I want stock recovery to receive future OTA updates without problems.

Then remember to unroot as well to get OTA.
Usually OTA and root don't go together.

SaHiLzZ said:
Then remember to unroot as well to get OTA.
Usually OTA and root don't go together.
Click to expand...
Click to collapse
Hi @SaHiLzZ, i just checked the asserts in an OTA, and i THINK, he can keep root shouldn't affect the OTA, but he may loose root after reboot and need to flash it again.
@M_Shaaban, once you start receiving OTAs, I recommend you "download & install later", then take a copy of the OTA to your PC, and extract "stock recovery" (recovery.img in firmware.zip), to keep a record of stock recoveries on your PC, when you need to flash it back.

nkk71 said:
Hi @SaHiLzZ, i just checked the asserts in an OTA, and i THINK, he can keep root shouldn't affect the OTA, but he may loose root after reboot and need to flash it again.
@M_Shaaban, once you start receiving OTAs, I recommend you "download & install later", then take a copy of the OTA to your PC, and extract "stock recovery" (recovery.img in firmware.zip), to keep a record of stock recoveries on your PC, when you need to flash it back.
Click to expand...
Click to collapse
Isn't it possible to extract the recovery.img from the htcdev files - RUU files?
On a side note, HTC One is not listed in the devices on htcdev.com for unlocking the bootloader?

M_Shaaban said:
Isn't it possible to extract the recovery.img from the htcdev files - RUU files?
Click to expand...
Click to collapse
Not sure the RUUs are there, but then again, I never checked.
Personally, I would keep the OTAs on my PC, cause they also include complete and signed firmware packages. (just something i personally would do, everybody has their own way)
M_Shaaban said:
On a side note, HTC One is not listed in the devices on htcdev.com for unlocking the bootloader?
Click to expand...
Click to collapse
You have to select "other" (or whatever it's named).

nkk71 said:
Not sure the RUUs are there, but then again, I never checked.
Personally, I would keep the OTAs on my PC, cause they also include complete and signed firmware packages. (just something i personally would do, everybody has their own way)
You have to select "other" (or whatever it's named).
Click to expand...
Click to collapse
Thanks!

[Q] using RUU on HTC One M8 HK

I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!

cristhefur said:
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
Click to expand...
Click to collapse
You can use the RUU with S-ON as long as it is not an older version than what is already on your phone - I believe you are probably talking about 1.54.654.9 right? Check the about settings on your phone to see if you have upgraded from that (1.54.654.13 or 1.54.654.15 or the 2.16 something).
If the phone version is newer, you will not be able to use the RUU without S-OFF. Since you actually have the HK version, you will not need to change your CID. Successfully running the RUU will flash all the major partions, radios, and more and will bring you completely back to stock. It will also wipe your data/media partition (internal SC card) so make sure you backup anything you need to keep.

Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app

cristhefur said:
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
The RUU will actually remove the TAMPERED banner because that flag is in mmcblk0p6, named "pg2fs", which is one of the images that the RUU overwrites. UNLOCKED, if you have it, will remain because that flag is mmcblk0p2, named "pg1fs" which does not get overwritten by the RUU. It can be removed by hex editing that block with an echo command http://forum.xda-developers.com/showthread.php?t=2708571
If you are already unlocked, rooted, and have version 1.54.654.9, I would highly suggest you run sunshine and get S-OFF before you run the RUU and update the OTAs; who knows if that exploit will be blocked in further updates.

I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app

cristhefur said:
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Not sure since I did it on .9, but I would definitely try it - in fact, if you are on 15, the only way you will be able to run the .9 RUU is if you S-OFF.
Sunshine will not ask you to pay until it has run compatibility tests and verified that it can get S-OFF on your phone - so run it and if you see the message to pay, you are good to go. Having S-OFF just makes things SO much easier.
Just follow the directions on the sunshine site http://theroot.ninja/ and run it entirely from the phone; couldn't be easier. You will need to sideload the APK, easiest if you just run the command "adb install SunShine-latest.apk" after making sure Unknown Sources is checked in your phone settings.

Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app

cristhefur said:
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
It's the other way around - look a few posts up - there's a "not older than your phone's version" in front of that statement.
To be clear, the .9 RUU will not work on a .15 phone if you are S-ON, you must be S-OFF to do that. However, if you had a .15 RUU (which doesn't exist) it would work on a .9 phone.
Sorry about the confusion. That is just one of the benefits of being S-OFF (not to get sidetracked but my favorite benefit is being able to flash from hboot or fastboot rebootRUU with the bootloader locked)

Ah yes, I see that now- my mistake. I guess I'll s-off tomorrow afternoon then. Thank you very much for your help!
Sent from my 831C using XDA Free mobile app

It's encouraging that the Sunshine devs recently made fixes to deal with Sprint 4.4.3 M8 devices - that's version 2.16.654.4 which is higher than yours, so I think you have a good chance of success. Good luck!

Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.

AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
I'm fairly certain that if you're S-on you can only run a RUU with the same software & firmware version that's installed on the phone. It was that way on the EVO LTE and I'm fairly certain that's how it is now.
Sent from my HTC M8

you may want to try http://firewater-soff.com/ first, if nogo, then sunshine
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
nope, you can't flash a older RUU if you're s-on

Oh ok...my apologies.
Is there a reason that my phone boots directly into the bootloader every time that I relock it?
I am unable to boot into anything after using fastboot oem lock, and it only loads the bootloader until I run the RUU (granted, this was before the latest update).

So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?

neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.

PillowMetal said:
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
Click to expand...
Click to collapse
Is it possible to flash the recovery from SD card or do I need to use my computer?

neudof said:
Is it possible to flash the recovery from SD card or do I need to use my computer?
Click to expand...
Click to collapse
When you download say TWRP from their webiste, you get an image file (IMG) that is meant to be flashed using fastboot from your computer. But you can rename it to "recovery.img", place that in a zip file along with an android.txt file with specific contents onto your external SD Card, and then you can flash it from the bootloader (if you are S-OFF). The file has to be specifically named as well - e.g., the Sprint HTC One M8 is "0P6BIMG.zip".
If you don't have an external SD Card, you may also be able to flash from the bootloader using a powered USB-OTG cable (like we did on the M7). Again, this is only if you are S-OFF, otherwise you will have to fastboot flash the image from your computer because bootloader flashes with S-ON have to be signed.
One last method that doesn't require S-OFF, is to copy the image file anywhere on internal or external SD cards, then use the "dd" command to copy the image over your recovery block (specific numeric device block depending on phone) using either your computer or a terminal emulator on the phone.
So yeah, you have options.

Update: I achieved S-Off as suggested, locked my boot loader using an adb command from another thread then ran the HK .9 RUU. I went through the 3 updates then took the phone to sprint, had no problems at all. Thanks for your help guys. :thumbup: