Database Develop

Flashing RUU after S-OFF

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.

[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/

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] How to find out what carrier this phone is?

i got the phone stuck on TWRP so i downloaded the telus ruu and installed it fine, then i noticed there was a rogers one too. is there anyway to tell what carrier this phone is for? i have no sim cards to test it out besides a fido one. its the 801e UL variant. someone must be able to help me i have searched everywhere for answers.

In fastboot: fastboot getvar all
This will display your CID

Marc199 said:
In fastboot: fastboot getvar all
This will display your CID
Click to expand...
Click to collapse
ya but what if the cid was changed to 1111111111 to get s-off?

I don't think it is possible to find out what your original CID was. Where did you buy the phone?

gnome9er said:
ya but what if the cid was changed to 1111111111 to get s-off?
Click to expand...
Click to collapse
that's SuperCID, keep it as is and download CIDGetter from Play Store, when it sees SuperCID it will pull CID from a secondary location, hopefully that wasn't changed and it will show your original CID.

[Q] Can i convert my Htc one with Vodafone Cid to Stock and receive ota updates?

Can i convert my Htc one with Vodafone Cid to Stock and receive ota updates?

shaktihtcone said:
Can i convert my Htc one with Vodafone Cid to Stock and receive ota updates?
Click to expand...
Click to collapse
Both cid # and mid # MUST match the main-ver you want to flash. CID and MID require s-off to be modified.
i.e if you have a x.xx.161.x main-ver, you need corresponding MID PN0710000 and one of compatible CID like VODAP001 or VODAP102, etc... (Vodafone)
i.e if you have a x.xx.401.x main-ver, you need corresponding MID PN0710000 and one of compatible CID like HTC__001 or HTC__101, HTC__203 etc... (stock international)
If you have a CID that doesn't match your main-ver, your phone will not find any OTA update
If you have proper CID but wrong MID, your phone will find and download OTA, but will fail the update process.
f you want to convert using a RUU, both CID and MID must match otherwise the ruu will not flash.
copy/paste the output of this command
Code:
fastboot getvar all
minus emei and sn and it will be much easier to tell you what options you have.

shaktihtcone said:
Can i convert my Htc one with Vodafone Cid to Stock and receive ota updates?
Click to expand...
Click to collapse
the correct answer to your question is YES
(i couldnt resist)

Thanks for replying, and my cid is voda001, could u pls let me know the whole procedure of how to do that and where can i get the required softwares.
Thanks in advance:fingers-crossed:

And i'm totally new to this, so just wanna know after the whole procedure is completed will there be any problems?
And does it need rooting?
If u could give the detailed procedure it would be of gr8 help.

shaktihtcone said:
Thanks for replying, and my cid is voda001, could u pls let me know the whole procedure of how to do that and where can i get the required softwares.
Thanks in advance:fingers-crossed:
Click to expand...
Click to collapse
you want to convert to stock international? Stock GPE? Stock dev edition? what is your hboot version?

alray said:
you want to convert to stock international? Stock GPE? Stock dev edition? what is your hboot version?
Click to expand...
Click to collapse
Stock International, so that i could receive kitkat which has already been delivered to international unlocked phones.
And my hboot version is 1.55.0000

shaktihtcone said:
Stock International, so that i could receive kitkat which has already been delivered to international unlocked phones.
And my hboot version is 1.55.0000
Click to expand...
Click to collapse
Fisrt of all, do you have ADB and Fastboot installed on your computer and HTC one drivers working properly?

alray said:
Fisrt of all, do you have ADB and Fastboot installed on your computer and HTC one drivers working properly?
Click to expand...
Click to collapse
Sorry, but i don't have either of them installed as i don't know how to use them
And i Do have HTC Sync manager installed, so i guess HTC drivers are working properly.

