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/
Related
Hi everyone,
Got my 3 branded HTC One S-Offed today, with the aim of getting the stock cid HTC__001 ROM on there so I can get OTA update ON TIME (Yup, Three still haven't released the 1.29 update)
So my CID's been changed to HTC__001 and flashed the RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe RUU
All went smooth and all the bloatware disappeared, however my software version is still showing as 1.28.771.6 which is the Three ROM software version, which is why i'm guessing it's still not shoiwng any OTA updates available?
Tried flashing again with SuperCID instead and when flashing this tume the RUU utility showed my phone's software version as 1.28.401 like it should have been, however flashed again and same thing, software version still showing up 1.28.771.6!
Feel as though i'm missing something stupid if anyone can help please!
You have to change more than your cid in bootloader it appears twice if not 3 times go read supercid thread in development section
Sent from my HTC One using XDA Premium HD app
ac3kill said:
You have to change more than your cid in bootloader it appears twice if not 3 times go read supercid thread in development section
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Aah thanks mate, i'll have a look
ac3kill said:
You have to change more than your cid in bootloader it appears twice if not 3 times go read supercid thread in development section
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Checked it out, my HTC One is showing HTC__001 as CID with the getprop "ro.cid" command also without having to do anything, so in all three places my CID is correct, am I missing something else?
Sorted this by the way, extracted the rom.zip from the RUU and flashed manually through fastboot, now working!
jinx27 said:
Sorted this by the way, extracted the rom.zip from the RUU and flashed manually through fastboot, now working!
Click to expand...
Click to collapse
that will install the rom, but doesnt flash the firmware.
c5satellite2 said:
that will install the rom, but doesnt flash the firmware.
Click to expand...
Click to collapse
The radio seems to be the right version now as well? I think I may just run the RUU exe over this again to make sure
This is exactly what i want to do. I have a HTC One from from 3 and want to debrand and go to a stock rom. Have you recieved an OTA update since you have done this? Or are you still on 1.28.401.7 that you flashed?
cptblackgb said:
This is exactly what i want to do. I have a HTC One from from 3 and want to debrand and go to a stock rom. Have you recieved an OTA update since you have done this? Or are you still on 1.28.401.7 that you flashed?
Click to expand...
Click to collapse
+1
Sent from my HTC One using XDA Premium HD app
ac3kill said:
+1
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Finally managed to get it working after a bit of messing around, OTA came straight through! Installed fine as well. It's taken a day but I've got there, an OTA update at last lol. Let me know if you need any help
I'm locked, s-off, after check with command getprop. My cid 11111111.. if I flash RUU.. my recovery will lost?
Sent from my HTC One using Tapatalk 2
iamaniff said:
I'm locked, s-off, after check with command getprop. My cid 11111111.. if I flash RUU.. my recovery will lost?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yeah, the RUU set's everything back to stock, including recovery
You do NOT need to change all Cid locations for RUU and OTA's. Just the Fastboot one is sufficient. I just tested RUU and OTA and it works fine. You can RUU without even re locking the bootloader with supercid, but to install an OTA you will have to relock bootloader and change cid from 11111111 to whatever carrier you are trying to OTA. I personally have an ATT CWS__001, changed CID to 11111111 with fastboot oem writecid 11111111. (get prop cid is still CWS__001) Ran older Dev edition ruu, installed fine without locking or changing cid. Booted and system Downloaded OTA, of course wouldnt install due to improper system files. Fastboot oem lock and fastboot oem write cid BS_US001 was all i needed to successfully install the OTA. NO HEX EDIT needed.
I see you are on 3, is that in the UK? ... I'm curious that's all as mine is a sim free one and I wondered, when it comes to the 4.2.2 update, will a sim free user get the update at a different time to someone who has a carrier branded phone? I'm on Tesco and just wondered if I'll get the update when they decide to send it to my phone, or will it work differently seeing as I bought the phone sim free?
AllAboutTheCore said:
I see you are on 3, is that in the UK? ... I'm curious that's all as mine is a sim free one and I wondered, when it comes to the 4.2.2 update, will a sim free user get the update at a different time to someone who has a carrier branded phone? I'm on Tesco and just wondered if I'll get the update when they decide to send it to my phone, or will it work differently seeing as I bought the phone sim free?
Click to expand...
Click to collapse
Yup in the UK, I had a Three branded phone, which officially never even received the 1.29 OTA. If you've got a SIM free phone then it doesn't matter what network your on, you'll get the update same time as the other SIM free phones, it's just branded phones that get updates at different time
jinx27 said:
Yup in the UK, I had a Three branded phone, which officially never even received the 1.29 OTA. If you've got a SIM free phone then it doesn't matter what network your on, you'll get the update same time as the other SIM free phones, it's just branded phones that get updates at different time
Click to expand...
Click to collapse
Ah sound, operators are a ***** lol, glad I opted for sim free, especially as my contract costs me £7.50 a month and the same one, with a contract phone, cost me £25.
c5satellite2 said:
that will install the rom, but doesnt flash the firmware.
Click to expand...
Click to collapse
Yes it does as the ROM.zip in the RUU is the complete file - radio, ROM, fw, the lot
Sent from my Nexus 4 using xda premium
Can you please give a few more details about how you installed ROM.zip through fastboot? I have followed all the steps. S-OFFed, HTC__001 cid but when I install the RUU my version number refuses to change.
mortakos said:
Can you please give a few more details about how you installed ROM.zip through fastboot? I have followed all the steps. S-OFFed, HTC__001 cid but when I install the RUU my version number refuses to change.
Click to expand...
Click to collapse
I'm in the exact same situation but managed to dig a bit more and bumped into this http://www.youtube.com/watch?v=BWqUlTSvr8U
---------- Post added at 09:12 PM ---------- Previous post was at 09:07 PM ----------
I'm also guessing that i need to relock my bootloader to flash this ?
I started with the 3 Branded uk phone. I had an unlocked bootloader and TWRP recovery on it as i was going to go for a custom rom to fix my Bluetooth issues.
But after seeing the original post and realizing s-off was now available this is what i did.
With Bootloader unlocked and recovery still there i S-Off'd the phone and then set my CID to HTC__001
Then i downloaded RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I ran this as the .exe i downloaded no extracting or anything it was untouched. It installed fine and i double checked the version on the phone once booted and they all matched.
While i was checking version numbers the update for 1.29.401.12 popped up so i installed that straight away.
Bootloader is still unlocked and i am just waiting for the 4.2.2 update now.
Hi all, just wondering if someone with some knowledge can help assist me debranding my HTC One. I came from Samsung devices, and knew the ins and outs of rooting, flashing roms etc, but HTC devices seems so over complicated after reading through various forums.
All I want to do is debrand my Vodafone HTC One, and install the international uk firmware, and be able to receive ota updates in future.
I have been reading about changing Ruu, changing CID, and im just baffled by everything, although slowly starting to gain some knowledge.
Please I would appreciate if someone could give me the correct procedure to do this, do I need to unlock the bootloader before doing it? Already registered on HTCDEV website, just havnt unlocked bootloader yet.
I have spent hours reading info, and my head is practically going round in circles lol.
What do you mean by debranding? Do you mean putting a custom Rom on it?
Edit: I missed a section of what you said. I believe you have to unlock the bootloader, turn security off, and get Super CID.
Sent from my HTCONE using xda premium
Sent from my SPH-L900 using xda app-developers app
Thank you, So I need to unlock bootloader, get s-off, then install supercid. Then all I do is install the international stock rom? and I will receive ota updates?
I believe so, but you must have the international stock recovery on too for the OTA updates to work.
Sent from my HTCONE using xda premium
honda1979 said:
Hi all, just wondering if someone with some knowledge can help assist me debranding my HTC One. I came from Samsung devices, and knew the ins and outs of rooting, flashing roms etc, but HTC devices seems so over complicated after reading through various forums.
All I want to do is debrand my Vodafone HTC One, and install the international uk firmware, and be able to receive ota updates in future.
I have been reading about changing Ruu, changing CID, and im just baffled by everything, although slowly starting to gain some knowledge.
Please I would appreciate if someone could give me the correct procedure to do this, do I need to unlock the bootloader before doing it? Already registered on HTCDEV website, just havnt unlocked bootloader yet.
I have spent hours reading info, and my head is practically going round in circles lol.
Click to expand...
Click to collapse
All the following is dependant on having an hboot of less than 1.54. If you are already on hboot 1.54, you will not yet be able to s-off and follow this process until an exploit is found for the 1.54 hboot. To check this, turn off your device and restart it whilst holding the volume down button. The information will be displayed.
1 Get S-Off http://forum.xda-developers.com/showthread.php?t=2314582
2 Install super cid : fastboot oem writecid 11111111
3 Run RUU 1.28.401.7 http://forum.xda-developers.com/showthread.php?t=2207874
4 Change cid to generic : fastboot oem writecid HTC__001
You will now receive ota updates to 2.24.401.1
honda1979 said:
Thank you, So I need to unlock bootloader, get s-off, then install supercid. Then all I do is install the international stock rom? and I will receive ota updates?
Click to expand...
Click to collapse
Run revone, unlocked bootloader and s-off
change CID to HTC__001 or 11111111
run RUU for international M7 i would start with PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4
once this is on the phone you should get all the OTA releases bringing you up to date.
bobsie41 said:
All the following is dependant on having an hboot of less than 1.54. If you are already on hboot 1.54, you will not yet be able to s-off and follow this process until an exploit is found for the 1.54 hboot. To check this, turn off your device and restart it whilst holding the volume down button. The information will be displayed.
1 Get S-Off http://forum.xda-developers.com/showthread.php?t=2314582
2 Install super cid : fastboot oem writecid 11111111
3 Run RUU 1.28.401.7 http://forum.xda-developers.com/showthread.php?t=2207874
4 Change cid to generic : fastboot oem writecid HTC__001
You will now receive ota updates to 2.24.401.1
Click to expand...
Click to collapse
Thanks for that info mate. I just checked and im on hboot 1.54, which means I wont be able to do this at the moment. Was that RUU you state an exe file? I guess I don't have to root or install any custom recovery to do this? First I need to wait on an exploit for sboot 1.54 to get s-off. Also it might be easier for me going down the custom rom route?
honda1979 said:
Thanks for that info mate. I just checked and im on hboot 1.54, which means I wont be able to do this at the moment. Was that RUU you state an exe file? I guess I don't have to root or install any custom recovery to do this? First I need to wait on an exploit for sboot 1.54 to get s-off. Also it might be easier for me going down the custom rom route?
Click to expand...
Click to collapse
Until s-off is achieved for hboot 1.54, your only choice is custom roms. This should be fine as you are already updated to the latest firmware through Vodafone.
Sent from my HTC One using xda premium
bobsie41 said:
Until s-off is achieved for hboot 1.54, your only choice is custom roms. This should be fine as you are already updated to the latest firmware through Vodafone.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Ok cheers. I thought that I needed to be S-Off before I could install any custom rom, but I could root and install custom recovery with s-on?
honda1979 said:
Ok cheers. I thought that I needed to be S-Off before I could install any custom rom, but I could root and install custom recovery with s-on?
Click to expand...
Click to collapse
Yes
needbyna mechanism
bobsie41 said:
Yes
Click to expand...
Click to collapse
Ok, now here goes lol. My understanding so far is that in order to install any stock ruu I must first get s-off. As im running stock Vodafone firmware, the CID must match this firmware. If I get s-off, I will be able to install any CID and stock rom, as long as they match one another. and as im on hboot 1.54 just now, supercid wont work yet, so s-off is a no no at the moment. I can still root and install a custom firmware though.
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
I understand that the only differences between HTC One and developer edition is the storage and the unlocked bootloader. I have got HTC Unlocked International Edition (32 GB) from Amazon. Now the KitKat update is going to be released 60 days earlier to the dev edition. Is there a way to convert to a dev edition to receive future updates faster? Would unlocking the bootloader turn the phone into a dev edition? Or those handsets receive the updates according to IME, serial or something? Thanks in advance!
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
EsJayEs said:
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
Click to expand...
Click to collapse
Will this method change to developer edition and will ensure future OTA released for the Developer Edition? Thanks!
Yes it will get OTA , if the last step is to run RUU for Dev edition.
If you install custom recovery/root on top of it, then you will have isssues with OTA.
EsJayEs said:
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
Click to expand...
Click to collapse
Do I have to change to SuperCID at any stage?
No you do not. As per the post from EsJayEs , you only need to change CID to BS_US001
To add to that, there's no reason to ever use superCID. It's takes less than a minute to change your CID. And this is part of what ensures you receive OTA updates.
EsJayEs said:
To add to that, there's no reason to ever use superCID. It's takes less than a minute to change your CID. And this is part of what ensures you receive OTA updates.
Click to expand...
Click to collapse
Thanks... It seems like it's not so common for people to convert to Developer Edition, all the search results I'm getting is about converting to-from GPE. Is that so uncommon right?
It's fairly common. For people on carrier branded phones that like the Sense user interface, the options are Dev Edition or International. Dev Edition has the advantage of significantly faster updates. International version has no real advantage that I know of. At the moment, the international version has a newer version of Sense, but they'll be waiting until January for Android 4.4. But those using the Dev Edition should receive that update any day now (including the updated version of Sense).
EsJayEs said:
It's fairly common. For people on carrier branded phones that like the Sense user interface, the options are Dev Edition or International. Dev Edition has the advantage of significantly faster updates. International version has no real advantage that I know of. At the moment, the international version has a newer version of Sense, but they'll be waiting until January for Android 4.4. But those using the Dev Edition should receive that update any day now (including the updated version of Sense).
Click to expand...
Click to collapse
Thanks!
I have the international version, but I will convert to Dev Ed once the 4.4 update (RUU) is released. Usually when the OTA update is released, the RUU is released at the same time? This is my first HTC phone, so I'm clueless
Hard to say. If they release the RUU, it could be a few days or weeks after the OTA is being pushed. But the OTA will almost definitely come first. If you were to convert now, you'd have verification that your work was done properly when the OTA is pushed and successfully installs.
EsJayEs said:
Hard to say. If they release the RUU, it could be a few days or weeks after the OTA is being pushed. But the OTA will almost definitely come first. If you were to convert now, you'd have verification that your work was done properly when the OTA is pushed and successfully installs.
Click to expand...
Click to collapse
Good to know, I'd start converting then once I hear the OTA is being pushed to find out the result of the conversion quickly. Thanks a lot for all your help!
EsJayEs said:
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
Click to expand...
Click to collapse
Sorry to bother you again with my questions!
At any point do I need to install a custom recovery? I'm not going to root at the moment. What's the best and easy method to install/flash the RUU?
Sent from my HTC One using XDA Premium 4 mobile app
You will need to custom recovery & root to gain S-Off, but once you have ran the dev RUU and the phone is converted, you will not need to root/recovery again.
M_Shaaban said:
Sorry to bother you again with my questions!
At any point do I need to install a custom recovery? I'm not going to root at the moment. What's the best and easy method to install/flash the RUU?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You do not need to install custom recovery.or root. Once you have S-Off (download and use the latest version of Rumrunner http://rumrunner.us/downloads-2/ for this), change your CID to BS_US001 and change your MID to PN712000.
Change your MID using the information here http://forum.xda-developers.com/showthread.php?t=2322820
Changing your CID using the Fastboot command
Code:
fastboot oem writecid BS_US001
After that, run the RUU program downloaded from here http://dl4.htc.com/RomCode/Source_a...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
Again, custom recovery and root are not required (or even useful) for this process. I strongly prefer not to use any custom recovery because it makes future OTA updates impossible.
EsJayEs said:
You do not need to install custom recovery.or root. Once you have S-Off (download and use the latest version of Rumrunner http://rumrunner.us/downloads-2/ for this), change your CID to BS_US001 and change your MID to PN712000.
Change your MID using the information here http://forum.xda-developers.com/showthread.php?t=2322820
Changing your CID using the Fastboot command
Code:
fastboot oem writecid BS_US001
After that, run the RUU program downloaded from here http://dl4.htc.com/RomCode/Source_a...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
Again, custom recovery and root are not required (or even useful) for this process. I strongly prefer not to use any custom recovery because it makes future OTA updates impossible.
Click to expand...
Click to collapse
Thanks again for your response, the MID is mentioned in other posted slightly different than the one you mentioned here - PN0712000. Which one is correct? Or is there no difference between PN712000 and PN0712000? My current MID is PN0714000
Sent from my HTC One using XDA Premium 4 mobile app
Also do I need to relock the bootloader at any stage of the process?
Rumrunner S-OFF must have the phone rooted and requires custom recovery. Can I unroot and install stock recovery before flashing the RUU? Or Installing the RUU will overwrite the custom recovery and installing stock recovery and removing root? If I have to flash the stock recovery to overwrite the custom one, how to do so? Where can I find the compatible latest version of stock recovery?
Do I need to downgrade the hboot at any point? I'm running Windows 8.1 -if that's relevant.
Thanks a lot again for all your help!
Sent from my HTC One using XDA Premium 4 mobile app
M_Shaaban said:
Also do I need to relock the bootloader at any stage of the process?
Click to expand...
Click to collapse
As long as you're S-Off, no you don't. I highly recommend, you do not go back to S-On!!
M_Shaaban said:
Rumrunner S-OFF must have the phone rooted and requires custom recovery. Can I unroot and install stock recovery before flashing the RUU? Or Installing the RUU will overwrite the custom recovery and installing stock recovery and removing root? If I have to flash the stock recovery to overwrite the custom one, how to do so? Where can I find the compatible latest version of stock recovery?
Click to expand...
Click to collapse
Installing RUU, will wipe everything, and install everything back to stock (hboot, recovery, firmware, rom).
M_Shaaban said:
Do I need to downgrade the hboot at any point?
Click to expand...
Click to collapse
If running the RUU gives error 155, then downgrade to hboot 1.44 first; you'll get error 155 on hboot 1.55+
M_Shaaban said:
I'm running Windows 8.1 -if that's relevant.
Click to expand...
Click to collapse
If you have problems with fastboot and/or adb might be best to use Win7. Win8 and 8.1 are known to sometimes have "issues"
nkk71 said:
As long as you're S-Off, no you don't. I highly recommend, you do not go back to S-On!!
Installing RUU, will wipe everything, and install everything back to stock (hboot, recovery, firmware, rom).
If running the RUU gives error 155, then downgrade to hboot 1.44 first; you'll get error 155 on hboot 1.55+
If you have problems with fastboot and/or adb might be best to use Win7. Win8 and 8.1 are known to sometimes have "issues"
Click to expand...
Click to collapse
Thanks a lot for your response! Just to confirm MID for HTC One Developer Edition is it PN712000 or PN0712000? Or there is no difference.
M_Shaaban said:
Thanks a lot for your response! Just to confirm MID for HTC One Developer Edition is it PN712000 or PN0712000? Or there is no difference.
Click to expand...
Click to collapse
yes it makes a difference
It's PN0712000
http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/variants.png
and iirc correctly, you may need to use an engineering hboot to change mid, if the normal hboot doesnt work.
EDIT: an be careful with engineering hboot, they have some very powerful commands, that could brick your phone. i think there's a guide somewhere around here, but i don't have the link right now
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