[Q] security warning with OTA update - One (M8) Q&A, Help & Troubleshooting

[Q] security warning with OTA update - One (M8) Q&A, Help & Troubleshooting

Hi all, this is my first post here but I have been reading and searching here for a while.
After weeks of searching and trying different things nows its time to ask for help.
I have recently jumped from iPhones to HTC One M8. Every iPhone I had a Jailbroken and thought I would root my HTC so Ima bit new to all this.
Here's what I've done.
I have a Telstra branded HTC One M8.
After a week I decided to root it, after a lot of reading I Unlocked the Bootloader and installed TWRP, Did a backup straight away with TWRP and then I tried to S-off but firewater said it couldn't be done after 1 chug so I left it s-on.
That night I got the new OTA update so now I have to undo all I have done. I thought I would try the HTC one toolkit by Hasoon and followed the step by step instructions from TheUnlocker site ( can't post links yet)
I used Nandroid: CID TELST001 - 1.12.841.17 and Recovery 1.12.771.17.
All went smoothly and I was back to a stock phone, well AFAIK. I then downloaded and tried to install thew OTA update. Then phone reboots into the bootloader saying security warning under the tampered flag. I have tried unlocking the bootloader again and re-flashing the phone, I have even tried to s-on just in case when I tried to S-off it left something undone.
I'm now at my wits end so I'm asking for help.
Here's what I get when I try to return to S-on
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 0.002s]
finished. total time: 0.003s
D:\Android\toolkit\One_M8_All-In-One_Kit_v\data>
Also I got some error msgs when doing the bootloader (i think).
This is a copy from someone else but its the same error msg
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.170s
I hope someone can help out, I,m sick of the update screen popping up.
Thanks in advance.

Johnsy75 said:
Hi all, this is my first post here but I have been reading and searching here for a while.
After weeks of searching and trying different things nows its time to ask for help.
I have recently jumped from iPhones to HTC One M8. Every iPhone I had a Jailbroken and thought I would root my HTC so Ima bit new to all this.
I hope someone can help out, I,m sick of the update screen popping up.
Thanks in advance.
Click to expand...
Click to collapse
If you failed to get s-off then you are s-on. There is no middle state.
Run "fastboot getvar all" and post the output here please. Remember to hide your sensitive info like imei and serial.

stathis95194 said:
If you failed to get s-off then you are s-on. There is no middle state.
Run "fastboot getvar all" and post the output here please. Remember to hide your sensitive info like imei and serial.
Click to expand...
Click to collapse
Here's what I've got
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********************
(bootloader) imei: ***************
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: TELST001
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
Thanks

