Soft Brick No OS - One (M8) Q&A, Help & Troubleshooting

Hello XDA,
I have an HTC one m8 in my possession which i am trying to unbrick but i'm having some issues.
The phone has custom recovery Philz
I have no SD card available to me at the moment
I have relocked the bootloader to try and run the RUU 'RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4'
installer as part of my efforts to unbrick, but this doesn't work, the RUU installer gets stuck at 0% while 'Sending'.
Any help would be much appreciated

Not enough info. Do a fastboot getvar all, and post the results (be sure to delete IMEI and serial numbers, as these are private info).
In particular, need (at a minimum):
CID
MID
s-off or s-on
firmware (main) version
hboot number
radio number
Bootloader status (locked, relocked, unlocked)
Original version (CID, MID) if those numbers have been modified
Also, did you try the RUU just once, or multiple times? A number of folks have reported it hanging on sending, but then it will run properly on a subsequent attempt.

Thanks for the reply, here is all the information i could acquire.
***TAMPERED***
***RELOCKED***
***Security Warning***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have tried running the RUU multiple times

Redragonrc said:
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
I have tried running the RUU multiple times
Click to expand...
Click to collapse
The RUU you stated in the top post won't work (its the RUU for the Developer's Edition). The RUU needs to match your CID and MID, meaning you need the RUU for the Euro version, which doesn't have Marshmallow yet.
Best bet is to run the Lollipop RUU for the Euro version (4.16.401.10) which can be found here: http://forum.xda-developers.com/showthread.php?t=2701376

I have run the 4.16.401.10 RUU.exe but it just gets stuck at Updating...(0/7) Sending...
I have done done the prerequisites for running the RUU:
disabled antivirus, updated HTC drivers, run the RUU as admin
I checked that i have USB data communications with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT43JWM06196 fastboot

Redragonrc said:
I have run the 4.16.401.10 RUU.exe but it just gets stuck at Updating...(0/7) Sending...
I have done done the prerequisites for running the RUU:
disabled antivirus, updated HTC drivers, run the RUU as admin
I checked that i have USB data communications with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT43JWM06196 fastboot
Click to expand...
Click to collapse
Hi ,can you try on another pc/ laptop

Redragonrc said:
I have run the 4.16.401.10 RUU.exe but it just gets stuck at Updating...(0/7) Sending...
Click to expand...
Click to collapse
Try running it again. RUU is known to hang from time to time, then work on subsequent attempts.
If it still doesn't work, try another PC, as suggested above. Win7 and USB 2.0 have the best chance of success.
Or you can download the zip version, rename to 0P6BIMG.zip and put it on the phone. Reboot to bootloader, and it should install.

bombo_b said:
Hi ,can you try on another pc/ laptop
Click to expand...
Click to collapse
Hi,
I just tried it on another computer and the same result.

redpoint73 said:
Try running it again. RUU is known to hang from time to time, then work on subsequent attempts.
If it still doesn't work, try another PC, as suggested above. Win7 and USB 2.0 have the best chance of success.
Or you can download the zip version, rename to 0P6BIMG.zip and put it on the phone. Reboot to bootloader, and it should install.
Click to expand...
Click to collapse
I managed to reach 1/7 through the RUU.exe and gave me a 155 error.
I don't have a Windows 7 computer avaliable to me only Windows 10.
I could try buying an SD card, putting the rom onto the SD card, unlock the bootloader and run the custom recovery again and try to install the from from the SD card?
It also appears there is TWRP and Philz recovery on this device, could this be the cause of any problems?

Redragonrc said:
I could try buying an SD card, putting the rom onto the SD card, unlock the bootloader and run the custom recovery again and try to install the from from the SD card?
Click to expand...
Click to collapse
You can do that, but you'd have to use a Kitkat ROM, as your firmware is (old) Kitkat. And you would be stuck on the KitKat ROM until you updated the firmware.
I think its better to get the RUU to work, such as adb push the RUU zip to the phone's internal storage, and run in bootloader.
Redragonrc said:
It also appears there is TWRP and Philz recovery on this device, could this be the cause of any problems?
Click to expand...
Click to collapse
Its one or the other, you can't have both (TWRP and Philz) on the phone at the same time.
Do you mean, is it the cause of RUU not running? NO.

Hello,
The RUU.exe has made some progress and now hangs at 1/8 consistantly.
redpoint73 said:
I think its better to get the RUU to work, such as adb push the RUU zip to the phone's internal storage, and run in bootloader..
Click to expand...
Click to collapse
I have tried to adb sideload the rom but i just get 'cannot read'

