[Q] Unable to flash firmware - One (M8) Q&A, Help & Troubleshooting

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.

Related

Softbricked my HTC One M8, any advice is much appriciated

Well its been some time since was rooting and romming phones (so please give advice step by step) but just the other day I soft bricked my One M8 and I am at wit's end trying to fix it.
Scenario was I was happy running gpe 4.4.2 on my phone awhile now until I saw the GPE rom was getting an OTA update with Lollipop. To avoid the hassle of installing an ota updat the dirty way I thought to just re-lock my bootloader, flash recovery and just update. Well it went like this.
1. Had 4.4.2
2.Flashed stock recovery (I forgot to do fastboot oem lock)
3.Booted back into 4.4.2, ran update checker, downloaded 4.4.3
4.Phone updated to 4.4.3 with no issue.
5. Ran update checker again to grab 4.4.4
6.Rebooted to install and bam on boot I just got the white "HTC" boot screen for about an hour
OS is broke.
I do still have access via fastboot and have since re flashed recovery to twrp. However I am unable to flash a new rom, I keep getting "E error executing updater binary in zip" in twrp and "status 7" in clockwork.
Sideloads fail with the same error.
I've also tried re-locking the phone and flashing stock recovery and trying HTC's RUU app however that fails as well with Error 553.
Any help is much appreciated! My goal is just to have clean lollipop gpe rom installed.
What can I do to fix this?
Current Bootloader screen:
++Tamperered++
++ Unlocked ++
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio - 1.16.21331931.LA24G
Open-DSP-v38.2.2-00542-M8974.0311
OS-*blank* ----------something to note this was previously red with a 2.12 number
eMMC-boot 2048MB
fastboot getvar version-main yeilds:
version-main:
finished. total time: 0.001s
fastboot oem readcid yeilds:
(bootloader) cid: T-MOB010
OKAY [ 0.003s]
finsihed.
fastboot getvar all yeilds:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
tin_can_ said:
Well its been some time since was rooting and romming phones (so please give advice step by step) but just the other day I soft bricked my One M8 and I am at wit's end trying to fix it.
Scenario was I was happy running gpe 4.4.2 on my phone awhile now until I saw the GPE rom was getting an OTA update with Lollipop. To avoid the hassle of installing an ota updat the dirty way I thought to just re-lock my bootloader, flash recovery and just update. Well it went like this.
1. Had 4.4.2
2.Flashed stock recovery (I forgot to do fastboot oem lock)
3.Booted back into 4.4.2, ran update checker, downloaded 4.4.3
4.Phone updated to 4.4.3 with no issue.
5. Ran update checker again to grab 4.4.4
6.Rebooted to install and bam on boot I just got the white "HTC" boot screen for about an hour
OS is broke.
I do still have access via fastboot and have since re flashed recovery to twrp. However I am unable to flash a new rom, I keep getting "E error executing updater binary in zip" in twrp and "status 7" in clockwork.
Sideloads fail with the same error.
I've also tried re-locking the phone and flashing stock recovery and trying HTC's RUU app however that fails as well with Error 553.
Any help is much appreciated! My goal is just to have clean lollipop gpe rom installed.
What can I do to fix this?
Current Bootloader screen:
++Tamperered++
++ Unlocked ++
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio - 1.16.21331931.LA24G
Open-DSP-v38.2.2-00542-M8974.0311
OS-*blank* ----------something to note this was previously red with a 2.12 number
eMMC-boot 2048MB
fastboot getvar version-main yeilds:
version-main:
finished. total time: 0.001s
fastboot oem readcid yeilds:
(bootloader) cid: T-MOB010
OKAY [ 0.003s]
finsihed.
fastboot getvar all yeilds:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Click to expand...
Click to collapse
I'm at work rt now but I'm 95% I can fix this for you say after work today..do u use hangouts?
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
Something you can try now....you still get stuck at splash screen try fastboot the boot.IMG from the ROM you r running.
Yeah I use hangouts. And I'll be available at 7pm est today. I left the phone at home today just out of frustration of fiddling with it all night. Message me your gmail account and we'll take a look.
tin_can_ said:
Yeah I use hangouts. And I'll be available at 7pm est today. I left the phone at home today just out of frustration of fiddling with it all night. Message me your gmail account and we'll take a look.
Click to expand...
Click to collapse
Sent you a pm with gmail
all better now
thanks for the assist @Tigerstown
What was the fix for this? I am having the same problem
dottat said:
all better now
thanks for the assist @Tigerstown
Click to expand...
Click to collapse
joelmi12 said:
What was the fix for this? I am having the same problem
Click to expand...
Click to collapse
You tried to convert to gpe??? Cause that's what he did to begin with.
joelmi12 said:
What was the fix for this? I am having the same problem
Click to expand...
Click to collapse
I doubt you are having the same exact problem. I would be willing to take a look at it if you wanted though.
dottat said:
I doubt you are having the same exact problem. I would be willing to take a look at it if you wanted though.
Click to expand...
Click to collapse
I might be in a similar situation. I was running blisspop 5.0 just to see how it feels. I started having problems so i went to wipe and go back to CM11 only to find out Philz E: could not mount/data to setup . Now I have no ROM and a broken recovery.. any thoughts?
tommyamo said:
I might be in a similar situation. I was running blisspop 5.0 just to see how it feels. I started having problems so i went to wipe and go back to CM11 only to find out Philz E: could not mount/data to setup . Now I have no ROM and a broken recovery.. any thoughts?
Click to expand...
Click to collapse
Did you flash a different radio/baseband as part of this?
Are you S-OFF?
I am S off. I hadn't flashed a new radio. I found my fix. I think i inadvertantly wiped my data from the internal sd. That was throwing me off. I managed to get back to CM11. I still can't read any data on my ext SD, but at least my phone is on and stabilized. Thanks for replying!! Happy holidays!
Sent from my One M8 using XDA Free mobile app
So kinda messed up my wife's m8 :/ well I was running cm12 withe 500 gpe, she's trying to return it back so i decided to go back to stock I flashed the stock gpe and boom I get the e: data not mounted and it won't do a side load or nothing also was able to flash a recovery 2 different Recovery's but nothing is flashing or pushing any help would be appreciated thank you...
Sent from my Nexus 6 using Tapatalk

