Develop Bugs

[Q] Need to flash firmware and radio

Hey,
I need to flash firmware and radio.
I am on ARHD 7 with PhilZ Touch 6.
Since i upgraded to ARHD 7 i've got very bad radio connectivity.
I've been browsing the forums to search for a firmware and radio file for my modelID and CID. I am unable to find them.
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
Are there any files around that i can use?
I am kinda lost in the process...
Thanks in advance,

I've been thinking of going back to stock to get the latest update and then go back to ARHD! But i need some confirmation on this.
I am learning/reading myself into the getting back to stock procedure using the guide mike refers to in his ARHD post. ( http://forum.xda-developers.com/showthread.php?t=2265618 )
I have to go by the first method i guess, since method 2 and 3 are a no go. Can't find the RUU needed for method 2. And the nandroid backup i had done before flashing custom recovery and rom got deleted once all that worked fine!
So...
I've downloaded the following as mentioned in the guide. ( http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html )
- Download stock odexed 1.54.4015
- Download stock recovery 1.54.401.5
Procedure should be as below, if i am correct.
1. Place (One_M8_1.54.401.5_odexed.zip) file on virtual SDCard.
2. Get (recovery.img) file from Flash_recovery_1.54.401.5.rar and place it in fastboot folder. -- Or should i unrar the whole package and run the batch file as step 4.!?
3. Boot device in recovery, install zip (One_M8_1.54.401.5_odexed.zip) file.
4. Reboot device in bootloader, use cmd <fastboot flash recovery recovery.img>
5. Relock bootloader, use cmd <fastboot oem lock>
6. Reboot device? Get updates etc...

Any feedback please...? I am kinda worried I **** things up!

Above worked, no OTA though... Kept searching for updates, unlocked bootloader tried again and said there are no updates available.
So dumb that i've deleted the stock nandroid backup!
Guess i'll never really find out what version I originally had.

[Q] Broken recovery HTC M8 (Devil's Loop)

Hei guys I managed to **** up my HTC M8 pretty bad (I think..)
I had a rooted M8 with 4.4.4 so 5.0.2 came out a few days ago and I tried to update my phone today. To do so I wanted to unroot my phone so I did the following things:
1. I did a factory reset using the option in Clockworkmod
2. I flashed the stock recovery to my phone
3. I (re)locked my bootloader
The problem is something seems to be wrong with the flashed recovery, Factory Resetting or booting into recovery just restarts the phone and the OTA also just reboots the phone. Unlocking the bootloader and CHECK SMARTSD also won't work anymore..
I really don't know what to do now/where to ask for help..
Here is some information I can provide:
Bootloader looks like this:
*** Software status: Modified ***
*** Relocked ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.000
RADIO-1.22.21331147A1.29G
OpenDSP-v46.2.2-00564-M8974_F0.0811
OS-3.28.401.9
eMMC-boot 2048MB
Getvar All (Toolkit) gives me this:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT46PWM01039
(bootloader) imei: 357871053519784
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.010s
I really don't know hat to do now..
Hope you can help me, thanks for reading.

Unrooting and relocking the bootloader was a useless move. OTA accepts rooted phones and with bootloader unlocked. OTA needs a stock recovery and a clean system.
What you can do is flash via adb TWRP and restore a working backup of your firmware.
P.S. Delete your IMEI and SERIAL NUMBER from your post.

Sensor_hub ... Damaged ... Any solution ?

Hi guys, i screwed up .... Was trying to go back to STOCK version and i think i screwed up the sensors --> Auto-Rotate doesn't work, Flashlight too, take 2 seconds to show the screen if it was off --> (by clicking the power button), double tap doesn't work too.
So i tried to go to stock, erase everything etc .... Nothing is working. Any help ? Please ...

Hello,
I would like to help, but you must provide much more details about what happened. How did you go about getting back to stock? From which rom? to which rom? Can you do a "get var all"?
Cheers

The "getvar all" as requested :
(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) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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
all: Done!
finished. total time: 0.007s
bootloader screen :
*** Software status: Official ***
*** RELOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12.G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:28.0
and i don't really remember from which rom to which rom... Sorry...

Excellent, you're on the international version. However, your post includes some private information (unique identifiers) that -for your privacy and safety - shouldn't be posted. Please, either delete your post, or edit it to remove the serial number and imei.
Many people have complaints about the latest update to marshmallow, with similar system problems. For example, sensors not working properly, camera malfunction, screen malfunction, inaccessible internal & external memories, and or, sudden death
My proposed solution is simple: RE-flash your firmware & rom from stock source, then hardreset your phone to factory condition.
Cheers.
BloodyMoon95 said:
The "getvar all" as requested :
(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) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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
all: Done!
finished. total time: 0.007s
bootloader screen :
*** Software status: Official ***
*** RELOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12.G
OpenDSP-v51.2.2-00593-M8974_F0.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015, 14:15:28.0
and i don't really remember from which rom to which rom... Sorry...
Click to expand...
Click to collapse

Edited the message. Ok, your solution seems feasible. But could you guide me in every step of it? I think i am always messing up a step without realizing it.

BloodyMoon95 said:
Edited the message. Ok, your solution seems feasible. But could you guide me in every step of it? I think i am always messing up a step without realizing it.
Click to expand...
Click to collapse
Following is a link to HTC's official stock RUU, and instructions to flash it. This will install your phone's current firmware/software from scratch.
https://www.androidfilehost.com/?fid=24369303960687057
To flash the RUU zip file:
A. You need to put it at the root of your SD CARD and rename it to 0P6BIMG.zip (first character is a zero, and careful not to rename it to 0P6BIMG.zip.zip)
B. Turn your phone off, then start it into bootloader. It will recognize the 0P6BIMG.zip file and give you instructions in RED for proceeding forward.
C. Follow the instructions in RED to flash. You will lose all data as the RUU will format all partitions.
Cheers

shirreer posted the best way to flash it, so I'm just gonna add here, I bought a GSM M8, originally an Australian variant (0P6B11000) and I S-OFF'd it and converted it to the Intl version with 6.12.401.4 and it's very stable, everything works fine, including double tap, flashlight, auto rotate and all other features. Only thing that sucks is the extremely horrible battery life, which was somewhat fixed with a re-calibration, but it still drains.

Ok i am gonna trying it AGAIN actually. Already done your solution. Last time i have done this, it was bypassing the sensor_hub, which is super weird. But i'll let you know. Downloading it right now, and going to flash it soon.
Edit After Flashing :
Sensor_hub; TP (2); SBL1 (3) are bypassed....

So yea... still same situation i flashed it as you said and explained. Sensor hub is bypassed. I hard reset as you said. Nothing changed... So basically .... i am screwed ....

No one has an answer for me ?..... Come on guys .... there must be something .... FYI bluetooth not working i think.

Where to get latest firmware.zip for htc one m8

I have an htc one m8 ATT phone I want to install the ViperOneM8 5.02 rom on which says I need to update the firmware to a marshmellow firmware I think.
Or the latest.
While I have found some documentation how to do this on the net, I am not sure where I obtain these files.
The firmware.zip I believe it is
Help on this would be appreciated
Right now I am using hboot 3.16 and twrp 2.7

I found this link
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
https://www.androidfilehost.com/?w=files&flid=32780
and grabbed the 4.16.1540.8.zip but want to make sure I am grabbing the correct and latest version. Because I don't want to brick my phone

Post your fastboot getvar all result without serial & imei no.
You may need a different firmware if it's AT&T & S-On and also don't use that outdated 2.7 TWRP.

ckpv5 said:
Post your fastboot getvar all result without serial & imei no.
You may need a different firmware if it's AT&T & S-On and also don't use that outdated 2.7 TWRP.
Click to expand...
Click to collapse
For some devices, TWRP 2.7 is recommended due to how older boot loaders may not take it well.
I like TWRP. When its workable, its array of tools is superior to CWM. But after I tried 2.8.x, I decided CWM or TWRP at or below 2.7.0.2 is safer and less crash prone.
When I attempted to boot to recovery it would boot loop. Please be mindful of boot signing. If you so slightly make your OEM software notice things a fuse will make your phone implode.
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?

furboom1240 said:
For some devices, TWRP 2.7 is recommended due to how older boot loaders may not take it well.
Click to expand...
Click to collapse
Read again what he is trying to do man ... he's going to update to Marshmallow firmware and that outdated TWRP 2.7 won't work for him (he can't even install his intended ViperOneM8 5.02 ROM with that outdated TWRP)
..... that's why I said don't use that outdated TWRP

ckpv5 said:
Read again what he is trying to do man ... he's going to update to Marshmallow firmware and that outdated TWRP 2.7 won't work for him (he can't even install his intended ViperOneM8 5.02 ROM with that outdated TWRP)
..... that's why I said don't use that outdated TWRP
Click to expand...
Click to collapse
Good point. For some odd reason CM pairs ROMs and Recoveries. If you check the Dev Auto update option would that be unnecessary.
It's been an itching question I actually had...
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?

I originally had twrp 2.8 on and tried to install the latest. But it was freezing because I think I need a newer version of hboot. which I have 3.16 on it.
I then downgraded to 2.7 to get it working. I installed ViperOnem8 Rom not reading the website successfully. but have issues with wifi, and 2 minute boot times.
"The 5.0.x ROM is based on HTC’s latest M8 Sense 7 Android 6.0.x base and requires you to update your firmware to at least the 6.0.x (Marshmallow) version! If you don’t you will run into some issues such as Wi-Fi not working or No Boot, etc.
We cannot install the firmware for you during ROM installation so you will need to take the steps to update the firmware on your own."
So I need to update my firmware. I have an ATT S-ON phone. But I have no clue where to get the firmware from, and make sure it is the right one and recent.
I need to update my firmware in order for this rom and a newer version of twrp to work correctly

ok, so
I upgraded to 3.11.1700.5 firmware I found. and that was successful.
Then I upgraded my twrp to twrp-3.0.2-0-m8 and that was successful
Now I am trying to install either Revolution Rom, or ViperOnem8 and both have the same problem. After install they keep booting into twrp and won't load.
I tried Cynamod and that installed and booted fine.
I believe both Revolution and Viper use the Aroma installer. Anyone know what is going on with these and a fix to stop it from booting into twrp?

Need advice
ckpv5 said:
Post your fastboot getvar all result without serial & imei no.
You may need a different firmware if it's AT&T & S-On and also don't use that outdated 2.7 TWRP.
Click to expand...
Click to collapse
This my phone info
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21331147A1.14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.34.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(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: 260ae94e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Which RUU can I use ?

vertigo262 said:
ok, so
I upgraded to 3.11.1700.5 firmware I found. and that was successful.
Then I upgraded my twrp to twrp-3.0.2-0-m8 and that was successful
I believe both Revolution and Viper use the Aroma installer. Anyone know what is going on with these and a fix to stop it from booting into twrp?
Click to expand...
Click to collapse
Wrong firmware. You installed an old version of GPE firmware.
You can't install Sense ROM like Revolution and Viper on GPE firmware.
I asked you to post fastboot getvar all to help you but it seems that you made it harder now because you installed a wrong firmware. If it is S-Off, then it is easy to fix.

ckpv5 said:
Wrong firmware. You installed an old version of GPE firmware.
You can't install Sense ROM like Revolution and Viper on GPE firmware.
I asked you to post fastboot getvar all to help you but it seems that you made it harder now because you installed a wrong firmware. If it is S-Off, then it is easy to fix.
Click to expand...
Click to collapse
sorry, I must have missed your response. was in phone hell world!
here it is.
this is what it was
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
this is now
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

vertigo262 said:
sorry, I must have missed your response. was in phone hell world!
here it is.
this is what it was
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
this is now
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First - remove all serial & imei no. from your above post.
As I said, it is not easy to fix this with S-On device. What you can try is to install the latest AT&T 6.20.502.5 firmware first then run 6.20.502.5 RUU
Read this for the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
You can get the RUU here : http://www.htc.com/us/support/htc-one-m8-att/news/

ckpv5 said:
First - remove all serial & imei no. from your above post.
As I said, it is not easy to fix this with S-On device. What you can try is to install the latest AT&T 6.20.502.5 firmware first then run 6.20.502.5 RUU
Read this for the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
You can get the RUU here : http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse
so your saying, install the ruu, update the firmware, then re install viper?
Can't I just update the firmware like I did before? It was S-On before I updated the firmware

The ruu won't install. it says needs more then 30% battery, yet it is fully charged

vertigo262 said:
so your saying, install the ruu, update the firmware, then re install viper?
Click to expand...
Click to collapse
No .. I don't say that ... read again ...
Flash firmware.zip first then RUU ...
or install ROM first, don't reboot the system, but reboot to bootloader, relock bootloader then flash firmware.zip
As you already flashed a wrong firmware, as I said this may work and may not work but the only way that you can try to fix the wrong firmware installed.
---------- Post added at 02:49 PM ---------- Previous post was at 02:49 PM ----------
vertigo262 said:
The ruu won't install. it says needs more then 30% battery, yet it is fully charged
Click to expand...
Click to collapse
Because you have wrong firmware installed.

but with what firmware.zip? I never got the right firmware.zip to begin with so I don't have any firmware files to update with

vertigo262 said:
but with what firmware.zip? I never got the right firmware.zip to begin with so I don't have any firmware files to update with
Click to expand...
Click to collapse
That show you don't read all the posts that I posted .. the firmware.zip is posted in the post that earlier posted
You have to wait for someone else I guess who can write a post that you can understand .. maybe my English is not good enough ... good luck
ckpv5 said:
First - remove all serial & imei no. from your above post.
As I said, it is not easy to fix this with S-On device. What you can try is to install the latest AT&T 6.20.502.5 firmware first then run 6.20.502.5 RUU
Read this for the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
You can get the RUU here : http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse

ok .. now that I understand what you are saying. because you had the RUU .exe and also were explaining how to update the firmware at the same time while the firmware was burried a couple of levels of posts, I didn't understand what you were saying.
so it looks like the firmware updated successfully
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I unlocked the firmware through the htc website with the Unlock_code.bin
because fastbook oem unlock didn't work.
had to reinstall twrp and that worked after reinstall. although lots of mounting file system errors. with /Data I don't know if that's normal.
seems to be fixed after formatting
Now I will try installing a rom

vertigo262 said:
had to reinstall twrp and that worked after reinstall. although lots of mounting file system errors. with /Data I don't know if that's normal.
seems to be fixed after formatting
Now I will try installing a rom
Click to expand...
Click to collapse
Now you got it.
And yes, after changing from GPE to Sense GSM (AT&T) firmware, you need to reinstall TWRP (the latest 3.0.2-0) and you MUST format data partition, in TWRP - select WIPE, Format Data - yes ... because GPE & Sense data partition is of different size.

Please where can i get compatible firmware for my htc one m8s with S.O 1.12.1405.6 . I have been on this over 3 weeks now but all no avail.

[Help] My HTC one M8 has no OS.

I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
The bootloader screen displays the following
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Nov 27 2015,01:21:29.0
fastboot getval all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
And I have TWRP v2.7.0.2 on recovery.
I am at my wits end on this, so any help would be greatly appreciated.

Since it appears you are using the US unlocked version, why not use the Windows RUU to restore it? I don't have the link handy, but you can download it from HTC. Just put your device into download mode and go. It will blow away your recovery, but that's easy enough to restore.

jshamlet said:
Since it appears you are using the US unlocked version, why not use the Windows RUU to restore it? I don't have the link handy, but you can download it from HTC. Just put your device into download mode and go. It will blow away your recovery, but that's easy enough to restore.
Click to expand...
Click to collapse
I forgot to mention I tried that, and it errored out near the end. I think I may have managed to fix it by loading the rom from Insert-coin onto an SD card, and mounted it and installed through TWRP.
Its currently optimizing apps, so I think I should be home free at this point.
I feel kinda dumb by asking for help then figuring it out myself not long after, but it happens sometimes.

Voidablemelon said:
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
The bootloader screen displays the following
*** Software status: Modified ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.24_2G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Nov 27 2015,01:21:29.0
fastboot getval all returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
And I have TWRP v2.7.0.2 on recovery.
I am at my wits end on this, so any help would be greatly appreciated.
Click to expand...
Click to collapse
Your "OS" and version-main are blank because there was a bug in the TWRP version you are using.
Update to TWRP v2.8.7.0 or newer, reflash your current firmware or update it if you haven't already, and your OS and version-main will show the version of firmware you are running again.

Voidablemelon said:
I forgot to mention I tried that, and it errored out near the end. I think I may have managed to fix it by loading the rom from Insert-coin onto an SD card, and mounted it and installed through TWRP.
Its currently optimizing apps, so I think I should be home free at this point.
I feel kinda dumb by asking for help then figuring it out myself not long after, but it happens sometimes.
Click to expand...
Click to collapse
Figuring out yourself is always better than anything else,don't you felt like Einstein or something when you did it yourself w/o any help?

Voidablemelon said:
I forgot to mention I tried that, and it errored out near the end.
Click to expand...
Click to collapse
If you tell us what RUU (exact file name) and the specific error number and error message, we can probably tell you why the RUU failed.
---------- Post added at 10:39 AM ---------- Previous post was at 10:25 AM ----------
Voidablemelon said:
I may have been an idiot and managed to remove the OS from my phone, and cannot for the life of me figure out how to get it back to working order.
Click to expand...
Click to collapse
Good job figuring it out yourself.
You're not an idiot (common mistake) but here are a few good rules to live by, when modding Android devices:
1) Always make a TWRP backup of your current ROM (and user data, if desired - but that's always a good idea too) and have it handy, so you can recover from such situations (no OS). That is one of the main functions an benefits of having TWRP, the ability to make backups and use them to recover.
If you have a TWRP backup, recovering from "no OS" is simply as booting into TWRP, and restoring the backup.
My typical recommendation, is to make a TWRP backup before root (so you have a backup of the "stock" unrooted ROM) and prior to every time you flash a new ROM, or flash other mods. That way, if any of those mods go wrong, you can still revert back to a "known good" configuration.
2) If you don't have a TWRP backup on hand, know how to flash a ROM to recover from "no OS" (now you know how!)
3) I'm guessing you wiped "system" in TWRP to cause no OS (this the most usual cause)? If so, be careful what you choose to wipe in the "Advanced" wipe options of TWRP. Don't wipe anything, if you don't know what it is, or what the result will be. You've probably already learned this lesson, to some extent.