Redragonrc said:
could you explain how i can do this? thanks
Click to expand...
Click to collapse
Actually, I'm realizing (reading in another thread) that the RUU zip needs to be on a removable SD, not on internal storage (haven't actually done it this way, I always use the RUU.exe).
From what I understand, put the 0p6bimg.zip on the SD card (as you mentioned, you will need to buy one) then boot into bootloader, and it will install.
Another alternative, you can apparently also fastboot flash the RUU:
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
---------- Post added at 04:35 PM ---------- Previous post was at 03:54 PM ----------
Redragonrc said:
I have tried to adb sideload the rom but i just get 'cannot read'
Click to expand...
Click to collapse
A ROM or an RUU? What file exactly?
Post a screenshot of the adb commands and responses, if you can.

Hi again,
Went and got myself and SD card and put cm13 on it from which i've loaded the rom and got myself a working phone now.
I went ahead an ran the RUU after installing cm13 and the RUU ran perfectly.
It seems using the SD card was the best option for me.
Thanks Redpoint73 for all the help so far.
P.S it seems my m8 is a retail version as the stock rom i installed has a demo application that wipes the phone everyday, but this is an easy solution as i will just install another custom os or something. i just can't use stock. :<

Redragonrc said:
P.S it seems my m8 is a retail version as the stock rom i installed has a demo application that wipes the phone everyday, but this is an easy solution as i will just install another custom os or something. i just can't use stock. :<
Click to expand...
Click to collapse
What "stock ROM" are you referring to?
The ROM installed by the RUU you stated in Post #1 shouldn't be doing this.

Related

No OS installed. Can't transfer files.

Alrighty, so I was rooting my Htc m8 and installing a rom called android revolution and something went wrong. Now my phone won't go past the htc bootscreen or would get stuck in a loop.
On bootloader mode I can see instead of S-Off, I see Tampered.
I'm currently on TWRP 2.7.0.2 and while trying to fix this, i erased cashe and wiped and on doing so, I wiped the OS. So when I try to reboot, it says no OS installed.
I read online on how to fix this and it said to install another rom over it, that way it can boot into the rom. However, I can't transfer any files onto my phone while its in recovery mode.
I checked how to transfer files and tried using adb push. That didn't work either. When i used the command prompt and wrote 'adb devices' It said ''list of devices attached'' without anything underneath where there shouldve been a serial number. So when I wrote adb push, there were no devices attached.
I tried to reinstall adb drivers twice and I definitely see its there.
Am I wrong somewhere? How do I fix my phone? Is there an easier way to transfer files onto my phone?
I can suggest to flash the latest twrp recovery. It mounts the sdcard as a mtp and as a disk drive (in my case) or get an sdcard with a reader and put a rom on it via the pc and insert it in the phone and flash the rom
I don't really have an sdcard or reader. I'll try the new twrp but how is it any different than this? Will it help me transfer more easily?
update: I tried adb sideload with two roms, but of them loaded to 100% on cmd prompt, but on my phone it says:
ADB sideload complete
Failed
update 2: when flashing the recovery, it said:
waiting 'flash' ...<bootloader> signature checking...
FAILsignature verify fail
FAILED <remote: signature verify fail>
Shiverfire said:
I don't really have an sdcard or reader. I'll try the new twrp but how is it any different than this? Will it help me transfer more easily?
update: I tried adb sideload with two roms, but of them loaded to 100% on cmd prompt, but on my phone it says:
ADB sideload complete
Failed
update 2: when flashing the recovery, it said:
waiting 'flash' ...<bootloader> signature checking...
FAILsignature verify fail
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
hmm can you post the outcome of :
fastboot getvar all (delete the imei and serial before posting it)
(bootloader) version-baseband: 1.16.21331931.LA11
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ----------------------------
(bootloader) imei: ------------------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I'm missing the bootloader info, what hboot is the device on ? (3.16/3.18/3.19) CWS thats at&t device right ?
this is exactly what it says on the hboot mode:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.1621331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014, 16:06:33.0
and yes, its an at&t, but im not in the usa.
The latest twrp probably doesn't work because of the lower (3.16) hboot. Adb sideload should work or get a sdcard that's the easiest way
Mr Hofs said:
The latest twrp probably doesn't work because of the lower (3.16) hboot. Adb sideload should work or get a sdcard that's the easiest way
Click to expand...
Click to collapse
adb sideload didnt work like I said. I just got an sdcard. Trying that now. WIll let you know.
Shiverfire said:
adb sideload didnt work like I said. I just got an sdcard. Trying that now. WIll let you know.
Click to expand...
Click to collapse
Ah yes i know that it didn't work here in your case but in general it should work. Not sure as i never needed it myself
I tried flashing two different roms with an external sd card and it failed almost immediately.
Is there anything else I can do? Does anyone have a backup I can restore to?
Shiverfire said:
I tried flashing two different roms with an external sd card and it failed almost immediately.
Is there anything else I can do? Does anyone have a backup I can restore to?
Click to expand...
Click to collapse
What's the error ? What failed ? You can't flash the newer roms due to your low hboot.
Ow and there is a great backup thread stickied in the general section. It's worth a lot to have careful read there !
here is what it says on my twrp:
Updating partition details. . .
Full SELinux support is present.
Installing '/external_sd/rom.zip' . . .
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Verifying zip signature. . .
E:Zip signature verification failed: 1
Error flashing zip '/external_sd/rom.zip'
Updating partition details. . .
Failed
ok so can you suggest what rom I use? and what update of the rom that will work on my hboot? Anything will do, I just need to get my phone running.
After that, I can try updating the hboot so the newer roms work.
For reference, the roms I was using Android Revolution (the Lolipop verision) and Skydragon.
You got to get your hands on a older kitkat based roms. When you go for a rom based on 1.54.xxx you are good to go.
Mr Hofs said:
You got to get your hands on a older kitkat based roms. When you go for a rom based on 1.54.xxx you are good to go.
Click to expand...
Click to collapse
ok im currently downloading this:
Download Android Revolution HD 22.2
Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9)
In the meantime, do you have any idea how to update my hboot so the newer roms work? Is the Tampered bar have to do with any of this?
Sorry for double posting, but I used the sdcard to download a kitkat rom and it worked. The bootscreen takes about 5-10 minutes and still has the following error:
This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission
Failure to comply may
lead to legal action
however, the phone works fine. Thank you!

