M9 won't boot ROM(s), only boots to fastboot/bootloader/recovery - One (M9) Q&A, Help & Troubleshooting

Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,

Can you install a custom ROM with S-ON?
I don't think you can ...

andTab said:
Can you install a custom ROM with S-ON?
I don't think you can ...
Click to expand...
Click to collapse
I haven't touched the Android scene since the M7, so it's been a while for me. But if I recall correctly, S-OFF isn't a prerequisite to installing custom roms, as S-OFF is only required to run custom firmware or to run special fastboot commands. Perhaps somethign has changed over the past few years, but I'd be unaware.

Realized the getvar output was clipped:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227xxxxxxxxx
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s

I started my Android experiences with the One S in 2012. Since that time S-OFF has never been needed for custom roms. It's only needed for firmware downgrades, flashing unsigned/unofficial firmware packs or flashing RUUs with a different SKU than your phone was shipped with.
@kikokazuma: It's almost impossible to help you without knowing you firmware version (version-main) since your phone is S-ON.
Edit: Seems like I didn't type fast enough. Maybe you should take a look at the AT&T forum of the M9. They might have a RUU or a TWRP Backup you could use.

Since I am in the same boat with exactly the same results, I don't think it is possible to flash custom ROMs without S-OFF
I have now tried at least 10x flashing CandySix ... same result: Just stuck on the HTC logo (HTC This build is for development purposes only ....)
TWRP (the latest recommended beta version BTW) even says that everything flashes fine ... just no booting to the OS.

Your firmware needs to match the rom base. Many of the latest custom rom versions need a 3.x firmware. Not every SKU already got the Android M update so it's no miracle that some roms don't boot if you use a 2.x firmware like the OP does. This has nothing to do with S-OFF. The only difference for S-OFF users is that they can change their SKU to one that already got the Android M update. But according to Llabtoofer more M9 updates are goint to be distributed during the next week.
Nevertheless every custom rom has an older version that is compatible with the 2.x firmware. For example if you want to flash the Viper rom then you need to use version 3.5. So either wait for the update or look for older versions of the rom you want to flash.
Edit @andTab: In your case it's the other way round.

Flippy498 said:
Your firmware needs to match the rom base. Many of the latest custom rom versions need a 3.x firmware. Not every SKU already got the Android M update so it's no miracle that some roms don't boot if you use a 2.x firmware like the OP does. This has nothing to do with S-OFF. The only difference for S-OFF users is that they can change their SKU to one that already got the Android M update. But according to Llabtoofer more M9 updates are goint to be distributed during the next week.
Nevertheless every custom rom has an older version that is compatible with the 2.x firmware. For example if you want to flash the Viper rom then you need to use version 3.5. So either wait for the update or look for older versions of the rom you want to flash.
Edit @andTab: In your case it's the other way round.
Click to expand...
Click to collapse
The unofficial version DOES support 3.x firmware so that can't be it!
See here: http://forum.xda-developers.com/showpost.php?p=64892501&postcount=249

andTab said:
The unofficial version DOES support 3.x firmware so that can't be it!
See here: http://forum.xda-developers.com/showpost.php?p=64892501&postcount=249
Click to expand...
Click to collapse
And in post #250 someone says that he can't get them to boot. So it's obviously a problem caused by the rom and not the phone. Please go and ask the dev in his thread what to do or just wait until there is official 3.x support. I don't think that it is very polite to hijack kikokazuma's thread with problems that clearly do not belong to the OP's problems.
Edit @kikokazuma: I forgot that HTC US itself provides RUUs for the US carriers. Here's the download link for the RUU you need.

andTab said:
Can you install a custom ROM with S-ON?
I don't think you can ...
Click to expand...
Click to collapse
You definitely can !
I'm still with S-ON and I just installed ViperOne 4.2.1 few days ago.

Flippy498 said:
And in post #250 someone says that he can't get them to boot. So it's obviously a problem caused by the rom and not the phone. Please go and ask the dev in his thread what to do or just wait until there is official 3.x support. I don't think that it is very polite to hijack kikokazuma's thread with problems that clearly do not belong to the OP's problems.
Edit @kikokazuma: I forgot that HTC US itself provides RUUs for the US carriers. Here's the download link for the RUU you need.
Click to expand...
Click to collapse
Gotcha, so basically the newer ROMs require 3.x firmware or higher, and since I'm S-On with 2.x, I can either:
- Pay for Sunshine and load a firmware of my choice, or
- Wait for the official RUU to marshmallow to get the latest firmware, and THEN unlock + load ROM.
Makes sense. Thanks for the help!

