Develop Bugs

Hi, need some help

Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.

ajg008 said:
Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.
Click to expand...
Click to collapse
Lock your bootloader fastboot oem lock after this run RUU 1.29.401.11 as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back

thanks. Downloading now, will try when i return home from work

Thant said:
Lock your bootloader fastboot oem lock after this run as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
Click to expand...
Click to collapse
thanks for your help that got the phone back to booting properly
I flashed it and it worked. I got myself back to the latest update. Now i tried various roms again as i'm one for experimenting but some of the newest ones dont seem to want to work.
ones i've tried>
Android_Revolution_HD-One_X_33.1
HTC_One_X_-_MaximusHD_21.0.0
OneX The Next Chapter! v1.2
but none of them worked for me.
So i went lower with
cm-10.1.3-endeavoru which worked
then updated to
cm-10.2.0-endeavoru and flashed the boot.img for it to work.
Now for the other roms, what am i missing? is it the firmware.zip? hboot level?
Am bowing down to Thant, and hoping he can tell a mere minion what he's doing wrong

I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......

Mr Hofs said:
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Click to expand...
Click to collapse
the result is:
version-main: 2.17.401.2

What i thought. You need to run another ruu and update many more ota's
Here is the ruu
http://www.persianhtc.net/index.php...Radio_2.1204.135.20_release_274900_signed.exe

Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]h*tp://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
downloading now, but need sleep now and will report back tomorrow.
thanks very much for your help.
bows to Mr Hofs

Same here.

cyanogenmod stable rom not recognising sim, and not being recognised by htc sync
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21

tekkr said:
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
Click to expand...
Click to collapse
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install

Thant said:
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Click to expand...
Click to collapse
the reason i'm so frustrated is aside from the supposedly stable build of cyanogen mod i downloaded in rommanager not working, the rom doesnt recognise my sim, i dont have access to the internet, so i cant simply download a new rom to flash straight from rom manager...as well as this the wifi doesn't seem to work on this flash...and to make matters worse it's not being recognised by the drivers...i'm using htc sync manager..when i plug in the phone it will open htc sync manager but wont show that a phone is paired to my macbook
...when u say manually can i do this directly from my phone or do i need to connect it to a computer?

You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..

big noob said:
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
Click to expand...
Click to collapse
its not being recognised as a device since i flashed the *cyanogen mod stable rom*...i plugged it to my computer though, and put it into fastboot and it says FASTBOOT USB...the options it gives me from here are
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN

Here is guide how to use ADB on macbook:
http://forum.xda-developers.com/showthread.php?t=1917237
And then you can use fastboot commands..

Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]ht*p://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
ive tried that but keep getting signature error

ajg008 said:
ive tried that but keep getting signature error
Click to expand...
Click to collapse
Relocked the bootloader ?

Mr Hofs said:
Relocked the bootloader ?
Click to expand...
Click to collapse
yep fastboot oem lock

Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
http://forum.xda-developers.com/showthread.php?t=1957376

Mr Hofs said:
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
[rl]htp://forum.xda-developers.com/showthread.php?t=1957376[/url]
Click to expand...
Click to collapse
i already had the ota 3.14.401 and got the firmware.zip from there.
its installed fine and i now can put most roms onto it.
:victory: thank you Mr Hofs
So i get this right in my head. The phones firmware.zip needed updated so it would update hboot and other things.
Now to flash roms is the procedure to flash the boot.img contained inside first then install the rom <----which is they way ive being doing it

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

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__038​He 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

Which version is the M8 I bought ? Tampered/compromised phone ?

Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.

Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.

Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.

ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.

Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot

ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.

Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.

You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.

hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip

ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.

I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1

ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same

alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.

ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan

alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999

ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you

alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.

ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........

alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14

[SOLVED] Just restore to stock

