[Q] GPe to Sense - One (M7) Q&A, Help & Troubleshooting

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 ?

Related

Security Warning

hi i have incredible s canadian version sasktel and i have try to install rom from ruu and i renamed it to pg32img.zip and i install from bootloader and when it finish the appear cid incorrect and failed and the device now is freezing on bootloader and it appear Security Warning and s-on and i cant use usb connection..how can i installed the orginal rom via memory card or what?
any body can help me??
hashnoz said:
hi i have incredible s canadian version sasktel and i have try to install rom from ruu and i renamed it to pg32img.zip and i install from bootloader and when it finish the appear cid incorrect and failed and the device now is freezing on bootloader and it appear Security Warning and s-on and i cant use usb connection..how can i installed the orginal rom via memory card or what?
any body can help me??
Click to expand...
Click to collapse
Before you attempted this, did you run AlphaRevX to gain S-OFF? Which RUU were you attempting to install? There was another thread about this 'Security Warning' on the HBOOT screen and I'm not sure the OP was able to get this resolved.
yes the phone was s-off but after i install the rom the phone back to s-onn now i cant connect via usb or connection just it appear 'Security Warning' how can install orginal rom?
hashnoz said:
yes the phone was s-off but after i install the rom the phone back to s-onn now i cant connect via usb or connection just it appear 'Security Warning' how can install orginal rom?
Click to expand...
Click to collapse
Here is the other thread about the Security Warning. You may want to read through it and see if any of the suggestions will work for you.
http://forum.xda-developers.com/showthread.php?t=1136041
The only way to get out of that is by flashing the stock RUU the phone came with. In your case it would have to be Sasktel and if that doesn't work because you receive the error "Main Version is Older!" then your screwed. Your going to have to wait until Sasktel or Bell releases their official gingerbread updates.
I am in the exact same boat as I am the composer of the thread from above lol.
Hi All My phone dead because I try to installed 2.30.405.1 from RUU extracted PG32IMG.zip. when phone is power ON top side write "Security Warning" MY Phone CID is HTC__038 (for Indian) but I had european Rom 2.12.405.7.
phone boot only fastboot and getvar /all info here
C:\fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.13.0000
INFOversion-baseband: 3805.06.03.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.12.405.7
INFOserialno: HT15********
INFOimei: 35*************
INFOproduct: vivo
INFOplatform: HBOOT-7630
INFOmodelid: PG3213000
INFOcidnum: HTC__038
INFObattery-status: good
INFObattery-voltage: 4168mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8a731c6e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
I Installed 2.12.405.7 with goldcard. and new can't make goldcard because not ADB
I try add android_info.txt this text cidnum: HTC__038 but not worked
I hope I need Indian RUU Rom with CID: HTC__038 Or who know this Problem? and who can help me?
I had the same problem with my Bell IS, I just ran the ruu.exe from a Windows pc and it installed with no problems at all. Now I'm back to a stock rom, with no problems at all.
I am going to S-off and root again later, whenever a stable Rom comes round. If you don't have a stock RUU, you can get it on HTC'S website, if one for you carrier is available.
Sent from my HTC Incredible S using XDA Premium App
In official htc site can't find stock ruu installer for my IS with cid:HTC__038.
You can create a gold card and try flashing your original rom or the rom you were originally trying to flash on your phone.
Can you tell me were or how to make? I have not CID for Gold card
How to make w/o ADB and w/o XTC-Clip?
You can buy a card reader and try and make one that way. Then put the goldcard into the inc s.
Sent from my HTC Incredible S using XDA App
Have you tried to install the SaskTel ruu.exe gb upgrade from Windows?
If that won't work, then you will have to find the proper ruu for your phone and install via a pc.
Sent from my HTC Incredible S using XDA Premium App
sasktel ruu and zip file not worked - 'model id incorrect'
:-(
Try removing android.txt, leave it out and run ruu again.
It is pretty hard to brick a phone, it just takes some time and a lot of trying different things, but you should be able to succeed.
Sent from my HTC Incredible S using XDA Premium App
ste1164 said:
You can buy a card reader and try and make one that way. Then put the goldcard into the inc s.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
How to I do. I have card reader from my Laptop
budleyca said:
Try removing android.txt, leave it out and run ruu again.
It is pretty hard to brick a phone, it just takes some time and a lot of trying different things, but you should be able to succeed.
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Not worked
i need to bypass signature checking (it is my problem)
what i made:
first it boot in fastboot, then erase cache, boot ruu mode and
ran installer ruu 2.12.405.7 then i change android_info.txt
modelid: PG3213000
cidnum: HTC__038
mainver: 2.12.405.7
hbootpreupdate:13
made pack rom.zip and overwrite original rom.zip (temp folder)
but installer sad sending, cleaning user data, and checking signature and stoped - "incorrect signature"
what i must do?
kuba28ms said:
i need to bypass signature checking (it is my problem)
what i made:
first it boot in fastboot, then erase cache, boot ruu mode and
ran installer ruu 2.12.405.7 then i change android_info.txt
modelid: PG3213000
cidnum: HTC__038
mainver: 2.12.405.7
hbootpreupdate:13
made pack rom.zip and overwrite original rom.zip (temp folder)
but installer sad sending, cleaning user data, and checking signature and stoped - "incorrect signature"
what i must do?
Click to expand...
Click to collapse
The only way to by-pass the HTC signature check in RUU mode is if you have S-OFF (security off).
so no way to repair phone?
kuba28ms said:
so no way to repair phone?
Click to expand...
Click to collapse
Ok so I have gone back and reread your posts. I would suggest you go back and try flashing 2.30.405.1 instead of trying to go back to 2.12.405.7. According to your getvar output, the radio from the 2.30.405.1 has been flashed. It would probably help if you could make a gold card and then try flashing the 2.30.405.1 RUU. Or you can try it without a gold card.

[Solved] Back to stock

All right, here comes a noob question:
My HTC One is from Israel, and though I made a nandroid backup of my phone after I rooted it, I don't have one from before my rooting it. That said, my CID was HTC__K18...there is no RUU for that CID, so I used rumrunner to s-off my phone, changed my CID to HTC__01 and used the European RUU (the U not the UL because my phone is a U) to get %100 back to stock. The RUU that I flashed has a hboot of 1.44 and my stock was already a 1.54 and 4.2.2 (maybe 4.1.2?)...anyway after flashing the RUU, I'm not able to OTA and I really just want to get %100 stock...in a way that I'd be capable of receiving all the updates OTA and have the highest firmware/software. Thanks in advance!
Oh, and here's some of my info:
version-bootloader: 1.44.0000 (it shipped with 1.54 but I RUUed an older version)
version-baseband: 4A.14.3250.13
version-main: 1.29.401.2 (it shipped with 2.24.401.2)
version-misc: PVT SHIP S-OFF (used rumrunner to s-off hboot of 1.54)
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__001 (I changed the cid from HTC__k18)
shpongleeyes said:
All right, here comes a noob question:
My HTC One is from Israel, and though I made a nandroid backup of my phone after I rooted it, I don't have one from before my rooting it. That said, my CID was HTC__K18...there is no RUU for that CID, so I used rumrunner to s-off my phone, changed my CID to HTC__01 and used the European RUU (the U not the UL because my phone is a U) to get %100 back to stock. The RUU that I flashed has a hboot of 1.44 and my stock was already a 1.54 and 4.2.2 (maybe 4.1.2?)...anyway after flashing the RUU, I'm not able to OTA and I really just want to get %100 stock...in a way that I'd be capable of receiving all the updates OTA and have the highest firmware/software. Thanks in advance!
Oh, and here's some of my info:
version-bootloader: 1.44.0000 (it shipped with 1.54 but I RUUed an older version)
version-baseband: 4A.14.3250.13
version-main: 1.29.401.2 (it shipped with 2.24.401.2)
version-misc: PVT SHIP S-OFF (used rumrunner to s-off hboot of 1.54)
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__001 (I changed the cid from HTC__k18)
Click to expand...
Click to collapse
Question: where do you want to go?
1- To an European stock model
2- To your version (I have a nandroid of 2.24.401.2 for a PN0711000, M7_U)
nkk71 said:
Question: where do you want to go?
1- To an European stock model
2- To your version (I have a nandroid of 2.24.401.2 for a PN0711000, M7_U)
Click to expand...
Click to collapse
Whatever would give me OTA updates and allow me to be as stock as possible! Just out of curiosity, what would the benefits of each be? Thank you!
shpongleeyes said:
Whatever would give me OTA updates and allow me to be as stock as possible! Just out of curiosity, what would the benefits of each be? Thank you!
Click to expand...
Click to collapse
LOL, this just resulted in another question: why not use a custom ROM, they get updated way more frequently than OTAs? If you want "stock as possible" you can check out ARHD, it's very stock. (and since you're S-Off you can upgrade/downgrade anytime, including firmware!!)
As for benefits of the other two options:
1) I think HTC__001 (or was it Y13, not sure), are usually among the first WWE editions to get OTAs (not as fast as custom ROMs )
2) HTC_K18 would put you back to a state where you bought the phone.
It's all personal choice, eg I like stock but want it rooted so I'm currently running ARHD 13.3 (until I decide to upgrade), others like their Venom Tweaks or InsertCoin etc... and again for others they need to be unrooted because of some banking apps.
So give it a thought and let me know, which road you wanna take
PS: Hit the thanks button if I helped
nkk71 said:
LOL, this just resulted in another question: why not use a custom ROM, they get updated way more frequently than OTAs? If you want "stock as possible" you can check out ARHD, it's very stock. (and since you're S-Off you can upgrade/downgrade anytime, including firmware!!)
As for benefits of the other two options:
1) I think HTC__001 (or was it Y13, not sure), are usually among the first WWE editions to get OTAs (not as fast as custom ROMs )
2) HTC_K18 would put you back to a state where you bought the phone.
It's all personal choice, eg I like stock but want it rooted so I'm currently running ARHD 13.3 (until I decide to upgrade), others like their Venom Tweaks or InsertCoin etc... and again for others they need to be unrooted because of some banking apps.
So give it a thought and let me know, which road you wanna take
PS: Hit the thanks button if I helped
Click to expand...
Click to collapse
Thank you for the quick reply!
Okay, so I'd like to go with the European road...as far as custom ROMs are concerned, I had ARHD, both GE and Sense, but I just want things to run smoothly and not worry about OTAs....I'd like to receive them as soon as they're available with the least amount of headache...
On that note, can I receive OTA updates directly from HTC while I'm s-off? Because currently I don't have that option...it doesn't even show that I have an update available.
Also, is your nandroid of 2.24.401.2 made with cid HTC__k18?
P.s. I don't even need/want to root the phone again...it's just too much for me. I'd like to get as stock as possible while keeping the options open (that's why I want to leave s-off).
Thank you again for your help! You're awesome!
shpongleeyes said:
Thank you for the quick reply!
Okay, so I'd like to go with the European road...as far as custom ROMs are concerned, I had ARHD, both GE and Sense, but I just want things to run smoothly and not worry about OTAs....I'd like to receive them as soon as they're available with the least amount of headache...
On that note, can I receive OTA updates directly from HTC while I'm s-off? Because currently I don't have that option...it doesn't even show that I have an update available.
P.s. I don't even need/want to root the phone again...it's just too much for me. I'd like to get as stock as possible while keeping the options open (that's why I want to leave s-off).
Thank you again for your help! You're awesome!
Click to expand...
Click to collapse
Ok, European road
1- You've already changed your CID, you still need to change your MID: "fastboot oem writemid PN0710000"
(keep a record of your original CID, MID, and software/firmware version somewhere in case you ever need it)
2- remove tampered either using revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- set your phone to LOCKED (not relocked) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- then use the full European RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
you should keep S-Off and not go back S-On.
After installing the RUU you should immediately start receiving OTAs all the way up to 3.62
PS: remember the above procedure will wipe everything off your phone, so back up anything you may need first!!
nkk71 said:
Ok, European road
1- You've already changed your CID, you still need to change your MID: "fastboot oem writemid PN0710000"
(keep a record of your original CID, MID, and software/firmware version somewhere in case you ever need it)
2- remove tampered either using revone or http://forum.xda-developers.com/showthread.php?t=2477792
3- set your phone to LOCKED (not relocked) using revone or http://forum.xda-developers.com/showthread.php?t=2475914
4- then use the full European RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
you should keep S-Off and not go back S-On.
After installing the RUU you should immediately start receiving OTAs all the way up to 3.62
PS: remember the above procedure will wipe everything off your phone, so back up anything you may need first!!
Click to expand...
Click to collapse
You're awesome. However, I did all those steps except for the first step...when I go into recovery mode now, there's still the red lettering as well as when I go into "Tell HTC and error reporting" the red lettering says "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings." Oh, and I'm not able to receive the OTAs.
Now, if I change the MID, do I need to do all the steps again or can I just do the first step now? Will that help get rid of the "test device" warnings that I have on the phone?
Oh, and I used this European one before (cause I have a U and not UL) http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
Why would I use the UL one?
Thank you again for you time and help!
shpongleeyes said:
You're awesome. However, I did all those steps except for the first step...when I go into recovery mode now, there's still the red lettering as well as when I go into "Tell HTC and error reporting" the red lettering says "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings." Oh, and I'm not able to receive the OTAs.
Now, if I change the MID, do I need to do all the steps again or can I just do the first step now? Will that help get rid of the "test device" warnings that I have on the phone?
Thank you again for you time and help!
Click to expand...
Click to collapse
You won't get any OTAs because of your MID, change it, and see if you start getting the OTAs. M7_U and M7_UL share pretty much most of the software stuff, the hardware is different of course, but MID 0711 and CID HTC__001 won't get any OTAs.
The "Tell HTC and error reporting" red text is because you're S-Off, personally I wouldn't care. But if it bothers you A LOT, you'll need to go S-On again, and AT THIS TIME you should NOT!!! we can deal with that later.
Change MID, and confirm you are now getting OTAs
Again DO NOT GO S-ON, at least for the time being!!
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
shpongleeyes said:
Oh, and I used this European one before (cause I have a U and not UL) http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
Click to expand...
Click to collapse
Oh I didnt see that one, but it should give you updates till 2.24.401.9 at least. Don't know if 3.62 out yet for that PN.
nkk71 said:
You won't get any OTAs because of your MID, change it, and see if you start getting the OTAs. M7_U and M7_UL share pretty much most of the software stuff, the hardware is different of course, but MID 0711 and CID HTC__001 won't get any OTAs.
The "Tell HTC and error reporting" red text is because you're S-Off, personally I wouldn't care. But if it bothers you A LOT, you'll need to go S-On again, and AT THIS TIME you should NOT!!! we can deal with that later.
Change MID, and confirm you are now getting OTAs
Again DO NOT GO S-ON, at least for the time being!!
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
Oh I didnt see that one, but it should give you updates till 2.24.401.9 at least. Don't know if 3.62 out yet for that PN.
Click to expand...
Click to collapse
Okay, I tried to change the mid but the console is giving me an error:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.031s
shpongleeyes said:
Okay, I tried to change the mid but the console is giving me an error:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.031s
Click to expand...
Click to collapse
Let's slow it down a little, if I understand correctly:
1- you are now unTAMPERED
2- you are now LOCKED, not RElocked or UNlocked
3- you have CID: HTC__001
4- you have MID: PN0711000
5- you ran the RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- you are still S-Off (please!)
If all of the above are true, when you go to Settings->About->Software Update (or whatever it's called), does it show an update? or what does it say
EDIT: can you repost a "fastboot getvar all" (remove IMEI and s/n)
nkk71 said:
Let's slow it down a little, if I understand correctly:
1- you are now unTAMPERED
2- you are now LOCKED, not RElocked or UNlocked
3- you have CID: HTC__001
4- you have MID: PN0711000
5- you ran the RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- you are still S-Off (please!)
If all of the above are true, when you go to Settings->About->Software Update (or whatever it's called), does it show an update? or what does it say
EDIT: can you repost a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
you're correct about everything:
All it says is that my software is up-to-date...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
shpongleeyes said:
you're correct about everything:
All it says is that my software is up-to-date...
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
Before we go on messing with MID, can you just change CID to HTC__J15 (two underscores) and check for a software update, don't know the original 1.xx version, but I am sure that J15 PN0711 got the 2.24.401.2 and (possibly) 2.24.401.9.
Just check if it gives an update with HTC__J15, no need to download it!!
nkk71 said:
Before we go on messing with MID, can you just change CID to HTC__J15 (two underscores) and check for a software update, don't know the original 1.xx version, but I am sure that J15 PN0711 got the 2.24.401.2 and (possibly) 2.24.401.9.
Just check if it gives an update with HTC__J15, no need to download it!!
Click to expand...
Click to collapse
Yes
That gives me an option to upgrade...
now what?
shpongleeyes said:
Yes
That gives me an option to upgrade...
now what?
Click to expand...
Click to collapse
Oh man, sorry to keep you hanging, but we may need to pick this up tomorrow, going for dinner now, wont be back till tomorrow,
but try setting CID to your original one, and see if you get any updates for your original CID.
sorry, got to go, I'll check back on you tomorrow
whatever you decide to do, do NOT GO S-ON (at least for now)
Have a good evening...
nkk71 said:
Oh man, sorry to keep you hanging, but we may need to pick this up tomorrow, going for dinner now, wont be back till tomorrow,
but try setting CID to your original one, and see if you get any updates for your original CID.
sorry, got to go, I'll check back on you tomorrow
whatever you decide to do, do NOT GO S-ON (at least for now)
Have a good evening...
Click to expand...
Click to collapse
When I set it back to my original CID there are no updates...enjoy the food
I look forward to tomorrow!
shpongleeyes said:
When I set it back to my original CID there are no updates...enjoy the food
I look forward to tomorrow!
Click to expand...
Click to collapse
Hey, how are you today?
I'll be online later (around 5 or 6), but it looks like that RUU is fully compatible with ur original CID. So go ahead with your original CID, and get the OTAs. U should be able to get at least to 2.24.401.9, don't know if 3.62 is out for u yet.
Keep s-off in case we need to change something later.
C u later...
Sent from my HTC One using Tapatalk
nkk71 said:
Hey, how are you today?
I'll be online later (around 5 or 6), but it looks like that RUU is fully compatible with ur original CID. So go ahead with your original CID, and get the OTAs. U should be able to get at least to 2.24.401.9, don't know if 3.62 is out for u yet.
Keep s-off in case we need to change something later.
C u later...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Hey, no the RUU is not compatible with my original CID (HTC__K18) as there are no available upgrades after I change the CID...also the same is true when I change it to HTC__001, though it did work when you told me to update to J something or other...weird.
shpongleeyes said:
Hey, no the RUU is not compatible with my original CID (HTC__K18) as there are no available upgrades after I change the CID...also the same is true when I change it to HTC__001, though it did work when you told me to update to J something or other...weird.
Click to expand...
Click to collapse
Well I guess you have 2 choices:
1- set CID to HTC__J15 -> a friend of mine has PN0711000 HTC__J15, it's basically the M7_U version and HTC__J15 is a nonbranded WWE edition but usually for the Middle East
2- set CID to HTC__001, set MID to PN0710000, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
by changing to MID PN0710000, it will make the software on your phone think it's a UL model, but since the hardware isn't there for LTE, it won't make any difference.
Step 1, is probably the easiest to do, so why not just set it to J15 and see how far the updates go. (ie if 3.62 is out for J15).
Hope that helps
nkk71 said:
Well I guess you have 2 choices:
1- set CID to HTC__J15 -> a friend of mine has PN0711000 HTC__J15, it's basically the M7_U version and HTC__J15 is a nonbranded WWE edition but usually for the Middle East
2- set CID to HTC__001, set MID to PN0710000, and use this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
by changing to MID PN0710000, it will make the software on your phone think it's a UL model, but since the hardware isn't there for LTE, it won't make any difference.
Step 1, is probably the easiest to do, so why not just set it to J15 and see how far the updates go. (ie if 3.62 is out for J15).
Hope that helps
Click to expand...
Click to collapse
Thank you for you patience and your help! You've been amazing!
shpongleeyes said:
Thank you for you patience and your help! You've been amazing!
Click to expand...
Click to collapse
No problem, glad to be of help. If everything's OK now, could I please ask you to change the main thread title to include [SOLVED]. Thanks & take care

stock using RUU - Help

hello, imma cut it short :
i have an m7_u, i want to go back to stock , so i can update the phone, so it updates my firmware by itself ( no flashing manual cuz i dnt want to risk a brick.. here's my getvar :
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.25.599.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3742mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e0349bfc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
i want to use the simpe method, ruu.exe
how to know my ruu ?
what do i need to do before running the ruu ? like , lock bootloader , go back s-on ? anything ?
any help is apretiated , thanks alot !
ali-k95 said:
hello, imma cut it short :
i have an m7_u, i want to go back to stock , so i can update the phone, so it updates my firmware by itself ( no flashing manual cuz i dnt want to risk a brick.. here's my getvar :
i want to use the simpe method, ruu.exe
how to know my ruu ?
what do i need to do before running the ruu ? like , lock bootloader , go back s-on ? anything ?
any help is apretiated , thanks alot !
Click to expand...
Click to collapse
like said in your other thread, there is no RUU for .599 version.
NEVER go back s-on
you don't need to lock the bootloader to use a RUU because you have S-OFF
just make sure both your CID and MID match the ruu you want to use, if not you can change both of these values, thanks to S-OFF.
alray said:
like said in your other thread, there is no RUU for .599 version.
NEVER go back s-on
you don't need to lock the bootloader to use a RUU because you have S-OFF
just make sure both your CID and MID match the ruu you want to use, if not you can change both of these values, thanks to S-OFF.
Click to expand...
Click to collapse
Can you send me a link to the ruu ? and how to know to what cid and mid i shoud change ?
can it be more like
1-..
2-...
3-... steps ? thankss
ali-k95 said:
Can you send me a link to the ruu ?
Click to expand...
Click to collapse
You have s-off which mean you can use every ruu intended for M7_UL or M7_U phones.
http://www.htc1guru.com/
and how to know to what cid and mid i shoud change ?
Click to expand...
Click to collapse
CID and MID must match the ruu you will use.
i.e, if you want to use a .401 ruu, cid should be HTC__001 and MID PN0710000
if you want to use dev eidtion, cid: BS_US001 mid: PN0712000
etc
etc
can it be more like
1-..
2-...
3-... steps ?
Click to expand...
Click to collapse
choose the ruu.exe or ruu.zip you want to use
does your cid match the ruu you want to use? yes go to next step, no: change your cid
Code:
fastboot oem writecid <insert correct cid here>
fastboot reboot-bootloader
does your mid match the ruu you want to use? yes: go to next step, no:change your mid
flash the ruu.exe or ruu.zip
ruu.exe ---> lauch the .exe and follow instructions
ruu.zip ---->
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
alray said:
You have s-off which mean you can use every ruu intended for M7_UL or M7_U phones.
http://www.htc1guru.com/
CID and MID must match the ruu you will use.
i.e, if you want to use a .401 ruu, cid should be HTC__001 and MID PN0710000
if you want to use dev eidtion, cid: BS_US001 mid: PN0712000
etc
etc
choose the ruu.exe or ruu.zip you want to use
does your cid match the ruu you want to use? yes go to next step, no: change your cid
Code:
fastboot oem writecid <insert correct cid here>
fastboot reboot-bootloader
does your mid match the ruu you want to use? yes: go to next step, no:change your mid
flash the ruu.exe or ruu.zip
ruu.exe ---> lauch the .exe and follow instructions
ruu.zip ---->
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
Click to expand...
Click to collapse
This is what i'm talking about !
so , is this okaii ?
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
Click to expand...
Click to collapse
if that's not a good one , give me a link or something ?
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
i can choose whatever cid of those , and just that 1 MID , and change my phone's to them , run ruu , the phone is stock , i get an update , udpate it , firmware is updated , and then unlock bootloader again ( in case it relocks by itself due to ruu ) , flash recovery , flash rom again.. is that right ?
ali-k95 said:
This is what i'm talking about !
so , is this okaii ?
if that's not a good one , give me a link or something ?
i can choose whatever cid of those , and just that 1 MID , and change my phone's to them , run ruu , the phone is stock , i get an update , udpate it , firmware is updated , and then unlock bootloader again ( in case it relocks by itself due to ruu ) , flash recovery , flash rom again.. is that right ?
Click to expand...
Click to collapse
the ruu you have linked have PN0710000 and yours is PN0711000, so you'll need to change your mid to use that one. Follow the guide to change mid, its pretty easy to do. Yes you can choose whater cid of those but i'll recommend you to use HTC__001 (don't forget its 2 underscore __ 8 characters total). The bootloader will not relocks by itself
alray said:
the ruu you have linked have PN0710000 and yours is PN0711000, so you'll need to change your mid to use that one. Follow the guide to change mid, its pretty easy to do. Yes you can choose whater cid of those but i'll recommend you to use HTC__001 (don't forget its 2 underscore __ 8 characters total). The bootloader will not relocks by itself
Click to expand...
Click to collapse
Alright , so imma change MID and CID then just run the ruu
downloading it right now , might take a while.. thanks ! i'll re post any new things
alray said:
the ruu you have linked have PN0710000 and yours is PN0711000, so you'll need to change your mid to use that one. Follow the guide to change mid, its pretty easy to do. Yes you can choose whater cid of those but i'll recommend you to use HTC__001 (don't forget its 2 underscore __ 8 characters total). The bootloader will not relocks by itself
Click to expand...
Click to collapse
everything is done ! i changed MID and CID to PN0710000 & HTC__001 respectivly .. now all i have to do is download the ruu i posted and run it right ?
alray said:
the ruu you have linked have PN0710000 and yours is PN0711000, so you'll need to change your mid to use that one. Follow the guide to change mid, its pretty easy to do. Yes you can choose whater cid of those but i'll recommend you to use HTC__001 (don't forget its 2 underscore __ 8 characters total). The bootloader will not relocks by itself
Click to expand...
Click to collapse
Okaii, so i have the ruu file, i ran it, htc went to silver htc screen , then it gave a 155 error.. What ?
( Note : phone is still okaii , nothing wrong happened )
ali-k95 said:
Okaii, so i have the ruu file, i ran it, htc went to silver htc screen , then it gave a 155 error.. What ?
( Note : phone is still okaii , nothing wrong happened )
Click to expand...
Click to collapse
Lock your bootloader, HTC ruu requires it, even if you are s-off
What I don't get is after you have updated your Rom, firmware, and hboot, you are then going to flash a custom Rom ??????
You are making things very difficult and complicated for yourself, just manually update your firmware.
Seanie280672 said:
Lock your bootloader, HTC ruu requires it, even if you are s-off
What I don't get is after you have updated your Rom, firmware, and hboot, you are then going to flash a custom Rom ??????
You are making things very difficult and complicated for yourself, just manually update your firmware.
Click to expand...
Click to collapse
the problem is that i read some people had bricks upgrading manually through firmware.zip files , so let the ruu make it for me , the ota , then i'll just unlock it again , flash custom recovery and custom rom .. ik it's complicated but i have no htc service here if i bricked my phone so yeah :/
Seanie280672 said:
Lock your bootloader, HTC ruu requires it, even if you are s-off
What I don't get is after you have updated your Rom, firmware, and hboot, you are then going to flash a custom Rom ??????
You are making things very difficult and complicated for yourself, just manually update your firmware.
Click to expand...
Click to collapse
EDIT : i relocked it and it's still not working . error 155 , i guess imma try now firmware.zip method ?
( i unlocked bootloader again , changed cid back to 11111111 .. what to do now with MID ? and can i go for this firmware fw_6.06.401.1_custom.zip
or should i use this fw_5.11.401.10_custom.zip ?
thanks.
EDIT : i opened firmware.zip and checked for the mid's, mine was there , so i did it and it went okaii
i'm updated now , thanks all for the help
just one more q. , can i updat fw_6.06.401.1_custom.zip ( i'm on fw_5.11.401.10_custom.zip ) if my ROM is still on fw_5.11.401.10_custom.zip ? thanks.
ali-k95 said:
EDIT : i relocked it and it's still not working . error 155 , i guess imma try now firmware.zip method ?
( i unlocked bootloader again , changed cid back to 11111111 .. what to do now with MID ? and can i go for this firmware fw_6.06.401.1_custom.zip
or should i use this fw_5.11.401.10_custom.zip ?
thanks.
EDIT : i opened firmware.zip and checked for the mid's, mine was there , so i did it and it went okaii
i'm updated now , thanks all for the help
just one more q. , can i updat fw_6.06.401.1_custom.zip ( i'm on fw_5.11.401.10_custom.zip ) if my ROM is still on fw_5.11.401.10_custom.zip ? thanks.
Click to expand...
Click to collapse
as your s-off you can upgrade and downgrade as you please, ive heard the radio file contained in the new firmware is the best to date.
Here's a handy one to add to your bookmarks: http://forum.xda-developers.com/showthread.php?t=2316726
NEVER S-ON, with the custom firmware's, if you s-on, you will have an instant brick due to the modded HBOOT.

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

[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