Johnsy75 said:
Here's what I've got
Thanks
Click to expand...
Click to collapse
OK good...first of all i'm not sure if you have relocked your bootloader, so if you did please unlock it again.
On stock backups thread i could find a TWRP stock nandroid for your cid but couldn't find a stock recovery so that's a bummer
I have found this:
http://forum.xda-developers.com/showpost.php?p=51906969&postcount=324
It's both stock rom and stock recovery but you will need to flash CWM instead of TWRP.
So to summarize
1. Unlock bootloader (if it's locked)
2. Flash CWM
3. Flash nandroid backup from the link above
4. Flash stock recovery from the link above
5. You will now be able to receive the OTA and upgrade firmware.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
by the way what message did you get from firewater? was it the whelp unfortunately??? i don't know how fast is Telstra releasing OTA's but you might consider s-off to be able to debrand and flash an even newer firmware and rom ie. 2.22.xxx.x
If firewater doesn't work you also have the option of sunshine but you will have to pay $25 for this

4725
stathis95194 said:
OK good...first of all i'm not sure if you have relocked your bootloader, so if you did please unlock it again.
On stock backups thread i could find a TWRP stock nandroid for your cid but couldn't find a stock recovery so that's a bummer
I have found this:
http://forum.xda-developers.com/showpost.php?p=51906969&postcount=324
It's both stock rom and stock recovery but you will need to flash CWM instead of TWRP.
So to summarize
1. Unlock bootloader (if it's locked)
2. Flash CWM
3. Flash nandroid backup from the link above
4. Flash stock recovery from the link above
5. You will now be able to receive the OTA and upgrade firmware.
Click to expand...
Click to collapse
The bootloader is locked, when I look in the bootloader menu I have the "Tampered" & "Relocked" Flags.
As for the recovery, in the tutorial in TheUnlocker he was saying along the lines that if I/you couldn't find a matching recovery for the backup just match the first two numbers of the CID to a recovery, which did work but it must not be "stock" enough for the OTA update.
Thanks for finding that info for me, I will give it a crack a bit later on and I'll post back with the out come.:good:

[/COLOR]by the way what message did you get from firewater? was it the whelp unfortunately??? i don't know how fast is Telstra releasing OTA's but you might consider s-off to be able to debrand and flash an even newer firmware and rom ie. 2.22.xxx.x
If firewater doesn't work you also have the option of sunshine but you will have to pay $25 for this[/QUOTE]
When I tried firewater I got welp on the first bottle. I tried around 8 times then gave up. I read somewhere that if I flash a different rom it might make it easier to S-OFF. But as I said before I'm still a noob to "Rooting" so there's a high chance I could be wrong

Johnsy75 said:
[/COLOR]by the way what message did you get from firewater? was it the whelp unfortunately??? i don't know how fast is Telstra releasing OTA's but you might consider s-off to be able to debrand and flash an even newer firmware and rom ie. 2.22.xxx.x
If firewater doesn't work you also have the option of sunshine but you will have to pay $25 for this
Click to expand...
Click to collapse
When I tried firewater I got welp on the first bottle. I tried around 8 times then gave up. I read somewhere that if I flash a different rom it might make it easier to S-OFF. But as I said before I'm still a noob to "Rooting" so there's a high chance I could be wrong [/QUOTE]
If you got the Whelp no matter how many times you try you cannot get s-off then you are out of luck.
If not, then keep trying because you might still have chances. Seeing that you are on an old base you might still have a chance for s-off without having to pay the $25 for sunshine

After all this time I finally got time to sit down and try the stock ROM and recovery you found. It worked and my HTC is updating as we speak.
It just done a software update and I checked the Android version and its still 4.4.2, software 1.54.841.8. It's D/L another update as I type this.
I'll let you know the outcome.
Once again thanks for your help.:good:

Johnsy75 said:
After all this time I finally got time to sit down and try the stock ROM and recovery you found. It worked and my HTC is updating as we speak.
It just done a software update and I checked the Android version and its still 4.4.2, software 1.54.841.8. It's D/L another update as I type this.
I'll let you know the outcome.
Once again thanks for your help.:good:
Click to expand...
Click to collapse
It's all good.
Version 4.4.3
Software 2.23.841.1

Related

[Q] Bricked M8

Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s

Answer me this quickly, if you have a Vodafone, S-ON, why on God's green earth would you flash a RUU for T-Mobile US?

arnasx69 said:
Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Flash a custom ROM. Put the firmware and gapps on your sdcard.

I think he should just restore his phone to stock ROM after he flashed a custom ROM. If he doesn't know the difference between Vodafone and T-Mobile then I don't know... To make matters worst he knows he has no OS on his device and then he goes to try and lock the bootloader, in the hopes of achieving what?
Put a ROM on a SD card, flash it through custom recovery, download a stock ROM for your device from the Collection thread in General section. Restore the device back to stock and rather leave the flashing until you read up on the basics and get a better understanding of these things before you really mess up mate.

Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.

arnasx69 said:
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
Click to expand...
Click to collapse
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?

RossMacgill said:
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
Click to expand...
Click to collapse
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.

arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.

arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
RossMacgill said:
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
Click to expand...
Click to collapse
Also, your MID (model id) and CID must match the firmware you are flashing since you are not S-off, and therefore not superCID.
In fastboot and hooked up to your PC in ADB, type fastboot getvar all. The output it gives you will tell you your CID and MID(modelid).
Then look for firmware that matches those.
Or get S-off with sunshine (best $25 you will spend on your phone), and go superCID to flash firmware from any carrier.

Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.

Gunman84 said:
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Click to expand...
Click to collapse
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you

also éven if he would try on s-on a T-Mobile RUU von vodafone cid it would never work
if you really don't know how to Flash custom roms etc properly please Keep your phone stock!

If you got the stock Rom working i would go S-Off with Sunshine and go Super CID (11111111) with Sunshine.
Then you can flash what ever Rom you want.

arnasx69 said:
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
Click to expand...
Click to collapse
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom

Gunman84 said:
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Click to expand...
Click to collapse
Actually, CID is Carrier ID, not country identifier.. That's why his says VODAP001 (his carrier being Vodafone) and not his country (whichever of the 21 countries Vodafone is available in)

arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
Click to expand...
Click to collapse
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader

ckpv5 said:
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
Click to expand...
Click to collapse
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks

arnasx69 said:
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
Click to expand...
Click to collapse
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!

One-M8-Master said:
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
Click to expand...
Click to collapse
Not true, not 100 %. Maybe V3 will do that. Keep in mind that the version of sunshine that is now on the market is not working with all the devices.

HTC m8 not starting up correctly. Tried everything i can think of and find.

Hello there!
I have now searched and searched and come upon many great threads in this massive forum however i have yet to find a solution to my current problem. Every time i have went here i have always managed to find something to help me fix my phones over the years but this this time I've hit a wall it seems.
What happened was that my phone started to crash the google apps like gallery etc. No big deal at first but then i decided to do a factory reset thinking that might fix the problem but then my phone just starts up to the HTC logo and throws several different error messages that Google.xxx.xxx could not start/has crashed. IF i click these away they appear after a while again and the phone will be stuck like that.
I can start the phone in fastboot mode to be able to use ADB etc..
The phone is currently bootloader unlocked and with S-on
Now this is what i have done:
First of all the phone wasn't in debugging mode when it crashed so I'm guessing its still not which might complicate the matter further.
* Using a TWRP.img file i managed to get the phone in to the TWRP mode on the phone. (Fastboot boot TWRPfilename.img)
I do not have any TWRP files on my phone nor any apps this was all from the files on the PC. I just mention this because thats the only sign of life the phone has given me so far.
*I tried to go in from the adb shell and enabling it using the following code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
I have no idea as to if it worked or not but the phone rebooted again.
* Tried to reflash with the right RUU for my phone with the right CID thanks to guides on this forum -- i get error 159 (this is because the CID is wrong from what ive read in other threads)
* Tried changing the CID to 11111111 but that did not work i got another error doing that:
C:\adb>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 3
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 0
(bootloader) sdhci_open: id=0
(bootloader) Initializing MMC host data structure and clock!
(bootloader) mmc slot#2 clock enabled
(bootloader) sdhci_set_clock: slot 2, freq 192000000
(bootloader) GPLL0 is enabled
(bootloader) clock_update_cfg_sd is done
(bootloader) sd clock set done
(bootloader) sdhci_set_bus_width: bus width 0
(bootloader) sdhci_clk_supply: freq 400000
(bootloader) Decoded CID fields:
(bootloader) Manufacturer ID: 2
(bootloader) OEM ID: 0x544d
(bootloader) Product Name: SA16G
(bootloader) Product revision: 1.1
(bootloader) Product serial number: 37A24E6D
(bootloader) Manufacturing date: 10 2013
(bootloader) sdhci_clk_supply: freq 50000000
(bootloader) sdhci_set_bus_width: bus width 1
(bootloader) Done initialization of the card
(bootloader) erase_grpsize: -16777216
(bootloader) erase_grpmult: 261077976
(bootloader) wp_grpsize: 0
(bootloader) wp_grpen: 0
(bootloader) perm_wp: 0
(bootloader) temp_wp: 0
(bootloader) [Tuxera][Error] No exFAT partition found
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.132s]
finished. total time: 0.132s
* Tried flashing from a .zip file with the fastboot commands.
ALL of these things I have tried with the bootloader locked and unlocked. (if this is any important info)
The phone ran the 6.12.401.4 version at the moment of the crash and that's what shows in the RUUs ive tried as well. Also the phone is not rooted.
Now is there a way to completely flush the phone out of any info and just reinstalling it like you can do with windows on a PC for example since whatever i try is met by an error message or a failed flash etc..?
some more info about the phone from getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__Y13
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s

1. remove your serial & imei no. on your post
2. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
3. relock bootloader with command -
fastboot oem lock
fastboot reboot-bootloader
4. http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

Thank you for your fast reply!
I have removed the lines from the post as you said and tried your links unfortunately without success. This is why im hoping you like a challange! hehe.
This is the result from the cmd when trying to flash the new RUU:
C:\Users\Genocide\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
I followed your steps 1 by 1 downloaded all needed files and installs etc... Something is terribly wrong with my device it seems.
Any further ideas?

Did you skip no.3 ?
Why it is zipp not zip ?
Try again ..
If still fails, tomorrow I'll give you another method.. already in bed.

oh! ive done goofed!
It was my bad with some **** spelling there.
IT WORKED!!
I thank you sooooo much from the bottom of my heart I was sure my phone was unsaveable for a moment.
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
I'm just curious on how you could spot the problem so that i can learn more about how it works.
Thanks again! Truly great work!

Sambeg said:
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
Click to expand...
Click to collapse
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.

redpoint73 said:
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
Click to expand...
Click to collapse
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
redpoint73 said:
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
Click to expand...
Click to collapse
I think this is where all else failed since all the ones i tried had either the ADB or a file called only Fastboot.exe not this one that said HTC_fastboot.exe
redpoint73 said:
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Click to expand...
Click to collapse
I tried all the solutions in both locked/relocked state just to be sure i had no real understanding of this before but I am now enlighten thanks to you
redpoint73 said:
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
Click to expand...
Click to collapse
Yeah those things are clear for me as well. I just had the problem with the RUU not working for me. Thanks again for all the help and the good information provided even after my problem has been solved

Sambeg said:
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
Click to expand...
Click to collapse
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Only if you are still curious why the RUUs didn't work, of course. I understand its somewhat of a moot (or purely academic) point, now that the phone is working.

redpoint73 said:
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Click to expand...
Click to collapse
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3

Sambeg said:
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Click to expand...
Click to collapse
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
Third RUU: As you know, this isn't for your phone. You can run it a million times, and it will still fail every time; as its intended to fail since the CID and MID on your device doesn't match what the RUU is looking for. The only way to run this RUU is to s-off and change your phone's CID and MID.
Forth RUU: Again, not for your phone. Plus, the Sprint version, which has partition differences from your M8 version (and most other M8 versions). You absolutely should stay away from any Sprint or Verizon firmware, as if they do manage to flash, will often lead to a radio brick on your device.
This would never flash anyway with s-on, and the safeguards of the CID and MID did their job and saved you, in this case.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.

redpoint73 said:
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
Click to expand...
Click to collapse
Yes indeed this cleared up most of my suspicions as well as i said i knew the 3rd and 4th was wrong from the get go it was more of a test..
Thank you for all this good info i feel like im starting to get a good grip on whats good and whats working etc... I really appreciate it! Thumbs up indeed.
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.

Sambeg said:
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Click to expand...
Click to collapse
You can only change the CID (and also MID) with s-off.

redpoint73 said:
You can only change the CID (and also MID) with s-off.
Click to expand...
Click to collapse
Right as I thought then Well thanks again for helping out and clearing up my questions.
I shall now retire from this thread in peace

[SOLVED] Emergency Calls Only (SIM/Radio not working?) [AT&T HTC M8]

Hello, I've been learning how to root my phone and flashing new ROMS. I was having a pleasant time doing it when I made the mistake of possibly flashing the wrong version of GPE to my phone. After that, it seems my phone won't connect to 3G, LTE, or even basic phone service to make calls.
I've been looking for two days trying to find answers on the forum but I couldn't find a straightforward answer to my question. If anyone could help, I would greatly appreciate it. I think my next step is to use SunShine to S-OFF my phone and attempt to install stock firmware, but I'm a bit hesitant after doing something so negative to my phone.
My bootloader has the following information:
Code:
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-
eMMC-boot 2048MB
Mar 4 2016, 18.56.55.0
^ Yes, OS is actually empty. I haven't seen any instances of this on the forums yet...
fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Other steps I've taken:
- Tried SIM card in another phone, it was working fine
- Flash stock ROM and recovery using this thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860. The flashing worked but I still can't connect to AT&T.
- A couple of other miscellaneous things around the forums that didn't really amount to much when I tried them
Again, any help would be greatly appreciated!
EDIT:
SOLVED
I encourage you to read the details to make sure the case matches yours, but TL;DR: no need for S-OFF, simply use lock the bootloader again using "fastboot oem lock" and install the stock RUU. If stock RUU fails make sure you have the correct version. Thanks so much to redpoint73 for their help!

My responses below in red font:
norcrel said:
I made the mistake of possibly flashing the wrong version of GPE to my phone.
What exactly did you flash (exact file name)?
After that, it seems my phone won't connect to 3G, LTE, or even basic phone service to make calls.
I think my next step is to use SunShine to S-OFF my phone and attempt to install stock firmware
You don't need s-off to do that, I don't know why folks keeping thinking that you do. Don't spend the money on sunshine yet (at least, not just to restore to stock).
^ Yes, OS is actually empty. I haven't seen any instances of this on the forums yet...
I've seen this on the forums literally maybe 100 times or more. It means you used a very outdated (over a year old) version of TWRP, which has the known bug of wiping the main version info. What version TWRP did you use? And why?
- Flash stock ROM and recovery using this thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860. The flashing worked but I still can't connect to AT&T.
Which version number did you flash, if you don't know the version number?
Click to expand...
Click to collapse
My suggestion would be to relock the bootloader with fastboot command: fastboot oem lock
(don't worry, you can always unlock it again when the phone is working properly)
Then run the following RUU: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502.2_Radio_4.0.U605611%4050319A_40.45.C33065.00_F_release_446225_signed_2.exe
RUU is a Windows executable program. Just connect the phone to PC, boot into bootloader-fastboot mode, and run the RUU, and it will do the rest (restore all partitions to stock condition).

redpoint73 said:
My suggestion would be to relock the bootloader with fastboot command: fastboot oem lock
(don't worry, you can always unlock it again when the phone is working properly)
Then run the following RUU: http://dl3.htc.com.s3.amazonaws.com/application/RUU_M8_UL_L50_SENSE60_ATT_MR_Cingular_US_4.28.502.2_Radio_4.0.U605611%4050319A_40.45.C33065.00_F_release_446225_signed_2.exe
RUU is a Windows executable program. Just connect the phone to PC, boot into bootloader-fastboot mode, and run the RUU, and it will do the rest (restore all partitions to stock condition).
Click to expand...
Click to collapse
Thanks for the quick response. I used the GPe ROM in this thread: http://forum.xda-developers.com/showthread.php?t=2708589
The file name was HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H13_AROMA-Installer.zip
The TWRP version I used was 3.0.2, the file was named Flashable_TWRP_3.0.2-0_M8.zip and I found it here: https://www.androidfilehost.com/?w=files&flid=49756
Before using 3.0.2 I was using an earlier 2.x.x version. I believe it was 2.7.0.2, because I used the tool in this thread to do my initial unlock: http://forum.xda-developers.com/showthread.php?t=2699065
The stock TWRP backup/recovery version I used was 4.28.502.2, found on this thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 I used TWRP 3.0.2 to perform the backup.
I actually already downloaded the RUU and attempted to use it, but it failed. I didn't perform a 'fastboot oem lock' before trying to use it, however, so I'll try that again when I get the chance and get back to you. Unfortunately at work I don't have a windows PC to run the executable, so I'll have to do it tonight when I get home in a couple of hours from now. Thanks again for taking time to give me advice!

norcrel said:
Thanks for the quick response. I used the GPe ROM in this thread: http://forum.xda-developers.com/showthread.php?t=2708589
The file name was HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H13_AROMA-Installer.zip
Click to expand...
Click to collapse
That version looks fine for use with your phone (not the wrong version, as you mention in your top post). Not sure why you have the SIM issue. Did you do a default wipe (user data, Dalvik, and cache) in TWRP before flashing the ROM? This is recommended.
Also recommended to make a TWRP backup, before wiping and flashing any ROM.
norcrel said:
The TWRP version I used was 3.0.2, the file was named Flashable_TWRP_3.0.2-0_M8.zip and I found it here: https://www.androidfilehost.com/?w=files&flid=49756
Before using 3.0.2 I was using an earlier 2.x.x version. I believe it was 2.7.0.2, because I used the tool in this thread to do my initial unlock: http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
As suspected, it was the 2.7 version TWRP that cause your version-main number to be erased in getvar and bootloader. This doesn't cause any particular issues, except making it harder to determine the firmware number. When you run the RUU, the version number will be restored.
Your main mistake was using the toolkit. As you see from the toolkit thread, it hasn't been updated since April 2014! So it contains a number of obsolete files, that will cause various issues. Its easy to do the steps manually (unlock bootloader, flash TWRP via fastboot, etc.) and use the current files; and I encourage folks to do so, as its a better learning experience.
norcrel said:
I actually already downloaded the RUU and attempted to use it, but it failed. I didn't perform a 'fastboot oem lock' before trying to use it
Click to expand...
Click to collapse
The RUU should work, once you unlock the bootloader. But if it fails again, not the Error number and error message, and post those here.

redpoint73 said:
The RUU should work, once you unlock the bootloader. But if it fails again, not the Error number and error message, and post those here.
Click to expand...
Click to collapse
When I tried to do fastboot oem lock I also got something strange. Here is the log posted below:
Code:
fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Invalid argument))
finished. total time: 1.212s
But afterwards my phone still read *** RELOCKED ***, so I continued on.
I tried the RUU and it failed (error code 155 - unknown) but I realized I was using a different one than the one you posted. I got mine off HTC's webpage, a file named RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5. Downloading your file now and I'll give it another shot.

And it worked! Thank you so much for your help! I'll make some notes on the original post. Am I correct in thinking that I downloaded the wrong version for my stock RUU? How did you know which version to use?

norcrel said:
Am I correct in thinking that I downloaded the wrong version for my stock RUU? How did you know which version to use?
Click to expand...
Click to collapse
Wrong RUU? Yes and no, its a bit complicated.
The RUU you tried is correct, in that its for the AT&T version M8 (right CID and MID). And in the past, running a newer RUU (then the firmware currently on the phone) would have been fine (as long as its intended for your M8 version's CID and MID). But HTC did something new (and a bit strange IMO) with all the Marshmallow RUUs; in that if you try to come from a lower version (LP or KK) you get Error 155. Of course, the description of Error 155 "unknown error" isn't very helpful, and has left lots of folks puzzled. But the solution to running the MM RUU is to first flash the MM firmware manually with fastboot command, then run the RUU again. The process is described in more detail here: http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Or the other option to update to MM, if you actually use AT&T as your provider, is to OTA update from LP to MM (which works fine).
Now how I guessed you were still on LP (and the corresponding RUU) is a bit complicated as well. As you know, your main version was blank, so you can't determine the firmware number that way. You can normally correlate the radio numbers with the firmware version (some RUUs actually include the radio number in the file name, otherwise you just have to know what radio numbers correspond to which OS version). But in your case, the baseband numbers actually didn't match any of the radio numbers known by me, or listed in the RUU file names. So frankly, it was an educated guess. I've assumed that many folks have not yet updated to MM firmware (by official OTA, or otherwise), so I picked the latest version LP RUU.
If my guess was wrong, it would have meant your device was already on MM firmware, and trying to run the LP RUU would similarly give you Error 155, or wrong version number error. In which case, I would have just told you to run the MM RUU (the 6.20.520 you first tried)!
Make sense? Of course not!

htc m8 - bricked while updating ota stock marshmallow

While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(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: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow

pauluthupm said:
I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Click to expand...
Click to collapse
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).

Solved : Unbrick HTC M* - Revert to Stock
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
Thank you for the help. fortunately i did find the solution. just the way u said only. I was in office and dint have access to xda in office. Let me also put what i have done.
pauluthupm said:
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(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: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
Click to expand...
Click to collapse
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Make sure u download the htc fastboot files: Google is ur friend.
Place the image in the same folder as the htc fastboot files are.
rename the file to 0P6BIMG.zip( remember not to add two zips at the end.,windows generally hides the extension
Now open ur command prompt.
naviagate to the htc fastboot folder , i my case, i put in c drive
so it would like c:\htc_fastboot_files
Now Voulme Down Button and then press the power button.
In my case i had to use Power+Volume up to reboot the phone . And the moment it rebooted i pressed just the vol down button.
So we would be in Bootloader. Now switch phone to fastboot mode.
Navigate using volume buttons and power button to enter.
in fast boot mode
bring up ur command prompt:
We are already in the fastboot file folder. like i mentioned before: c:\htc_fastboot_files
type fastboot get var all
look for this info: (bootloader) version-main: 6.12.401.4 ( This might be different case to case, according to this you can search for relevant ruu, just google with the version number firmware)
Now htc_fastboot oem lock ( To relock the bootloader)
htc_fastboot oem rebootRUU
htc_fastboot flash zip Firmware_xx.zip ( in my case its 0P6BIMG.zip)
Once the flash completes, you will have a window which says Flash complete. OKAY. Mind you it takes some time.
After this,
htc_fastboot reboot . Thats it. Phone will take quite some time to reboot and complete the process.
My phone was up and running from here. But in case of errors. You might want look down.
IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (don’t use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot (below this section you find CRITICAL errors, please observe):
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 24 android-info fail (means something wrong with android-info.txt in the zip)
- 32 header error (means the zip couldn't be read and unzipped properly)
- 41 Wrong Model ID (means it's not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap CID first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot in-between).
- 99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues.
- 130 wrong model ID (seems it's the same like 41, just that it shows in the FUU as 130.
- 155 seems to indicate different things. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match.
- 170 Check USB - FUU won’t run because of not working ADB.
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 24 "android-info fail" do:
- check that your ZIP isn’t some HTC OTA or anything thats got no android-info.txt - those cannot be flashed with fastboot flash zip nameof.zip command.
- check that your zip has a good MD5 and is not broken, check android-info.txt etc...
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn't help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
htc_fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
htc_fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn't brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definitely this means the ZIP is not signed - get an unmodified zip!
For “Error 130 wrong model ID" do:
- Please refer to Error Code 41/42.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn't work well currently.
NOT safe to reboot / Flash (partly) happened Errors (if you encounter one of them, DON’T reboot:
- 152 Image Error - Phone Screen shows a little triangle beside a full green bar
For “Error 152 Image Error" do:
- Error 152 is quite rare, have seen it only once with a friend’s phone and it aborted the flash nearly at the end. The flash was started by the FUU. We could resolve the matter by NOT rebooting the phone and flashing the zip again through a manual fastboot flash as outlined further up.

pauluthupm said:
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).

redpoint73 said:
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
Click to expand...
Click to collapse
Yep. That's straight up stolen (copy/pasted) from @Sneakyghost's threads.
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again

xunholyx said:
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
Click to expand...
Click to collapse
Yeah, hard to tell what OP is talking about, if they don't even get the name right.
Also completely unnecessary of him to clutter up the board by copy and pasting huge amounts of text when a link can be provided (or refer to a thread, if he can't link).

NEW HTC m8 on custom recovery
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
--------------------------------------------------------------
Hi redpoint, need your help.
i want to revert my htc m8 to stock marshmallow. i am currently running ,mi ui with twrp recovery.
i am posting getvar results below. i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? can u help me with which firm ware i should download and which stock recovery should i install ?
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

pauluthupm said:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
What's going on here, is this a different phone than what you listed in the first post?
pauluthupm said:
i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Click to expand...
Click to collapse
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
pauluthupm said:
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? 0
Click to expand...
Click to collapse
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.

m8 revert to stock
redpoint73 said:
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
Click to expand...
Click to collapse
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
My device id belongs to India when i googled hence i m searching for these ruu. I wanted to try sunshine s off so that change the mid and cid to eu version and then try different ruu. Sunshine keeps giving me an error while running the initial tests it requires an non debuggable boot.img. So that doesnt help either.
do you require anymore info ? i can give u remote access if it requires.
PS: MIUI Rom is still working if i want to use my phone

pauluthupm said:
do you require anymore info ? i can give u remote access if it requires.
Click to expand...
Click to collapse
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).

redpoint73 said:
You didn't even provide any of the info I requested in my last post.
I had answered to your questions right below it. Did u mean i dint answer with details?
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
i have No clue how i found it. I googled lot of pages and somehow i found this this link. butyes i downloaded it from http://forum.gsmhosting.com/vbb/f48...-ruu-4-x-x-6-x-x-updated-19-3-2016-a-1940130/
I am not sure its signed or not. to be honest i have no clue.

answers to what you had asked?
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
Originally Posted by redpoint73
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.

pauluthupm said:
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery.
Click to expand...
Click to collapse
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
pauluthupm said:
Now i tried flashing that ruu downloaded from gsm developers. but i failed with it.
Click to expand...
Click to collapse
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
How big is the file (MB)?
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
pauluthupm said:
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
Click to expand...
Click to collapse
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.720.xx specifically refer to your version M8 (CID and MID).
EDIT: fixed a typo, the number in red in the last line should read 720.

redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
redpoint73 said:
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
HTML:
[QUOTE]Yes i renamed it to 0P6BIMG.zip
[/QUOTE]
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
remote: 12 signature verify fail)
Execution time is 115(s)
Click to expand...
Click to collapse
How big is the file (MB)?
1.66 GB
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.709.xx specifically refer to your version M8 (CID and MID).
Click to expand...
Click to collapse
Can you help me with the link i should download ? the correct ruu for my m8 ?
i can post the getvar values here if its of any help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

pauluthupm said:
Yes i renamed it to 0P6BIMG.zip
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
Click to expand...
Click to collapse
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?

redpoint73 said:
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Bootloader is currently unlocked. Since you said i can run ruu in custom recovery also. I went and reinstalled custom recovery twrp 2.7 from Hasoons All in one Kit.
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
Click to expand...
Click to collapse
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.

pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
Click to expand...
Click to collapse
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
htc_fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR

pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
Click to expand...
Click to collapse
pauluthupm said:
Being very honest, i have very little knowledge, its a new learning for me.
Click to expand...
Click to collapse
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
pauluthupm said:
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Click to expand...
Click to collapse
It won't work. You need version numbers with 720, not 709.
I see in my last post, I said you needed 720 (which is correct) then a typo which implies you need 709 (not correct). So there may have been some confusion or conflicting info there.
Also, that version is too old (software number 1.54). You can only run RUU with equal or greater version than the firmware on the phone, which in your case is 4.xx.
pauluthupm said:
]
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
Click to expand...
Click to collapse
RELOCKED is the important part. Not sure why you got in error , but it looks to be properly relocked to run RUU.
Was it RELOCKED or UNLOCKED when you tried the RUU 6.20.709.2 and got Error 12: Signature Error?

redpoint73 said:
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
I should have. Now i regret for messing up the phone
Click to expand...
Click to collapse
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Absolutely learned it. I wouldnt want mod any phones anymore. Too much of headache, since am i am noob.
Click to expand...
Click to collapse
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
Click to expand...
Click to collapse
In fact i did have twrp back up. bt i had kept this sd card in my wallet. I broke the sd card by mistake. thats how i lost it.

OP cannot install RUU 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2 on his current firmware version.
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038He needs to install the signed 6.15.720.2 firmware first before install the RUU zip
Easier method is - install RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe
Download from : http://androidruu.com/?developer=M8
then OTA to 4.18.720.10 then later to 6.15.720.2
Or restore 4.18.720.10 backup & install 4.18.720.10 stock recovery (yeah .. skip a version) then OTA to 6.15.720.2
Download from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck

Need Help with HTC m8 Demo Unit Stock Rom - Wants to Flash Custom ROM

Hey everyone!
I just got HTC M8 from a friend, and figured out it is a demo unit. It comes with a demo app, which I am unable to get rid off. It was firstly rooted and mistakenly I removed the internal storage. After all the mayhem, researching for hours on this forum, I am finally able to get my device back running but still the demo app is there. I am unable to make any changes in developer options or through control center. I am new to all modding, HTC, Android and custom / stock roms.
I have few questions after reading a lot. After accidentally deleting the OS, and wiping internal memory - I was able to get it back, but now wants to run a custom ROM on it but not sure if I am able to do it with current status of my device.
Information about device:
HBoot: 3.16.000
S-ON
HTC__002
Unlocked Bootloader
TWRP installed (but throws error whenever I try flashing a zip file)
The question: Can I install a custom rom without getting S-OFF and if yes, which custom ROM can I use on my device? I understand there is some limitation to HBoot version, but I am unable to figure out how to update it to latest version. I would like to update my device from Android Kitkat to Marshmallow or some custom ROM which doesn't have a demo app.
P.S: A noob!
Update:
After reading lots of threads, I finally bought Sunshine license and activated S-OFF, now, I am with SuperCID 11111111 on my demo unit. Now, I want know about which Custom ROM I can run, and how can I update my Hboot to latest version?

You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
If you still need help contact me on :
[email protected]

HamzaSheikh said:
[*]HBoot: 3.16.000
[*]TWRP installed (but throws error whenever I try flashing a zip file)
Click to expand...
Click to collapse
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
Hero_elmehrik22 said:
You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
Click to expand...
Click to collapse
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.

Yes, Hboot version is too old. I had a long fight with getting it restored. I had to try every other TWRP version and suddenly TWRP 2.8.0.0 worked for me!
Here is the output from getvar all:
Hamzas-iMac:~ hamza$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.203s
Click to expand...
Click to collapse
Problem I face:
- Current TWRP is old, I am unable to make most out of it. (v2.8.0.0)
- Hboot is like hanging in stone age, I need to update it - but I have a demo unit (it comes with annoying demo app!)
- I want to run Custom ROM or at least a newer Android version.
redpoint73 said:
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.
Click to expand...
Click to collapse

You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.

Thanks @redpoint73 for the help. Here is an update:
I finally able to get rid of demo app using SuperCID - means, now I have S-OFF device. I used Sunshine apk. Now I would like to update my device to latest Android (Marshmallow) - so should I follow the instructions on the thread you pointed me or is there something else I can try instead of locking the bootloader again?
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse

Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse

HamzaSheikh said:
Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
Click to expand...
Click to collapse
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.

Lots of love man! I finally got it. It worked like a charm through HTC_fastboot.exe. I was on macOS earlier and tried flashing ruu.zip through it, but after your message. I tried on Windows with HTC fastboot and wow!
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Latest Getvar All:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Anything else I should be doing to make it work awesome and fast?
ckpv5 said:
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.
Click to expand...
Click to collapse

HamzaSheikh said:
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Click to expand...
Click to collapse
Honest mistake. Relocking the bootloader is mandatory to run an RUU with s-on. So it's easy to miss the fact that the requirement (to relock the bootloader to RUU) is bypassed with s-off.
As you said, you can always unlock the bootloader again, if you want to install custom recovery, root, flash custom ROM, etc. Alternately, if you want to stay stock with no root, you can just leave it relocked.
HamzaSheikh said:
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Click to expand...
Click to collapse
You're very welcome. I wasn't sure if you wanted to pay for sunshine, so that is why I was suggesting some possible solutions with s-on. But glad to have pointed you in the right direction, regardless.
HamzaSheikh said:
Thanks [MENTION=830797]
Anything else I should be doing to make it work awesome and fast?
Click to expand...
Click to collapse
That is a very open-ended and subjective question. It's completely up to your preference, if you want to do any more mods. You can try custom ROMs, root, custom kernels, and much more. There really isn't much limit on what you can try.

Develop Bugs

welcome