Develop Bugs

[Q] Unable to flash firmware

So I've just picked up myself a HTC One M8 on Optus in Australia, first thing I did was install TWRP and root the phone, only to discover that there was then OTA updates to install, so I installed a stock recovery that I downloaded from here, ran the process to get the OTA update and it started but displayed no progress on the screen, just a HTC logo that remained there for at least 20 mins, so I rebooted the phone, this time the logo only stayed up for about 4 mins, the device rebooted and it was updated. The only problem was that it looks like the firmware hadn't installed/crashed/shouldn't have been rebooted and I had no wifi (Whenever I tried turning it on it remained off and no networks were shown) so I'm assuming the firmware update failed when it either crashed or I got too impatient (20 mins isn't impatient is it?).
I tried putting the firmware.zip from the OTA install onto an SD as 0P6BIMG.zip which gave an error:
Loading [0P6BIMG.zip]
Checking
Wrong zipped image!
When trying to flash with fastboot I get:
fastboot flash zip firmware.zip
target reported max download size of 1778626560 bytes
sending 'zip' (50763 KB)...
OKAY [ 2.194s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.454s
Any idea how I can flash this stock firmware to the device?
Edit: Firmware I'm trying to upload is here in case it assists: http://www.fast-files.com/getfile.aspx?file=77675

acecombat said:
So I've just picked up myself a HTC One M8 on Optus in Australia, first thing I did was install TWRP and root the phone, only to discover that there was then OTA updates to install, so I installed a stock recovery that I downloaded from here, ran the process to get the OTA update and it started but displayed no progress on the screen, just a HTC logo that remained there for at least 20 mins, so I rebooted the phone, this time the logo only stayed up for about 4 mins, the device rebooted and it was updated. The only problem was that it looks like the firmware hadn't installed/crashed/shouldn't have been rebooted and I had no wifi (Whenever I tried turning it on it remained off and no networks were shown) so I'm assuming the firmware update failed when it either crashed or I got too impatient (20 mins isn't impatient is it?).
I tried putting the firmware.zip from the OTA install onto an SD as 0P6BIMG.zip which gave an error:
Loading [0P6BIMG.zip]
Checking
Wrong zipped image!
When trying to flash with fastboot I get:
fastboot flash zip firmware.zip
target reported max download size of 1778626560 bytes
sending 'zip' (50763 KB)...
OKAY [ 2.194s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.454s
Any idea how I can flash this stock firmware to the device?
Edit: Firmware I'm trying to upload is here in case it assists: http://www.fast-files.com/getfile.aspx?file=77675
Click to expand...
Click to collapse
First of all, I assume you are trying to flash the firmware in rebootRUU mode right? or else it will fail
Second can you post the outcome of "fastboot getvar all" hiding first all the sensitive info like imei.

stathis95194 said:
First of all, I assume you are trying to flash the firmware in rebootRUU mode right? or else it will fail
Second can you post the outcome of "fastboot getvar all" hiding first all the sensitive info like imei.
Click to expand...
Click to collapse
Yes I am doing that in rebootRUU mode (Didn't think of mentioning it, I didn't realise it was possible to send firmware without it).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.07.980.2
(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: OPTUS001
(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: cdb72c6d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I connected the device to my PC with internet passthrough and there was another OTA update which I installed and looked correct this time and didn't take as long, I have my wifi back but I noticed in the earlier firmware there's a adsp.img that is missing from the latter. I'm guessing it's to do with the 'Enhanced sound' etc. features that came with that update so I'd like to check if it is on there.

acecombat said:
Yes I am doing that in rebootRUU mode (Didn't think of mentioning it, I didn't realise it was possible to send firmware without it).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.07.980.2
(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: OPTUS001
(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: cdb72c6d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I connected the device to my PC with internet passthrough and there was another OTA update which I installed and looked correct this time and didn't take as long, I have my wifi back but I noticed in the earlier firmware there's a adsp.img that is missing from the latter. I'm guessing it's to do with the 'Enhanced sound' etc. features that came with that update so I'd like to check if it is on there.
Click to expand...
Click to collapse
This looks like the latest firmware for Optus so you must be ok.
(bootloader) version-bootloader: 3.18.0.0000 - This is the latest hboot version
(bootloader) version-baseband: 1.19.21331147A1.16G - This is the latest radio version
(bootloader) version-main: 2.07.980.2 - This must be the latest firmware but check your ROM settings about Software info to see if it's a 4.4.3 android version.
But it all looks good to me.
Edit: reboot to bootloader and check the dsp version. If it's v45.2 (if my memory serves me right) then you are on the latest adsp.img as well

stathis95194 said:
This looks like the latest firmware for Optus so you must be ok.
(bootloader) version-bootloader: 3.18.0.0000 - This is the latest hboot version
(bootloader) version-baseband: 1.19.21331147A1.16G - This is the latest radio version
(bootloader) version-main: 2.07.980.2 - This must be the latest firmware but check your ROM settings about Software info to see if it's a 4.4.3 android version.
But it all looks good to me.
Edit: reboot to bootloader and check the dsp version. If it's v45.2 (if my memory serves me right) then you are on the latest adsp.img as well
Click to expand...
Click to collapse
Android version is correct but DSP is not up to date so it looks like the firmware didn't install that first time. Bootloader tells me DSP is @ V26.2 (Obviously someone doesn't like subversions much!)

acecombat said:
Android version is correct but DSP is not up to date so it looks like the firmware didn't install that first time. Bootloader tells me DSP is @ V26.2 (Obviously someone doesn't like subversions much!)
Click to expand...
Click to collapse
Well maybe that's the latest DSP version that Optus released, i'm not really sure to tell you the truth. But still you have no other choice now as with s-on i don't think you can flash older firmwares.
Nothing to bother yourself though as you are on 4.4.3 with the latest hboot and radio from your carrier.

stathis95194 said:
Well maybe that's the latest DSP version that Optus released, i'm not really sure to tell you the truth. But still you have no other choice now as with s-on i don't think you can flash older firmwares.
Nothing to bother yourself though as you are on 4.4.3 with the latest hboot and radio from your carrier.
Click to expand...
Click to collapse
If I restore a stock NANDroid backup, will the OTA file update the firmware again or is the firmware version check saved elsewhere?

acecombat said:
If I restore a stock NANDroid backup, will the OTA file update the firmware again or is the firmware version check saved elsewhere?
Click to expand...
Click to collapse
No, nandroid backup doesn't include firmware (hboot,radio,adsp,etc)

stathis95194 said:
No, nandroid backup doesn't include firmware (hboot,radio,adsp,etc)
Click to expand...
Click to collapse
I mean, if I install a nandroid backup, can I apply the OTA updates (As it will be a base version) and will the OTA firmware files still install? Or does it skip the firmware install if it detects a newer version already installed?

i'm not really sure about this and you can try it after taking a nandroid of your current setup, but i believe the OTA will skip the rom installation since it will find a newer firmware.

stathis95194 said:
i'm not really sure about this and you can try it after taking a nandroid of your current setup, but i believe the OTA will skip the rom installation since it will find a newer firmware.
Click to expand...
Click to collapse
Correct, OTAs need to be installed sequentially (no "downgrading"), so it will fail when it sees a higher hboot number.

Stuck with no OS & no recovery

I Was following the guide > http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792 to update my firmware and CID which i successfully did. As per the tutorial, it mentioned that i should copy a ROM on sdcard before procedding. Which i did but amazingly the ARWWizard also flashed my SDCARD (? Not sure but my card was empty).
Anyways, I was able to boot into the OS (old) and i realized i need to install recovery. I issued
Code:
adb reboot bootloader
fastboot flash recovery <recovery_image>
I tried installing TWRP 2.8 but it remains stuck at "Entering Recovery", so i isntalled 2.7 and I was successfully in the recovery. There I wanted to cleaned everything, internal storage, cache, delvik cache etc (not microsd). And went on to menu to install OS from sdcard but it was empty.
I thought lets do the sideload with
Code:
adb sideload rom.zip
and got error Can not read rom.zip.
I changed the location of rom.zip to other location and did adb from that location but still no luck. I was under the impression that since i have installed recovery ... I can reboot ... I tried and now i am stuck at Android Boot loading screen ...
While on that screen, my computer shows that it is trying to install MTP drivers but it fails and hence now i can't use ADB to reboot or do anything.
Any help would be appreciated.

I answered you here!

Forsaked said:
I answered you here!
Click to expand...
Click to collapse
alright .. after struggling so much i am finally able to have my phone running. But i guess the ARUWizard didn't upgraded the firmware. The reason i am saying this is that I installed Viper4.1 ROM and it clearly stats in their FAQ that my WiFi wouldn't work if i don't have proper firmware.
Looking at this guide I am confused which firmware to install.
Code:
(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-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s

If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go

EddyOS said:
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
Click to expand...
Click to collapse
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing

..alee said:
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
Click to expand...
Click to collapse
Very nearly right...
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
[B]fastboot reboot-bootloader[/B]
fastboot flash recovery twrp.img
You missed the dash
The firmware flash might need to be done twice. If it says it's failed and reboots the unit, do the same command again to flash it but if it says complete then reboot the bootloader to flash TWRP

Thanks ...
I got it working but now there are two weird issues.
1. My camera doesn't work. Whenever i click on HTC Camera, it shows a black screen (as if camera view is blocked, I can see on screen buttons and options but black background).
2. My phone doesn't recognize the SD Card which i was using before.

Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?

EddyOS said:
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
Click to expand...
Click to collapse
Just want to let you know that the camera issue is before installing this ROM. It was because of the camera that i decided to upgrade from 4.3 to 5.0 Android. The SD card issue has been resolved. Here is my fastboot command details
Code:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s

I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now

EddyOS said:
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
Click to expand...
Click to collapse
my main version is blank ever since I started upgrading my phone. Even if you look at the posts which posted 3 days before (before upgrading) they all had blank main-version.

True. If you are willing to try putting your phone back to 100% you could use the guide in my signature and then at least you'll be back to a point where it should all work

okay ... from your post it seems like only devices with HTC_* CID's can be restored to stock. Given that I am supercid, I can write whatever CID I Can but my original cid was VODP001. Do i have to worry about that ? Would your method work on my device as well ?

Super CID means you can flash anything so just try it. OK, it'll go back to the unbranded build as opposed to the Vodafone build but that's not a bad thing

[Q] i broke my m8 stuck i logo and 4 triangle any advice ?! help

i try ro flash gpe ruu and it dos not run it is broke my mobile
i change cid to 1111111 not work
is any one can advise
C:\Users\m.banamah\Desktop\New folder\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.36.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT529WM00523
(bootloader) imei: 358705060044932
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: CWS__001
(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: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s​

iioodii said:
i try ro flash gpe ruu and it dos not run it is broke my mobile
i change cid to 1111111 not work
is any one can advise
C:\Users\m.banamah\Desktop\New folder\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.36.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT529WM00523
(bootloader) imei: 358705060044932
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: CWS__001
(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: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s​
Click to expand...
Click to collapse
fastboot oem rebootRUU
then you need to run the command twice fastboot flash zip RUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip
my bad and u need to change your mid inbox me

not working
C:\Users\m.banamah\Desktop\New folder\adb> fastboot flash zip RUU-HTC_One_M8_GPE
_5.1-4.04.1700.4.zip
target reported max download size of 1826418688 bytes
sending 'zip' (655035 KB)...
OKAY [ 29.719s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 30.298s

iioodii said:
not working
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
There's your answer right there. You need to change MID to one that is supported by the GPE RUU. Looks like you've already changed your CID to one that works with the GPE RUU. But you need to change CID and MID.

OK I will try

iioodii said:
OK I will try
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2708581
thats how to change your mid since you have no rom i guess, you can flash the latest version of twrp and boot into it and once in it you can put the commands in

i try to change it from this http://forum.xda-developers.com/showthread.php?t =2733850
but my mainver: 2.04.605.2 not listed
also adb commands not working . only fastboot command working .
and i try to flash custom recovery it's flashed but i can not inter it
any suggesting gays

toysoldierq said:
http://forum.xda-developers.com/showthread.php?t=2708581
thats how to change your mid since you have no rom i guess, you can flash the latest version of twrp and boot into it and once in it you can put the commands in
Click to expand...
Click to collapse
Adb command not work

iioodii said:
Adb command not work
Click to expand...
Click to collapse
adb commands dont work in fastboot mode, you need to flash the latest version of twrp boot into it and then use the adb commands if your unsure of what to do and dont want to furher damage your phone i can help you over teamviewer, changing your mid is risky if your not sure and can damage your device badly any wrong mistake and its game over.

iioodii said:
i try to change it from this http://forum.xda-developers.com/showthread.php?t =2733850
but my mainver: 2.04.605.2 not listed
Click to expand...
Click to collapse
The link is for flashing a new splash screen. Don't know why you are linking or trying to follow this.
iioodii said:
and i try to flash custom recovery it's flashed but i can not inter it
Click to expand...
Click to collapse
adb commands will only work while booted in OS or custom recovery. That is what the previous post (Post #6 above) was talking about.
iioodii said:
and i try to flash custom recovery it's flashed but i can not inter it
Click to expand...
Click to collapse
The photo in your first post indicates your bootloader is relocked. Did you unlock it again?
If its still relocked, custom recovery will never flash properly.

redpoint73 said:
The link is for flashing a new splash screen. Don't know why you are linking or trying to follow this.
adb commands will only work while booted in OS or custom recovery. That is what the previous post (Post #6 above) was talking about.
The photo in your first post indicates your bootloader is relocked. Did you unlock it again?
If its still relocked, custom recovery will never flash properly.
Click to expand...
Click to collapse
i fix the problem over teamviewer red point, what i did was edit the model id in the zip from the google play stock rooted rom to match his and flash it, then unlock his bootloader with adb and change both mid and cid to google play, his phone was stuck at the htc logo black screen that fix it.

Cant go back to Sense (from gpe)

Hello
Since i flashed the gpe ruu, i cant get back to sense.
I tried almost everything. I tried 3 different ruu.exe's, 2 different ruu.zip's and dozens of firmwares. (old and new ones, international and devEd's)
My Bootloader is unlocked, i have s-off and supercid.
(I tried everything with a relocked bootloader, too!)
I followed this guide right here. (And a good hand full of other guides, here on xda)
Currently i have cm13 installed (without gapps!! -.- because /system is too small), but i really want sense back tho
I downloaded 3 different sense based custom roms and tried them all. But twrp is unable to flash them, due to the changed /system partition size. (i tried twrp 2.8.7.0 AND 3.0.0-1)
For those of you who are able to speak or read german, I have a different thread in a german forum.
I appreciate any help!
Thanks

What specific RUUs (file name) and firmwares (version numbers) did you try?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Firmware's:
1.54.401.5-W_Splash.zip
M8_4.16.401.13_WWE_TWRP2870.zip
M8_6.12.401.4_WWE_FullStock.zip
M8_6.12.401.4_WWE_TWRP2870.zip
M8_6.12.1540.4_DevEd_FullStock.zip
RUU's:
RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
RUU_3.28.401.9_M8_WWE_Stock.exe
0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
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.zip
fastboot getvar all: (i restored an old cm13 backup. i dont know why there is no version-main)
(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-OFF
(bootloader) serialno: ----
(bootloader) imei: ----
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

crruell said:
(bootloader) modelid: 0P6B17000
Click to expand...
Click to collapse
There is your problem .. you need to change it to 0P6B10000 then flash the firmware.zip then install RUU.
See this on how to change it : http://forum.xda-developers.com/showthread.php?t=2708581

ckpv5 said:
There is your problem .. you need to change it to 0P6B10000 then flash the firmware.zip then install RUU.
See this on how to change it : http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Oh my god..
Thank you mate! I will try this, when im back home

crruell said:
fastboot getvar all: (i restored an old cm13 backup. i dont know why there is no version-main)
Click to expand...
Click to collapse
Known TWRP bug, usually happens due to an older version TWRP being used at some point in the past.
Once you flash a firmware successfully, that firmware's version number will be properly shown as main version again.

Hm.
i still cant flash the ruu.
ruu.exe is still giving me errors and the .zip in hboot still says, that the /system partition is too small.
(i also tried the original mid [t-mobile])

solution:
ruu.exe & ruu zip wont work for me.
i tried flashing the firmware & latest twrp and then restoring 6.12.401.4-twrp backup.
and..
it actually worked.
(sorry for double post. i didnt mean to :s)

crruell said:
solution:
ruu.exe & ruu zip wont work for me.
i tried flashing the firmware & latest twrp and then restoring 6.12.401.4-twrp backup.
and..
it actually worked.
(sorry for double post. i didnt mean to :s)
Click to expand...
Click to collapse
As I said earlier.. flash firmware.zip first to change partition size then only you can install RUU.
Restoring a backup after firmware.zip is as same as install RUU after firmware.zip is flashed.
And to install RUU zip, you need to use htc_fastboot.exe

HTC m8 phone keeps booting into fastboot mode

hello,
after root my phone
every time i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
please help me !!

Need more info.
What version SuperSU? What version TWRP?
What "official update" file did you use? Was it an OTA or an RUU (list the exact file name)?
Also, do fastoboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
Need more info.
What version SuperSU? What version TWRP?
What "official update" file did you use? Was it an OTA or an RUU (list the exact file name)?
Also, do fastoboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
HI
Pls refer Bellow details
C:\miniadb_v1031>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.213311771.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.82.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(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: 8d01ca6e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s

In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.

redpoint73 said:
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
Click to expand...
Click to collapse
Hi
It's work
Thanks for your support

redpoint73 said:
In addition to the fastboot output, I asked 4 questions, none of which you answered.
You have the M8 eye, not the "standard" M8. Far as I can tell (not many folks on xda have the "eye") you need a special version of TWRP for this version. You can try the right version TWRP, and flash SUperSU again, see if that helps. No idea if this version TWRP will work on not (can't personally vouch for it): https://forum.xda-developers.com/htc-one-m8/general/m8-eye-recovery-root-t3159648
Depending on what you did to the phone by flashing the wrong TWRP, it's hard to tell what the proper way to proceed.
Click to expand...
Click to collapse
hi
can i have stock recovery download link in that phone pls

I have a similar issue, but with a standard M8
£10 off ebay, so not expecting ,much (also means no known history) . 1 week old noob reading here and flashing phones
1) only boots to fastboot, and even does this when you leave it powered off, but charging.
2) select hboot, then to recovery, recovery doesn't run, just resets back to fastboot eventually, after screen goes white not black.
3) can partially speak to phone in fastbook and get versions ok (included below)
Getver all as below:
C:\Program Files (x86)\Minimal ADB and Fastboot>
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA615WM01404
(bootloader) imei: 357336060194484
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.114s
4) never been able to boot to full o/s so not in developer mode, so cant get response in adb (and dont know how to use this anyway)
5) tried RUU.exe - fails with usb error after it tries to restart bootloader
6) tried ruu.zip from memory card - fails with partition update fail
7) tried fastboot recovery image 6.12.401.4 and it fails to write - error is 'remote:signature verify fail'
8) random google lead me to fastboot oem reboot RUU which does this:
E:\android tools>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.052s]
finished. total time: 10.053s
9) htcdev unlock bootloader didnt work initially but has done now - is this a path i should try?
aim is to get a standard phone working again
Thanks
G

ok got my unlock token, seemed to flash it, but no status change/reaction on phone and rebooting still shows locked
E:\android tools>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.125s
G

My responses to some of your points below, in red font:
gda_scooby said:
(bootloader) version-main: 6.12.401.4
4) never been able to boot to full o/s so not in developer mode, so cant get response in adb (and dont know how to use this anyway) That is correct, you will not be able to use adb unless you can boot to OS or alternately TWRP custom recovery. So you are basically limited to fastboot in the current condition.
5) tried RUU.exe - fails with usb error after it tries to restart bootloader There isn't a valid exe format RUU for your version number (6.12.401.4) so you are probably using the wrong RUU. What is the version number or file name for the RUU.exe?
6) tried ruu.zip from memory card - fails with partition update fail Exactly what partition(s) is it failing to update? What is the version RUU you are using? The only valid one for your version would be the RUU.zip from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
7) tried fastboot recovery image 6.12.401.4 and it fails to write - error is 'remote:signature verify fail' You can't flash an unsigned recovery image, unless the bootloader is unlocked. It also seems you are trying to flash stock recovery, and I don't see how that is going to help your current condition.
Click to expand...
Click to collapse
I think your best bet right now, is to try the correct RUU.zip which I linked above.