[Q] Hi, no OS on M8, flash rom in TWRP "some symlinks fail"

Hi,
Apologies in advance because I'm sure this is a very noob problem, but I was trying to update my M8 to lollipop and ended up messing it up somewhere. It was rooted before, S-Off, unlocked, using Android HD 4.4.4.
When I try to flash the Android HD Lollipop rom in TWRP from internal or external sdcard, or from USB OTG, the installer starts and looks successful until it gets to "Creating toolbox symlinks". After that it says "symlink: some symlinks failed"
When it finishes, it goes back into recovery and TWRP says "Successful"
When I go to reboot TWRP says it isn't rooted and asks if I'd like to root. Whether I say "yes" or "no" it reboots to a white HTC screen with a little lock at the bottom. The lock wasn't there when I started. After a few seconds the screen turns off then back on, then it goes into recovery.
If I try to install the update-supersu from internal or external card, or from USB OTG, in TWRP it says "success" and no errors, but then when I go to reboot it, it says "does not appear to be rooted" and asks if I'd like to root it. Whether I say yes or no it reboots, freezes, then boots into recovery and I start over.
In boot where it used to say "tampered" it now says "modified", and under that "unlocked", "s-off", a bunch of numbers that look important, but nothing in "OS-".
I can get into recovery and fastboot or hboot just fine. I have ADB, fastboot, and I think all the drivers I need on my laptop, and both recognize my phone when it's plugged in and I type "adb devices". I've tried like 10 different guides to push and flash and honestly too many commands to remember, but nothing that can get it to boot into a working rom.
To be honest, every single time I've tried to root something, I've broken something, but usually if I keep looking I can find the same problem and someone who's fixed it and figure it out, but I've been at it nearly 20 hours straight now and I just can't see what I'm missing (besides OS Dx)
If anyone knows what I've done and how to undo it, I'd be grateful for any advice.
Thanks,
Josh
*** I think I got the wrong firmware, but not sure how to find the right one without downloading them reandomly and checking the android-info***
Boot to bootloader/fastboot then run command fastboot getvar all
Post here the result (delete serial no. & imei no.)
Will see what we can do later
Your problem most probably is the old version of TWRP (2.7.0.2) that you use.
You should try 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware.
Sure
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader)
(bootloader)
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Blue67982 said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
So you have a AT&T device.
What actually you want to do because there is no lollipop update for AT&T yet.
Since your device is S-Off, you can change
CID : CWS__001 to 11111111
MID : 0P6B12000 to 0P6B10000
then flash a EU firmware.
Or you take any unsigned EU firmware.zip, open it with 7-zip and extract out the android-info.txt and edit this android-info.txt to include your CID and MID (use notepad++ for this), drag the modded android-info.txt into the unsigned firmware.zip
Flash this modded firmware, should work too.
And important thing about TWRP : 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware
Then you can install any of the lollipop Sense base custom ROM.
Thanks. I'll chug some coffee and give it a try.
Ok, I changed my CID and MID without too much trouble, but about "TWRP : 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware", how can I tell which I have?
Oh, I used the ADB method if that matters.
After change of CID/MID, you need to flash firmware.zip in RUU mode not ADB.
Your current firmware is KitKat .. if you stick to it, you need 2.8.3.0
After you flash a 4.xx.xxx.x firmware - you need 2.8.5.0
Check this : http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Thanks for putting up with all the questions.
I just want to make sure I'm doing this correctly. I need to update the firmware to a 4x one, then twrp 2.8.5.0, then root and rom? I'm reading the guide you linked, but I'm not sure which firmware to use, for example it lists 5xxBase, then underneath it lists firmwares starting with 4xx.
Or does it not matter?
1. Update firmware, flash the widely use - 4.16.401.10
2. Flash TWRP 2.8.5.0
3. Install ROM
No need manual root because custom ROM is prerooted.
I got to go now .. be back in next 4 hrs
ckpv5 said:
flash the widely use - 4.16.401.10
Click to expand...
Click to collapse
TYSM!! That's what I was looking for
Ok, I updated the firmware and TWRP (I think), but when I try to do anything like flash a rom all the partitions come up as unmountable before the installer starts. I know I read something similar before so I'll try to find that.
\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(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
You don't seems be using the updated TWRP 2.8.5.0
Your fastboot shows that you may use the old 2.7.0.2
Download and install TWRP 2.8.5.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.5.0-m8.img
Then boot to recovery - select wipe - advance - format data - yes
Go to reboot menu - select recovery (to reboot back to recovery
Select "Mount" menu - enable MTP
Transfer the ROM zip to either Internal Storage or MicroSD (if you have one)
Then try to install the ROM.zip
that's so weird...from within twrp the little info bar thing at the top says v2.8.5.0
Ill install again
Yeah .. unless you remove the (bootloader) version-main: info, TWRP 2.8.5.0 should not remove that after you flash the firmware.
Anyway ... try the other steps that I mentioned.
You did it man, you fixed the phone I thought I would have to throw away.
Thanks for answering so many noob quuestiuns
I owe you one
Blue67982 said:
You did it man, you fixed the phone I thought I would have to throw away.
Thanks for answering so many noob quuestiuns
I owe you one
Click to expand...
Click to collapse
Great :good::good:
You don't owe me anything ... just love to help
Since he had a at&t phone, why did you not tell him the change the cid to dev edition and run the ruu in fastboot mode, that wont have been easier?
toysoldierq said:
Since he had a at&t phone, why did you not tell him the change the cid to dev edition and run the ruu in fastboot mode, that wont have been easier?
Click to expand...
Click to collapse
Different ways to skin the same cat. There is nothing "wrong" with the solution that was used.
It worked, and now I know to make 100% sure I have the right versions of everything BEFORE I start, so I'm happy.

TWRP straight back to BootLoader

I've recently installed Firmware and another ROM (RUU) they went thru successfully but only updated to Lollipop 5.01 which i thought was strange.. well anyway, i flashed TWRP and now it says entering recovery for about a second then goes back to the Boatloader page (fastboot etc) tried to restart and try again and it does the same every time..tried re-flashing TWRP and still does the same.. any ideas please?
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44xxx xxx xxx
(bootloader) imei: 354 xxx xxx xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: HTC__032
(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: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
C:\adb>
Forgot to mention, i need recovery to change the MID ..have tried manually without success.
Thank you
Try wipe cache, and flash TWRP again.
Make sure its TWRP version 2.8.7.0 or 3.0.0.0. Some folks have been trying to flash older versions, some of which don't work on LP or later.
redpoint73 said:
Try wipe cache, and flash TWRP again.
Make sure its TWRP version 2.8.7.0 or 3.0.0.0. Some folks have been trying to flash older versions, some of which don't work on LP or later.
Click to expand...
Click to collapse
Thank you, tried fastboot erase cache and flashed 2.8.7.0 and it still does the same thing.. i already flashed 3.0.0.1 before - would you know how to change the MID without having to use recovery? once i have changed that i can get the European RUU installed on my device - i have changed the CID already .. the phone was US on T-Mobile but i'm wanting it on UK O2 now ..thank you again
Did you flash TWRP before booting up at least once?
RUU to marshmallow doesn't seem to exist yet. (aka I haven't found one)
So update to 4.25 firmware which is lollipop 5.0.2 - I think.
Then allow phone to boot (make sure to have stock recovery), go through with all the OTAs which will come.
Once OTAs are completed successfully feel free to flash TWRP back.
Kyuubi10 said:
Did you flash TWRP before booting up at least once?
RUU to marshmallow doesn't seem to exist yet. (aka I haven't found one)
So update to 4.25 firmware which is lollipop 5.0.2 - I think.
Then allow phone to boot (make sure to have stock recovery), go through with all the OTAs which will come.
Once OTAs are completed successfully feel free to flash TWRP back.
Click to expand...
Click to collapse
Hi and thanks again, to be honest i dont know what i've done.. i got the phone from eBay..new M8 but when i spoke to HTC they said the phone was US on T-Mobile.. i just wanted to change the CID & MID so i can install a European ROM maybe O2 or something ..i'm really quite new to this ..i had a M7 before which i did manage to flash and update to LP but with this M8 i'm struggling .. i just downloaded Firmware 4.25.651.18.zip ..which ROM would be best to use with this please? i'm sorry for my lack of knowledge here.. and should i wipe the phone completely? factory format as i cannot get into Recovery..
Thanks again
Sorry, i'm getting this when i try to flash that Firmware
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot flash zip 4.25.651.18.zip
target reported max download size of 1826418688 bytes
sending 'zip' (54607 KB)...
OKAY [ 3.122s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 5.542s
Fixed for now
hi again, the reason the original ROM did not instal was because i had changed the CID to a European one and was trying to instal a US TMOB ROM ..i changed the the CID back to a SuperCID 1st then installed the ROM and then changed the CID back to the original T-MOB010 CID so i could get all the OTA updates ..i will just leave it at this for now as i thought originally i had bricked my M8 - after the 1st flash the phone went into a boot loop :/ ...anyway, it's all sorted now and doing the many OTA updates but this particular one only updates to LP 5.01 .... i'm just wondering how i could get it to update to 5.02 or even 6.0? i will still try and change the CID & MID when i have enough information and am completely confident (and have a spare phone) then instal a European ROM and see if that get me the updates - thanks for the help
Craig_CFC said:
hi again, the reason the original ROM did not instal was because i had changed the CID to a European one and was trying to instal a US TMOB ROM ..i changed the the CID back to a SuperCID 1st then installed the ROM and then changed the CID back to the original T-MOB010 CID so i could get all the OTA updates ..i will just leave it at this for now as i thought originally i had bricked my M8 - after the 1st flash the phone went into a boot loop :/ ...anyway, it's all sorted now and doing the many OTA updates but this particular one only updates to LP 5.01 .... i'm just wondering how i could get it to update to 5.02 or even 6.0? i will still try and change the CID & MID when i have enough information and am completely confident (and have a spare phone) then instal a European ROM and see if that get me the updates - thanks for the help
Click to expand...
Click to collapse
Perfect, so you figured it out Well Done.
Yeh, the best way is by changing MID and CID then flashing what you wish.
I wouldn't know since I am S-on.
Kyuubi10 said:
Perfect, so you figured it out Well Done.
Yeh, the best way is by changing MID and CID then flashing what you wish.
I wouldn't know since I am S-on.
Click to expand...
Click to collapse
I used Sunshine S-Off to do that.. payed the $25 ..its really easy and don't take long.
As for the phone, i think i'm going to do some serious research before i attempt anything like that again - its all up and running again, i'm not even going to flash TWRP this time until i really need it .. it's currently updated to 5.01 which i can live with.. i just wanted to taste a bit of Marshmallow i suppose it's a waiting game now - thanks again
Craig_CFC said:
i just downloaded Firmware 4.25.651.18.zip
Sorry, i'm getting this when i try to flash that Firmware
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
How did you come about picking that firmware? Its not for T-Mobile US, its for Sprint.
In fact, its a good thing the firmware failed to install. If it succeeded, it may have bricked your phone due to partitioning differences between the Sprint version and most other M8 versions.
Be very careful about what firmware you flash. Don't flash any firmware you if you aren't 100% sure its the right one you should be using.
---------- Post added at 10:38 AM ---------- Previous post was at 10:17 AM ----------
Craig_CFC said:
would you know how to change the MID without having to use recovery?
Click to expand...
Click to collapse
I do, but I'm confused since you stated in the OP that you already tried to do it "manually"?
Craig_CFC said:
Forgot to mention, i need recovery to change the MID ..have tried manually without success.
Click to expand...
Click to collapse
Before we head in that direction, you need to understand a couple things about changes made requiring s-off. By definition s-off means that all (or at least most) security checks are off. So this means:
1) Changing the MID is a bit risky, in that you are manually editing/modifying memory blocks (not sure if "block" is technically the right term, but I think you understand what I'm getting at) using adb. Enter the command incorrectly (and modify the wrong memory block), and you can brick the phone! You have to be extremely careful about the process of changing the MID, and double check and triple check every single commands is correct (not a single typo) before pressing "Enter".
2) As mentioned above, flashing firmware also requires close attention and care. You need to be 100% of the firmware you are flashing. Once you've changed the MID, you are bypassing the very safety check that is designed to prevent bricks (from flashing the wrong firmware).
If you are prepared to use extreme caution and exercise the required care, then we can proceed with what you want to do (change MID, flash Euro RUU so that you can "convert" the phone to official Euro version, with full OTA updates).
Although another method (if you don't mind the lack of OTA updates) is to ensure you are on LP firmware (or flash T-Mobile US firmware or RUU to get to LP firmware). Then flash a MM custom ROM (which should work fine with LP firmware). This direction is much safer, as its nearly impossible to brick the phone flashing the firmware meant for your original CID/MID or from flashing a custom ROM.
Really, the lack of OTA is not a big deal, in my opinion. The custom (or near stock) ROMs get updated just as fast as the official OTAs (in fact, often faster depending on which CID you are talking about) so you can continue to keep updated by flashing custom ROMs. Honestly, this is my 3rd HTC phone, and the number of times I've installed official OTA updates is zero, due to the fact that the ROMs posted by devs here are just as good (or better) and just as timely.
Thank you for the advice & tips... the phone is S-Off (Sunshine) and bootloader Unlocked - all i'm wanting to do is go from T-Mobile US to a UK ROM like maybe O2 ..i'm on the giffgaff which run on the O2 network ... i have been searching for the correct Firmware without success - i have RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed
but just need to find the correct firmware to flash so i can instal this.. any ideas please? am very new to this and don't completely understand how to find the correct FW for a particular RUU
D:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.034s
as you can see it is US T-MOB - how can i change this so i have O2 UK please?
Many many thanks
I discovered the reason TWRP was not flashing properly... i needed to update to Android 5.01 1st then flash TWRP custom recovery..that all works well now and i have recovery back but just put MID_Changer_03.07.14 on my phone and ran it in recovery - it all worked great but when i checked the MID it hadnt changed so ran again an still no change - i'm wanting to change that too 0P6B1000 (Europe) then the CID to HTC__032 ...then i will try to instal the above RUU - does this all sound like the right thing to do? i have been trying to find the right firmware for that RUU but cannot seem to find one or rather don't know what i am looking for - thanks again
Craig_CFC said:
I discovered the reason TWRP was not flashing properly... i needed to update to Android 5.01 1st then flash TWRP custom recovery..that all works well now and i have recovery back but just put MID_Changer_03.07.14 on my phone and ran it in recovery - it all worked great but when i checked the MID it hadnt changed so ran again an still no change - i'm wanting to change that too 0P6B1000 (Europe) then the CID to HTC__032 ...then i will try to instal the above RUU - does this all sound like the right thing to do? i have been trying to find the right firmware for that RUU but cannot seem to find one or rather don't know what i am looking for - thanks again
Click to expand...
Click to collapse
Are you s-off? If not, you need to be s-off to change the mid.
robocuff said:
Are you s-off? If not, you need to be s-off to change the mid.
Click to expand...
Click to collapse
Yes S-Off (sunshine) and unlocked bootloader .. it just won't let me change it for some reason
Craig_CFC said:
D:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I'm getting more and more confused. This doesn't match the getvar output in Post #1. Did you change something to get to this point?
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
Craig_CFC said:
i have recovery back but just put MID_Changer_03.07.14 on my phone and ran it in recovery - it all worked great but when i checked the MID it hadnt changed so ran again an still no change
Click to expand...
Click to collapse
Haven't heard of such a method. Can you link to where you got this from?
There is a proven method for changing MID on the M8, and that is not it.
redpoint73 said:
I'm getting more and more confused. This doesn't match the getvar output in Post #1. Did you change something to get to this point?
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
Haven't heard of such a method. Can you link to where you got this from?
There is a proven method for changing MID on the M8, and that is not it.
Click to expand...
Click to collapse
I flash differnt firmware from OP i think... i'm still none the wiser though.. my updates OTA to 5.01 but i'm sure i can get 6.0 with sense 7.0 if i use a UK ROM but i need the correct firmware for that particular ROM and i do not know what to look for - the MID Changer was here http://www.droidviews.com/change-cid-mid-htc-one-devices/ thanks
Craig_CFC said:
I flash differnt firmware from OP i think...
Click to expand...
Click to collapse
Looks like you flashed an older firmware (really old, as in Kitkat Android 4.4.2), based on Post #10 (versus what you had originally in Post #1).
Craig_CFC said:
i'm still none the wiser though.. my updates OTA to 5.01
Click to expand...
Click to collapse
So its updated back to Lollipop?
Do another fastboot getvar all, and post the current status.
Craig_CFC said:
the MID Changer was here http://www.droidviews.com/change-cid-mid-htc-one-devices/ thanks
Click to expand...
Click to collapse
That isn't for the M8. If you look at that webpage's "Source" it links to the XDA One M7 section. That mod is for the M7, not the M8.
You're lucky it didn't brick the phone. I've already stated above in Post #6 how dangerous MID changing can be, if not performed properly. But it seems that you've chosen to ignore that advice.
No offense intended, it seems you are going about things rather recklessly. Already you've flashed an incorrect old T-Mobile firmware, tried flashing the firmware for the wrong version (Verizon) and now tried changing the MID with a mod for the M7. There is a proper process to change the MID on the M8. But I'm hesitant to lead you to that (of course, you can find it yourself - but that's your own deal), as you haven't demonstrated you are capable of the proper carefulness. And frankly, I don't want you messing with things that can easily brick your phone.
My suggestion would be to flash back to 4.20.531.5 firmware (if its not the current firmware) then just leave it that way until T-Mobile releases Marshmallow. Alternately, install a custom recovery (unlocked bootloader required, if its not presently), and simply flash a MM ROM; which should work find with LP firmware. These options are relatively safe, and don't require you messing with the MID.
redpoint73 said:
Looks like you flashed an older firmware (really old, as in Kitkat Android 4.4.2), based on Post #10 (versus what you had originally in Post #1).
So its updated back to Lollipop?
Do another fastboot getvar all, and post the current status.
That isn't for the M8. If you look at that webpage's "Source" it links to the XDA One M7 section. That mod is for the M7, not the M8.
You're lucky it didn't brick the phone. I've already stated above in Post #6 how dangerous MID changing can be, if not performed properly. But it seems that you've chosen to ignore that advice.
No offense intended, it seems you are going about things rather recklessly. Already you've flashed an incorrect old T-Mobile firmware, tried flashing the firmware for the wrong version (Verizon) and now tried changing the MID with a mod for the M7. There is a proper process to change the MID on the M8. But I'm hesitant to lead you to that (of course, you can find it yourself - but that's your own deal), as you haven't demonstrated you are capable of the proper carefulness. And frankly, I don't want you messing with things that can easily brick your phone.
My suggestion would be to flash back to 4.20.531.5 firmware (if its not the current firmware) then just leave it that way until T-Mobile releases Marshmallow. Alternately, install a custom recovery (unlocked bootloader required, if its not presently), and simply flash a MM ROM; which should work find with LP firmware. These options are relatively safe, and don't require you messing with the MID.
Click to expand...
Click to collapse
Thank you ..i'm really no good at this as you clearly can tell .... as requested, here is my phone info:
D:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.531.5
(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: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Thanks again

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.

Cannot flash RUU on my European HTC ONE M8

Hello
I can't flash RUU on my M8
I always get "device halted due to large image update fail" message at the end of flashing.
fastboot getvar all command shows me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: my secret
(bootloader) imei: my secret
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried 6.12.401.4 and 4.16.401.10 RUU but non was succesful. The only RUU which flashing was succesful was the GPE series 5 (I don't remember the full number) RUU, but I couldn't boot the device with it.
The files I tried are not damaged.
Help me please
Try flash 6.12.401.4 full stock firmware before install 6.12.401.4 RUU
ckpv5 said:
Try flash 6.12.401.4 full stock firmware before install 6.12.401.4 RUU
Click to expand...
Click to collapse
Thanks ckpv5
I managed to flash firmware. But i still canot flash RUU. I tried sd card method and fastboot flash zip command and it says:
target reported max download size of 1826418688 bytes
sending 'zip' (1687272 KB)...
OKAY [ 52.515s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 52.649s
I've downloaded RUU file again, but it won't help.
Sd card method says the same as before. What can I do now?
Full stock firmware ? Not some modded one.
You need htc_fastboot to fastboot flash ruu zip
See - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
In case you need full stock firmware, you can check my backup thread post #5
Frankly, I have no idea why you can't flash/install RUU when on S-Off, unless the partition is GPE size (you need to resize it back to Sense using full stock firmware, then install twrp to format data (not wipe data but format) before you can install RUU)
ckpv5 said:
Full stock firmware ? Not some modded one.
You need htc_fastboot to fastboot flash ruu zip
See - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
In case you need full stock firmware, you can check my backup thread post #5
Frankly, I have no idea why you can't flash/install RUU when on S-Off, unless the partition is GPE size (you need to resize it back to Sense using full stock firmware, then install twrp to format data (not wipe data but format) before you can install RUU)
Click to expand...
Click to collapse
Thanks to your firmware i managed to format cache data and system partition and install lineage 15.1
Before I couldn't do it because there was a problem with the cache partition. I still cannot install RUU, but since LOS is working I don't need RUU. Now I have only /carrier partition error in TWRP but the system is working so I'm satisfied.
Sent from my Alcatel Idol 5 using XDA Labs

Categories

Resources