HELP PLEASE HTC ONE M8 stuck on bootloader when flashing stock rom

Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: --------
(bootloader) imei2: Not Support
(bootloader) meid: --------
(bootloader) product: m8_whl
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Someone can help me ?
Someone can help me ?
kimpak said:
Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: --------
(bootloader) imei2: Not Support
(bootloader) meid: --------
(bootloader) product: m8_whl
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Click to expand...
Click to collapse
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Mr_Jack_Frost said:
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Click to expand...
Click to collapse
The OP is already in bootloader, and stuck there.
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
bombo_b said:
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
Tho latest Ruu should already contain the 3.19 Hboot
bombo_b said:
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
redpoint73 said:
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
Click to expand...
Click to collapse
Error 155 is usually fixed by relocking Bootloader. Since the phone is in a funny state I would advise putting all chances on your side. Dont worry if the logic says S-off doesnt need BL relocked , you just need every chance to flash Stock ruu back to the phone
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
Click to expand...
Click to collapse
All right tout marche bien
kimpak said:
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
Click to expand...
Click to collapse
kimpak said:
All right tout marche bien
Click to expand...
Click to collapse
Good to hear that it worked for you.
How do you saw that my phone is for sprint version ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
How do you saw that my phone is for sprint version ?
Click to expand...
Click to collapse
(bootloader) product: m8_whl
m8_whl is Sprint device
m8_ul is GSM device
Boot Loader Loop, Unlocked, S-Off, Rooted HTC M8 Tmobile
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
---------- Post added at 05:02 PM ---------- Previous post was at 04:49 PM ----------
JamesM8 said:
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
Click to expand...
Click to collapse
**** I just realized it would be more appropriate to create a new thread for my problem rather than intruding on this mans problem, please see the One (M8) Q&A, Help & Troubleshooting. And respond there*****

