M8 frozen system - One (M8) Q&A, Help & Troubleshooting

Hello all,
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
"fastboot getvar all" returns this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
Now the interesting part. Every time the phone reboots, it is always in the same state as if the partitions were frozen. That is to say for instance if I uninstall an app and then reboot, the app is there again. If I connect to a Wifi network and reboot, it disappears. Every single modification is erased and returns back to the same state. The most annoying thing is that when I connect to a Wifi the apps start synchronizing, crash and the phone reboots.
I tried the following:
- Factory reset from the interface to no avail as it returns to the state it was as well
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
- Tried "fastboot oem rebootRUU", which simply reboots the phone into android
- Tried to unlock the bootloader, which again reboots the phone into android
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
- Tried to flash only the zip from the RUU and ends up with the same signature error
I simply can't think of anything else to do, and I hope one of the gurus can help me in my quest
Thank you for the time you spent reading my post.

My responses/comment below in red font:
tyraek said:
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
(bootloader) version-main: 1.58.502.1
It doesn't appear to have had any OTA updates. Or at most a minor update from 1.54>1.58.
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
Try pressing vol up and power to show the stock recovery menu options. I believe factory reset is one of those options, although if wiping in OS didn't work; I doubt doing so from stock recovery will be any different.
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
Which RUU (exact filename)? There are many, and the RUU has to be intended for your CID version.
What error number, and what error message? This is very important, otherwise we have no idea why it failed.
You're on the right track, by trying to run an RUU. I think its your best bet to fix the issue. But we need to make sure you run the right RUU.
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
You can't flash recovery with a locked bootloader.
- Tried to flash only the zip from the RUU and ends up with the same signature error
Again, which RUU specifically is very important. Can't tell if the RUU is the right one based on the info given.
Also, please verify on the hboot screen, near the top, if it says LOCKED (other possibilities being UNLOCKED and RELOCKED)
Click to expand...
Click to collapse

Thank you so much for your reply.
I have tried the factory reset from the recovery and the result is the same.
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
The update states it will upgrade from 1.58.502.1 to 4.28.502.2. Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.

bump

tyraek said:
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
Click to expand...
Click to collapse
Yes, this is for your model (AT&T) and the version number will work.
tyraek said:
Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
.
Click to expand...
Click to collapse
This is means there is a USB communication issue, usually on the PC side, and there is nothing wrong with the RUU or the phone.
RUU is very finicky, and this issue is common. Try a different cable, different USB port, and try to re-install HTC Sync.
But you may have to resort to using another computer. Win7 and USB 2.0 (USB 3.0 is known to cause issues with RUU) are the best bet to get the RUU to run properly.
tyraek said:
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.
Click to expand...
Click to collapse
Do not unlock the bootloader if you intend to RUU. Unlocked bootloader will actually cause the RUU to fail, by definition. RUU requires the bootloader by LOCKED or RELOCKED (or else you need s-off to run an RUU with the bootloader UNLOCKED).

Related

