[Q] HTC One M7 RUU IMG Error - One (M7) Q&A, Help & Troubleshooting

Hey guys,
I recently got S-Off on my device and downgraded my HBoot to 1.44 and changed to SuperCID 11111111
The RUU i downloaded is " Sprint_HTC_One_m7wls_4.06.651.4_RUU"
The reason i need to go back to stock to see if i can get my Wifi and Bluetooth to start working again since it's stuck in "turning on mode" I have tried flashing new roms, radios, kernals, factory reset etc. No idea why Wifi and Bluetooth stopped working i just woke up one morning and it wouldn't turn on.
For some reason when flashing this RUUi keep on getting 158 IMG error? I have tried running as admin, and making sure phone is in Fastboot USB but still wont work.
Which RUU should i try, any help would be awesome as i would love to get my Wifi and Bluetooth working again, here are my phones details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4079mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks guys.

iAMuSIK said:
Hey guys,
I recently got S-Off on my device and downgraded my HBoot to 1.44 and changed to SuperCID 11111111
The RUU i downloaded is " Sprint_HTC_One_m7wls_4.06.651.4_RUU"
The reason i need to go back to stock to see if i can get my Wifi and Bluetooth to start working again since it's stuck in "turning on mode" I have tried flashing new roms, radios, kernals, factory reset etc. No idea why Wifi and Bluetooth stopped working i just woke up one morning and it wouldn't turn on.
For some reason when flashing this RUUi keep on getting 158 IMG error? I have tried running as admin, and making sure phone is in Fastboot USB but still wont work.
Which RUU should i try, any help would be awesome as i would love to get my Wifi and Bluetooth working again, here are my phones details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4079mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Thanks guys.
Click to expand...
Click to collapse
Sprint_HTC_One_m7wls_4.06.651.4_RUU
Click to expand...
Click to collapse
this ruu isn't for your phone at all !
You have a M7_UL (GSM) not a M7WLS (sprint CDMA) !!
What was your original CID?
Your main-ver is .401 so you probably need a .401 ruu

alray said:
this ruu isn't for your phone at all !
You have a M7_UL (GSM) not a M7WLS (sprint CDMA) !!
What was your original CID?
Your main-ver is .401 so you probably need a .401 ruu
Click to expand...
Click to collapse
Its a good thing that RUU check for MID/CID... or I can't imagine posts from the amount of mis-match flashing.. :cyclops:

@iAMuSIK
From this thread:
You:
My HTC is a M7 on Optus Australia network.
Click to expand...
Click to collapse
so your cid was probably OPTUS001 and you need a .980 version
LS.xD:
Seems as there is no matching RUU
Click to expand...
Click to collapse
You:
So there is no Ruu for my phones carrier which does suck.
Click to expand...
Click to collapse
So why did you attempted to flash an incompatible RUU even if you already know there is none compatible for your phone?

I was
I was under the impression that if i was S-OFF and had SuperCID that i could run any RUU.
I know there is no RUU for my device hence why i wanted to get S-OFF and SuperCID so i could try another RUU, so this is not possible?
I have the nandroid backup for my device but when i flashed it Wifi and Bluetooth would still not work. Looks like i might have to send it into the shop for repairs.

iAMuSIK said:
I was under the impression that if i was S-OFF and had SuperCID that i could run any RUU.
Click to expand...
Click to collapse
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
Click to expand...
Click to collapse
I thought i did read everything, which obviously i missed a few parts. Since the nandroid backup didn't work ill take defeat and accept my Wifi and Bluetooth is possibly a hardware issue. Can't send phone in for warrenty since its "Rooted" so hopefully i can find a good repair center around my part of town.

iAMuSIK said:
I thought i did read everything, which obviously i missed a few parts. Since the nandroid backup didn't work ill take defeat and accept my Wifi and Bluetooth is possibly a hardware issue. Can't send phone in for warrenty since its "Rooted" so hopefully i can find a good repair center around my part of town.
Click to expand...
Click to collapse
try what I said above (post edited)

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.
Click to expand...
Click to collapse
Just saw your added info, thanks a lot mate. Will give his a try today and report back if it works, fingers crossed!

