Database Develop

[Solved] Back to stock

All right, here comes a noob question:
My HTC One is from Israel, and though I made a nandroid backup of my phone after I rooted it, I don't have one from before my rooting it. That said, my CID was HTC__K18...there is no RUU for that CID, so I used rumrunner to s-off my phone, changed my CID to HTC__01 and used the European RUU (the U not the UL because my phone is a U) to get %100 back to stock. The RUU that I flashed has a hboot of 1.44 and my stock was already a 1.54 and 4.2.2 (maybe 4.1.2?)...anyway after flashing the RUU, I'm not able to OTA and I really just want to get %100 stock...in a way that I'd be capable of receiving all the updates OTA and have the highest firmware/software. Thanks in advance!
Oh, and here's some of my info:
version-bootloader: 1.44.0000 (it shipped with 1.54 but I RUUed an older version)
version-baseband: 4A.14.3250.13
version-main: 1.29.401.2 (it shipped with 2.24.401.2)
version-misc: PVT SHIP S-OFF (used rumrunner to s-off hboot of 1.54)
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__001 (I changed the cid from HTC__k18)

shpongleeyes said:
All right, here comes a noob question:
My HTC One is from Israel, and though I made a nandroid backup of my phone after I rooted it, I don't have one from before my rooting it. That said, my CID was HTC__K18...there is no RUU for that CID, so I used rumrunner to s-off my phone, changed my CID to HTC__01 and used the European RUU (the U not the UL because my phone is a U) to get %100 back to stock. The RUU that I flashed has a hboot of 1.44 and my stock was already a 1.54 and 4.2.2 (maybe 4.1.2?)...anyway after flashing the RUU, I'm not able to OTA and I really just want to get %100 stock...in a way that I'd be capable of receiving all the updates OTA and have the highest firmware/software. Thanks in advance!
Oh, and here's some of my info:
version-bootloader: 1.44.0000 (it shipped with 1.54 but I RUUed an older version)
version-baseband: 4A.14.3250.13
version-main: 1.29.401.2 (it shipped with 2.24.401.2)
version-misc: PVT SHIP S-OFF (used rumrunner to s-off hboot of 1.54)
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__001 (I changed the cid from HTC__k18)
Click to expand...
Click to collapse
Question: where do you want to go?
1- To an European stock model
2- To your version (I have a nandroid of 2.24.401.2 for a PN0711000, M7_U)

nkk71 said:
Question: where do you want to go?
1- To an European stock model
2- To your version (I have a nandroid of 2.24.401.2 for a PN0711000, M7_U)
Click to expand...
Click to collapse
Whatever would give me OTA updates and allow me to be as stock as possible! Just out of curiosity, what would the benefits of each be? Thank you!

shpongleeyes said:
Whatever would give me OTA updates and allow me to be as stock as possible! Just out of curiosity, what would the benefits of each be? Thank you!
Click to expand...
Click to collapse
LOL, this just resulted in another question: why not use a custom ROM, they get updated way more frequently than OTAs? If you want "stock as possible" you can check out ARHD, it's very stock. (and since you're S-Off you can upgrade/downgrade anytime, including firmware!!)
As for benefits of the other two options:
1) I think HTC__001 (or was it Y13, not sure), are usually among the first WWE editions to get OTAs (not as fast as custom ROMs )
2) HTC_K18 would put you back to a state where you bought the phone.
It's all personal choice, eg I like stock but want it rooted so I'm currently running ARHD 13.3 (until I decide to upgrade), others like their Venom Tweaks or InsertCoin etc... and again for others they need to be unrooted because of some banking apps.
So give it a thought and let me know, which road you wanna take
PS: Hit the thanks button if I helped

nkk71 said:
LOL, this just resulted in another question: why not use a custom ROM, they get updated way more frequently than OTAs? If you want "stock as possible" you can check out ARHD, it's very stock. (and since you're S-Off you can upgrade/downgrade anytime, including firmware!!)
As for benefits of the other two options:
1) I think HTC__001 (or was it Y13, not sure), are usually among the first WWE editions to get OTAs (not as fast as custom ROMs )
2) HTC_K18 would put you back to a state where you bought the phone.
It's all personal choice, eg I like stock but want it rooted so I'm currently running ARHD 13.3 (until I decide to upgrade), others like their Venom Tweaks or InsertCoin etc... and again for others they need to be unrooted because of some banking apps.
So give it a thought and let me know, which road you wanna take
PS: Hit the thanks button if I helped
Click to expand...
Click to collapse
Thank you for the quick reply!
Okay, so I'd like to go with the European road...as far as custom ROMs are concerned, I had ARHD, both GE and Sense, but I just want things to run smoothly and not worry about OTAs....I'd like to receive them as soon as they're available with the least amount of headache...
On that note, can I receive OTA updates directly from HTC while I'm s-off? Because currently I don't have that option...it doesn't even show that I have an update available.
Also, is your nandroid of 2.24.401.2 made with cid HTC__k18?
P.s. I don't even need/want to root the phone again...it's just too much for me. I'd like to get as stock as possible while keeping the options open (that's why I want to leave s-off).
Thank you again for your help! You're awesome!

shpongleeyes said:
Thank you for the quick reply!
Okay, so I'd like to go with the European road...as far as custom ROMs are concerned, I had ARHD, both GE and Sense, but I just want things to run smoothly and not worry about OTAs....I'd like to receive them as soon as they're available with the least amount of headache...
On that note, can I receive OTA updates directly from HTC while I'm s-off? Because currently I don't have that option...it doesn't even show that I have an update available.
P.s. I don't even need/want to root the phone again...it's just too much for me. I'd like to get as stock as possible while keeping the options open (that's why I want to leave s-off).
Thank you again for your help! You're awesome!
Click to expand...
Click to collapse
Ok, European road
1- You've already changed your CID, you still need to change your MID: "fastboot oem writemid PN0710000"
(keep a record of your original CID, MID, and software/firmware version somewhere in case you ever need it)
2- remove tampered either using revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- set your phone to LOCKED (not relocked) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- then use the full European RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
you should keep S-Off and not go back S-On.
After installing the RUU you should immediately start receiving OTAs all the way up to 3.62
PS: remember the above procedure will wipe everything off your phone, so back up anything you may need first!!