SOLVED - THANKS!
Dear community,
Goal: I want to put a HTC One M8 device into stock. The phone used to be unlocked before and had a custom rom (think it was LineAge).
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Please understand, that I am very new to the topic and have read a lot of stuff, tutorials and because of so many different information and missing experience from my side, I am not sure what to do.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(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__203
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s​
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s​
Think because the bootloader is locked?
I have really no clue how to proceed.

gskill150 said:
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Click to expand...
Click to collapse
Probably correct, that mostly likely, you restored the wrong TWRP backup version (not compatible with the firmware on the phone - firmware is not the same thing as the ROM or TWRP backup - that part may be confusing).
What version number TWRP backup did you restore (using the guide)?
gskill150 said:
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s​
Think because the bootloader is locked?
Click to expand...
Click to collapse
Yes, this is because you relocked the bootloader. You can't flash a custom recovery with a locked or relocked bootloader, by definition.
But relocking the bootloader is not part of the guide, in regards to restoring a TWRP backup. What exactly were you trying to accomplish the relocking the bootloader?

I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories. I would try this next. Or what do you recommend?
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Thanks and best regards

gskill150 said:
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
Click to expand...
Click to collapse
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
gskill150 said:
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories.
Click to expand...
Click to collapse
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
gskill150 said:
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Click to expand...
Click to collapse
In short, yes, that is the current version number of the firmware on the phone.
When "firmware" is discussed for this device, it does not refer to the ROM or OS number. But rather, firmware is a small file that is needed for the ROM to work and includes hboot, radio, and a number of other partitions (Bluetooth, WiFI), but does not contain the ROM itself. This is confusing, as some folks like to use the terms "firmware" and "ROM" interchangeably. At least for this device, you should wipe that notion from your mind.
Flashing a custom ROM or restoring a stock TWRP backup will not touch firmware, as flashing a ROM by TWRP will only change the system and boot.img partitions, and not touch things like hboot, radio. And flashing a ROM in TWRP will also not affect the version number reported in getvar. That number will only change if you flash firmware.zip or RUU.
RUU is a complete factory image (40+ partitions) which also includes firmware. Some folks will call the RUU the "stock ROM" but you can now see, it is much more than that.
A little confusing, right?

First of all, many thanks for your detailed help and sorry for providing incomplete information from my side. This topic is really hard to understand and confuses me a lot. Sorry for that.
redpoint73 said:
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
Click to expand...
Click to collapse
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
Click to expand...
Click to collapse
Sorry for that - as written I am new to the topic and was mixing up things that do not belong together (RUU, ROM, firmware). Again in a few words: phone used to have LineAgeOS (CustomRom) and I just wanted get rid of it and restore the original android version as if I had bought the phone completely new
I tried it through TWRP because I found this tutorial here in the forum and thought this would be the right path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
Click to expand...
Click to collapse
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
Click to expand...
Click to collapse
I meant the RUUs from the other guide I have just posted above
A little confusing, right?
Click to expand...
Click to collapse
To be honest, now it is completely clear to me thanks to your really good explanation. Thanks mate!
So I could go for the ruu.zip flashing path to achieve what I want right?

gskill150 said:
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
Click to expand...
Click to collapse
That is the right number stock backup to restore (same number as firmware number - version main in getvar). I don't know why you are having issues with WiFi and Bluetooth.
Might be a problem with the firmware. Flashing RUU is probably the best approach. Not only will it restore the stock ROM, but also restore stock firmware. Which hopefully will resolve your WiFi and Bluetooth issue.
gskill150 said:
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
So I could go for the ruu.zip flashing path to achieve what I want right?
Click to expand...
Click to collapse
That RUU should be okay. Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).

redpoint73 said:
Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
Click to expand...
Click to collapse
Hi, thanks for your reply. I will give it a try! :good:

gskill150 said:
Hi, thanks for your reply. I will give it a try! :good:
Click to expand...
Click to collapse
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!

gskill150 said:
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
Click to expand...
Click to collapse
You're quite welcome. Glad it worked for you.

Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(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.062s

Jjohnson0830 said:
I have tried out diverse RUU but all seems not working...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
Click to expand...
Click to collapse
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.

redpoint73 said:
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
Click to expand...
Click to collapse
Ok, pls where can i get the stock TWRP backup and how am i going to return to stock using it?
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again

Jjohnson0830 said:
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Click to expand...
Click to collapse
No, you really don't. Please.