try to root htc m8 i ahve red text on screen - One (M8) Q&A, Help & Troubleshooting

when i tery root and s-off let the info and picture to explan more " sory for my english"
this all info
:\Program Files\Minimal ADB and Fastboot>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:
bootloader) version-misc: PVT SHIP S-ON
bootloader) serialno: SH469WM04000
bootloader) imei: 357871051160565
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
ll: Done!
inished. total time: 0.137s
​and the phone now like this
​on phon screnn
software status modified
m8-ul-pvt ship- s-on
hboot-3.19.0.000
radio-1.29.214500021.126
opendsp-v51.2.2.00593-m8974-f001015
os- ---------------------------nothing here
emmc-boot 2048mb
dec 17 2015,14.15.48.27717

So the info on the bootloader screen is actually in red? And the phone won't boot to OS?
What exactly did you do when trying to root. Describe, step by step, and in as much detail as possible, with file names, versions, etc. How far did you get, what worked, where did you get stuck, with specific results, error messages, etc.
OS number blank usually means you used a really old and obsolete version TWRP.

redpoint73 said:
So the info on the bootloader screen is actually in red? And the phone won't boot to OS?
What exactly did you do when trying to root. Describe, step by step, and in as much detail as possible, with file names, versions, etc. How far did you get, what worked, where did you get stuck, with specific results, error messages, etc.
OS number blank usually means you used a really old and obsolete version TWRP.
Click to expand...
Click to collapse
thanks for replay
i am not sure what exactly happend i receved th phone like as say befor
but once power on the phone appear red text on down screen and stop
i am enter the recover
1- s-off
2- twrp is installed
3- i use androiad one toolkit and relock again s-on
4- wipe phone
5- now cannot enter recovery again
6- can enter fastboot
7= itry to flash the phone by ruu more an version but all trying is Failed

The steps you posted cleared up the issue, quite a bit. However, I have some additional questions about these steps, below in red font:
amira77 said:
but once power on the phone appear red text on down screen and stop
i am enter the recover
1- s-off how exactly did you try to s-off?
2- twrp is installed Did you also try to root at this point? Did you get stuck (no OS)?
3- i use androiad one toolkit and relock again s-on Why did you relock the bootloader?
4- wipe phone
5- now cannot enter recovery again
6- can enter fastboot
7= itry to flash the phone by ruu more an version but all trying is Failed You phone will only run one RUU that matches your CID/MID, you can't just run any one you want.
Click to expand...
Click to collapse
Being stuck in fastboot is an expected result of relocking the bootloader, as it expects RUU to be run.
Additionally, you should stop using the toolkit. It hasn't been updated for over 2 years, and therefore contains files (TWRP and SuperSU) which are horribly obsolete, and will cause multiple problems. The OS number being blank is one known issue with old versions TWRP (old versions TWRP are also not compatible with your phone's current firmware).
The toolkit doesn't accomplish anything, that can't be done with simple fastboot commands. And if you can't handle fastboot commands, you should not be trying to modify the phone, in the first place.

redpoint73 said:
The steps you posted cleared up the issue, quite a bit. However, I have some additional questions about these steps, below in red font:
Being stuck in fastboot is an expected result of relocking the bootloader, as it expects RUU to be run.
Additionally, you should stop using the toolkit. It hasn't been updated for over 2 years, and therefore contains files (TWRP and SuperSU) which are horribly obsolete, and will cause multiple problems. The OS number being blank is one known issue with old versions TWRP (old versions TWRP are also not compatible with your phone's current firmware).
The toolkit doesn't accomplish anything, that can't be done with simple fastboot commands. And if you can't handle fastboot commands, you should not be trying to modify the phone, in the first place.
Click to expand...
Click to collapse
okay thanks for replay again
can help me by send ruu compatible with this phone?
iwas use this ruu befor
1- RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
2-GQbYQWPsDSOxW4-6y5SiHg/1499132695/24369303960687057/0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
The first stopped at 3%
And the second did not accept the phone
write on the back of phone 0P6B100

amira77 said:
okay thanks for replay again
can help me by send ruu compatible with this phone?
iwas use this ruu befor
1- RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
2-GQbYQWPsDSOxW4-6y5SiHg/1499132695/24369303960687057/0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
The first stopped at 3%
And the second did not accept the phone
write on the back of phone 0P6B100
Click to expand...
Click to collapse
The 1st RUU you listed won't work. It's for the AT&T version M8.
The 2nd one should work, but I don't know what you mean when you say it did not accept the phone. What exactly happened, and what was the error message? It needs to be flashed in fastboot-RUU mode, and with HTC fastboot drivers. What commands did you use to flash it? Cut and paste the command prompt inputs and outputs.
Also, I asked a number of questions in my last post in red font which you either ignored or missed. Please answer them, as it would help me understand what you did, and why.