You don't need to wait for a Android M RUU. If you use the RUU I linked to get back to stock you can install Android 6 with the update function in settings>about once HTC distributes the update for your SKU. From my experiences OTAs get distributed a bit earlier than RUUs.

Flippy498 said:
You don't need to wait for a Android M RUU. If you use the RUU I linked to get back to stock you can install Android 6 with the update function in settings>about once HTC distributes the update for your SKU. From my experiences OTAs get distributed a bit earlier than RUUs.
Click to expand...
Click to collapse
Would that update also upgrade my firmware so I could then install custom ROMs? I'm not trying to stay on a stock ROM. Just making sure I understand
Thanks again,

Yes it would. Btw: You can already flash custom roms. You only need to look for the Android LP versions of the roms.

Flippy498 said:
Yes it would. Btw: You can already flash custom roms. You only need to look for the Android LP versions of the roms.
Click to expand...
Click to collapse
Oh but who would want LP with all this cutting edge technology around? My bad, I thought my search for Marshmallow was a given!

kikokazuma said:
Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,
Click to expand...
Click to collapse
So after playing around with any possible combination of flashing, here is the fix:
1. Flash the ROM
2. Flash Gapps
3. Flash a Kernel!!!!!!
Without #3, no ROM worked for me on S-ON.
Since most ROM's actually ONLY work with 2.xx you may be better off with it at the moment.
3.xx is the problem, since it requires some fix to get sound to work.

andTab said:
So after playing around with any possible combination of flashing, here is the fix:
1. Flash the ROM
2. Flash Gapps
3. Flash a Kernel!!!!!!
Without #3, no ROM worked for me on S-ON.
Since most ROM's actually ONLY work with 2.xx you may be better off with it at the moment.
3.xx is the problem, since it requires some fix to get sound to work.
Click to expand...
Click to collapse
That only applies to CM roms and it's derivates (or maybe only to CandySix; I don't use Sense-less roms so I'm not completely sure). Sense roms work perfectly fine with the latest firmware.

please help me here. i am now really confused
Elixir_ said:
You definitely can !
I'm still with S-ON and I just installed ViperOne 4.2.1 few days ago.
Click to expand...
Click to collapse
hello i own a htc one m9 with unlocked bootloader, fully rooted with twrp v3.0 which was the only one that worked, fully s-off using sunshine app and supercid 11111111, i have tried to install viperone m9 5.3 on my phone it wipes successfully with twrp recovery but after the installation process i wont boot OS, instead it boots straight to bootloader, i can access recovery and download very well. i have restored backup on my phone inorder to get my phone back. i really need viperone on my phone because i have also tried to install other lower versions of viperone still the same problem all. please help me here i really need help. what am i not doing right here?

Did you ever get this resolved??
kikokazuma said:
Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,
Click to expand...
Click to collapse
I'm having the same issue and I can't even flash the RUU because USB debugging is not on because I wiped with out a backup stupid me I know so any way I'm stuck did you resolve your problem

kikokazuma said:
Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,
Click to expand...
Click to collapse
First you need to install stock rom(with stock recovery,boot,kernel etc) in ur htc and update the mobile using OTA(over the air) updates to marshmallow or higher
Then try installing rom custom rom
Note:- S-off is not required to install custom rom

Related

Marshmallow OTA failed

