Develop Bugs

[Q] [RUU] Error: 152. Unable to Restore TMob One M8

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.

I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?

grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.

Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.

grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

help: bricked htc one m7 ?

Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.

redmapleleaf said:
Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.
Click to expand...
Click to collapse
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.

Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
redmapleleaf said:
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.
Click to expand...
Click to collapse

Update: all problems are fixed, the phone is returned to its stock state completely. Here is what I did.
1. Change the CID to T-MOB010 by using "fastboot oem writecid T-MOB010
2. with CID=T-MOB010 and model number MID=PN0713000 I look up the RUU exe that support those two parameters and download it from htc1guru.com
3. down grade my hboot from 1.54 to 1.44 by flashing a hboot.zip file
4. put the phone in fastboot mode and run the RUU exe . After it is done the phone is back to stock rom.
That's it. Hope these steps could help some sorry soul out there. This HTC root/unroot is NOT FUN at all! If you happen to read this HTC, please make your bootloader idiot proof. Otherwise we will just go with your competitor whoever has a better bootloader.
redmapleleaf said:
Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
Click to expand...
Click to collapse

[Q] HTC one M8 (dual sim) stuck on bootloader! What can I do?

Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!

Flash it again via adb, the flashing command must be executed twice.

I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!

Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.

Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!

Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s

Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.

OP - Do you want it back to Sense?

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.

Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...

EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.

We should be able to sort things out, but I'll need to get to a proper PC and get links together

EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!

OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!

EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.

I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!

The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you

At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?

Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.

Soft bricked with S-On

I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.

xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.

You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.

R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!

R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs

ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================

smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.

HTC 820 Desire Flashing Firmware Tutorial