shaktihtcone said:
Sorry, but i don't have either of them installed as i don't know how to use them
Click to expand...
Click to collapse
Np, just want to go step by step, that is why im asking you
shaktihtcone said:
And i Do have HTC Sync manager installed, so i guess HTC drivers are working properly.
Click to expand...
Click to collapse
Yes it should
So go to this thread and install adb/fastboot.
turn on usb debugging mode on your phone ''settings ---> developer option ---> check the usb debug box'' if developer option menu is messing from you settings menu do this: settings ---> about phone ---> tap the build number rapidly until you are prompted you unlocked developers option.
connect phone to pc via usb while phone is normally booted in Android (better to use port behind the pc instead of usb port in front. also i will recommend you not to use a windows 8.1 computer.
quote me when this step is done. (use reply below my post so i can see you replied)

alray said:
Np, just want to go step by step, that is why im asking you
Yes it should
So go to this thread and install adb/fastboot.
turn on usb debugging mode on your phone ''settings ---> developer option ---> check the usb debug box'' if developer option menu is messing from you settings menu do this: settings ---> about phone ---> tap the build number rapidly until you are prompted you unlocked developers option.
connect phone to pc via usb while phone is normally booted in Android (better to use port behind the pc instead of usb port in front. also i will recommend you not to use a windows 8.1 computer.
quote me when this step is done. (use reply below my post so i can see you replied)
Click to expand...
Click to collapse
Done and also i have windows 8.1 installed. Will there be any prob? Or can i continue?

shaktihtcone said:
Done and also i have windows 8.1 installed. Will there be any prob? Or can i continue?
Click to expand...
Click to collapse
You'll probably encounter problem later in the process with win 8.1. Win 8.1 require hboot 1.55 for fastboot to work. During the process you will need to downgrade hboot to 1.44 to flash the international RUU. And your phone will not be recognized by computer when using fastboot and you will be stuck there. So better to find a windows 7 computer or maybe you could dual boot win 7 on the same comp.
now you should be able to continue with next step even with win 8.1
so start Minimal ADB and Fastboot, a command prompt should open. with phone connected to pc and usb debugging enabled, check that drivers are working properly with this command:
Code:
adb devices
should output this:
Code:
List of devices attached
HT(yourserial#) device

alray said:
You'll probably encounter problem later in the process with win 8.1. Win 8.1 require hboot 1.55 for fastboot to work. During the process you will need to downgrade hboot to 1.44 to flash the international RUU. And your phone will not be recognized by computer when using fastboot and you will be stuck there. So better to find a windows 7 computer or maybe you could dual boot win 7 on the same comp.
now you should be able to continue with next step even with win 8.1
so start Minimal ADB and Fastboot, a command prompt should open. with phone connected to pc and usb debugging enabled, check that drivers are working properly with this command:
Code:
adb devices
should output this:
Code:
List of devices attached
HT(yourserial#) device
Click to expand...
Click to collapse
Hope this is what u were asking earlier.

shaktihtcone said:
Hope this is what u were asking earlier.
Click to expand...
Click to collapse
so now you have to
unlock your bootloader
install a custom recovery + root
gain s-off using rumrunner
note that unlocking bootloader may void your warranty as advised by htc on htcdev.com

alray said:
so now you have to
unlock your bootloader
install a custom recovery + root
gain s-off using rumrunner
Click to expand...
Click to collapse
So does this procedure requires rooting?
And if it does how can a rooted device receive updates from HTC?
And once the whole procedure is complete will my HTC One be still rooted?
And i could get a window 7 pc tomorrow , so will continue the remaining procedure tomorrow.
If u could pls give the detailed procedure, i would perform it tomorrow and will let u know .
Thank u so much for helping out.

shaktihtcone said:
So does this procedure requires rooting?
Click to expand...
Click to collapse
Yes you need root to s-off. You need s-off to change cid and downgrade hboot. you need to change cid and downgrade hboot to flash international ruu.
shaktihtcone said:
And if it does how can a rooted device receive updates from HTC?
Click to expand...
Click to collapse
When you will flash the international RUU.exe, your device will go back to 100% stock (stock recovery, stock OS, stock hboot) means no root anymore like if your device was brand new.
shaktihtcone said:
And once the whole procedure is complete will my HTC One be still rooted?
Click to expand...
Click to collapse
no the ruu.exe will remove root. You can always re-root if you need root after all that procedure and after downloaded the latest OTA
shaktihtcone said:
And i could get a window 7 pc tomorrow , so will continue the remaining procedure tomorrow.
If u could pls give the detailed procedure, i would perform it tomorrow and will let u know .
Click to expand...
Click to collapse
after you gained S-OFF:
Change your CID
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
note there is 2 lower cases H T C _ _ 0 0 1
confirm cid has changed
Code:
fastboot oem readcid
and then follow this guide to downgrade hboot, removed tempered flag from hboot, lock bootloader and flash the ruu.exe. Use this RUU.exe for international
shaktihtcone said:
Thank u so much for helping out.
Click to expand...
Click to collapse
Just hit the thanks button if I helped
edit: And don't go back to S-ON the ruu will not turn S-On, it can manually be done but stay S-OFF!

just a quick note, after "fastboot oem writecid HTC__001"
do a "fastboot reboot-bootloader" and continue with @alray
(sorry if i bugged in)

nkk71 said:
just a quick note, after "fastboot oem writecid HTC__001"
do a "fastboot reboot-bootloader" and continue with @alray
(sorry if i bugged in)
Click to expand...
Click to collapse
your help is always welcome

shaktihtcone said:
Thank u so much for helping out.
Click to expand...
Click to collapse
on @alray's behalf: you're welcome, and if you want to thank him because his posts are useful you can hit the THANKS button on his posts

shaktihtcone said:
So does this procedure requires rooting?
And if it does how can a rooted device receive updates from HTC?
And once the whole procedure is complete will my HTC One be still rooted?
And i could get a window 7 pc tomorrow , so will continue the remaining procedure tomorrow.
If u could pls give the detailed procedure, i would perform it tomorrow and will let u know .
Thank u so much for helping out.
Click to expand...
Click to collapse
for s-off which procedure should i follow as mine is uk vodafone model?
verizon one or international one? or any other?