nkk71 said:
Ok, European road
1- You've already changed your CID, you still need to change your MID: "fastboot oem writemid PN0710000"
(keep a record of your original CID, MID, and software/firmware version somewhere in case you ever need it)
2- remove tampered either using revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- set your phone to LOCKED (not relocked) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- then use the full European RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
you should keep S-Off and not go back S-On.
After installing the RUU you should immediately start receiving OTAs all the way up to 3.62
PS: remember the above procedure will wipe everything off your phone, so back up anything you may need first!!
Click to expand...
Click to collapse
You're awesome. However, I did all those steps except for the first step...when I go into recovery mode now, there's still the red lettering as well as when I go into "Tell HTC and error reporting" the red lettering says "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings." Oh, and I'm not able to receive the OTAs.
Now, if I change the MID, do I need to do all the steps again or can I just do the first step now? Will that help get rid of the "test device" warnings that I have on the phone?
Oh, and I used this European one before (cause I have a U and not UL) http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
Why would I use the UL one?
Thank you again for you time and help!

shpongleeyes said:
You're awesome. However, I did all those steps except for the first step...when I go into recovery mode now, there's still the red lettering as well as when I go into "Tell HTC and error reporting" the red lettering says "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings." Oh, and I'm not able to receive the OTAs.
Now, if I change the MID, do I need to do all the steps again or can I just do the first step now? Will that help get rid of the "test device" warnings that I have on the phone?
Thank you again for you time and help!
Click to expand...
Click to collapse
You won't get any OTAs because of your MID, change it, and see if you start getting the OTAs. M7_U and M7_UL share pretty much most of the software stuff, the hardware is different of course, but MID 0711 and CID HTC__001 won't get any OTAs.
The "Tell HTC and error reporting" red text is because you're S-Off, personally I wouldn't care. But if it bothers you A LOT, you'll need to go S-On again, and AT THIS TIME you should NOT!!! we can deal with that later.
Change MID, and confirm you are now getting OTAs
Again DO NOT GO S-ON, at least for the time being!!
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
shpongleeyes said:
Oh, and I used this European one before (cause I have a U and not UL) http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
Click to expand...
Click to collapse
Oh I didnt see that one, but it should give you updates till 2.24.401.9 at least. Don't know if 3.62 out yet for that PN.

nkk71 said:
You won't get any OTAs because of your MID, change it, and see if you start getting the OTAs. M7_U and M7_UL share pretty much most of the software stuff, the hardware is different of course, but MID 0711 and CID HTC__001 won't get any OTAs.
The "Tell HTC and error reporting" red text is because you're S-Off, personally I wouldn't care. But if it bothers you A LOT, you'll need to go S-On again, and AT THIS TIME you should NOT!!! we can deal with that later.
Change MID, and confirm you are now getting OTAs
Again DO NOT GO S-ON, at least for the time being!!
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
Oh I didnt see that one, but it should give you updates till 2.24.401.9 at least. Don't know if 3.62 out yet for that PN.
Click to expand...
Click to collapse
Okay, I tried to change the mid but the console is giving me an error:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.031s

