[Solved] Back to stock - One (M7) Q&A, Help & Troubleshooting

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

Related

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

[Q] New HTC One - S-OFF!!

Hi,
My friend purchased a new HTC One and it gave the following information on bootloader. I was surprised to see its S-OFF by default.
M7_UL PVT ship S-Off RH
CID - 111111111
HBOOT-1.54.0000
radio-4a.18.3250.15
open dsp - v31.120.274.0617
os-2.24.708.4
eMMC-boot 2048MB
and Build No is : 2.24.708.4 cl2111355 htc build
Can anyone please tell me if this is a debranded phone or anything.
If this is kept, would there be any issues for flashing custom ROMs? Like after S-off and Unlocked Bootloader. Would it still restrict that I would be able to flash only certain ROMs on it..
Please tell asap
Rah0ol said:
Hi,
My friend purchased a new HTC One and it gave the following information on bootloader. I was surprised to see its S-OFF by default.
M7_UL PVT ship S-Off RH
CID - 111111111
HBOOT-1.54.0000
radio-4a.18.3250.15
open dsp - v31.120.274.0617
os-2.24.708.4
eMMC-boot 2048MB
and Build No is : 2.24.708.4 cl2111355 htc build
Can anyone please tell me if this is a debranded phone or anything.
If this is kept, would there be any issues for flashing custom ROMs? Like after S-off and Unlocked Bootloader. Would it still restrict that I would be able to flash only certain ROMs on it..
Please tell asap
Click to expand...
Click to collapse
i think that this phone is regenerated or phone test! You do not have any problem to flash rom! the s-off is the best thing for our phones! where did you buy it?
mago988 said:
i think that this phone is regenerated or phone test! You do not have any problem to flash rom! the s-off is the best thing for our phones! where did you buy it?
Click to expand...
Click to collapse
He he .. Its from eBay from a known seller The Mobile is S-off and SID is 111111 .. That means I can flash any RUU Right? or Unlock bootloader is mandetory?
Yes
Sent from my HTC One using xda premium
Rah0ol said:
He he .. Its from eBay from a known seller The Mobile is S-off and SID is 111111 .. That means I can flash any RUU Right? or Unlock bootloader is mandetory?
Click to expand...
Click to collapse
If your phone is S-OFF you can flash a ruu with a locked/unlocked/relocked bootloader, with s-on you need a LOCKED bootloader to flash a ruu.
You can flash any ruu that match you CID (not a problem with supercid) and MID (MID can be changed easily with s-off).
Don't forget you will not receive ota updates with super cid.
alray said:
If your phone is S-OFF you can flash a ruu with a locked/unlocked/relocked bootloader, with s-on you need a LOCKED bootloader to flash a ruu.
You can flash any ruu that match you CID (not a problem with supercid) and MID (MID can be changed easily with s-off).
Don't forget you will not receive ota updates with super cid.
Click to expand...
Click to collapse
So as u said, I have a SuperCID and a locked bootloader and S-OFF, I can flash any RUU (international, anything coz I wanna flash Indian RUU or atleast International) so will it work fine without bootloop etc?? ??
Rah0ol said:
So as u said, I have a SuperCID and a locked bootloader and S-OFF, I can flash any RUU (international, anything coz I wanna flash Indian RUU or atleast International) so will it work fine without bootloop etc?? ??
Click to expand...
Click to collapse
MID must match too
better to post a ''fastboot getvar all'' except imei/sn so we can tell if you can flash that ruu
also post a link to the ruu you want to flash.
and you can always pull mmcblk0p6 to find the true origins of your phone
nkk71 said:
and you can always pull mmcblk0p6 to find the true origins of your phone
Click to expand...
Click to collapse
How to do that? I dont know about that
Rah0ol said:
How to do that? I dont know about that
Click to expand...
Click to collapse
you need a custom recovery, or a rooted ROM, do you have that?
then you open a shell and dd it out, for example:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6_bak.img
exit
exit
adb pull /sdcard/mmcblk0p6_bak.img
^^ careful with "dd" commands, you don't want to write something to one of your partitions (with S-Off you can brick easily using this command)
in particular the "of=" (output file)... do not want to write something to one of your partitions!! (by mistake)
reading (and saving to /sdard) is perfectly safe, just not writing
this is what a p6 looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the MID the system reads is at offset 0x4000, the others remain unchanged, and CID the system reads is in a completely different partition(s).... so from here you can pretty much get the all the info what your phone originally was.
<typed this by Mistake>
alray said:
MID must match too
better to post a ''fastboot getvar all'' except imei/sn so we can tell if you can flash that ruu
also post a link to the ruu you want to flash.
Click to expand...
Click to collapse
Here is the info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.708.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3888mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0\
Not sure of flashing any RUU right now.. as I will nt be doing it now.. But would like to know if I can flash any RUU I want...
Rah0ol said:
Here is the info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.20.708.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
Not sure of flashing any RUU right now.. as I will nt be doing it now.. But would like to know if I can flash any RUU I want...
Click to expand...
Click to collapse
I highly recommend you either change your MID and/or pull that partition i was talking about earlier... obviously the previous owner thought that there is something called SuperMID, which (in my very humble opinion) doesn't exist
SuperCID (CID = Carrier ID)... fine, you're just changing carrier ID
MID = model ID = hardware... not fine, thinking you can change it that easily and "get away with it", you cannot change the phone hardware simply by changing MID.
nkk71 said:
I highly recommend you either change your MID and/or pull that partition i was talking about earlier... obviously the previous owner thought that there is something called SuperMID, which (in my very humble opinion) doesn't exist
SuperCID (CID = Carrier ID)... fine, you're just changing carrier ID
MID = model ID = hardware... not fine, thinking you can change it that easily and "get away with it", you cannot change the phone hardware simply by changing MID.
Click to expand...
Click to collapse
'
Thanks a lot for that information. My question was, Secondly, I need to know if this phone can be used for development purposes? Like.. In future if I unlock the bootloader by HTC Dev method, and as its S-OFF and SuperCID already present, will I be able to flash recovery and flash any Firmware present here in dev section? Or I need to correct the MID else it wouldnt allow flashing?
Rah0ol said:
'
Thanks a lot for that information. My question was, Secondly, I need to know if this phone can be used for development purposes? Like.. In future if I unlock the bootloader by HTC Dev method, and as its S-OFF and SuperCID already present, will I be able to flash recovery and flash any Firmware present here in dev section? Or I need to correct the MID else it wouldnt allow flashing?
Click to expand...
Click to collapse
As long as you're S-Off you can unlock even without HTCdev.
and yes, you can flash pretty much anything for the m7_u or ul models (m7_u and ul software/firmware works for both models), the exceptions are CDMA phones (such as Sprint and Verizon), and Dual-SIM stuff.
As for the MID, (for firmware flashing) you may get MID mismatch if the android-info.txt doesn't contain "PN071****"
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
And the most important part: do not go S-On!!!!!
.
nkk71 said:
As long as you're S-Off you can unlock even without HTCdev.
and yes, you can flash pretty much anything for the m7_u or ul models (m7_u and ul software/firmware works for both models), the exceptions are CDMA phones (such as Sprint and Verizon), and Dual-SIM stuff.
As for the MID, (for firmware flashing) you may get MID mismatch if the android-info.txt doesn't contain "PN071****"
MIDs should be (as far as I'm aware):
PN0710000 -> international M7_UL
PN0711000 -> international M7_U
PN0712000 -> US/Canada M7_UL
PN0713000 -> US T-Mobile M7_UL
PN0714000 -> Asia M7_UL
To change your MID to one of the above (PN0710000 for example), you can use this tool: [TOOL] MID change without ENG HBOOT | Aroma GUI
which you use in a custom recovery.
And the most important part: do not go S-On!!!!!
.
Click to expand...
Click to collapse
Awesome! Thanks for the info.. One more small thing.. In the HTC help and error reporting, it said that this is a test device... Will that restrict flashing new FW and all?? Also will that error message disappear if I flash a different FW or RUU? I think it shud be because of OS, but I wanna know..
Rah0ol said:
Awesome! Thanks for the info.. One more small thing.. In the HTC help and error reporting, it said that this is a test device... Will that restrict flashing new FW and all?? Also will that error message disappear if I flash a different FW or RUU? I think it shud be because of OS, but I wanna know..
Click to expand...
Click to collapse
That message (test device and error reporting is always on) is due to the device being S-Off (on a stock ROM)... but who cares?
--1) Do you think HTC collects more information than google, your provider, etc
--2) how often does your phone crash? cause that's when it's supposed to send the information
--->> if you are the paranoid type, and think you need to go S-On (because it won't "allow" them to collect information), you're going to get into a lot of trouble if you don't know when and how to do it (which firmware, which ROM, which CID, which MID), and you'll be seriously stuck!!
And that message won't affect your ability to flash anything.
nkk71 said:
That message (test device and error reporting is always on) is due to the device being S-Off (on a stock ROM)... but who cares?
--1) Do you think HTC collects more information than google, your provider, etc
--2) how often does your phone crash? cause that's when it's supposed to send the information
--->> if you are the paranoid type, and think you need to go S-On (because it won't "allow" them to collect information), you're going to get into a lot of trouble if you don't know when and how to do it (which firmware, which ROM, which CID, which MID), and you'll be seriously stuck!!
And that message won't affect your ability to flash anything.
Click to expand...
Click to collapse
Nah, I am not that paranoid type and not concerned about HTC Collecting informartion.. Just wanted to know about the ability to flash The information you gave is perfect and what I wanted to read. Thanks a lot nkk71 ..
Rah0ol said:
Nah, I am not that paranoid type and not concerned about HTC Collecting informartion.. Just wanted to know about the ability to flash The information you gave is perfect and what I wanted to read. Thanks a lot nkk71 ..
Click to expand...
Click to collapse
no problem, remember to:
1- stay s-off
2- flash things only for m7_u/ul models... if you are unsure, then better ask first!!
for example this: http://forum.xda-developers.com/showthread.php?t=2626050 almost looks like for the HTC One, but it does say:
* Target device: HTC Droid DNA (PL8320000)
and it's in the:
forum!!!
you flash that, and you have yourself a serious problem!!
So stick to the correct forum, and make sure what you flash is m7_u/ul
Happy flashing
nkk71 said:
no problem, remember to:
1- stay s-off
2- flash things only for m7_u/ul models... if you are unsure, then better ask first!!
for example this: http://forum.xda-developers.com/showthread.php?t=2626050 almost looks like for the HTC One, but it does say:
* Target device: HTC Droid DNA (PL8320000)
and it's in the:
forum!!!
you flash that, and you have yourself a serious problem!!
So stick to the correct forum, and make sure what you flash is m7_u/ul
Happy flashing
Click to expand...
Click to collapse
Oh that much I am used to.. I was in Incredible S Dev forum earlier and have efficiently used all ROMs starting from GB to KK.. Just that I didnt understand the concept of CID which was not there(or I didnt have to take a look at) but after the information got from you, I think I am sufficient info to start D
I am not a Noob at flashing and Rooting but some concepts change in a higher end phones and its always better to know stuffs indepth before trying it

[Q] Flashed Wrong RUU Trying to go back to Stock, Booloop and Recovery Won't Work

Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
bradreputation said:
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
Click to expand...
Click to collapse
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
nkk71 said:
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
Click to expand...
Click to collapse
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
bradreputation said:
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
Click to expand...
Click to collapse
Technically, you can, but shouldn't reboot the OS because of the OTA notification, which may make it tempting to take, but I'll try and rephrase the guide.
bradreputation said:
version-bootloader: 1.54.0000
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0712000
cidnum: CWS__001
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
Click to expand...
Click to collapse
bootloader is unlocked, good... do NOT try and lock it!!
reflash TWRP and a custom ROM (you can try ARHD 31.6 or similar), and get S-OFF using rumrunner and/or firewater
i'm off for tonight, sorry about the mess
The stock att RUU's would almost certainly have the stock CWS_001 Cid. You just need one that is the same or postdated to your current hboot version since you are s-on now. Unfortunately, now that you are s-on, you will also need to relock the bootloader to flash an RUU. I would do that and then use firewater/rumrunner/latest s-off method to get s-off and unlock boot loader. Then you want to fix the "relocked" flag to "locked", and s-on again, and get it repaired.
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
AFH Mirror: http://www.androidfilehost.com/?fid=23501681358544977
nkk71 said:
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE:
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
]
Click to expand...
Click to collapse
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
bradreputation said:
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
Click to expand...
Click to collapse
It's really very country/carrier/people specific, in theory, S-Off shouldn't matter as some phones accidentally ship S-Off (ok, it's very very very rare), but S-Off shouldn't void warranty https://twitter.com/htc/status/377422743626842112
Then again, in practice some carriers/technicians may try to use any excuse to refuse warranty.

HTC One M7 RUU Europe Search

Hi,
I recently managed to fix my HTC One from a boot loop and accidentally put on an Asia HTC One RUU even though it said it was for Europe. Since then, I've been trying to look for a Europe based one, more specifically the UK and I've had no luck. Could anyone point me in the right direction or provide a fully stock 4.4.3 Rom with sense 6 and full OTA update capability?
Would really appreciate it.
Thanks.
~ 5H1R42 ~
5H1R42 said:
Hi,
I recently managed to fix my HTC One from a boot loop and accidentally put on an Asia HTC One RUU even though it said it was for Europe. Since then, I've been trying to look for a Europe based one, more specifically the UK and I've had no luck. Could anyone point me in the right direction or provide a fully stock 4.4.3 Rom with sense 6 and full OTA update capability?
Would really appreciate it.
Thanks.
~ 5H1R42 ~
Click to expand...
Click to collapse
there is no 4.4.3 ruu, only older versions and will require s-off to be used.
what is your "fastboot getvar all" ?
alray said:
there is no 4.4.3 ruu, only older versions and will require s-off to be used.
What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
mid: Pn0710000
cid: Vodap001
5H1R42 said:
mid: Pn0710000
cid: Vodap001
Click to expand...
Click to collapse
what is your "fastboot getvar all" ?
alray said:
there is no 4.4.3 ruu, only older versions and will require s-off to be used.
what is your "fastboot getvar all" ?
Click to expand...
Click to collapse
alray said:
what is your "fastboot getvar all" ?
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.161.8
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4091mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
5H1R42 said:
I recently managed to fix my HTC One from a boot loop and accidentally put on an Asia HTC One RUU even though it said it was for Europe.
Click to expand...
Click to collapse
5H1R42 said:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.161.8
INFOversion-misc: PVT SHIP S-ON
remove
remove
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4091mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
I don't understand, you said that you have flashed an Asian RUU but according to your getvar, everything is 100% stock Vodaphone version. Your phone is s-on which prevent to flash the wrong RUU and there is no RUU for that version which make me beleive what you said at post #1 is incorrect.
However if you want to convert it to an european version like the x.xx.401.x version and receive ota updates, you'll need s-off
or you can use custom roms.
btw edit your above post and remove your imei and serialno
O no, I reverted to a custom Rom because the Asian one wouldn't accept ota updates
alray said:
I don't understand, you said that you have flashed an Asian RUU but according to your getvar, everything is 100% stock Vodaphone version. Your phone is s-on which prevent to flash the wrong RUU and there is no RUU for that version which make me beleive what you said at post #1 is incorrect.
However if you want to convert it to an european version like the x.xx.401.x version and receive ota updates, you'll need s-off
or you can use custom roms.
btw edit your above post and remove your imei and serialno
Click to expand...
Click to collapse
I reverted back to a rooted stock rom but i don't really like it. Ive checked the rom that you've linked in your signature and was wondering if that would work on my device in order to restore OTA updates however, I can't get S-OFF due to a certain firmware update
5H1R42 said:
O no, I reverted to a custom Rom because the Asian one wouldn't accept ota updates
Click to expand...
Click to collapse
if you want ota updates you must use the 6.12.161.8 version like in your getvar, otherwise you'll need s-off to convert to another version or keep using custom roms.
Btw 6.12.161.8 is the latest vodaphone version
---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------
5H1R42 said:
I can't get S-OFF due to a certain firmware update
Click to expand...
Click to collapse
Tried sunshine?
alray said:
if you want ota updates you must use the 6.12.161.8 version like in your getvar, otherwise you'll need s-off to convert to another version or keep using custom roms.
Btw 6.12.161.8 is the latest vodaphone version
---------- Post added at 06:34 PM ---------- Previous post was at 06:32 PM ----------
Tried sunshine?
Click to expand...
Click to collapse
So if i flash a vodafone version back on to my phone, i should have OTA updates back? The thing is, i don't want the vodafone bloatware so i'm looking for a stock version with no bloatware so, if I flashed a vodafone RUU and then flahsed your version, would I be ok and have what I want?
5H1R42 said:
So if i flash a vodafone version back on to my phone, i should have OTA updates back? The thing is, i don't want the vodafone bloatware so i'm looking for a stock version with no bloatware so, if I flashed a vodafone RUU and then flahsed your version, would I be ok and have what I want?
Click to expand...
Click to collapse
Your phone CID and MID is vodafone so you can only receive ota updates for vodafone plus your rom must be on the same version as listed on your fastboot getvar all, otherwise you will not be able to install ota updates (firmware and software mismatch).
If you want to debloat your rom by installing another version (like the dev edition or the european version) and receive ota updates, you will need s-off to do a full conversion which include to change your CID, MID and flashing a RUU.
Or you can use latest custom rom versions.
alray said:
I don't understand, you said that you have flashed an Asian RUU but according to your getvar, everything is 100% stock Vodaphone version. Your phone is s-on which prevent to flash the wrong RUU and there is no RUU for that version which make me beleive what you said at post #1 is incorrect.
However if you want to convert it to an european version like the x.xx.401.x version and receive ota updates, you'll need s-off
or you can use custom roms.
btw edit your above post and remove your imei and serialno
Click to expand...
Click to collapse
alray said:
Your phone CID and MID is vodafone so you can only receive ota updates for vodafone plus your rom must be on the same version as listed on your fastboot getvar all, otherwise you will not be able to install ota updates (firmware and software mismatch).
If you want to debloat your rom by installing another version (like the dev edition or the european version) and receive ota updates, you will need s-off to do a full conversion which include to change your CID, MID and flashing a RUU.
Or you can use latest custom rom versions.
Click to expand...
Click to collapse
Ok. So how would I force s-off then? If I can get the done, I'll install the dev edition one you've got linked in your signature and I'm good to go.
5H1R42 said:
Ok. So how would I force s-off then? If I can get the done, I'll install the dev edition one you've got linked in your signature and I'm good to go.
Click to expand...
Click to collapse
You can achieve s-off using sunshine. The rom linked in my signature is not a RUU and you will not receive ota update because your firmware will not match the software version. Use a RUU and change your cid and mid so they match the RUU version
alray said:
You can achieve s-off using sunshine. The rom linked in my signature is not a RUU and you will not receive ota update because your firmware will not match the software version. Use a RUU and change your cid and mid so they match the RUU version
Click to expand...
Click to collapse
In that case, I may well install the Vodafone ruu and be back at square one. I'll just have to disable all the Vodafone bloatware through the app manager.
alray said:
You can achieve s-off using sunshine. The rom linked in my signature is not a RUU and you will not receive ota update because your firmware will not match the software version. Use a RUU and change your cid and mid so they match the RUU version
Click to expand...
Click to collapse
Sorry to be a pain but I've got a 6.12.161.8 firmware zip file from the HTC dev site. If I was to install this on to my HTC one, would I be able to go back to stock android?

[Q] Htc M7 Soft Bricked Need Advice

Hi guys,
I have gone through the the forum and have read up on the issure, I have made some progress, I need some expert advice on the last few stages.
The Htc one M7 is soft bricked, i have unlocked the bootloder via the htc site, i know how to use ADB and fastboot command line. I have installed TWRP on the phone, now i can see my phone as a drive on my computer. the phone is still S-ON
What i want to achieve:
Put a stock firmware on the phone and thats that.
Not too keen on putting customs firmwares, if there is a Google Edition firmware, that will be a plus if not then the firmware with sense 5 or 6 etc.
The CID is 332 ( could this be an issue)
I just need the phone to work as normal with stock or google play edition stock.
Do i need to get s-on to S-off? whats the easiest way. what firmware would work for this cid-332, do i need to change my CID to get best firmware, these are the stages i need advice.
Thanks a lot guys.
Phone details below
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.13.599.101
version-misc: PVT SHIP S-ON
serialno: HT386xxxxxxxx
imei: 354xxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
feeldennis said:
Hi guys,
I have gone through the the forum and have read up on the issure, I have made some progress, I need some expert advice on the last few stages.
The Htc one M7 is soft bricked, i have unlocked the bootloder via the htc site, i know how to use ADB and fastboot command line. I have installed TWRP on the phone, now i can see my phone as a drive on my computer. the phone is still S-ON
What i want to achieve:
Put a stock firmware on the phone and thats that.
Not too keen on putting customs firmwares, if there is a Google Edition firmware, that will be a plus if not then the firmware with sense 5 or 6 etc.
The CID is 332 ( could this be an issue)
I just need the phone to work as normal with stock or google play edition stock.
Do i need to get s-on to S-off? whats the easiest way. what firmware would work for this cid-332, do i need to change my CID to get best firmware, these are the stages i need advice.
Thanks a lot guys.
Phone details below
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.13.599.101
version-misc: PVT SHIP S-ON
serialno: HT386xxxxxxxx
imei: 354xxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
Click to expand...
Click to collapse
you seem to have a carrier that has never released a RUU or any useful files really. Did you make a Nandroid backup of you stock software ?
If you have no backup the best you can do is just flash an international Rom that matches you firmware version like this one
https://www.androidfilehost.com/?fid=23501681358543706
During install choose No to stock recovery and No to installing the Radio
clsA said:
you seem to have a carrier that has never released a RUU or any useful files really. Did you make a Nandroid backup of you stock software ?
If you have no backup the best you can do is just flash an international Rom that matches you firmware version like this one
https://www.androidfilehost.com/?fid=23501681358543706
During install choose No to stock recovery and No to installing the Radio
Click to expand...
Click to collapse
Hi there,
I had no back up. So it is like bad luck with this cid 332.
Will this rom "Guru_Reset_M7_5.11.401.10-TeHashX.zip" work?
Thanks for reply.
thanks
feeldennis said:
Hi there,
I had no back up. So it is like bad luck with this cid 332.
Will this rom "Guru_Reset_M7_5.11.401.10-TeHashX.zip" work?
Thanks for reply.
thanks
Click to expand...
Click to collapse
you'll be able to flash it but you will never get ota uptades using this version because of your cid and mismatch between software version and firmware version.
Its not possible to return it to stock .599 so you should either s-off it and do a conversion to another version or use custom roms.
alray said:
you'll be able to flash it but you will never get ota uptades using this version because of your cid and mismatch between software version and firmware version.
Its not possible to return it to stock .599 so you should either s-off it and do a conversion to another version or use custom roms.
Click to expand...
Click to collapse
Cool, best way to S-off?
please advice or put a link, keep in mind it is soft bricked, i can get into the bootmenu and TWRP MENU.
THANKS
feeldennis said:
Cool, best way to S-off?
please advice or put a link, keep in mind it is soft bricked, i can get into the bootmenu and TWRP MENU.
THANKS
Click to expand...
Click to collapse
SunShine S-Off
http://theroot.ninja/
but you still have to flash the rom i listed first and get ROOT
feeldennis said:
Cool, best way to S-off?
please advice or put a link, keep in mind it is soft bricked, i can get into the bootmenu and TWRP MENU.
THANKS
Click to expand...
Click to collapse
flash a close to stock rom and s-off using sunshine
once s-off, change you cid
Code:
fastboot oem writecid HTC__001
then change your MID to PN0710000 using this tool
and finally, flash a x.xx.401.x RUU.
or if you prefer the dev edition version:
change cid to BS_US001
MID to PN0712000
and use the latest ruu 6.07.1540.2
alray said:
flash a close to stock rom and s-off using sunshine
once s-off, change you cid
Code:
fastboot oem writecid HTC__001
then change your MID to PN0710000 using this tool
and finally, flash a x.xx.401.x RUU.
or if you prefer the dev edition version:
change cid to BS_US001
MID to PN0712000
and use a the latest ruu 6.07.1540.2
Click to expand...
Click to collapse
Let me get this clear,
1st i need to flash the above firmware,
2nd S-off with sunshine, is sunshine free?
3rd chand cid and Mid.
then i can use latest RUU.
Can i s-off with out installing any rom first?
Thanks
feeldennis said:
Let me get this clear,
1st i need to flash the above firmware,
2nd S-off with sunshine, is sunshine free?
3rd chand cid and Mid.
then i can use latest RUU.
Can i s-off with out installing any rom first?
Thanks
Click to expand...
Click to collapse
SunShine = $25
Getting s-off and converting to Developers Edition Worth = $1,000,000
Update, functioning M7
clsA said:
SunShine = $25
Getting s-off and converting to Developers Edition Worth = $1,000,000
Click to expand...
Click to collapse
Hi guys, thanks so much for your help and advice,
I decided to go the easy route, and just droped in the cyanogen mod rom and flashed.
Maybe i will do the S-off at a later date.
The phone works super.
Thanks guys.
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0

Categories

Resources