Hi All,
I'd like a bit of advice/help.
I went to update my phone to Marshmallow OTA and it did it's thing. I left the phone for hours and it appeared to be stuck on android is starting. I restarted the phone and it's now stuck on the HTC splash screen. Recovery options don't work etc.
I've searched around and there are loads of guides but these tend to lean towards rooting. I'm not looking to root but instead looking to get the phone back to factory software that it was originally on.
It's a UK model locked to the 3 network. See below for info taken from the phone.
Thanks in advance.
(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.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH46HWM04949
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can anyone assist? I'm desperate here. I've not had a working phone for days here. The guides I've seen appear to apply to either previously rooted phones or suggest I get the file from the HTC us site but my software versions is newer than those listed.
I have HTC tool kit installed and android studio so any tips would be greatly appreciated.
Thanks.
Is the bootloader UNLOCKED ? or LOCKED or RELOCKED ?
If it is UNLOCKED, I can suggest to restore a non-rooted stock backup.
If it is LOCKED, you can try going to recovery and do data wipe from there (provided that is stock recovery)
and don't use Toolkit .. it brings more harm for less experience user
I've managed to unlock the boot loader. How do restore using a non rooted standard backup? Thanks for replying.
1. You need these files adb/fastboot and HTC USB drivers installed
Read this for the files : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. Read this thread post #1 on How-To restore a backup and install stock recovery
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
3. Install TWRP 3.0.0.1 - https://dl.twrp.me/m8/
4. Download and restore 6.13.771.4 backup (from post #3 from link on no.2)
5. Download and install 6.13.771.4 stock recovery (from post #4 link on no.2)
6. Reboot and see whether it works or not
Thanks for that.
It's now at the stage where the apps have been optimized and it's now just hanging at the "Android is starting..." "Starting Apps...".
This was my original issue I had when the software was updated first time round.
Any clues on how to get past that?
Thanks
Mcbane16 said:
Any clues on how to get past that?
Thanks
Click to expand...
Click to collapse
No clues ... hopefully it's not hardware problem.
What you can try .. restore one version lower, then do OTA becuase OTA will reinstall the firmware.
Restore 4.25.771.6 backup & its recovery.img then check for OTA, download and install.
The downgrade worked and I updated to Marshmallow but for some reason, the phone still hangs on Android is upgrading and starting apps. I'm at a loss as to what to do next. I don't want to use a phone on an old version of software and never upgrade.
So you can boot the lollipop but not Marshmallow ?
I don't know whether you can find htc signed 6.13.771.4 firmware.zip .. this is the only thing I have in mind. Maybe manually flashing the firmware.zip will fix your problem.
I'm already in bed as I will be outstation in the morning. If you can wait, just run the lollipop for the time being. I will give you the firmware.zip on Sunday night (GMT +8) to try to fix it.
Hopefully someone else will be able to help you while I'm not around.
Would changing the CID and MID and selecting a different software package work perhaps?
You only can change CID & MID on a S-Off device.
To S-Off your device you need to pay usd25 for the Sunshine app.
Why don't you try a Marsmallow custom ROM to see whether you can boot it.
If you can at least you can run a Marshmallow ROM until you fix your problem.
I'm signing off now .. goodnight & good luck
Thanks, if anyone else could assist that would be appreciated. I've installed a custom marshmallow rom and all went well but it still suffers with the same fault. It hangs on starting apps. No matter what I do this phone doesn't like Marshmallow!
ckpv5 said:
You only can change CID & MID on a S-Off device.
To S-Off your device you need to pay usd25 for the Sunshine app.
Why don't you try a Marsmallow custom ROM to see whether you can boot it.
If you can at least you can run a Marshmallow ROM until you fix your problem.
I'm signing off now .. goodnight & good luck
Click to expand...
Click to collapse
Hi, I'll wait for your offer of the firmware zip and try that. For some reason this phone doesn't like anything to do with marshmallow.
Mcbane16 said:
Hi, I'll wait for your offer of the firmware zip and try that. For some reason this phone doesn't like anything to do with marshmallow.
Click to expand...
Click to collapse
Sure can .. I get back to you once I'm back from outstation tomorrow evening.
1. Restore the Marshmallow 6.13.771.4 backup if you're on different ROM
2. Download firmware.zip
3. Put your device on bootloader/fastboot mode and put the firmware.zip in your fastboot/adb folder and open a command prompt from this folder
4. Run below commands
fastboot oem lock - to relock your bootloader because your device is S-On
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
You'll see -
if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip
fastboot reboot
check whether your wifi is working now ..
Thanks for that, what I did in the mean time was use the sunshine app to S-Off and change my CID and MID to a deveolper phone. All was fine until the phone upgraded to marshmallow. It still hangs on the Android is upgrading starting apps. It seems no matter what I do this phone will not accept marshmallow.
Any other ideas as to why? So odd why marshmallow doesnt boot past this screen.
Since now your device is S-Off .. instead of updating it to Marshmallow, have you tried running a Marshmallow RUU on it ?
(Assuming your current firmware installed is 6.12.1540.4)
Here is the RUU : http://www.htc.com/us/support/htc-one-m8/news/
If after running the RUU and still the same problem .. I have to say that I'm out of idea.
ckpv5 said:
Since now your device is S-Off .. instead of updating it to Marshmallow, have you tried running a Marshmallow RUU on it ?
(Assuming your current firmware installed is 6.12.1540.4)
Here is the RUU : http://www.htc.com/us/support/htc-one-m8/news/
If after running the RUU and still the same problem .. I have to say that I'm out of idea.
Click to expand...
Click to collapse
I'm downloading one now. I'll update you with the outcome. I'm at a loss as to why this is happening. What does the RRU contain?
It has every images that a device need. Means it removes everything on your device and replace them with new images that come from the RUU.
One thing to note, other that those drivers and HTC USB Drivers that you need (in my previous post), you need a PC with USB2.0
It's currently optimizing apps so we'll see if it boots up. Is there much difference between doing an OTA through all the various updates and going straight via an RRU?
Mcbane16 said:
It's currently optimizing apps so we'll see if it boots up. Is there much difference between doing an OTA through all the various updates and going straight via an RRU?
Click to expand...
Click to collapse
Sadly, it still does the same thing. Would a hardware fault possibly cause this?

HTC One M9 please help me fix Cyanogenmod or restore stock

I have a HTC One M9 from Rogers that I've been trying to flash with Cyanogenmod 13.0. I used the nightly build cm-13.0-20160617-NIGHTLY-himaul.zip
I think the flashing process worked OK but it won't recognize any SIM card. My understanding is that it doesn't have the proper baseband.
I am trying to either load the correct baseband (I haven't been able to find out where to get it) or revert back to Rogers's stock.
My current versions show:
Code:
D:\Cyanogenmod\HTC>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: removed
(bootloader) version-main: 3.38.631.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: ROGER001
all:
finished. total time: 0.013s
I talked to one of the CM guys on this thread.
https://forum.cyanogenmod.org/topic/125939-no-sim-detected/
He said we might need to go back to 3.35 baseband, but I'm not sure what that means exactly. I just got my phone S-OFF and super cid like 10 minutes ago so gonna look around the forums, but if you already know what/how to do, give it a go.
It seems that all custom ROMs are based on the older baseband and I can't figure out how to push an official firmware (I'm not even sure if that would downgrade the baseband)
I tried to flash the M9 radio for 3.35, but it didn't work for me. Not sure if I used the wrong file, flashed it wrong, or I'm just one unlucky idiot.
M9_3.35.617.12_NoWipe_NoRed (Developers/Unlocked) is what I tried to flash. It said that it worked and my device is S-OFF and supercid.
If anyone figures out a zip and flash process that works with CM13, I'm interested.
After many failed attempts I was able to flash back the official 3.38.631.2 firmware from Rogers so at least I have a working phone now.
xoy74 said:
It seems that all custom ROMs are based on the older baseband and I can't figure out how to push an official firmware (I'm not even sure if that would downgrade the baseband)
Click to expand...
Click to collapse
I was going through similar issues. Read this short thread it may help you.
http://forum.xda-developers.com/one-m9/help/rom-38-xx-firmware-canadian-t3405102/page2#post67482568

How to flash ROM to my HK M9?

I went thru a few threads but couldn't find any direct tutorial to flash my m9. I downloaded ota, but i cant s-off my unit(sunshine doesn't work), thus i cant flash it. maybe its running new OS?
I wanted to flash any rom to my m9, either stock or wwe or cyanogenmod, but all seems to require s-off.
my play store is missing & even though i did a master reset(tried from normal menu n also bootloader mode), playstore just wont appear.
here are my details :
Non-rooted
S-ON
LK-1.0.0.0000
firmware 3.42.708.3
fastboot result :
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: Mod Edit: Removed
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
I went thru about 5 threads but cant find a direct solution, I hope I'm not asking something that is widely posted here, seems i just can't S-off. Any helps to flash roms in my situation?
Anyone care to help out?
There is no other publicly available RUU for your SKU than a 1.32.708.15 one which you can't use due to downgrades not being possible without S-OFF.
Taken from my sticky thread in the general section:
Flippy498 said:
Llabtoofer's RUU Service
he can help you out if there is no freely available RUU for your phone​
Click to expand...
Click to collapse
dear flippy, can i install custom rom while its S-ON? I know how 2 do it on prev HTCs(unlock bootloader, flash recovery, flash rom, flash boot.img), but no sure if m9 is applicable..
Yes, you can. However you need to re-flash the stock boot.img of your phone afterwards or you'll loose your mobile reception (this only applies to sense-based roms). If you want to use a non-sense-based rom like cm you need to flash thicklizard's mono kernel instead of the stock boot image.
Sent from my HTC One M9 using XDA Labs

Help, my Htc one m9 is bricked from relocking the bootloader.

Hi, I am new on this forum.
I have a problem with my M9. About a year ago, I installed TWRP recovery and rooted android 6.0. Since then I hadn't made any changes to my phone. Once android nougat came out, i couldn't update it with ota update so i decided to return to stock recovery. I flashed the recovery and everything worked fine. I decided to update it with a RUU as the safest bet, and i read somewhere that you need to relock the bootloader. I relocked it and everything seemed fine, it was relocked in bootloader mode but now I can't boot to recovery mode and cannot boot the phone. I can access download mode and bootloader mode. I also can't update it with the ruu because I get signature error 132. I also can't unlock the bootloader, everything goes fine and at the end it still says "relocked". My cid is htc_032 european. What should I do now?
Razor2211 said:
Hi, I am new on this forum.
I have a problem with my M9. About a year ago, I installed TWRP recovery and rooted android 6.0. Since then I hadn't made any changes to my phone. Once android nougat came out, i couldn't update it with ota update so i decided to return to stock recovery. I flashed the recovery and everything worked fine. I decided to update it with a RUU as the safest bet, and i read somewhere that you need to relock the bootloader. I relocked it and everything seemed fine, it was relocked in bootloader mode but now I can't boot to recovery mode and cannot boot the phone. I can access download mode and bootloader mode. I also can't update it with the ruu because I get signature error 132. I also can't unlock the bootloader, everything goes fine and at the end it still says "relocked". My cid is htc_032 european. What should I do now?
Click to expand...
Click to collapse
You shouldn't have relocked it... As far as I know, relocking the m9 is not required... Try searching for solutions or wait for someone with more knowledge regarding your situation...
Sent from my HTC One M9 using Tapatalk
teddy0209 said:
You shouldn't have relocked it... As far as I know, relocking the m9 is not required... Try searching for solutions or wait for someone with more knowledge regarding your situation...
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I think that I may have been using a wrong RUU, but is can't find the correct one. Since I am s-on, it must be for atleast android 6.0 i think.
Here are my details
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
finished. total time: 0.016s
Razor2211 said:
I think that I may have been using a wrong RUU, but is can't find the correct one. Since I am s-on, it must be for atleast android 6.0 i think.
Here are my details
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: -
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
all:
finished. total time: 0.016s
Click to expand...
Click to collapse
What RUU are you using?
Also, I recommend editing your post to remove your IMEI.
computerslayer said:
What RUU are you using?
Also, I recommend editing your post to remove your IMEI.
Click to expand...
Click to collapse
Thanks for the tip about IMEI.
I tried the developer ruu version from the HTC website but i saw that it isn't compatible. I can't find a ruu for my phone that is compatible. I only found zips, but i have no clue how to use them. I know how to flash them, but my bootloader won't unlock. Do you have any idea how to proceed?
Razor2211 said:
I tried the developer ruu version from the HTC website but i saw that it isn't compatible. I can't find a ruu for my phone that is compatible. I only found zips, but i have no clue how to use them. I know how to flash them, but my bootloader won't unlock. Do you have any idea how to proceed?
Click to expand...
Click to collapse
Read the ReadMe thread and all you questions should be answered since that's what that thread is made for.

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

Categories

Resources