iAMuSIK said:
Can't send phone in for warrenty since its "Rooted".
Click to expand...
Click to collapse
you can go back to stock with your nanadroid backup using this guide: http://forum.xda-developers.com/showthread.php?t=2541082 en send your phone for warranty repair

alray said:
Not ANY ruu! Only RUU for M7_UL models. CID and MID must match the ruu (can be easily changed to match RUU with s-off)
M7WLS is a different phone and flashing things for the WLS variant on your UL variant WILL brick your phone.
BTW Never flash things to your phone ''under the impression'' it is ok, read carefully and ask questions
---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------
@iAMuSIK
now you could try the 1.28.401.7 ruu
Be sure the MD5 value match the downloaded RUU: 2fd46305b6080830e2ca27a080999b93
fastboot oem writecid HTC__001
change MID to PN0710000 using this tool
then run the ruu
Never s-on
and stay bootloader unlocked for now
if your issue persist, your phone is hardware damaged and you will need to send it back for repair.
Click to expand...
Click to collapse
Just in the middle of doing this process now and im getting a error when trying to write CID.
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot oem writecid H
TC_001
...
(bootloader) fail: [writecid] Invalid cid
OKAY [ 0.013s]
finished. total time: 0.014s
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
EDIT: 2 underscores and not 1 lol.

So
@alray
So finally got the RUU but still not Wifi and Bluetooth working. Hardware issue it is. Thanks a lot for the help in getting this to work bud

Related

[SOLVED] RUU related problem and query [SOLVED]

