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/
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
808phone said:
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
808phone said:
I have an ATT M7. I am on T-Mobile. The phone is now unlocked. It is still running Android 4.3.
ATT software update doesn't find any updates - presumably because I need an ATT sim in there.
So how can I upgrade this to 4.4 and later 5.0?
Thanks!
Click to expand...
Click to collapse
convert the phone to Developers Edition
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
http://forum.xda-developers.com/htc-one/general/stock-rom-reset-developer-edition-t2915170
Thanks @alray
So I did more reading and yes developer edition or change CID and MID to T-Mobile
All require S-OFF.
So I need to unlock boot loader, install TWRP, S-OFF. etc?
This is the blue Best Buy version ATT - but ATT just unlocked it.
M7_UL PVT SHIP S-ON RH
HBOOT 1.55
Radio-4T.20.3218.13
808phone said:
So I did more reading and yes developer edition or change CID and MID to T-Mobile
All require S-OFF.
So I need to unlock boot loader, install TWRP, S-OFF. etc?
This is the blue Best Buy version ATT - but ATT just unlocked it.
M7_UL PVT SHIP S-ON RH
HBOOT 1.55
Radio-4T.20.3218.13
Click to expand...
Click to collapse
thats why I asked for your fastboot getvar all, unlock your bootloader and use rumrunner to s-off, do not take any updates until you get s-off as it gets harder the higher HBOOT you have.
Seanie280672 said:
thats why I asked for your fastboot getvar all, unlock your bootloader and use rumrunner to s-off, do not take any updates until you get s-off as it gets harder the higher HBOOT you have.
Click to expand...
Click to collapse
S-OFF now by using sunshine. I do have ADB and Fastboot working from my previous use with HTC One S.
808phone said:
OK, I believe I am S-OFF, just used sunshine.
Click to expand...
Click to collapse
well from there you can either follow clsA link and change to developer edition, which will require changing cid, mid and flash the RUU, dev edition gets the quickest updates, although its very touch and go at the moment as to whether the M7 is going to get anymore updates, or you can do the same with the latest T-mo RUU which is here: http://www.htc.com/us/support/htc-one-t-mobile/news/ that will also require you to change your cid and mid, after doing that follow the manual instructions on the HTC site, download link for the RUU is at the bottom.
Thanks!
Seanie280672 said:
well from there you can either follow clsA link and change to developer edition, which will require changing cid, mid and flash the RUU, dev edition gets the quickest updates, although its very touch and go at the moment as to whether the M7 is going to get anymore updates, or you can do the same with the latest T-mo RUU which is here: http://www.htc.com/us/support/htc-one-t-mobile/news/ that will also require you to change your cid and mid, after doing that follow the manual instructions on the HTC site, download link for the RUU is at the bottom.
Click to expand...
Click to collapse
808phone said:
Thanks!
Click to expand...
Click to collapse
at&t phones already have the required MID to flash the dev edition ruu (pn0712000) Only need to change the cid
alray said:
at&t phones already have the required MID to flash the dev edition ruu (pn0712000) Only need to change the cid
Click to expand...
Click to collapse
Darn it. Read this too late. OK, I changed CID to T-MOB010 and MID to PN0713000.
At this point, do I just run an RUU at some point? Hope it works.
808phone said:
Darn it. Read this too late. OK, I changed CID to T-MOB010 and MID to PN0713000.
At this point, do I just run an RUU at some point? Hope it works.
Click to expand...
Click to collapse
Yes this one >> http://www.htc.com/us/support/htc-one-t-mobile/news/
clsA said:
Yes this one >> http://www.htc.com/us/support/htc-one-t-mobile/news/
Click to expand...
Click to collapse
I used Sunshine to get S-OFF. Everywhere I read, it says I need to have the boot loader locked to apply the RUU. However, while contacting the sunshine authors, they told me that despite what I have read, I don't have to relock. Is this true?
808phone said:
I used Sunshine to get S-OFF. Everywhere I read, it says I need to have the boot loader locked to apply the RUU. However, while contacting the sunshine authors, they told me that despite what I have read, I don't have to relock. Is this true?
Click to expand...
Click to collapse
no you dont need to lock as your s-off, unlocked is fine.
locked / relocked for flashing firmware or RUU's is only required for s-on users and limited to 1 step forward or current only.
So now the ruu times out on sending.......
So I extracted the rom.zip. If I flash it from twrp since it has a recovery image in it, will it overwrite twrp?
I'm assuming yes and then I would have to fast boot twrp back again.
Is this correct? Thanks
Gave up and installed Maximus HD. Works fine. Just wanted to be on 5.0 to test things.
808phone said:
Gave up and installed Maximus HD. Works fine. Just wanted to be on 5.0 to test things.
Click to expand...
Click to collapse
Anyone know what the first part of this means? (unaligned ruu)
Where would I get this????
> Use an unaligned ruu or a matching hboot ruu
My phone has this CID HTC__332 for Latin American countries and I live in Middle East. Haven;t got the OTA lollipop update till now and would like to change CID, had gone through few posts related to changing CID but confused.
midhunmukund said:
My phone has this CID HTC__332 for Latin American countries and I live in Middle East. Haven;t got the OTA lollipop update till now and would like to change CID, had gone through few posts related to changing CID but confused.
Click to expand...
Click to collapse
You need s-off to change CID and also need to know how to use fastboot commands.
very simple procedure after that, one simple command of "fastboot oem wite cid HTC__001"
HTC__001 is WWE edition, and cid number is always 8 character long, so HTC__001 has 2 underscores to make up the 8 character, BS_US001 is developer edition and only has 1 underscore to make up the 8 characters etc etc, always capital letters too.
Those are the 2 most popular CID's unless your on an AT&T phone with a T-Mo sim or Vise versa.
Seanie280672 said:
You need s-off to change CID and also need to know how to use fastboot commands.
very simple procedure after that, one simple command of "fastboot oem wite cid HTC__001"
HTC__001 is WWE edition, and cid number is always 8 character long, so HTC__001 has 2 underscores to make up the 8 character, BS_US001 is developer edition and only has 1 underscore to make up the 8 characters etc etc, always capital letters too.
Those are the 2 most popular CID's unless your on an AT&T phone with a T-Mo sim or Vise versa.
Click to expand...
Click to collapse
thanks..could you guide me to S-OFF procedure?
will i be able to get OTA updates from after S-OFF
midhunmukund said:
thanks..could you guide me to S-OFF procedure?
will i be able to get OTA updates from after S-OFF
Click to expand...
Click to collapse
download an app called sunshine s-off onto your phone, not sure if you can get it from playstore, but just navigate to this link on your phone: http://theroot.ninja/
install the app once downloaded on your phone and then open it, it will run some tests, if it can s-off your phone then you have to pay $25 through paypal, if it cant s-off your phone then it will let you know why, your phone will reboot a couple of times, you will then have a free phone to do whatever you like with it.
after s-off, you can flash any RUU or firmware you like for your version of the M7 OTA's will be a thing of the past.
Seanie280672 said:
download an app called sunshine s-off onto your phone, not sure if you can get it from playstore, but just navigate to this link on your phone: http://theroot.ninja/
install the app once downloaded on your phone and then open it, it will run some tests, if it can s-off your phone then you have to pay $25 through paypal, if it cant s-off your phone then it will let you know why, your phone will reboot a couple of times, you will then have a free phone to do whatever you like with it.
after s-off, you can flash any RUU or firmware you like for your version of the M7 OTA's will be a thing of the past.
Click to expand...
Click to collapse
Awesome, that was cool done with S-OFF, thanks a ton and how to change the CID?
midhunmukund said:
Awesome, that was cool done with S-OFF, thanks a ton and how to change the CID?
Click to expand...
Click to collapse
Do you know how to use fastboot and the commands ?
Nope
midhunmukund said:
Nope
Click to expand...
Click to collapse
ok sent you a pm