[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.

Need an alternative for Sunshine to S-Off HTC M8

Okay, I'm kinda stuck here.
Used to have Cyanogen Mod, then upgraded to Venom. Wifi stopped working, as well as cellular connectivity.
According to FAQ, I need the newest firmware. Which I downloaded. Copied it to SD, renamed it 0P6BIMG.zip, booted to fastboot. Image not accepted.
Obviously it's not signed, and since I have S-ON, it's not being accepted. Google / Forum search suggested firewater, now sunshine. Firewater seems to be obsolete, so I installed sunshine - but changing S-ON to S-OFF failed. Installing a signed firmware, on the other hand, requires me to relock my bootloader, so I tried that next.
For that I'm required to use adb / fastboot command line, so I installed Android SDK. But when I start with "adb devices", it returns my device name with the status being offline. Google results suggested updating the SDK, checking USB settings etc etc.
Since it seemed I couldn't upgrade the firmware, I decided to try another ROM (Revolution HD), then I tried going back to Cyanogen, but now the install fails due to an error in the installer binary, if i recall the error message correctly.
Can someone point me to a solution how to:
- upgrade my firmware to the latest version or
- install another ROM which will work with my obviously outdated firmware or
- get my device to respond to adb / fastboot (get it online)?
I've by now read so many different tutorials I get the feeling the more I read, the more confused I am. It's not good for my sanity if the number of open browser tabs exceeds 12. Sigh.
The best option for you is the ruu. Find the ruu for your device needs to be the same version as the one your bootloader shows or newer ,older ones don't work.
Sent from my HTC One_M8
---------- Post added at 06:18 PM ---------- Previous post was at 06:17 PM ----------
You can run the ruu when the phone is booted in bootlader. Windows 7 works best for me. Good luck.
Sent from my HTC One_M8
grigoriisi said:
The best option for you is the ruu.
Click to expand...
Click to collapse
He can't run the RUU unless he relocks the bootloader first, which is part of the issue that was described.
But your point that an RUU will update the firmware is correct, and that the RUU or firmware (signed) can only be run if it matches the CID (correct CID, and same or newer version that what is on the phone - meaning no "downgrading").
---------- Post added at 10:40 AM ---------- Previous post was at 10:36 AM ----------
Wurmfutter said:
Since it seemed I couldn't upgrade the firmware, I decided to try another ROM (Revolution HD), then I tried going back to Cyanogen, but now the install fails due to an error in the installer binary, if i recall the error message correctly.
Can someone point me to a solution how to:
- install another ROM which will work with my obviously outdated firmware or
Click to expand...
Click to collapse
Impossible to troubleshoot this problem (flashing a custom ROM) if we don't know your current hboot number, carrier version, TWRP version, ARHD version.
---------- Post added at 10:44 AM ---------- Previous post was at 10:40 AM ----------
Wurmfutter said:
Installing a signed firmware, on the other hand, requires me to relock my bootloader, so I tried that next.
For that I'm required to use adb / fastboot command line, so I installed Android SDK. But when I start with "adb devices", it returns my device name with the status being offline. Google results suggested updating the SDK, checking USB settings etc etc.
Click to expand...
Click to collapse
To use, adb, the phone needs to be booted in OS (or alternatively in recovery). So if you are trying in bootloader or otherwise not booted into OS, this may be why its showing "offline".
However, for relocking the bootloader, you want to use fastboot, which is slightly different from adb.
Reboot to bootloader, select "fastboot" (if its not already selected) using the vol buttons, then confirm the selection with the power button. Then try the fastboot command:
fastboot devices
If the device ID is returned, and online, you relock the bootloader with the command:
fastboot oem lock
After that run the signed firmware or RUU, but either way, it needs to match your CID and MID, and can't be a lower version than what is on the phone (no "downgrading").
If you give us details on your CID and what you are trying to flash, I can see if its appropriate or not.
Thanks everyone for helping, but I solved it already. After flashing an older CM version and setting up android tools on an ubuntu system, i could finally connect and issue commands via adb / fastboot - before that, i never got the phone asking if i trust the computer for debugging.
I then wiped system, cache and data, flashed the newest twrp recovery and was finally able to install the latest CM 13 nightly, which works fine so far.
However, if someone could tell me how to s-off, it would still be appreciated.
[email protected]:~/Downloads$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.166.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP110
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
Sunshine is the only option you have (at least for a reasonable price). All other methods are
A: nearly impossible
B: way to expensive
Wurmfutter said:
Firewater seems to be obsolete, so I installed sunshine - but changing S-ON to S-OFF failed.
Click to expand...
Click to collapse
You need stock (or close to stock) ROM for sunshine s-off. I believe ARHD will work, not sure about Viper, CM13 no way.
Firewater stopped being supported by its developers over a year ago. Its an online service, so it hasn't worked since the dev support ceased. So, yes, its obsolete (no longer works).
I used sunshine to s off today and device war running SkyDragon-M8_&_DesireEYE-1.6.5 it worked perfectly, how did sunshine fail to S off it runs all kinds of test to guarantee S off before you purchase it just curious ?????
gazleyp said:
how did sunshine fail to S off it runs all kinds of test to guarantee S off before you purchase it just curious ?????
Click to expand...
Click to collapse
Sunshine app probably told the OP their device was "not compatible" (due to custom ROM, but the app doesn't really detail that) after performing the checks you mentioned. I assume that is what the OP means by "failed".
redpoint73 said:
Sunshine app probably told the OP their device was "not compatible" (due to custom ROM, but the app doesn't really detail that) after performing the checks you mentioned. I assume that is what the OP means by "failed".
Click to expand...
Click to collapse
Argh now i understand his explanation, now you have cleared it up lol

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