[Q] [RUU] Error: 152. Unable to Restore TMob One M8

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(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: 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: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

[Q] Stuck in fastboot and no connections in ADB

Hello everyone.
Im new here and my english is not on the highest lvl, so pls be patient.
My problem with HTC Desire 816 is that I'm stuck in fastboot with no OS and S-ON, like below:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
A5_UL PVT SHIP S-ON
HBOOT 3.19.0.0000
RADIO 1.101.1102.17.0506
OpenDSP v28.2.2.00546.0331
OS-
eMMC-boot 1536MB
Nov 10 2014
I can't do anything on my phone (recovery, factory reset) cuz after hiting 'power' phone just reboot into bootloader again.
When i plug my phone via USB, windows 8.1 found my device and I have installed it as "Android Composite ADB Interface" and HTC Sync starts running (so it can see my phone).
But my biggest problem is now!
I have installed fastboot in version 1.0.31 and when my phone is pluged in and everything looks good, then commend "adb devices" nothing shows up.
My question is, how can I get my phone visible in adb ?
PS. I have installed cm12 and tried to get back to stock rom and recovery, but in one second in middle on the instalation, power in my house stops and everything just turned off.
And now I have this problem. It looks exactly the same when I had USB debugging turned off in cm12 .. computer and htc sync could see my phone, but adb couldn't.
Any ideas ?
Regards,
Jeremi
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
riggerman0421 said:
ADB commands won't work in fastboot. Try using fastboot commands : "fastboot devices" and see if it shows up.
Click to expand...
Click to collapse
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
elcientifico said:
Use the command :
fastboot oem lock
And after run stock room ruu update.
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Device was already locked. Still the same problem.
I have to bypass "signature checking" .. but how ?
PLS can anyone help me ? :crying:
themonsterkk said:
PLS can anyone help me ? :crying:
Click to expand...
Click to collapse
What exactly are you trying to do and what is the exact message your getting?
FoxyDrew said:
What exactly are you trying to do and what is the exact message your getting?
Click to expand...
Click to collapse
Im stuck in fastboot. Ive got S-ON, Tampered, relocked, Security Warning.
I found somewhere here that I have to flash via fastboot RUU with mainver >= my current mainver.
But problem is:
c:\adbfastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.17.0506
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BFWW00545
(bootloader) imei: 352240067356325
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
As U can see above, version-main line is empty.
And after many tries flashing different roms, always the same info: FAILED (remote: 12 signature verify fail)
themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
From the screenshot you provided you are using the wrong command. To flash the recovery try this.
"fastboot flash recovery recovery_Stock.img"
Also the recovery_Stock.img file needs to be in your adbfastboot folder, and IIRC you need the bootloader unlocked to flash anything from fastboot.
themonsterkk said:
THX for fast reply!
okey it seems like I got it.
When I tried flash stock recovery i get info "signature verify fail"
How can I fix this ?
Click to expand...
Click to collapse
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
FoxyDrew said:
That's a recovery file your trying to flash. You need an UNLOCKED bootloader to flash a recovery.img file.
Click to expand...
Click to collapse
Ok, topic can be closed. I have done this.
But now, doesn't matter which custom rom I would flash, every time the same annoying problem with screen. My screen/touch doesn't work properly. I will say more. I can't do anything! Everything is poping out in one second..

[Solved] No OS, No Recovery HELP please HTC One (M8) Unlocked

I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
Are you S-Off? Is your device Developer Edition?
Sent from my HTC One_M8 using Tapatalk
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
How do I flash a new recovery?
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
AeroPeg said:
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
Click to expand...
Click to collapse
I can suggest couple of things, unlock the bootloader to install custom recovery and then you can flash any compatible rom,
Or to suggest some exact RUU, what's your device's exact model?
rawfire said:
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
Click to expand...
Click to collapse
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
AeroPeg said:
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
Click to expand...
Click to collapse
Considering your firmware, I would suggest you to try THIS RUU & flash...
Device info
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
try this one out, I'm sure it'll work.
Can't open
rawfire said:
try this one out, I'm sure it'll work.
Click to expand...
Click to collapse
Windows says invalid file, can't open.
7 zip can't extract either. I've tried both mirrors
Any other RUU suggestions?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Fastboot getvar all
ckpv5 said:
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Here's what I got when I typed fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
Update: just googled 0P6B12000 is Dev edition, my bad. Going to try easy method of installing the 4.16.1540.8 RUU. Thanks ckpv5. Will post with results.
AeroPeg said:
Here's what I got when I typed fastboot getvar all:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
4.16.1540.8 RUU stuck
ckpv5 said:
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
Click to expand...
Click to collapse
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now. Phone is showing just the silver htc logo, no progress bar or anything else.
Should I try flashing the 6.12.1540.4 firmware now? Thanks for the help so far ckpv5
Also, is the phone charging while connected to the computer & updating? Just asking since I can't see the battery percent (no OS) and don't want the phone to die while flashing.
AeroPeg said:
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now.
Click to expand...
Click to collapse
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To linked above for the HTC Sync Manager download page, install it as it will install the USB Driver, then uninstall the Sync Manager but leave the driver
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
ckpv5 said:
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To link above.
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
Click to expand...
Click to collapse
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
AeroPeg said:
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
Click to expand...
Click to collapse
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
SOLUTION - see ckpv5's 3 solutions
ckpv5 said:
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
Click to expand...
Click to collapse
Thanks a TON ckpv5. I followed your instructions & reinstalled HTC Sync Manager, then connected the cable to a USB 2.0 port instead of 3.0. The RUU method you originally suggested worked like a charm. I now have stock HTC software, stock recovery just like I wanted. I then did an OTA to the latest software. When I sell my device in a few days, I'll be sure to follow your tip and run the latest 6.12.1540.4 RUU to clear off all the old OTA files.
Many thanks again for your help - hopefully others will see the 3 solutions you posted.
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Thanks..
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT44LWM05174
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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.078s
ceylin45 said:
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Click to expand...
Click to collapse
Yes ... just follow what is written on top post above.

Update Android to 6.0 error

Hello. My problem is on picture. Please help.
http: // s23.postimg. org/5sizlitkb/DSC_0015.jpg
Please remove space.
Is the OTA file on the phone? Downloaded after getting the update notification?
I got an update and started downloading.
The system asked whether to install the update and clicked yes. And after 30 minutes, there was this error
I have exactly the issue too following OTA stock update
When speaking to HTC Support, they said that my IMEI showed up as a US device, even though the last ROM was definitely European stock. When going into Bootloader the following information is shown:
***Software Status Official***
***Locked***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OPENDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
HTC UK advised that they cannot help and pointed me in the direction of HTC US, but I cannot get through on their support chat pages, so currently have my phone stuck in this state. My phone is the 32GB version and upon further investigation I see that this was only released in the US.
I have tried to do a RUU update via http: // www .htc.com/us/support/rom-downloads .html#additional with the Unlocked/Developer version, but the RUU will not see the phone when in Recovery Mode, so fails to get along any further.
Any further assistance would be great so I can get my phone back!
Just to clarify, the European OTA stock update was downloaded, and then installed. The phone rebooted and started the install and completed the install. It then rebooted I assume to start up in Marshmallow, and this is when the error occurred and the Recovery screen was displayed. So the issue I suspect is a European ROM on a US device.
Thanks in advance
niloc said:
When speaking to HTC Support, they said that my IMEI showed up as a US device, even though the last ROM was definitely European stock. When going into Bootloader the following information is shown:
***Software Status Official***
***Locked***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OPENDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
HTC UK advised that they cannot help and pointed me in the direction of HTC US, but I cannot get through on their support chat pages, so currently have my phone stuck in this state. My phone is the 32GB version and upon further investigation I see that this was only released in the US.
I have tried to do a RUU update via http: // www .htc.com/us/support/rom-downloads .html#additional with the Unlocked/Developer version, but the RUU will not see the phone when in Recovery Mode, so fails to get along any further.
Click to expand...
Click to collapse
Go into bootloader-fastboot mode, and do fasboot getvar all, and post the output. Delete IMEI and serial number before posting.
I need this info to see what version the phone originally was, and for that matter what RUU will work.
If you have WWE (Euro) compatible CID and MID, you might try RUU linked here: http://forum.xda-developers.com/showpost.php?p=64869806&postcount=4
I can't personally vouch for this RUU, but I think several folks here have posted the link, and its probably legit.
Also, you need to run RUU in bootloader-fastboot mode, it will never work in recovery.
redpoint73 said:
Go into bootloader-fastboot mode, and do fasboot getvar all, and post the output. Delete IMEI and serial number before posting.
I need this info to see what version the phone originally was, and for that matter what RUU will work.
If you have WWE (Euro) compatible CID and MID, you might try RUU linked here: http://forum.xda-developers.com/showpost.php?p=64869806&postcount=4
I can't personally vouch for this RUU, but I think several folks here have posted the link, and its probably legit.
Also, you need to run RUU in bootloader-fastboot mode, it will never work in recovery.
Click to expand...
Click to collapse
Thank you for your prompt response - I'm not sure however to enter any commands in FASTBOOT, as when I select REBOOT FASTBOOT from the options, it just reboots the phone and I go back to the bootloader screen with FASTBOOT highlighted under the date and above the Vol Up Vol down insutructions. From your comments I suspect you are expecting the phone to go into another type of functionality
niloc said:
Thank you for your prompt response - I'm not sure however to enter any commands in FASTBOOT, as when I select REBOOT FASTBOOT from the options, it just reboots the phone and I go back to the bootloader screen with FASTBOOT highlighted under the date and above the Vol Up Vol down insutructions. From your comments I suspect you are expecting the phone to go into another type of functionality
Click to expand...
Click to collapse
Nope, if FASTBOOT is highlighted in red, its in fastboot mode, and no need to do anything else. Just connect the phone by USB (if not already) and do the fastboot command.
The only other bootloader mode would be HBOOT, which is not what we want.
redpoint73 said:
Nope, if FASTBOOT is highlighted in red, its in fastboot mode, and no need to do anything else. Just connect the phone by USB (if not already) and do the fastboot command.
The only other bootloader mode would be HBOOT, which is not what we want.
Click to expand...
Click to collapse
Sorry to be a pain, but as I have not flashed a ROM since the good old HD2 days, I'm a bit rusty and probably do not have all the tools on my laptop to do this. I only have HTC Sync Manager installed. Launching a command window in Windows and type: "fasboot getvar all" I get "fastboot is not recognised as an internal or external command". What additional tools do I need to install, as quickly looking around there seems to be a plethora of different thing for different setups
niloc said:
Sorry to be a pain, but as I have not flashed a ROM since the good old HD2 days, I'm a bit rusty and probably do not have all the tools on my laptop to do this. I only have HTC Sync Manager installed. Launching a command window in Windows and type: "fasboot getvar all" I get "fastboot is not recognised as an internal or external command". What additional tools do I need to install, as quickly looking around there seems to be a plethora of different thing for different setups
Click to expand...
Click to collapse
HTC Sync should be enough.
Do a search on Windows for fastboot.exe, once you find the folder where that is located, you will need to change directory in your command prompt to that same folder.
redpoint73 said:
HTC Sync should be enough.
Do a search on Windows for fastboot.exe, once you find the folder where that is located, you will need to change directory in your command prompt to that same folder.
Click to expand...
Click to collapse
Nothing found I'm afraid - downloaded "fastboot-win.zip" from https://www.htcdev.com/images/uploads/fastboot-win.zip?legal_license_terms=1, but when called from a command window I get "This program can't start because AdbWinApi.dll is missing from your computer", so looks like I only have one part of the jigsaw
niloc said:
Nothing found I'm afraid - downloaded "fastboot-win.zip" from https://www.htcdev.com/images/uploads/fastboot-win.zip?legal_license_terms=1, but when called from a command window I get "This program can't start because AdbWinApi.dll is missing from your computer", so looks like I only have one part of the jigsaw
Click to expand...
Click to collapse
You can find a couple good and simple installers if you use the XDA search function and search "easy adb".
Although, if you get Error 12 when running the RUU later, you may need to uninstall this.
niloc said:
Nothing found I'm afraid - downloaded "fastboot-win.zip" from https://www.htcdev.com/images/uploads/fastboot-win.zip?legal_license_terms=1, but when called from a command window I get "This program can't start because AdbWinApi.dll is missing from your computer", so looks like I only have one part of the jigsaw
Click to expand...
Click to collapse
I have found an ADB installer at http://forum.xda-developers.com/showthread.php?t=2588979 so have installed this and run the command to get all variable, but command window is just sitting at <waiting for device>. I have rebooted phone again back into bootloader, just to see if this would kick start the connection, but nothing. I have unplugged and plugged the USB cable again to try and get it to be seen, so scratching my head at the moment!
---------- Post added at 07:57 PM ---------- Previous post was at 07:52 PM ----------
niloc said:
I have found an ADB installer at http://forum.xda-developers.com/showthread.php?t=2588979 so have installed this and run the command to get all variable, but command window is just sitting at <waiting for device>. I have rebooted phone again back into bootloader, just to see if this would kick start the connection, but nothing. I have unplugged and plugged the USB cable again to try and get it to be seen, so scratching my head at the moment!
Click to expand...
Click to collapse
The phone is just not being seen by the laptop at all and does not appear in the Device Manager of Windows. I have tried it in different USB ports, but no difference....
Try to uninstall HTC Sync, and re-install.
redpoint73 said:
Try to uninstall HTC Sync, and re-install.
Click to expand...
Click to collapse
Uninstalled and reinstalled Sync Manager and rebooted laptop, but still Phone not being seen, so changed USB cable to voilà! So, back to answering your original question of the information of the origin of the phone:
(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:
(bootloader) imei:
(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!
finished. total time: 0.145s
i had the same problem as mentioned above. Downloaded official update as the phone sugested. Clicked install ... then restart instaling update and at the end error. Now it doesnt boot and goes directly into bootloader.
I restated into fastboot and in that pc finaly recognized mobile and instaled official RUU < RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 >
Installed and booted.. looks okay
(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:
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
Perfect - thank you shade550. That RUU worked a treat.
Thank you redpoint73, your patients and guidance was a god send and I could have not achieved any of this without you
niloc said:
Uninstalled and reinstalled Sync Manager and rebooted laptop, but still Phone not being seen, so changed USB cable to voilà!
Click to expand...
Click to collapse
Damn, I should have figured it was something simple like the cable. Its seems the simple, seemingly obvious stuff is most often the answer. So much so, I forgot to even consider it.
Glad you sorted it out. My pleasure helping, really.
Hi redpoint73, I'm still stuck with this problem. I don't understand how to install de RRU that you had post in the first page. My phone is manufactured in the UK.
I already installed the HTC Sync Manager, and the adb.
What's the next step for installing this? Sorry but I'm no quite good with this stuff.
sonoman87 said:
Hi redpoint73, I'm still stuck with this problem. I don't understand how to install de RRU that you had post in the first page. My phone is manufactured in the UK.
I already installed the HTC Sync Manager, and the adb.
What's the next step for installing this? Sorry but I'm no quite good with this stuff.
Click to expand...
Click to collapse
1) Connect phone to PC.
2) Boot phone to bootloader-fastboot mode
3) Run the RUU.exe, and it will walk you through the rest

htc m8 - bricked while updating ota stock marshmallow

While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
pauluthupm said:
I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Click to expand...
Click to collapse
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Solved : Unbrick HTC M* - Revert to Stock
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
Thank you for the help. fortunately i did find the solution. just the way u said only. I was in office and dint have access to xda in office. Let me also put what i have done.
pauluthupm said:
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
Click to expand...
Click to collapse
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Make sure u download the htc fastboot files: Google is ur friend.
Place the image in the same folder as the htc fastboot files are.
rename the file to 0P6BIMG.zip( remember not to add two zips at the end.,windows generally hides the extension
Now open ur command prompt.
naviagate to the htc fastboot folder , i my case, i put in c drive
so it would like c:\htc_fastboot_files
Now Voulme Down Button and then press the power button.
In my case i had to use Power+Volume up to reboot the phone . And the moment it rebooted i pressed just the vol down button.
So we would be in Bootloader. Now switch phone to fastboot mode.
Navigate using volume buttons and power button to enter.
in fast boot mode
bring up ur command prompt:
We are already in the fastboot file folder. like i mentioned before: c:\htc_fastboot_files
type fastboot get var all
look for this info: (bootloader) version-main: 6.12.401.4 ( This might be different case to case, according to this you can search for relevant ruu, just google with the version number firmware)
Now htc_fastboot oem lock ( To relock the bootloader)
htc_fastboot oem rebootRUU
htc_fastboot flash zip Firmware_xx.zip ( in my case its 0P6BIMG.zip)
Once the flash completes, you will have a window which says Flash complete. OKAY. Mind you it takes some time.
After this,
htc_fastboot reboot . Thats it. Phone will take quite some time to reboot and complete the process.
My phone was up and running from here. But in case of errors. You might want look down.
IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (don’t use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot (below this section you find CRITICAL errors, please observe):
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 24 android-info fail (means something wrong with android-info.txt in the zip)
- 32 header error (means the zip couldn't be read and unzipped properly)
- 41 Wrong Model ID (means it's not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap CID first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot in-between).
- 99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues.
- 130 wrong model ID (seems it's the same like 41, just that it shows in the FUU as 130.
- 155 seems to indicate different things. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match.
- 170 Check USB - FUU won’t run because of not working ADB.
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 24 "android-info fail" do:
- check that your ZIP isn’t some HTC OTA or anything thats got no android-info.txt - those cannot be flashed with fastboot flash zip nameof.zip command.
- check that your zip has a good MD5 and is not broken, check android-info.txt etc...
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn't help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
htc_fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
htc_fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn't brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definitely this means the ZIP is not signed - get an unmodified zip!
For “Error 130 wrong model ID" do:
- Please refer to Error Code 41/42.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn't work well currently.
NOT safe to reboot / Flash (partly) happened Errors (if you encounter one of them, DON’T reboot:
- 152 Image Error - Phone Screen shows a little triangle beside a full green bar
For “Error 152 Image Error" do:
- Error 152 is quite rare, have seen it only once with a friend’s phone and it aborted the flash nearly at the end. The flash was started by the FUU. We could resolve the matter by NOT rebooting the phone and flashing the zip again through a manual fastboot flash as outlined further up.
pauluthupm said:
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
redpoint73 said:
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
Click to expand...
Click to collapse
Yep. That's straight up stolen (copy/pasted) from @Sneakyghost's threads.
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
xunholyx said:
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
Click to expand...
Click to collapse
Yeah, hard to tell what OP is talking about, if they don't even get the name right.
Also completely unnecessary of him to clutter up the board by copy and pasting huge amounts of text when a link can be provided (or refer to a thread, if he can't link).
NEW HTC m8 on custom recovery
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
--------------------------------------------------------------
Hi redpoint, need your help.
i want to revert my htc m8 to stock marshmallow. i am currently running ,mi ui with twrp recovery.
i am posting getvar results below. i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? can u help me with which firm ware i should download and which stock recovery should i install ?
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
pauluthupm said:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
What's going on here, is this a different phone than what you listed in the first post?
pauluthupm said:
i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Click to expand...
Click to collapse
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
pauluthupm said:
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? 0
Click to expand...
Click to collapse
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
m8 revert to stock
redpoint73 said:
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
Click to expand...
Click to collapse
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
My device id belongs to India when i googled hence i m searching for these ruu. I wanted to try sunshine s off so that change the mid and cid to eu version and then try different ruu. Sunshine keeps giving me an error while running the initial tests it requires an non debuggable boot.img. So that doesnt help either.
do you require anymore info ? i can give u remote access if it requires.
PS: MIUI Rom is still working if i want to use my phone
pauluthupm said:
do you require anymore info ? i can give u remote access if it requires.
Click to expand...
Click to collapse
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
I had answered to your questions right below it. Did u mean i dint answer with details?
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
i have No clue how i found it. I googled lot of pages and somehow i found this this link. butyes i downloaded it from http://forum.gsmhosting.com/vbb/f48...-ruu-4-x-x-6-x-x-updated-19-3-2016-a-1940130/
I am not sure its signed or not. to be honest i have no clue.
answers to what you had asked?
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
Originally Posted by redpoint73
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
pauluthupm said:
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery.
Click to expand...
Click to collapse
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
pauluthupm said:
Now i tried flashing that ruu downloaded from gsm developers. but i failed with it.
Click to expand...
Click to collapse
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
How big is the file (MB)?
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
pauluthupm said:
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
Click to expand...
Click to collapse
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.720.xx specifically refer to your version M8 (CID and MID).
EDIT: fixed a typo, the number in red in the last line should read 720.
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
redpoint73 said:
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
HTML:
[QUOTE]Yes i renamed it to 0P6BIMG.zip
[/QUOTE]
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
remote: 12 signature verify fail)
Execution time is 115(s)
Click to expand...
Click to collapse
How big is the file (MB)?
1.66 GB
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.709.xx specifically refer to your version M8 (CID and MID).
Click to expand...
Click to collapse
Can you help me with the link i should download ? the correct ruu for my m8 ?
i can post the getvar values here if its of any help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
pauluthupm said:
Yes i renamed it to 0P6BIMG.zip
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
Click to expand...
Click to collapse
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
redpoint73 said:
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Bootloader is currently unlocked. Since you said i can run ruu in custom recovery also. I went and reinstalled custom recovery twrp 2.7 from Hasoons All in one Kit.
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
Click to expand...
Click to collapse
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
Click to expand...
Click to collapse
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
htc_fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
Click to expand...
Click to collapse
pauluthupm said:
Being very honest, i have very little knowledge, its a new learning for me.
Click to expand...
Click to collapse
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
pauluthupm said:
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Click to expand...
Click to collapse
It won't work. You need version numbers with 720, not 709.
I see in my last post, I said you needed 720 (which is correct) then a typo which implies you need 709 (not correct). So there may have been some confusion or conflicting info there.
Also, that version is too old (software number 1.54). You can only run RUU with equal or greater version than the firmware on the phone, which in your case is 4.xx.
pauluthupm said:
]
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
Click to expand...
Click to collapse
RELOCKED is the important part. Not sure why you got in error , but it looks to be properly relocked to run RUU.
Was it RELOCKED or UNLOCKED when you tried the RUU 6.20.709.2 and got Error 12: Signature Error?
redpoint73 said:
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
I should have. Now i regret for messing up the phone
Click to expand...
Click to collapse
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Absolutely learned it. I wouldnt want mod any phones anymore. Too much of headache, since am i am noob.
Click to expand...
Click to collapse
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
Click to expand...
Click to collapse
In fact i did have twrp back up. bt i had kept this sd card in my wallet. I broke the sd card by mistake. thats how i lost it.
OP cannot install RUU 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2 on his current firmware version.
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038​He needs to install the signed 6.15.720.2 firmware first before install the RUU zip
Easier method is - install RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe
Download from : http://androidruu.com/?developer=M8
then OTA to 4.18.720.10 then later to 6.15.720.2
Or restore 4.18.720.10 backup & install 4.18.720.10 stock recovery (yeah .. skip a version) then OTA to 6.15.720.2
Download from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck

Categories

Resources