So basically I made this guide for myself and though that It would be good for sharing it.
My problems started when phone just started restarting after one of the components failed. Sometimes it would be google play services, sometimes htc backup, sometimes others.. Plus, phone didnt wanna recognize my SIM card. Okay, tried with other roms here (sadly, there are only a couple of roms for this phone). None of them worked fully, while I could get rid of random restarts SIM still wasnt recognized. I was starting to lose my mind here, but hopefully found the solution. Here is a process of it:
Important note: Its really important that you read through everything first (especially useful links in the last section "Useful guides" ) and then to try and fix your phone
1. Usefull commands:
fastboot.exe getvar all -gets info about device, but you need to be in fastboot mode
Result:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U10305041_08.01.50512
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: MB622YC03068
(bootloader) imei: ***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ40000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1be89947
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
fastboot.exe oem readcid -gets CID from device. List of CIDs(https://forum.xda-developers.com/desire-820/general/htc-cid-list-t3359862)
Result:
Code:
(bootloader) cid: HTC__032
2. To unlock bootlader:
You need Unlock_code.bin file from htcdev.com(obtained by pasting the result of a command
fastboot oem get_identifier_token -gets you code for generating Unlock_code.bin.
Code:
<<<< Identifier Token Start >>>>
7AC0E35FE034FCAB88DEC6B8E650EC33
63556D84723B05EE4B2CE16AA8E6B1A4
B3E94B50C50EF1F6016D39CD16021F03
CBB2BEF798EE9FE77E395895449C4AC7
017E71B15D5E2C9AEBEBB41C491BA255
6D3F7E66005B5A36856DE0F59CCAE258
C944A80FACD0DBBD684297F15BE4AE26
183302EFBA2BF7A99B7A5CB1D4895E39
818A3F562FBCC159568F77C54C27EC16
6FD4F5200326F2B0E6E2B417A4145D85
1C692E7E62BDF4EC1B34A12CEB98E0EC
AB09CECABCDC11E60A3EAA28F0C81A0A
688F2A62591B21EEA7560DD07D14CBC8
9E536469D50C1DD79D5ACA6858D12155
199C47F8951658C98D11314467138082
787381ECA7DA832308497380A53EE403
<<<<< Identifier Token End >>>>>
After pasting that code into htcdev.com (you need to register), and getting Unlock_code.bin in your mailbox...
Run this command to unlock your bootloader.
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
And, to relock it, run this:
Code:
fastboot oem lock
Important: After the first unlock you will never get a status "LOCKED" in hboot.
Only "RELOCKED". Some say that to get trully again "LOCKED" status you need to S-OFF (Security-OFF)
3. To update firmware (not the same as rom
I was before on marshmallow.
First you need to download a firmware, which is in the zip format. Note that it cant be extracted and its not supposed to.
File name is in a like this format:
0PFJIMG_A51_UL_M60_DESIRE_SENSE70_MR_HTC_Europe_3.17.401.3_Radio_01.01.010_U10305041_08.01.50512_release_476105_signed_2.zip
Note the part A51_UL - matches the "product" property of "fastboot.exe getvar all" command;
M60 - i can only assume that it is a code for Marshmallow 6.0;
SENSE70 - HTC Sense version;
Europe - I can assume that this has to match your CID. (mine is 032 which is EastEurope);
3.17.401.3 - My assumption is that this has to match your bootloader version. Mine is 3.19.0.0000 so you should find a closest version to yours
Radio_01.01.010_U10305041_08.01.50512 - this is important also! Its the radio version and *must* be the same as the one you get from "fastboot.exe getvar all" command.
4. Flashing:
There are two ways to flash the firmware. Via usb(adb/fastboot) and directly copying firmware to your sdcard and booting into bootlader.
Keep in mind that your bootlader has to be either relocked or locked. It wont work if you have "UNLOCKED" status.
For both ways you have to rename that long file name to a short, in exactly following manner:
Mine, from "0PFJIMG_A51_UL_M60_DESIRE_SENSE70_MR_HTC_Europe_3.17.401.3_Radio_01.01.010_U10305041_08.01.50512_release_476105_signed_2.zip" became "0PFJIMG.zip". You only need to keep that first parameter as the file name.
4a. Via usb (boot into fastboot mode):
fastboot oem rebootRUU - Reboot into RUU mode, you will get black screen with silver htc logo
fastboot flash 0PFJIMG.zip -this will flash your file and take a while. However, you might get an error like me(failed remote: 32 header), or similar header number. If so, try the other method (4b).
4b. Via sd card:
Copy the 0PFJIMG.zip in the root of your sd card;
Reboot your phone into hboot and it should automatically recognize that file and start flashing.
It takes a bit, aroound 10-20 minutes? I forgot, but as long as the bar is moving you're good.
After that, phone will prompt for a restart and go into usual procedure of first start.
Keep in mind that your data on microsd card will not be deleted, so you're good.
5. Where to find image for your device?
This took me long to find but you have it on gsmdevelopers in this big thread:
For example I found mine on
You need to search through it by your product(model), radio, bootloader and android version. These three should match. Also, the CID too (or take the region closest to you if previos four parametres are matching and you cant find your specific cid).
6. Drivers:
The usual adb/fastboot binaries are required as well as the special "Htc special fastboot Driver" from here.
I dont think your fastboot will recognize your device without these drivers. If the link gets broken those drivers can be found on XDA too.
So if you are getting an error where fastboot cant recognize your device - check the drivers first from that and other sources as well.
7. What after?
You can now safely again unlock the bootloader and install twrp and after that root your phone if you need it.
8. Installing twrp:
Unlock bootloader(check 1.) and follow this guide:
For rooting I havent tried SuperSU, but used Magisk root.
9. Useful pages:
Flashing guide:
http://forum.gsmdevelopers.com/htc-...-file-flashing-via-sdcard-flashing-guide.html
https://www.hardreset.info/devices/htc/htc-desire-820/faq/firmware-flash/update-change-repair-htc/
To obtain Unlock_code: https://www.htcdev.com/
Firmware mention in this guide: https://androidfilehost.com/?fid=24572369242687630, taken from this page:http://forum.gsmdevelopers.com/htc-firmware-unified/42090-htc-desire-820n-a51-ul-firmware.html
Extremely useful guide: http://forum.gsmdevelopers.com/htc-...t-unrevealed-complete-guide-informations.html