Related

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.

bricked??

Hello, i am having a big trouble here
I was trying to format my phone but the bootloader's screen does not appear, it's been a while, when I enter the bootloader screen is just black, but the options work , I entered on recovery screen and went wipe, ticked all the options and I wipe , now my phone does not show anything, only black screen.
When i press power+up for 15 seconds, the cell shakes, i can flash recovery using fastboot by cmd, i can use anything with fastboot, but if i try something with adb, it says that i dont have adb devices. Can i solve my problem using fastboot option? i already flash a recovery by fastboot, but i cant enter on recovery, i can enter on fastboot reboot-bootloader for example.
Someone can help me plz?
Thx for attention. And sorry for bad english hehehe
Tirania_br said:
but if i try something with adb, it says that i dont have adb devices.
Click to expand...
Click to collapse
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
redpoint73 said:
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
Click to expand...
Click to collapse
thx, i found a RUU for my phone but very old, and found another current version here, but not for my version.
i have s-off on phone, these the information
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) cidnum: HTC__621
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
thx for help
Tirania_br said:
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Click to expand...
Click to collapse
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Tirania_br said:
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
Click to expand...
Click to collapse
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
redpoint73 said:
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
Click to expand...
Click to collapse
Hi, before i do all steps i want to know if i will do everyting ok
my cell's information again
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Tirania_br said:
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Click to expand...
Click to collapse
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
redpoint73 said:
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
Click to expand...
Click to collapse
thank you! i am almost there!
now the steps i have to do:
adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
adb reboot bootloader
fastboot getvar all //see if change mid
fastboot fastboot reboot-bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot getvar all //see if change cid
fastboot oem rebootRUU //need do this? if my Ruu is .exe
Double-click the file and run it as any other executable program. Follow the instructions by the program.
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
there is a command to do this with fastboot?
Tirania_br said:
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
Click to expand...
Click to collapse
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
redpoint73 said:
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
Click to expand...
Click to collapse
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Tirania_br said:
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Click to expand...
Click to collapse
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Tirania_br said:
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Click to expand...
Click to collapse
First .. your device is not a CDMA device, it is a GSM.
What you can try to fix that bootloader with black screen ... flash full signed 6.20.709.2 firmware.zip.
You can get the full signed firmware in my thread (post #5) : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

M8 stop booting

My HTC M8 stop booting when appears the white screen with HTC One. I can boot with power + down volume. I unlocked and locked it again. Before all this issue, I had to dry the phone. What can I do? Best regards, Guillermo
guillote4552 said:
My HTC M8 stop booting when appears the white screen with HTC One. I can boot with power + down volume. I unlocked and locked it again. Before all this issue, I had to dry the phone. What can I do? Best regards, Guillermo
Click to expand...
Click to collapse
If you relocked the bootloader, then stuck on HTC logo screen and no OS is normal and expected. Relocking the bootloader expects RUU to be run.
You need to provide more info on what has occurred (sequence of events), and what you did exactly so far:
- "dry the phone" means it got wet, did you drop it in water? Did it fail to boot after that?
- What was the intent of unlocking the bootloader? What else did you do with it unlocked? Did you install custom recovery TWRP, root, or anything else, was it successful (give in detail, the exact results of each step).
- What was the intent of relocking the bootloader?
-Yes, it fail after drop in water
-First I tried to root and I unlock
-Then I tried to install a RUU, and relock
-I tried to install a TWRP but I get an error messaje
-I run fastboot getvar all and this is the result:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-cpld: None
version-microp: None
version-main: 6.20.502.5
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.017s
My comments/questions below in red font:
In general, you need to give a lot more details and a lot more info.
guillote4552 said:
-Yes, it fail after drop in water What do you mean "fail"? No OS, but you can get into bootloader (I would assume so, if you were then able to unlock bootloader).
-First I tried to root and I unlock So you successfully unlocked the bootloader? Installed TWRP? Then what?
-Then I tried to install a RUU, and relock What RUU (exact version number of file name)? What happened when you tried to install? Success or fail? Did you get error message? If so, what was the error message.
-I tried to install a TWRP but I get an error message What was the error message? You can't install TWRP with a locked bootloader. What are you going to try once you install TWRP?
Click to expand...
Click to collapse
Failed: once wet, nothing worked. I let it dry for a month. Loaded battery, gave me access to fastboot. Its boot stopped.
-Bootloader: effectively once dry I can access. I figured a good way was to install the OS. And I tried to root it. First I unlock it. Then I tried to load TWRP without success. I do not remember the message, sorry it happened a weeks ago.
-I send the RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined, no success
-I know how to follow instructions; I forgot about error messages, I got tired
THANKS
guillote4552 said:
-I send the RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined, no success
I forgot about error messages, I got tired
Click to expand...
Click to collapse
It's the correct RUU. So run it again, and tell us what the error message says. Can't troubleshoot, if you don't give us the required info.
ok. Could you please remember me the steps / commands I have to follow? tks!
guillote4552 said:
ok. Could you please remember me the steps / commands I have to follow? tks!
Click to expand...
Click to collapse
Did you try to run the exe format RUU on a PC, or otherwise (zip file via fastboot, or SD card method)?
- I run the RUU, until in the PC appeared severals messages. like updating ... and at the end message like congratulations, your phone is ready ...
-the phone displayed severals black screens with a green bar indicating status ...
-then its boots, i saw att logo, then htc one white screen ... I left the phone three hours ... nothing changed
- no one error message
-nothing had changed = remain the white screen with htc one
RUU messages consist of each partitions attempting to be flashed. Did any partitions indicate failure, or did they all succeed?
Either way, since you ran the RUU, and the phone still won't boot, you likely have some hardware failure due to the water damage. Software isn't going to fix this.
none error messajes during install and finished with a congratulations, "now you can use your phone"
can i do a test to know if there are hardware damage?
guillote4552 said:
can i do a test to know if there are hardware damage?
Click to expand...
Click to collapse
Not a test that I know of for that. Really, based on the fact there was water damage, and you did RUU (which writes all software/firmware partitions to stock) installed, but hasn't fixed the issue, to me means a hardware problem is very likely.
so that it RIP, what a pity

Can't revert HTC One M8 to stock

I received an unlocked HTC One M8 (US, works on AT&T, not Harmon Kardon), factory reset, never been modded. Because it ran Android 6.x, I was concerned that it wasn't as secure as it could be, so I researched how to install the newest Android possible. I found many articles on these forums, guides from 2014 all the way to 2016. I didn't (and still don't) know enough to tell the difference between a good tutorial and a bad/outdated one. I saw that some tutorials were edited to reflect new mods, but now that I have read even more, I suspect that even those updated ones are now obsolete.
My problem is that I installed Resurrection Remix with v7.1.2, along with pico Open Gapps, and it won't let me install several apps like Chrome or even YouTube. I have decided that I don't want a newer ROM and I would rather just revert to stock. I have been attempting to revert to stock for the last three or four days, and I have spent many hours researching and reading (mostly this site...go figure), but so far I have not accomplished anything.
Current information about the phone: I did not make a backup (I've had little success doing this over the years on Android phones), I unlocked the bootloader with the HTC unlock code.bin file, the phone has S-ON and has not been rooted. In fact, I've tried SuperSU and Sunshine and neither worked. I have TWRP 2.7.1.0 installed. I have drivers from HTC Sync, but I also installed the Android Studio, along with some utilities that come with it. I have attempted the RUU from HTC (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4) and it always says that there was an error.
I have attempted several times to change the CID, but only because a tutorial told me to. I assume that it was changed when I installed the Remix mod. I have no idea what it should be. I have attempted to install firmware as well, both with the adb method and by copying it to the SD card and renaming it for bootloader, but both options fail. The adb method fails with...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
...and the SD card method thinks for a bit, then says "press power to reboot" in the same type of text as the bootloader text.
I am only a little familiar with adb and fastboot, so please, be gentle. If you list commands, I will use them without even thinking, like how Ron Burgandy reads everything on the teleprompter.
Please help.
Here's the getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!
speedee39 said:
Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Hi,
no you did not post in the wrong forum. This section is not that active but there are still a handful of people visiting and trying to help.
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.
maultasche said:
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Click to expand...
Click to collapse
The guide I found for reverting to stock said to change to the super CID (fastboot oem writecid 11111111). I only did that because I thought that it was the "right way" to do this. But if the CID can't be changed unless the phone is s-off, then it must still be stock, because I doubt that I've ever achieved s-off while flashing a different ROM.
maultasche said:
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Click to expand...
Click to collapse
Yes, I attempted the Sense stock because the tutorial told me to and also because that's what is listed on HTC's website. I don't want to go to Sense, just thought that I was supposed to. So you're saying that the phone is a Google Play Edition? I'll need to look that up.
maultasche said:
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Click to expand...
Click to collapse
Thank you for that, I didn't know. I'll get it. One question that I've never found the answer to is, if I installed TWRP to change the ROM, what is the stock recovery image? Or, is it bad to simply leave TWRP installed? I have no plans to sell the phone.
maultasche said:
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.
Click to expand...
Click to collapse
I think I did this correctly. Here's what I found through the shell:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p45 1032088 853196 178892 83% /system
Once I started looking this up, I found a post on XDA about GPe and different partition sizes. I'll check for GPe ROMs now. Do I need any other files besides that and the updated TWRP? Is the order to install a newer TWRP, then flash the GPe ROM, and then relock the bootloader?
I noticed that the bootloader has a persistent message about it being relocked and **WARNING**. Is there a way to clear the warning flag? One of the tutorials that I was following listed several shell commands to do this. I'm going to list them, so let me know if that is the way to clear the flag.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot-bootloader
Thanks for your help.
You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Since your device is a GPe device there is no need to change cid, mid etc. - with s-on you can't change them anyways. Just grab the latest GPe ruu and follow flashing instructions.
Stock recovery is only needed for ota-updates. On sense the updates would fail as this particular recovery is missing. I assume on GPe that would happen as well. It's up to you if you use twrp or stock recovery. GPe won't get updates anymore, same as sense.
I recommend not to mess with this stuff in bootloader. Once you go back to stock (ruu etc), it should fix itself. Besides that to temper with it you need to be s-off anyway.
maultasche said:
You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Yes, I had found that exact thread earlier today, thanks to you, and I was just replying to tell you that I have successfully reverted my phone back to stock.
In the spirit of contribution to the site that has helped a novice such as me, I want to share the steps I took so that others might be helped.
The phone, as mentioned earlier, is an HTC One M8 Google Play Edition (Gpe), was s-on, not rooted, bootloader unlocked. I had an old version of TWRP and Resurrection Remix ROM using Android 7.1.2.
Prerequisites
1. Stock GPe ROM: https://androidfilehost.com/?fid=817550096634750828
2. TWRP 3.1.1-0-m8: https://dl.twrp.me/m8/twrp-3.1.1-0-m8.img.html
3. Backup account fix (linked in aforementioned thread): https://www.androidfilehost.com/?fid=24686680535467942
4. ADB and fastboot
5. Unlocked bootloader
**This assumes that you have a Windows computer. I used Windows 10 v1709**
Steps
1. Copy the ROM and TWRP files to the same folder in which fastboot and ADB are located. This makes it easier to run commands.
2. (There might be another way to do this one, but I don't know it) Copy the backup account fix file "MRA58K.H15_backup-account-fix.zip" to a micro SD card and put it in the phone.
3. Open a command prompt or PowerShell window in the folder that contains ADB and fastboot by right-clicking + Shift in an open area and selecting "Open PowerShell/Command Prompt window here."
4. In the PowerShell/Command Prompt window, type "fastboot flash recovery twrp-3.1.1-0-m8.img" and press Enter to install TWRP
5. Reboot into the bootloader and choose "fastboot," then choose "recovery"
6. In TWRP, browse to ADB sideload and then "swipe to start sideload."
7. In your PowerShell/Command Prompt window, type "adb sideload HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H15_AROMA-Installer-v6-020817.zip" and press Enter to start the installation
8. On the phone's screen, choose the top option, which should be the unrooted, completely stock installation.
9. On my machine, the PowerShell/Command Prompt window showed progress up to 41% and then it finished successfully.
10. After that, do not reboot, but go back into the main TWRP menu and go to Install. Browse to the MRA58K.H15_backup-account-fix.zip file that you previously saved on your SD card and install it.
11. Once that is installed, reboot the phone. My phone took between 5 and 10 minutes to boot the first time.
12. (Optional) I wanted to have a completely reverted phone, so I locked the bootloader again by rebooting the phone into the bootlader and typing "fastboot oem lock" in the PowerShell/Command Prompt window. It then said "relocked" but no warnings or errors.
I hope this helps somebody. All credit goes to maultasche for pointing me in the right direction and to graffixnyc for the other thread.

Categories

Resources