shpongleeyes said:
Okay, I tried to change the mid but the console is giving me an error:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.031s
Click to expand...
Click to collapse
Let's slow it down a little, if I understand correctly:
1- you are now unTAMPERED
2- you are now LOCKED, not RElocked or UNlocked
3- you have CID: HTC__001
4- you have MID: PN0711000
5- you ran the RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- you are still S-Off (please!)
If all of the above are true, when you go to Settings->About->Software Update (or whatever it's called), does it show an update? or what does it say
EDIT: can you repost a "fastboot getvar all" (remove IMEI and s/n)

nkk71 said:
Let's slow it down a little, if I understand correctly:
1- you are now unTAMPERED
2- you are now LOCKED, not RElocked or UNlocked
3- you have CID: HTC__001
4- you have MID: PN0711000
5- you ran the RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- you are still S-Off (please!)
If all of the above are true, when you go to Settings->About->Software Update (or whatever it's called), does it show an update? or what does it say
EDIT: can you repost a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
you're correct about everything:
All it says is that my software is up-to-date...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

shpongleeyes said:
you're correct about everything:
All it says is that my software is up-to-date...
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
Before we go on messing with MID, can you just change CID to HTC__J15 (two underscores) and check for a software update, don't know the original 1.xx version, but I am sure that J15 PN0711 got the 2.24.401.2 and (possibly) 2.24.401.9.
Just check if it gives an update with HTC__J15, no need to download it!!

nkk71 said:
Before we go on messing with MID, can you just change CID to HTC__J15 (two underscores) and check for a software update, don't know the original 1.xx version, but I am sure that J15 PN0711 got the 2.24.401.2 and (possibly) 2.24.401.9.
Just check if it gives an update with HTC__J15, no need to download it!!
Click to expand...
Click to collapse
Yes
That gives me an option to upgrade...
now what?

shpongleeyes said:
Yes
That gives me an option to upgrade...
now what?
Click to expand...
Click to collapse
Oh man, sorry to keep you hanging, but we may need to pick this up tomorrow, going for dinner now, wont be back till tomorrow,
but try setting CID to your original one, and see if you get any updates for your original CID.
sorry, got to go, I'll check back on you tomorrow
whatever you decide to do, do NOT GO S-ON (at least for now)
Have a good evening...

nkk71 said:
Oh man, sorry to keep you hanging, but we may need to pick this up tomorrow, going for dinner now, wont be back till tomorrow,
but try setting CID to your original one, and see if you get any updates for your original CID.
sorry, got to go, I'll check back on you tomorrow
whatever you decide to do, do NOT GO S-ON (at least for now)
Have a good evening...
Click to expand...
Click to collapse
When I set it back to my original CID there are no updates...enjoy the food
I look forward to tomorrow!

shpongleeyes said:
When I set it back to my original CID there are no updates...enjoy the food
I look forward to tomorrow!
Click to expand...
Click to collapse
Hey, how are you today?
I'll be online later (around 5 or 6), but it looks like that RUU is fully compatible with ur original CID. So go ahead with your original CID, and get the OTAs. U should be able to get at least to 2.24.401.9, don't know if 3.62 is out for u yet.
Keep s-off in case we need to change something later.
C u later...
Sent from my HTC One using Tapatalk

nkk71 said:
Hey, how are you today?
I'll be online later (around 5 or 6), but it looks like that RUU is fully compatible with ur original CID. So go ahead with your original CID, and get the OTAs. U should be able to get at least to 2.24.401.9, don't know if 3.62 is out for u yet.
Keep s-off in case we need to change something later.
C u later...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hey, no the RUU is not compatible with my original CID (HTC__K18) as there are no available upgrades after I change the CID...also the same is true when I change it to HTC__001, though it did work when you told me to update to J something or other...weird.

shpongleeyes said:
Hey, no the RUU is not compatible with my original CID (HTC__K18) as there are no available upgrades after I change the CID...also the same is true when I change it to HTC__001, though it did work when you told me to update to J something or other...weird.
Click to expand...
Click to collapse
Well I guess you have 2 choices:
1- set CID to HTC__J15 -> a friend of mine has PN0711000 HTC__J15, it's basically the M7_U version and HTC__J15 is a nonbranded WWE edition but usually for the Middle East
2- set CID to HTC__001, set MID to PN0710000, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
by changing to MID PN0710000, it will make the software on your phone think it's a UL model, but since the hardware isn't there for LTE, it won't make any difference.
Step 1, is probably the easiest to do, so why not just set it to J15 and see how far the updates go. (ie if 3.62 is out for J15).
Hope that helps

nkk71 said:
Well I guess you have 2 choices:
1- set CID to HTC__J15 -> a friend of mine has PN0711000 HTC__J15, it's basically the M7_U version and HTC__J15 is a nonbranded WWE edition but usually for the Middle East
2- set CID to HTC__001, set MID to PN0710000, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
by changing to MID PN0710000, it will make the software on your phone think it's a UL model, but since the hardware isn't there for LTE, it won't make any difference.
Step 1, is probably the easiest to do, so why not just set it to J15 and see how far the updates go. (ie if 3.62 is out for J15).
Hope that helps
Click to expand...
Click to collapse
Thank you for you patience and your help! You've been amazing!

shpongleeyes said:
Thank you for you patience and your help! You've been amazing!
Click to expand...
Click to collapse
No problem, glad to be of help. If everything's OK now, could I please ask you to change the main thread title to include [SOLVED]. Thanks & take care

RUU_M7 for O2(UK)

Hello. I have a HTC One and need the RUU_M7....... file for O2 UK, but cannot find it anywhere? Will RUU_M7 for O2 (Germany) work?

Claus71 said:
Hello. I have a HTC One and need the RUU_M7....... file for O2 UK, but cannot find it anywhere? Will RUU_M7 for O2 (Germany) work?
Click to expand...
Click to collapse
Is it same CID and MID? if so yes it should work, if not then no it won't work (unless you are s-off).
Are you trying to go back to stock for warranty or for what's your goal? there's more than one way to skin a cat, but better be specific what you intend on doing, and post a "fastboot getvar all" (remove IMEI and s/n before posting).

Thank you for your quick reply. I am trying to run an update. The phone is rooted and gives me an error when trying. When I get home from work, I will try to send information about the phone. Once again, thank you

Claus71 said:
Thank you for your quick reply. I am trying to run an update. The phone is rooted and gives me an error when trying. When I get home from work, I will try to send information about the phone. Once again, thank you
Click to expand...
Click to collapse
Are you on stock recovery? is it an OTA update you are trying to achieve??

exocetdj said:
Are you on stock recovery? is it an OTA update you are trying to achieve??
Click to expand...
Click to collapse
I am new to Android, so I am not quite sure. I have just been looking around this great website to get help. This is my information:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3858mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
Jun 21 2013,23:49:03.0
To unlock and root the phone, I followed this great guide: http://www.youtube.com/watch?v=kJYAS2KN17Y
The recovery.img is this one: http://forum.xda-developers.com/showthread.php?t=2172979
I am looking forward to your reply.
Best regards,
Claus.

I am trying to achive the OTA update, and be able to get future updates.

You need to install a stock recovery if you want to install ota updates on stock Rom
Have u made a nandroid backup of your stock Rom? There should be a recovery. img file in therex flash that via Fastboot then you can update

No, I did not make a backup. But I have two identical phones, and the other one is rooted after the update. Will it be possible to get the ROM out of this phone and copy it to the one that will not update?
If this is an option, please be kind to explain (step by step) what to do. Thank

theres no ruu file and will never exist.
the only way to going back to stock, visit htc1guru.com donwload a nandroid backup
find your right version or what you need, but danger !!!
for example if you have Android 4.3 and restore a nandroid backup with Android 4.2.2 (Downgrade)
the touchscreen will not work, its not broken, cuz they are other driver.
you wil lbe able to use only usb otg mouse

Smilex93 said:
theres no ruu file and will never exist.
the only way to going back to stock, visit htc1guru.com donwload a nandroid backup
find your right version or what you need, but danger !!!
for example if you have Android 4.3 and restore a nandroid backup with Android 4.2.2 (Downgrade)
the touchscreen will not work, its not broken, cuz they are other driver.
you wil lbe able to use only usb otg mouse
Click to expand...
Click to collapse
The phone that will not update is Android 4.2.2 but the other phone is Android 4.3. Can I make a copy of the Android 4.3 phone?

Claus71 said:
The phone that will not update is Android 4.2.2 but the other phone is Android 4.3. Can I make a copy of the Android 4.3 phone?
Click to expand...
Click to collapse
Will somebody please link to the right recovery that I can use for my phone?

Claus71 said:
Will somebody please link to the right recovery that I can use for my phone?
Click to expand...
Click to collapse
That's going to be a bit difficult as:
(bootloader) version-main:
Click to expand...
Click to collapse
implies you firmware version has disappeared.
given you're on "(bootloader) version-bootloader: 1.54.0000"
means it should be a 2.24.xxx.x, you could try the 2.24.401.x from here: http://forum.xda-developers.com/showthread.php?t=2463387
but if you unlocked your phone using HTCdev, then the preloaded apps will be missing, and OTA won't succeed.
I know I'm not helping much, so let me ask something possibly useful instead: how did you end up in this situation?

nkk71 said:
That's going to be a bit difficult as:
implies you firmware version has disappeared.
given you're on "(bootloader) version-bootloader: 1.54.0000"
means it should be a 2.24.xxx.x, you could try the 2.24.401.x from here: http://forum.xda-developers.com/showthread.php?t=2463387
but if you unlocked your phone using HTCdev, then the preloaded apps will be missing, and OTA won't succeed.
I know I'm not helping much, so let me ask something possibly useful instead: how did you end up in this situation?
Click to expand...
Click to collapse
Thanks for helping me I ended up in this situation as follows:
1. I got the phones from a friend in Ireland, but I live in Denmark, and the Danish language was not in the phones.
2. I am new to Android, so thought that it just was a matter of a missing update. Phone no1 was updated to Android 4.3, but still no Danish language.
3. Did some research, and found out how to unlock and root the phone.
4. I was then able to install an App called morelocale2 which enabled the Danish language.
5. I would just do the same to phone no2, but did not realise that I wouldn't be able to update afterwards, so started with unlocking and rooting the phone. Phone no2 is in Danish now, and everything is working, except the update to Android 4.3. When I try to run the update, the phone goes into CMW-based Recovery v6.0.2.8, during bootup, and is not able to install the update due to an "unknown volume for path" O/DOWNLOAD/OTA_M7_UL_JB_50_S_02_UK_2.24.206.7 - 2.24.206.1_RELEASE_330728s8b3vbw3z7kcmsn.zip
Can I use something from the phone no1 to get no2 to work?
Looking forward to your reply.

Claus71 said:
Thanks for helping me I ended up in this situation as follows:
1. I got the phones from a friend in Ireland, but I live in Denmark, and the Danish language was not in the phones.
2. I am new to Android, so thought that it just was a matter of a missing update. Phone no1 was updated to Android 4.3, but still no Danish language.
3. Did some research, and found out how to unlock and root the phone.
4. I was then able to install an App called morelocale2 which enabled the Danish language.
5. I would just do the same to phone no2, but did not realise that I wouldn't be able to update afterwards, so started with unlocking and rooting the phone. Phone no2 is in Danish now, and everything is working, except the update to Android 4.3. When I try to run the update, the phone goes into CMW-based Recovery v6.0.2.8, during bootup, and is not able to install the update due to an "unknown volume for path" O/DOWNLOAD/OTA_M7_UL_JB_50_S_02_UK_2.24.206.7 - 2.24.206.1_RELEASE_330728s8b3vbw3z7kcmsn.zip
Can I use something from the phone no1 to get no2 to work?
Looking forward to your reply.
Click to expand...
Click to collapse
how about we just convert your phone to your phone completely to international unbranded
but i gotto go now (sorry), if you do want to convert, get S-Off using rumrunner, then you'll be able to change the phone into whatever version/country/carrier you want
Leave the working phone alone: "if it works, dont fix it!!"

nkk71 said:
Leave the working phone alone: "if it works, dont fix it!!"
Click to expand...
Click to collapse
Good point! Listen to it carefully OP! :good:

SaHiLzZ said:
Good point! Listen to it carefully OP! :good:
Click to expand...
Click to collapse
I would love to get it into "international" can someone please explain where to find a guide.
Thanks

S-OFF and then run x.x.401.x based RUU.. now find a guide!

SaHiLzZ said:
S-OFF and then run x.x.401.x based RUU.. now find a guide!
Click to expand...
Click to collapse
I have been trying now to run the rumrunner as described to get to S-OFF. Rumrunner starts doing its things, and after 10-12 min. Rumrunner ask me to press enter to exits the cmd prompt. The phone will now boot as normal, and I grant a permision from the Rumrunner. Everything seems fine, but the phone is still S-ON ???? I have done this now a couple of times with same result..??
What do I do now?

Well once you are S-Off:
Claus71 said:
1. I got the phones from a friend in Ireland, but I live in Denmark, and the Danish language was not in the phones.
Click to expand...
Click to collapse
you'll need to change your CID, here's a list of unbranded WWE CIDs:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
[B]HTC__Y13 --> HTC-Nor[/B]
So if you want Danish / Denmark, you'll need to change to use Y13, so in bootloader/FASTBOOT USB:
fastboot oem writecid HTC__Y13 (two underscores)
fastboot reboot-bootloader
then run this RUU.exe from Windows7: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
this will downgrade everything to 1.28, and you should immediately start receiving all the OTA updates.
stay S-Off
and you might wanna think about custom ROMs, they have some nice touches & optimizations, but if it's not your thing, i can understand.

nkk71 said:
Well once you are S-Off:
you'll need to change your CID, here's a list of unbranded WWE CIDs:
Code:
HTC__001 --> HTC-WWE
HTC__016 --> VODA-Africa-South
HTC__032 --> HTC-EastEurope
HTC__102 --> HTC-GER
HTC__203 --> HTC-FRA
HTC__304 --> HTC-SPA
HTC__405 --> HTC-ITA
HTC__A07 --> HTC-Russia
HTC__E11 --> HTC-Dutch
HTC__J15 --> HTC-GCC
[B]HTC__Y13 --> HTC-Nor[/B]
So if you want Danish / Denmark, you'll need to change to use Y13, so in bootloader/FASTBOOT USB:
fastboot oem writecid HTC__Y13 (two underscores)
fastboot reboot-bootloader
then run this RUU.exe from Windows7: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
this will downgrade everything to 1.28, and you should immediately start receiving all the OTA updates.
stay S-Off
and you might wanna think about custom ROMs, they have some nice touches & optimizations, but if it's not your thing, i can understand.
Click to expand...
Click to collapse
I cannot get the phone into S-OFF.. Please read the post on top of the one that you replyed to. And thank you very much for trying to help

[Q] If I take my phone to a repair shop will they get it back on stock firmware?

I've been pulling my hair out trying to return my phone to stock in order to recieve OTA updates,
it's been the most frustrating process ever.
It's been made infinitely more frustrating because of the fact that my laptop and my desktop both run on windows 8.1
and my HTC One M7 isn't recognized in fastboot in either of them. As a result of this i've been having to borrow friends
laptops which run on windows 7 in order to try and sort the process which i'm not comfortable with.
Tried installing different drivers to no avail.
Been trying all types of things like Hasoon's tool box and an infinite amount of other techniqeus. For hours straight i've been trying and other methods to sort out the issue but have always stumbled into
walls. It's been so frustrating.
Will a phoneshop like a little store in town (not a big store like THREE or Vodaphone) be able to return my phone's software to as new like when I got it from my phone store so that I can recieve OTA updates?

tomquartey said:
I've been pulling my hair out trying to return my phone to stock in order to recieve OTA updates,
it's been the most frustrating process ever
Click to expand...
Click to collapse
I understand its frustrating but you really don't need to send your device to phone shop to return stock and get ota. Its a relatively simple process and many users here can help you. But we can't help if you keep creating new threads each days for the same issue.
thread 1
thread 2
thread 3
thread 4
So as nkk71 said in thread 1
make up your mind, where you wanna post, so people can actually help
Click to expand...
Click to collapse
Now what I understand from all this (correct me if i'm wrong), you were on H3G, you were not able to receive ota to kitkat (even if I doubt H3G released kitkat yet...) So you s-off'ed your phone to install 1.29.401 Ruu.exe with supercid. Now you have these issues:
You can't receive ota
you are using windows 8.1 with hboot 1.44 so fastboot isn't working properly
To receive OTA updates, you need:
stock recovery
CID that match your main-version (the ruu version you installed.... a .401 base)
MID that match your main-ver
CID that match the ruu you used (1.28.401.7):
HTC__001
HTC__E11
HTC__102
HTC__203
HTC__405
HTC__Y13
HTC__304
HTC__032
HTC__A07
HTC__J15
HTC__016
ref here (4th download link in the list)
MID that match the ruu you used (1.28.401.7)
PN0710000
ref here (4th download link in the list)
So now you will need to confirm what you need with this command:
Code:
fastboot getvar all
and you need this:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: [COLOR="Red"]1.29.401.7[/COLOR] [COLOR="red"]-----> assuming this info is good[/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: [COLOR="red"]PN0710000[/COLOR] [COLOR="red"]-------> need this MID (PN0710000)[/COLOR]
(bootloader) cidnum: [COLOR="Red"]NEED CID LISTED ABOVE HERE NOT H3G, NOT SUPERCID[/COLOR]
(bootloader) partition-layout: Generic
(bootloader) security: off
now you should know how to change CID because you already did to be supercid but just in case:
Code:
fastboot oem writecid HTC__001 [COLOR="DarkOrange"]I'll suggest you use HTC__001 but its up to you to chose from the list above[/COLOR]
fastboot reboot-bootloader
then reboot and try to search for ota from your phone.
Now the Win8.1/Fastboot/hboot 1.44 issue: (Yes, you need to solve this first )
get your hands on a winXP, win7 computer or
install windows 7 on dual boot on your computer or
use a Ubuntu live cd instead of windows to use fastboot from terminal (require no installation of ubuntu) as sugested by tobesedated in thread 4 with his awesome guide including picutres (maybe her.. idk ) you can skip steps that involve rumrunner as you already have s-off. you just want adb/fastboot working from the terminal)
now try all this and feel free to ask other questions or pm me like you did, but please don't create another thread for this
Im going to sleep now so don't expect any reply from me for the next 10 hours.
oh and when you'll get fastboot working, post your ''fastboot getvar all'' here (except imei/sn) it will help.
---------- Post added at 08:57 AM ---------- Previous post was at 08:52 AM ----------
Feel free to add anything if i'm missing something

[Q] GPe to Sense

Hello members of XDA,
I ran into a problem trying to restoring my Htc One back to sense version, it sais on the conversion thread that I should have a backup of my original Hboot, which I do not have. I don't know if that's a problem, i downloaded the 1.44 hboot as I guess that's the one I should use to get back to stock. As of now I have S off, and am on hboot 1.54 and on official GPE.
Now comes the part where I'm stuck, I do not know what kind of RUU I need to return to stock, I know I need the hboot 1.44 one but I don't want any problems with bloatware or flashing a wrong baseband etc. Can anyone point me in the right direction of the right RUU? To be sure I'm pasting a getvar all
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-OFF
serialno: xxxx
imei: xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: off

Stefan0vic said:
Hello members of XDA,
I ran into a problem trying to restoring my Htc One back to sense version, it sais on the conversion thread that I should have a backup of my original Hboot, which I do not have. I don't know if that's a problem, i downloaded the 1.44 hboot as I guess that's the one I should use to get back to stock. As of now I have S off, and am on hboot 1.54 and on official GPE.
Now comes the part where I'm stuck, I do not know what kind of RUU I need to return to stock, I know I need the hboot 1.44 one but I don't want any problems with bloatware or flashing a wrong baseband etc. Can anyone point me in the right direction of the right RUU? To be sure I'm pasting a getvar all
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-OFF
serialno: xxxx
imei: xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4014mV
partition-layout: Generic
security: off
Click to expand...
Click to collapse
well all your getvar really shows is yes you converted to GPE
what was the phone before you converted it ? CID - MID and version-main

clsA said:
well all your getvar really shows is yes you converted to GPE
what was the phone before you converted it ? CID - MID and version-main
Click to expand...
Click to collapse
Thank god I saved that all in a word document,
Well my Cid was HTC__E11 it is now supercid, the version main was 4.19.401.11
my model ID was and still is PN0710000

Stefan0vic said:
Thank god I saved that all in a word document,
Well my Cid was HTC__E11 it is now supercid, the version main was 4.19.401.11
my model ID was and still is PN0710000
Click to expand...
Click to collapse
Then download this
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
change you CID back with fastboot
fastboot oem writecid HTC__E11
here's the 1.44 hboot >> https://www.dropbox.com/s/xyqurk33yh409bi/orig_hboot_1.44.0000_M7_RUUmode.zip
flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip <name of hboot>.zip
fastboot reboot
then run the RUU .exe you should be back to almost stock

clsA said:
Then download this
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
change you CID back with fastboot
fastboot oem writecid HTC__E11
here's the 1.44 hboot >> https://www.dropbox.com/s/xyqurk33yh409bi/orig_hboot_1.44.0000_M7_RUUmode.zip
flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip <name of hboot>.zip
fastboot reboot
then run the RUU .exe you should be back to almost stock
Click to expand...
Click to collapse
Thank you so much,
Why do so many threads advice to run 1.44 RUU though? After this I will have 1.44 hboot with android 4.4.2?
Edit: Download is taking aprox 2-3 hrs. Is there any way I can download it a little bit faster?

Stefan0vic said:
Thank you so much,
Why do so many threads advice to run 1.44 RUU though? After this I will have 1.44 hboot with android 4.4.2?
Edit: Download is taking aprox 2-3 hrs. Is there any way I can download it a little bit faster?
Click to expand...
Click to collapse
try here
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
and no you have hboot 1.56 after the RUU step
the hboot 1.44 insures the RUU will work smoothly
it's also a vital step if you want to remove tampered and show locked instead of relocked
to return for repair

clsA said:
try here
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Click to expand...
Click to collapse
Saw you edited your post, thank you so much

Stefan0vic said:
I'll just keep my pc on for a bit Thank you so much for your help.
Just 1 more question, will my bootloader be updated with the RUU itself? I need the phone as much stock possible since I need to give it for warranty for camera replacement.
Click to expand...
Click to collapse
now we are getting somewhere
before running the RUU you have more work then
you have to remove the tampered flag and lock before running the RUU
use this tool to do both >> http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
from @nkk71 SuperGuide
Method 2: Guru Bootloader Reset, more automated, but may freeze
adb push Guru_Bootloader_Reset_1.0.zip /data/media/
in recovery, "install zip" -> "choose zip" -> and select "Guru_Bootloader_Reset_1.0"
go through the installer and select "Remove TAMPERED" and "LOCK Bootloader"; once finished: continue with below reboot command
adb reboot bootloader
and confirm no TAMPERED and LOCKED status
Click to expand...
Click to collapse

clsA said:
now we are getting somewhere
before running the RUU you have more work then
you have to remove the tampered flag and lock before running the RUU
use this tool to do both >> http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
from @nkk71 SuperGuide
Click to expand...
Click to collapse
I dont have the tampered flag so i guess i dont have to do that,
I will use that to get my bootloader locked though, thank you. RUU is still downloading as we speak but I can almost run it
So its:
1. Flash hboot
2. lock bootloader
3. run RUU?

Help!! It returns me with an image fault!!
Error: 158 !

Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?

Stefan0vic said:
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Click to expand...
Click to collapse
don't panic .. just use a different ruu

clsA said:
don't panic .. just use a different ruu
Click to expand...
Click to collapse
I'm trying, I just don't know which one since I can't find an RUU that matches my radio

Stefan0vic said:
Can someone help me.. It's responding with an error 158 despite S off and changing CID back to original..
Is it the RUU?
Click to expand...
Click to collapse
ERROR [110]: FILE OPEN ERROR
This error message indicates that the RUU lacks some specific files or they are damaged, so the RUU cannot continue with the update. You have to get the complete RUU package and try again.
ERROR [120]: MAIN BATTERY POWER
This error message will appear when the Android phone’s battery power is not sufficient (Batter power should be more than 30%). Although RUU will instruct you to plug in the AC adapter, it will still need to make sure that your Android phone has enough power to complete the update. (The Android phone cannot charge the battery when it is connected to the PC while installing the RUU).
ERROR [130]: MODEL ID ERROR
ERROR [131]: CUSTOMER ID ERROR
One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone.
Sent from my HTC One using XDA Premium 4 mobile app

I know what the error means, but I don't know what RUU I need, i thought it accepted everything since I was s off

Stefan0vic said:
I'm trying, I just don't know which one since I can't find an RUU that matches my radio
Click to expand...
Click to collapse
did you change your CID ?
if so put it back to supercid and try
also did you md5 check your download
did you flash the 1.44 hboot ?
RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1
File Size: 1.5 GiB - Downloads: 69507
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Comments: modelid: PN0710000
cid: HTC__001, HTC__E11
HTC__102, HTC__203
HTC__405, HTC__Y13
HTC__304, HTC__032
HTC__A07, HTC__J15
HTC__016
Click to expand...
Click to collapse
after 69,000 plus downloads you think someone would report if it's a bad file

clsA said:
did you change your CID ?
if so put it back to supercid and try
also did you md5 check your download
did you flash the 1.44 hboot ?
after 69,000 plus downloads you think someone would report if it's a bad file
Click to expand...
Click to collapse
Yes I flashed the 1.44 HBOOT,
can I flash supercid with relocked bootloader?
I'll try another RUU in a bit. Does it matter that radio's dont match?

Stefan0vic said:
Yes I flashed the 1.44 HBOOT,
can I flash supercid with relocked bootloader?
I'll try another RUU in a bit. Does it matter that radio's dont match?
Click to expand...
Click to collapse
if you locked the bootloader all you can't do is flash a recovery (I think ? )
for a RUU all your really interested in is the x.xx.401.x part

clsA said:
if you locked the bootloader all you can't do is flash a recovery (I think ? )
for a RUU all your really interested in is the x.xx.401.x part
Click to expand...
Click to collapse
Tried another .401. ruu and its now giving usb error..
I have no idea what im doing wrong. Should HTC Sync be installed for this?

Stefan0vic said:
Tried another .401. ruu and its now giving usb error..
I have no idea what im doing wrong. Should HTC Sync be installed for this?
Click to expand...
Click to collapse
well if you flashed the 1.44 hboot your pc must work in fastboot
what state is the phone in when you run the RUU ? bootloader / recovery / Android OS ?

RUU install with correct CID yet no OTA allowed

Hi XDA gang,
I have a mind bender.. So, I have T-Mobile.. Worked great. Lately, I decided to install Viper Rom after installing kitkat update. Purple fuzz show up on camera and want to go back to Stock to send it in for warranty repair. I am S-off and unlocked and SU and changed my CID to 11111111 and was able to install the M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted" RUU and everything went through ok. My OS is back to stock. No "tampered", but still ***unlocked***. Changed my CID to T-MOB010 and am no longer SU.
I went to receive the OTA update 4.19.531.10 (563.3MB) and it started downloading without a problem. But when it gets to 100% and it wants to run the update package, I get the following error message,
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at htc dot com"
I just want to also note that when I checked the CID after ViperRom was installed, I noticed that my CID was set to "BS_US001". Does this matter? I bought the phone from a guy on craigslist but I was using it just fine on T-Mobile without a hassle and OTA updates were just fine.
Oh yea, I don't have my T-mobile SIM card in the phone at the moment. Can that prevent an OTA install as well?
Could use a kick in the arse.
Thanks!
Johnnie

jtlefebvre said:
Hi XDA gang,
I have a mind bender.. So, I have T-Mobile.. Worked great. Lately, I decided to install Viper Rom after installing kitkat update. Purple fuzz show up on camera and want to go back to Stock to send it in for warranty repair. I am S-off and unlocked and SU and changed my CID to 11111111 and was able to install the M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted" RUU and everything went through ok. My OS is back to stock. No "tampered", but still ***unlocked***. Changed my CID to T-MOB010 and am no longer SU.
I went to receive the OTA update 4.19.531.10 (563.3MB) and it started downloading without a problem. But when it gets to 100% and it wants to run the update package, I get the following error message,
"We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system, please contact us via the support section at htc dot com"
I just want to also note that when I checked the CID after ViperRom was installed, I noticed that my CID was set to "BS_US001". Does this matter? I bought the phone from a guy on craigslist but I was using it just fine on T-Mobile without a hassle and OTA updates were just fine.
Oh yea, I don't have my T-mobile SIM card in the phone at the moment. Can that prevent an OTA install as well?
Could use a kick in the arse.
Thanks!
Johnnie
Click to expand...
Click to collapse
BS_US001 is the dev edition CID. To install ota you must have CID and MID corresponding to your version

alray said:
BS_US001 is the dev edition CID. To install ota you must have CID and MID corresponding to your version
Click to expand...
Click to collapse
Right, but does this mean I have to go back and install a brightstar RUU and change my CID back to BS_US001? Wouldn't the phone not work on T-Mobile anymore? I don't know anything about MID either. Can you shed a little light about it? How would I know which version my phone should be?

jtlefebvre said:
Right, but does this mean I have to go back and install a brightstar RUU and change my CID back to BS_US001? Wouldn't the phone not work on T-Mobile anymore? I don't know anything about MID either. Can you shed a little light about it? How would I know which version my phone should be?
Click to expand...
Click to collapse
If you want to send the phone for repair under warranty, it must be back to 100% sctock, including the right version of OS, proper CID and MID.
If you are not sure what was your original CID and MID, that's a problem.
start by posting the output of "fastboot getvar all" except your IMEI and your SERIALNO. If we can't determine what was your original CID and MID with a getvar, we could pull the partition mmcblk0p6 where the original information is stored.

alray said:
If you want to send the phone for repair under warranty, it must be back to 100% sctock, including the right version of OS, proper CID and MID.
If you are not sure what was your original CID and MID, that's a problem.
start by posting the output of "fastboot getvar all" except your IMEI and your SERIALNO. If we can't determine what was your original CID and MID with a getvar, we could pull the partition mmcblk0p6 where the original information is stored.
Click to expand...
Click to collapse
Thanks for helping me out Alray. Here's the info I got from the getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

jtlefebvre said:
Thanks for helping me out Alray. Here's the info I got from the getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
is the phone 64Gb or 32Gb? and is it rooted?

alray said:
is the phone 64Gb or 32Gb? and is it rooted?
Click to expand...
Click to collapse
It's 32GB and rooted. Silver HTC One

jtlefebvre said:
It's 32GB and rooted. Silver HTC One
Click to expand...
Click to collapse
Something I've noticed when I was checking RUU's on htc1guru was that there's a google play edition RUU with my MID number in it.. I'm wondering if this is the ROM that I should've been using instead of the T-Mobile RUU I installed.. but then again, I'd rather be using the T-mobile RUU for this go round'.
RUU Zip M7 HTC Google Edition 3.06.1700.10
File Size: 418.9 MiB - Downloads: 5143
MD5: 976ae068b29367025a30178f5eb4099d
Comments: RUU For Google Edition Version compiled by XDA user graffixnyc
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
mainver: 3.06.1700.10

jtlefebvre said:
It's 32GB and rooted. Silver HTC One
Click to expand...
Click to collapse
ok its confusing a bit, if your phone was a dev edition it should be BS_US001 PN0712000 and 64gb. T-mobile should be T-MOB010 with MID PN0713000. So its looks like your phone was neither a Dev edition or T-mobile version originally.
I can check your mmcblk0p6 if you agree. This partition contain your original CID and MID. But it also contain your IMEI and SERIALNO which are sensitive number you should not share. If you are fine with this proceed with instructions below:
Make sure you have USB debug enabled from the dev option menu
make sure your phone is booted in the OS
open a command prompt from your adb/fastboot folder and type:
Code:
adb shell
su
You'll probably be prompted to allow/deny superuser access on your phone, if so, make sure to allow superuser access.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
be careful with above command, if you make a mistake, this could harm your phone, you may want to copy/paste the command instead of typing it.
then browse your phone storage (/sdcard) and PM me the file just created (mmcblk0p6_backup.img), do not post it in your thread, because like I said, this file contain your IMEI number.
---------- Post added at 02:35 PM ---------- Previous post was at 01:57 PM ----------
@jtlefebvre
from the information stored in your mmcblk0p6 partition, your original phone info are:
CID: BS_US001
MID: PN0712000
P/N: 99HT223-00
S/N: FA34TW9*****
IMEI: 354439*********
Production date: 2013/04/03
So change back your cid to BS_US001 and follow nkk71's guide linked in my signature using the 1.29.1540.16 ruu.zip

alray said:
ok its confusing a bit, if your phone was a dev edition it should be BS_US001 PN0712000 and 64gb. T-mobile should be T-MOB010 with MID PN0713000. So its looks like your phone was neither a Dev edition or T-mobile version originally.
I can check your mmcblk0p6 if you agree. This partition contain your original CID and MID. But it also contain your IMEI and SERIALNO which are sensitive number you should not share. If you are fine with this proceed with instructions below:
Make sure you have USB debug enabled from the dev option menu
make sure your phone is booted in the OS
open a command prompt from your adb/fastboot folder and type:
Code:
adb shell
su
You'll probably be prompted to allow/deny superuser access on your phone, if so, make sure to allow superuser access.
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bakup.img
be careful with above command, if you make a mistake, this could harm your phone, you may want to copy/paste the command instead of typing it.
then browse your phone storage (/sdcard) and PM me the file just created (mmcblk0p6_backup.img), do not post it in your thread, because like I said, this file contain your IMEI number.
---------- Post added at 02:35 PM ---------- Previous post was at 01:57 PM ----------
@jtlefebvre
from the information stored in your mmcblk0p6 partition, your original phone info are:
CID: BS_US001
MID: PN0712000
P/N: 99HT223-00
S/N: FA34TW9*****
IMEI: 354439*********
Production date: 2013/04/03
So change back your cid to BS_US001 and follow nkk71's guide linked in my signature using the 1.29.1540.16 ruu.zip
Click to expand...
Click to collapse
Holy crap.
Thanks for the help bro. I'll definitely get into that today. I really appreciate you looking into this for me.
But one question.. Isn't there a way to change the MID and CID to match the T-mobile RUU so that I can just use the stock T-Mobile ROM and get OTA that way? Because if I send this in for the warranty, they're going to expect the T-Mobile setup. I don't kn ow wtf the T-mobile dealer was doing when selling me the phone... maybe they had Brightstar phones that needed to be used.

jtlefebvre said:
Holy crap.
Thanks for the help bro. I'll definitely get into that today. I really appreciate you looking into this for me.
But one question.. Isn't there a way to change the MID and CID to match the T-mobile RUU so that I can just use the stock T-Mobile ROM and get OTA that way? Because if I send this in for the warranty, they're going to expect the T-Mobile setup. I don't kn ow wtf the T-mobile dealer was doing when selling me the phone... maybe they had Brightstar phones that needed to be used.
Click to expand...
Click to collapse
you said you have bought the phone from a guy on craigslist, I doubt t-mobile will accept to repair/replace your phone under warranty. Probably have to send your phone directly to HTC with everything stock (PN0712000, BS_US001, LOCKED bootloader, S-ON, no tampered flag and a X.XX.1540.X OS version).
Yes this is possible to change the MID to match T-MOB010 and use the t-mobile ruu. This all depends what you are planning to do with the phone (sending it back to HTC or sending it to T-mobile). If you send it to HTC and the phone doesnt match the info in the p6 partition, they will maybe notice it and charge your for the repair.

alray said:
you said you have bought the phone from a guy on craigslist, I doubt t-mobile will accept to repair/replace your phone under warranty. Probably have to send your phone directly to HTC with everything stock (PN0712000, BS_US001, LOCKED bootloader, S-ON, no tampered flag and a X.XX.1540.X OS version).
Yes this is possible to change the MID to match T-MOB010 and use the t-mobile ruu. This all depends what you are planning to do with the phone (sending it back to HTC or sending it to T-mobile). If you send it to HTC and the phone doesnt match the info in the p6 partition, they will maybe notice it and charge your for the repair.
Click to expand...
Click to collapse
Yeah the guy posted the phone for sale on craigslist but he had a little wireless shop a couple of towns over and he's an authorized T-mobile dealer. I got a good deal for it at $200 but I thought it was actually a T-mobile phone. I'm actually sending the phone directly over to HTC to fix the problem with my camera since it has pink fuzz all over my images. I had sent them the receipt for my purchase and they authorized my RMA. They're now just waiting for me to send them the phone. If they charge me to repair the phone, I'll have to deny it. But to prevent it all, I just want to give them a T-Mobile phone. Thus, here I am wondering, "why am I getting this message after returning the phone to stock". But if I can change the partition information to match T-Mobile's I will. I'm fairly tech savvy.

jtlefebvre said:
Yeah the guy posted the phone for sale on craigslist but he had a little wireless shop a couple of towns over and he's an authorized T-mobile dealer. I got a good deal for it at $200 but I thought it was actually a T-mobile phone. I'm actually sending the phone directly over to HTC to fix the problem with my camera since it has pink fuzz all over my images. I had sent them the receipt for my purchase and they authorized my RMA. They're now just waiting for me to send them the phone. If they charge me to repair the phone, I'll have to deny it. But to prevent it all, I just want to give them a T-Mobile phone. Thus, here I am wondering, "why am I getting this message after returning the phone to stock". But if I can change the partition information to match T-Mobile's I will. I'm fairly tech savvy.
Click to expand...
Click to collapse
no, you wont be able to change data in mmcblk0p6.
You are getting this error message because the OS doesnt match the MID. So go ahead and return your phone back to 100% stock before sending it to HTC (BS_US001, PN0712000, LOCKED (not relocked), S-ON and software x.xx.1540.x)

alray said:
no, you wont be able to change data in mmcblk0p6.
You are getting this error message because the OS doesnt match the MID. So go ahead and return your phone back to 100% stock before sending it to HTC (BS_US001, PN0712000, LOCKED (not relocked), S-ON and software x.xx.1540.x)
Click to expand...
Click to collapse
Thanks again for the help Alray. Very informative.