Code:
(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.707.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4085mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.079s
Hi i want to run a proper RUU on my phone
So can someone point me to correct guide on how to run the same?
I am bit confused.....do we need to be s-off to run the ruu or vice versa?
abhisheak.bansal said:
Code:
(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.707.17
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4085mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.079s
Hi i want to run a proper RUU on my phone
So can someone point me to correct guide on how to run the same?
I am bit confused.....do we need to be s-off to run the ruu or vice versa?
Click to expand...
Click to collapse
Firstly yes you need to be s-off to run RUU
secondly you seem to have indian cid and accordingly there is only one rom - 3.63.707.4( stock) available.
Go to www.htc1guru.com you will find that.
Bro i much appreciate a detailed guide on how to do the same?
and also running a ruu will update my hboot to 1.55?
abhisheak.bansal said:
Bro i much appreciate a detailed guide on how to do the same?
and also running a ruu will update my hboot to 1.55?
Click to expand...
Click to collapse
Do you want to go back on stock??
here it is http://www.htc1guru.com/downloads/stock-rom-downloads/
No, my data partition is messed up, so one of the recognized developer has told me to flash a full ruu.
But my head is bit messed up
cant figure out a full proper way of flashing a ruu and not losing my hboot 1.44
abhisheak.bansal said:
No, my data partition is messed up, so one of the recognized developer has told me to flash a full ruu.
But my head is bit messed up
cant figure out a full proper way of flashing a ruu and not losing my hboot 1.44
Click to expand...
Click to collapse
why don't you want your hboot to be updated?
AFAIK 1.55 didnt had a proper s-off
abhisheak.bansal said:
AFAIK 1.55 didnt had a proper s-off
Click to expand...
Click to collapse
yes there is s-off for 1.55. and btw your are already s-off...
abhisheak.bansal said:
Code:
(bootloader) version-misc: PVT SHIP [B][COLOR="Red"]S-OFF[/COLOR][/B]
(bootloader) security: [COLOR="red"][B]off[/B][/COLOR]
Click to expand...
Click to collapse
abhisheak.bansal said:
AFAIK 1.55 didnt had a proper s-off
Click to expand...
Click to collapse
It is impossible to find an Indian RUU so try flashing the stock rom from here http://www.htc1guru.com/downloads/stock-rom-downloads/
and flashing a ruu will not change s-off back to s-on even if it will update hboot to latest version.... just saying
so go ahead and flash the ruu @khandelwalsiddharth linked you, and please don't forget to thanks him for the files he found for you
---------- Post added at 02:26 PM ---------- Previous post was at 02:20 PM ----------
khandelwalsiddharth said:
It is impossible to find an Indian RUU so try flashing the stock rom from here http://www.htc1guru.com/downloads/stock-rom-downloads/
Click to expand...
Click to collapse
What about this ruu? http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
its not ''indian'' but it should flash fine on his device... or maybe he should use the guru reset you linked....
@abhisheak.bansal After installing the stock rom do make a nanroid backup of it. :good:
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
alray said:
and flashing a ruu will not change s-off back to s-on even if it will update hboot to latest version.... just saying
so go ahead and flash the ruu @khandelwalsiddharth linked you, and please don't forget to thanks him for the files he found for you
---------- Post added at 02:26 PM ---------- Previous post was at 02:20 PM ----------
What about this ruu? http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
Click to expand...
Click to collapse
Yup this should work.
Guys to flash a ruu do CIDNUM and region code (707) always match the ruu
or can we flash a different region ruu?
which android version is it? 3.63.707.4
1.2gb dowloading on 1mbps Connection (PITA)
abhisheak.bansal said:
Guys to flash a ruu do CIDNUM and region code (707) always match the ruu
or can we flash a different region ruu?
which android version is it? 3.63.707.4
1.2gb dowloading on 1mbps (PITA)
Click to expand...
Click to collapse
look when you are s-off u can flash any ruu. But you need to change the cid and mid from the android-info.txt if it doesnt match.
khandelwalsiddharth said:
@abhisheak.bansal After installing the stock rom do make a nanroid backup of it. :good:
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
Yup this should work.
Click to expand...
Click to collapse
alray said:
and flashing a ruu will not change s-off back to s-on even if it will update hboot to latest version.... just saying
so go ahead and flash the ruu @khandelwalsiddharth linked you, and please don't forget to thanks him for the files he found for you
---------- Post added at 02:26 PM ---------- Previous post was at 02:20 PM ----------
What about this ruu? http://www.htc1guru.com/dld/ruu-zip-m7_u_asia_wwe_custom_guruu_3-63-707-4-zip/
its not ''indian'' but it should flash fine on his device... or maybe he should use the guru reset you linked....
Click to expand...
Click to collapse
what is the difference bettwen the the link to the ruu you qouted and this one http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
abhisheak.bansal said:
what is the difference bettwen the the link to the ruu you qouted and this one http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
Click to expand...
Click to collapse
this is an older (lower version) official ruu (signed). the other one is an unofficial ruu more up to date.
Which on should i use?
Someone has recommended to run a full ruu to correct the /data partition problem
abhisheak.bansal said:
Which on should i use?
Someone has recommended to run a full ruu to correct the /data partition problem
Click to expand...
Click to collapse
imo you should use the latest ruu version even if its not an ''official'' one
the ruu will wipe the entire phone including /data partition
alray said:
imo you should use the latest ruu version even if its not an ''official'' one
the ruu will wipe the entire phone including /data partition
Click to expand...
Click to collapse
Ok,then I will download the latest RUU
should i follow this guide to run the latest ruu?
nkk71's SuperGUIDE to returning 100% back to stock
abhisheak.bansal said:
Ok,then I will download the latest RUU
should i follow this guide to run the latest ruu?
nkk71's SuperGUIDE to returning 100% back to stock
Click to expand...
Click to collapse
yes definitively! nkk71's guide is the best imo.
You already have s-off and hboot 1.44 so it should be pretty easy. follow post #1 and #3 of his guide. and please don't go back s-on
alray said:
yes definitively! nkk71's guide is the best imo.
You already have s-off and hboot 1.44 so it should be pretty easy. follow post #1 and #3 of his guide. and please don't go back s-on
Click to expand...
Click to collapse
khandelwalsiddharth said:
look when you are s-off u can flash any ruu. But you need to change the cid and mid from the android-info.txt if it doesnt match.
Click to expand...
Click to collapse
Guys i have flashed the RUU
Now hboot is updated to 1.55
how can i downgrade it to 1.44 ( & is there any real benefit of downgrading the hboot to 1.44?
And once again, thanks a ton guys. :highfive:

[Q] Unable to unlock, flash recovery or s-off or RUU

I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
j.sax.riley said:
I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
Click to expand...
Click to collapse
you probably have to redo the process at http://www.htcdev.com/bootloader/
redo the process and try to unlock your bootloader with the new unlock.bin
just follow the steps
OK.. Explain this. If you converted. You went SOFF. Then how do you end up with LOCKED Bootloader and SJON?
sent from my mobile device
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
http://www.htcdev.com/bootloader/
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Dosent go
Boachti said:
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Click to expand...
Click to collapse
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
j.sax.riley said:
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
Click to expand...
Click to collapse
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread: http://forum.xda-developers.com/showthread.php?t=2547894
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
alray said:
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread:
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
Click to expand...
Click to collapse
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
j.sax.riley said:
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
Click to expand...
Click to collapse
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
alray said:
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
j.sax.riley said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
alray said:
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
Click to expand...
Click to collapse
That sux.
Are you sure there is no other way?
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
i tired temp roots to see if i can s-off in os with firewater but i was unsuccesffully at gaining temp root.
Its funny to me because i swear reading somewhere that "andoid 4.4 is great" dont even have to root because of app ops or something but its obvious now thats a load of b.s and i should have just always run rooted as that has never done me wrong.
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
j.sax.riley said:
That sux.
Are you sure there is no other way?
Click to expand...
Click to collapse
If you can't s-off using rumrunner or firewater then no, idt there is other options.
j.sax.riley said:
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
Click to expand...
Click to collapse
The international version ruu is a .401 base (not .1700) and require to change CID and probably MID. Changing those values require S-OFF!
j.sax.riley said:
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
Click to expand...
Click to collapse
htcdev.com under the ''kernel source code'' section, http://htc1guru.com and http://androidruu.com/?developer=M7
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
This is my output from trying temp root with firewater method.
I am not sure what the issue is that is happening but i assume with the first failure the whole system collapses.
Thank you for the help btw, and i will keep my eyes open for a new ruu.
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
j.sax.riley said:
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
Click to expand...
Click to collapse
must be signed and same or higher version than 3.62.1700.1.
any .1700 version will match your CID and MID (GOOGL01 and PN0712000)
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
I like Htc phones and especially their commitment to bring timely updates.
But.....i do miss being able to use odin and never have to worry if your device gets f-ed up you can always reformat it to stock without trying to get a warranty replacement (which i cant because i'm rocking my google play edition) which is great and totally beats cyanogen mod for stability.
Although....i miss blink feed lol
j.sax.riley said:
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
Click to expand...
Click to collapse
Fomr the output of your fastboot getvar all, you are S-ON not S-OFF so you won't be able to flash a modifed hboot. Btw, if you flash a modified hboot in the future with s-off, you will brick your device if you s-on again (with a modified hboot)
j.sax.riley said:
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
Click to expand...
Click to collapse
Yes, 3.58 is a downgrade of version from what you have currently on your phone. Downgrading require S-OFF

[Q] Return to stock again, Q hboot

Hi,
So returning to stock again and Im planning on doing the following
Install the following zip as per video instructions on website.
Select option to include root
Then install this version of SuperSU >
Follow this guide to set the bootloader to LOCKED
Removed root from within SuperSu settings
Enter the following command via fastboot to go S-ON
./fastboot oem writesecureflag 3
However, when I completed this last year I was on hboot 1.54, now after upgrading a few times my setup is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3880mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I will change the cidnum back to VODAP001 before I do any of the above, but how do I get back to hboot 1.54 ?
The following is the status I need to get the phone back to:
(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: 2.24.161.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36JW907644
(bootloader) imei: 357864050522398
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4149mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
will the version-main and baseband also be downgraded when I use the Guru_Reset_M7_2.24.161.1.zip file ?
No the version main won't be downgraded with the guru reset file, that file is pretty much rom only, you need the firmware.zip file to do that, you also need it to downgrade your hboot, or an ruu, I've had a look and there is no ruu for Vodafone, however, there is some earlier ota's. You could try downloading those and pull firmware.zip from them, then manually flash that, firmware zip contains things like stock recovery, radio, hboot, partition layouts etc, try and get one which matches the number on the guru reset file, ie search for 2.24.161.xx firmware, flash that first, you will then need to put a custom recovery back on to run the guru reset file, during the installation, select wipe data, install stock recovery and install stock radio, once it's all done and booted at least once, only then lock your bootloader and s-on, be careful when going back s-on though, it's been known for the tampered flag to return, personally I would send it back s-off, high chance they wouldn't even notice.
Just one question, why do you want to root ?, if your returning to stock for warranty then skip that part completely, you won't need root.
You may be able to pull firmware.zip from this ota http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Seanie280672 said:
No the version main won't be downgraded with the guru reset file, that file is pretty much rom only, you need the firmware.zip file to do that, you also need it to downgrade your hboot, or an ruu, I've had a look and there is no ruu for Vodafone, however, there is some earlier ota's. You could try downloading those and pull firmware.zip from them, then manually flash that, firmware zip contains things like stock recovery, radio, hboot, partition layouts etc, try and get one which matches the number on the guru reset file, ie search for 2.24.161.xx firmware, flash that first, you will then need to put a custom recovery back on to run the guru reset file, during the installation, select wipe data, install stock recovery and install stock radio, once it's all done and booted at least once, only then lock your bootloader and s-on, be careful when going back s-on though, it's been known for the tampered flag to return, personally I would send it back s-off, high chance they wouldn't even notice.
Just one question, why do you want to root ?, if your returning to stock for warranty then skip that part completely, you won't need root.
You may be able to pull firmware.zip from this ota http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Click to expand...
Click to collapse
need root to remove the TAMPERED flag.
akuma24 said:
need root to remove the TAMPERED flag.
Click to expand...
Click to collapse
Nah you don't, on the guru reset site, there is a bootloader reset tool which you just run from custom recovery.
It will allow you to lock, relock, unlock the bootloader whilst s-off and also remove the tampered flag
http://www.htc1guru.com/guides/guru-bootloader-reset/
Seanie280672 said:
Nah you don't, on the guru reset site, there is a bootloader reset tool which you just run from custom recovery.
It will allow you to lock, relock, unlock the bootloader whilst s-off and also remove the tampered flag
http://www.htc1guru.com/guides/guru-bootloader-reset/
Click to expand...
Click to collapse
Thanks again, can you extract the firmware from this file for me ? I try to extract on a mac and it just zip's the file back up
http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Then again, Im thinking, is it necessary to downgrade the firmware to version 2.24.161.1, maybe downgrade to 4.06.1540.2 instead
akuma24 said:
Thanks again, can you extract the firmware from this file for me ? I try to extract on a mac and it just zip's the file back up
http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
Then again, Im thinking, is it necessary to downgrade the firmware to version 2.24.161.1, maybe downgrade to 4.06.1540.2 instead
Click to expand...
Click to collapse
I'm not near a computer at the moment so can't do that sorry, 161 is Vodafone, the other one you mentioned is 1540 developer edition, as you are s-off you can flash any ruu, but it might get questioned.
Seanie280672 said:
I'm not near a computer at the moment so can't do that sorry, 161 is Vodafone, the other one you mentioned is 1540 developer edition, as you are s-off you can flash any ruu, but it might get questioned.
Click to expand...
Click to collapse
what about 4.19.401.11, is that developer also ?
akuma24 said:
what about 4.19.401.11, is that developer also ?
Click to expand...
Click to collapse
That's WWE unbranded Europe, that's what I have on my phone, that would work, change your cid to HTC__001 first then get the ruu 4.19.401.9 and run it, you'll be full stock in no time.
4.19.401.11 is just an ota
Seanie280672 said:
That's WWE unbranded Europe, that's what I have on my phone, that would work, change your cid to HTC__001 first then get the ruu 4.19.401.9 and run it, you'll be full stock in no time.
4.19.401.11 is just an ota
Click to expand...
Click to collapse
what about this firmware:
http://d-h.st/WO9 (2.24.401.1)
akuma24 said:
what about this firmware:
http://d-h.st/WO9 (2.24.401.1)
Click to expand...
Click to collapse
You may as well just run the 401 ruu which will update the firmware too and hboot, it will do everything for you.
Seanie280672 said:
You may as well just run the 401 ruu which will update the firmware too and hboot, it will do everything for you.
Click to expand...
Click to collapse
Wouldnt the fact I have a WWE rom on my phone with a cid of VODA raise eyebrows over at htc ? True I can change the cid to HTC__xx but do they not have a record of which phone was given to which network etc
akuma24 said:
Wouldnt the fact I have a WWE rom on my phone with a cid of VODA raise eyebrows over at htc ? True I can change the cid to HTC__xx but do they not have a record of which phone was given to which network etc
Click to expand...
Click to collapse
I got mine from Vodafone UK, unbranded on HTC__001, you can't send it unbranded with a Vodafone cid, you will need to send it with the HTC cid
Seanie280672 said:
I got mine from Vodafone UK, unbranded on HTC__001, you can't send it unbranded with a Vodafone cid, you will need to send it with the HTC cid
Click to expand...
Click to collapse
Have downloaded the following and it contains the firmware for 4-19-161-11
http://www.htc1guru.com/dld/ota_m7_...-63-161-6_release_356881mwn487m942rk64ep-zip/
The download for 2.24.161.1 on the site times out after download 142MB so think it is corrupt.
The plan is to flash the firmware from 4-19-161-11, then run the guru reset for 2.24.161.1 and take the OTA's to bring it up to whatever it should currently be ?
These phones were so easy to reset back in the Hero days
akuma24 said:
Have downloaded the following and it contains the firmware for 4-19-161-11
http://www.htc1guru.com/dld/ota_m7_...-63-161-6_release_356881mwn487m942rk64ep-zip/
The download for 2.24.161.1 on the site times out after download 142MB so think it is corrupt.
The plan is to flash the firmware from 4-19-161-11, then run the guru reset for 2.24.161.1 and take the OTA's to bring it up to whatever it should currently be ?
These phones were so easy to reset back in the Hero days
Click to expand...
Click to collapse
Yu can't do that, the 4xxxxx firmware will contain too high a hboot for the otas to work, although the guru reset file will install, the otas will lead to a bootloop due to you already having a higher hboot
Seanie280672 said:
Yu can't do that, the 4xxxxx firmware will contain too high a hboot for the otas to work, although the guru reset file will install, the otas will lead to a bootloop due to you already having a higher hboot
Click to expand...
Click to collapse
Right, I need someone to fix that link then, have posted it in the collection thread, hopefully someone fixes it
Right so decided Im short on time so will run the following after changing the cid to HTC__001
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
This will downgrade the firmware and also flash the stock rom for htc europe.
Ill then need to change the recovery in order to run the following:
http://www.htc1guru.com/guides/guru-bootloader-reset/
then reflash stock recovery and finally remove s-off
????
akuma24 said:
Right, I need someone to fix that link then, have posted it in the collection thread, hopefully someone fixes it
Click to expand...
Click to collapse
which link, maybe there is another ?
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
im home now so im just downloading that ota, see if it contains a firmware.zip that I can extract, then i'll upload it for you if its there.
the download keeps getting reset, this site is starting to do my head in.
Seanie280672 said:
which link, maybe there is another ?
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
im home now so im just downloading that ota, see if it contains a firmware.zip that I can extract, then i'll upload it for you if its there.
Click to expand...
Click to collapse
this link here http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
think the one you are downloading
akuma24 said:
this link here http://www.htc1guru.com/2013/10/vodafone-ota-2-24-161-1-added/
think the one you are downloading
Click to expand...
Click to collapse
yeah, he has a problem with someone hacking that site and resetting the downloads every 5 mins or so, im just trying to source the file from somewhere else.
Seanie280672 said:
yeah, he has a problem with someone hacking that site and resetting the downloads every 5 mins or so, im just trying to source the file from somewhere else.
Click to expand...
Click to collapse
Thanks, would really appreciate it if you could an alternative download source\link

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.

[Q] In Deep Trouble with MID Change. HELP PLEASE!!!

I tried changing my HTC One M8_WHL PVT SHIP S-OFF into developer edition using the guide on http://htc-one.wonderhowto.com/how-...edition-for-super-fast-sense-updates-0156524/ . I successfully changed the MID and the CID without breaking a sweat. After, I used TWRP to restore the backup which the guide instructed me to download and restore. After restoring that backup, device could only boot HBOOT. Now I tried running the RUU.exe for Developer Edition and I get the error which asks that I run the correct RUU for the device. Now, the device doesn't boot pass HBOOT
What I can do ...
1. Boot into TWRP recovery
2. Give fastboot commands with HBOOT
3. Boot into RUU via fastboot
What I can't do ...
1. Boot the device
2. Revert the MID change to its original state cos I will need to run ADB Shell to do that, which cannot be done from HBOOT
3. No RUU.exe is responding to flashing the device
The specific help I need ...
1. Be able to Change MID using Fastboot so I can run a SPRINT RUU
fastboot getvar all results ...
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Mod Edit
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: Mod Edit
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
PLEASE HELP!
You forgot the most important thing to do before doing something like this....read.
Your M8 must be a GSM model, like AT&T, T-Mobile, and most international variants.
Click to expand...
Click to collapse
Have you tried running the command to change the MID while booted to twrp?
As I have been using my GSM SIM in it, it didn't occur to me that it could be any different from a GSM Model. When I bought it, it came with S-Off and CID 11111111, though the bootloader was locked (like any other locked HBOOT from factory, not relocked).
BD619 said:
You forgot the most important thing to do before doing something like this....read.
Have you tried running the command to change the MID while booted to twrp?
Click to expand...
Click to collapse
Kindly show me direct me to a thread on how I can change the MID while booted to twrp. Thank you.
Economistaterry said:
My M8 is a GSM Model. I use to use my GSM SIM in it.
Click to expand...
Click to collapse
HTC One M8_WHL
Click to expand...
Click to collapse
is Sprint which is CDMA not GSM.
You said in your first post you could not revert your MID because you can't run adb shell... adb works in recovery...it's worth a shot.
Try changing your CID to SuperCID then try the Sprint RUU.
BD619 said:
is Sprint which is CDMA not GSM.
You said in your first post you could not revert your MID because you can't run adb shell... adb works in recovery...it's worth a shot.
Click to expand...
Click to collapse
ADB Shell won't start in TWRP sideload. But ADB devices comes out positively with the list of devices attached.
BD619 said:
Try changing your CID to SuperCID then try the Sprint RUU.
Click to expand...
Click to collapse
This was one of my first options. Didn't work.
Economistaterry said:
This was one of my first options. Didn't work.
Click to expand...
Click to collapse
Have you tried changing it back to Sprint CID?
BD619 said:
Have you tried changing it back to Sprint CID?
Click to expand...
Click to collapse
I haven't. The device came with Super CID. Let me try that and see. However, I tried flashing the firmware of Sprint via RUU with Super CID. The MID error showed up. I feel same will happen even if I change to Sprint CID, but I'll give it a shot.
BD619 said:
Have you tried changing it back to Sprint CID?
Click to expand...
Click to collapse
No luck.
adb should work in twrp(dont use adb sideload option, it should work without doing anything), try reinstalling TWRP i just tested it on v2.8.6 2015-04-22 p1
---------- Post added at 05:06 AM ---------- Previous post was at 05:00 AM ----------
Economistaterry said:
Kindly show me direct me to a thread on how I can change the MID while booted to twrp. Thank you.
Click to expand...
Click to collapse
here is the link(post #2 has code for sprint), please be very careful it can easily turn your M8 into a piece of aluminum.
Vcek said:
adb should work in twrp(dont use adb sideload option, it should work without doing anything), try reinstalling TWRP i just tested it on v2.8.6 2015-04-22 p1
---------- Post added at 05:06 AM ---------- Previous post was at 05:00 AM ----------
here is the link(post #2 has code for sprint), please be very careful it can easily turn your M8 into a piece of aluminum.
Click to expand...
Click to collapse
Bookmarked thanks.
vcek said:
adb should work in twrp(dont use adb sideload option, it should work without doing anything), try reinstalling twrp i just tested it on v2.8.6 2015-04-22 p1
---------- post added at 05:06 am ---------- previous post was at 05:00 am ----------
here is the link(post #2 has code for sprint), please be very careful it can easily turn your m8 into a piece of aluminum.
Click to expand...
Click to collapse
yes! Yes! You are a life saver! Thank you so much!
It worked! It worked!
Phone is back alive! Wheew!

Categories

Resources