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
Related
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.
Hi everyone, I come to you with a very very very weird problem with my M8. In Bootloader mode, the screen is black. I know I am in bootloader mode because all the fastboot command works, I also flashed with a RUU.zip hoping this solves my problem, but it is always the same. The screen is constantly black in bootloader mode. So if anyone can help me, it would be really cool. thank you
Envoyé de mon SM-P605 en utilisant Tapatalk
I have this exact same problem after upgrading to marshmallow. Everything stock and would like to root, but this is not making it easy. Got into recovery just by pressing volume button once in the black screen but that comes up with a red triangle / exclamation mark.
nay solution to this problem?
I have the same thing, the black bootloader mean you have an GPE firmware.
Here it's my topic where i get some answer for my problem, maybe will help you too:
http://forum.xda-developers.com/htc-one-m8/help/problem-m8-start-t3347845
Your problem is a bit different, in our case its a entirely black screen no options nothing..
tpteam6 said:
Your problem is a bit different, in our case its a entirely black screen no options nothing..
Click to expand...
Click to collapse
did you solve the problem? i am struggling with the same issue
ddd777 said:
did you solve the problem? i am struggling with the same issue
Click to expand...
Click to collapse
I was helping someone with a similar issue a month of so ago. Fastboot still worked, even thought the screen was off (or on, but displaying black?) and they were able to get back to normal with RUU. Not sure why RUU didn't work for the OP, as they didn't give any detail on whether the RUU succeeded, or had error messages, etc.
recta said:
Hi everyone, I come to you with a very very very weird problem with my M8. In Bootloader mode, the screen is black. I know I am in bootloader mode because all the fastboot command works, I also flashed with a RUU.zip hoping this solves my problem, but it is always the same. The screen is constantly black in bootloader mode. So if anyone can help me, it would be really cool. thank you
Envoyé de mon SM-P605 en utilisant Tapatalk
Click to expand...
Click to collapse
i got the same problem and dont know what to do?
flashed ruu and didnt work for me..help me out bro @redpoint73
mandegar93 said:
i got the same problem and dont know what to do?
flashed ruu and didnt work for me..help me out bro @redpoint73
Click to expand...
Click to collapse
have you tried with sd card method ?
another way maybe work is flashing signed firmware then flash RUU
Sent from my HTC M8 using XDA Labs
mandegar93 said:
i got the same problem and dont know what to do?
flashed ruu and didnt work for me..help me out bro @redpoint73
Click to expand...
Click to collapse
For someone that has been on XDA for a while, you should know that just posting "I have the same problem" is never enough info for anyone to give any proper help. You need to provide some details:
- What M8 version (CID, MID, firmware number etc.) post output from fastboot getvar all, if you can (delete IMEI and serial number before posting).
- What RUU did you try (version number)?
- Did the RUU actually install to completion? Any error messages, or other outputs, results?
redpoint73 said:
For someone that has been on XDA for a while, you should know that just posting "I have the same problem" is never enough info for anyone to give any proper help. You need to provide some details:
- What M8 version (CID, MID, firmware number etc.) post output from fastboot getvar all, if you can (delete IMEI and serial number before posting).
- What RUU did you try (version number)?
- Did the RUU actually install to completion? Any error messages, or other outputs, results?
Click to expand...
Click to collapse
yes you are right, so: this is my getvar all
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.12.401.4
version-misc: PVT SHIP S-OFF
serialno: HT********
imei: 3***********
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
i tried lollipop ruu and marshmallow ruu ...
no there is no error message and installation completed..
check it out this picture..
few problem showing itself at the same time when i faced this situation:
1-as you see in the picture there is some line in status bar that is reflection or copy or something like that of my bottom of screen..check that color with the same color in status bar.
2-when i reboot my phone , phone vibrated but htc icon does not appeard and it goes directly to bootanimation
3-bootloader screen is totally dark but not gone..because when i reboot to bootloader and i pressed volume down and then power it goes to recovery mode.. so i have bootloader but its all dark and black screen , same thing htc icon not shown while booting up
4-when i double tap to wake up there is some delay about 2 second and the same delay when is increase the brightness
this is all of problem i faced
wish you can help me out
edit: and another thing this situation was fixed in some trying in install ruu or new firmware but something like installing 20 time ruu or firmware and just 1 time is randomly fixed and after some days and some normal reboot the problem shows itself again..its something mission impossible for me!!!
ahmed.ismael said:
have you tried with sd card method ?
another way maybe work is flashing signed firmware then flash RUU
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
you have no idea how many time i try in different way .. im just disappoint
mandegar93 said:
yes you are right, so: this is my getvar all
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.12.401.4
version-misc: PVT SHIP S-OFF
serialno: HT********
imei: 3***********
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
i tried lollipop ruu and marshmallow ruu ...
no there is no error message and installation completed..
check it out this picture..
few problem showing itself at the same time when i faced this situation:
1-as you see in the picture there is some line in status bar that is reflection or copy or something like that of my bottom of screen..check that color with the same color in status bar.
2-when i reboot my phone , phone vibrated but htc icon does not appeard and it goes directly to bootanimation
3-bootloader screen is totally dark but not gone..because when i reboot to bootloader and i pressed volume down and then power it goes to recovery mode.. so i have bootloader but its all dark and black screen , same thing htc icon not shown while booting up
4-when i double tap to wake up there is some delay about 2 second and the same delay when is increase the brightness
this is all of problem i faced
wish you can help me out
edit: and another thing this situation was fixed in some trying in install ruu or new firmware but something like installing 20 time ruu or firmware and just 1 time is randomly fixed and after some days and some normal reboot the problem shows itself again..its something mission impossible for me!!!
Click to expand...
Click to collapse
Sounds to me like you have hardware issues, most likely corrupt internal memory, time for a replacement or upgrade
LeeDroid said:
Sounds to me like you have hardware issues, most likely corrupt internal memory, time for a replacement or upgrade
Click to expand...
Click to collapse
That was the last shot on my heart :angel:
Maybe I'm upgrading to HTC 10 few months later
If I power the phone off, then turn it on the FASTBOOT screen appears. This has the HBOOT, RAMDUMP, REBOOT, REBOOT FASTBOOT, and POWER DOWN menu items. Invalid Radio Can Ayone help???? i tried orignal firmware files.. my phone is stock not rooted no twrp s-off.
jawad.ibm said:
If I power the phone off, then turn it on the FASTBOOT screen appears. This has the HBOOT, RAMDUMP, REBOOT, REBOOT FASTBOOT, and POWER DOWN menu items. Invalid Radio Can Ayone help???? i tried orignal firmware files.. my phone is stock not rooted no twrp s-off.
Click to expand...
Click to collapse
I believe you are in the wrong place
Anyway
more details needed
what you were try to achieve before your problems started ?
the result of fastboot getvar all will be helpful ( after removing serialno and imei )
what firmware you have tried ?
any detail is useful
Sent from my HTC M8 using XDA Labs
recta said:
Hi everyone, I come to you with a very very very weird problem with my M8. In Bootloader mode, the screen is black. I know I am in bootloader mode because all the fastboot command works, I also flashed with a RUU.zip hoping this solves my problem, but it is always the same. The screen is constantly black in bootloader mode. So if anyone can help me, it would be really cool. thank you
Envoyé de mon SM-P605 en utilisant Tapatalk
Click to expand...
Click to collapse
suffering from same problem...did you solve it?
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
redpoint73 said:
For someone that has been on XDA for a while, you should know that just posting "I have the same problem" is never enough info for anyone to give any proper help. You need to provide some details:
- What M8 version (CID, MID, firmware number etc.) post output from fastboot getvar all, if you can (delete IMEI and serial number before posting).
- What RUU did you try (version number)?
- Did the RUU actually install to completion? Any error messages, or other outputs, results?
Click to expand...
Click to collapse
hi..i am also suffering from black bootloader issue.is there any solution?
dr.estiack said:
hi..i am also suffering from black bootloader issue.is there any solution?
Click to expand...
Click to collapse
You quoted me, than completely ignored my statement that you quoted (which advised to never just say "I have the same problem" without posting any details about your device).
Plus, is the phone modded (bootloader unlocked, root, custom ROM)? What have you tried so far, what were the results of each method you tried. List steps, files and results in detail and with specific information.
Can't help without specifics.
redpoint73 said:
You quoted me, than completely ignored my statement that you quoted (which advised to never just say "I have the same problem" without posting any details about your device).
Plus, is the phone modded (bootloader unlocked, root, custom ROM)? What have you tried so far, what were the results of each method you tried. List steps, files and results in detail and with specific information.
Can't help without specifics.
Click to expand...
Click to collapse
Actually i didnt try anything..i m afraid of bricking the set as never faced this black bootloader issue. Infact though set is running rooted stock 4.4.2 and everything is working fine.Thats why i am afraid of expeimenting.But if there is any recognised solution i will try.My set is written 0p6b100 on back..but it shows sprint op6b700 in cid getter..and m8 mhl..also shows it has super cid.bt i couldnt check soff and bootloader as i dont have pc right now.And sorry for annoying you.
dr.estiack said:
Actually i didnt try anything..i m afraid of bricking the set as never faced this black bootloader issue. Infact though set is running rooted stock 4.4.2 and everything is working fine.Thats why i am afraid of expeimenting.But if there is any recognised solution i will try.My set is written 0p6b100 on back..but it shows sprint op6b700 in cid getter..and m8 mhl..also shows it has super cid.bt i couldnt check soff and bootloader as i dont have pc right now.And sorry for annoying you.
Click to expand...
Click to collapse
I'm confused whether to help you here, of the 5 other threads you've posted to.
I would suggest sticking to the following thread, as others have already started help you there, and it seems to be where you've posted the most info:
https://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783/page517
Hello all,
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
"fastboot getvar all" returns this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
Now the interesting part. Every time the phone reboots, it is always in the same state as if the partitions were frozen. That is to say for instance if I uninstall an app and then reboot, the app is there again. If I connect to a Wifi network and reboot, it disappears. Every single modification is erased and returns back to the same state. The most annoying thing is that when I connect to a Wifi the apps start synchronizing, crash and the phone reboots.
I tried the following:
- Factory reset from the interface to no avail as it returns to the state it was as well
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
- Tried "fastboot oem rebootRUU", which simply reboots the phone into android
- Tried to unlock the bootloader, which again reboots the phone into android
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
- Tried to flash only the zip from the RUU and ends up with the same signature error
I simply can't think of anything else to do, and I hope one of the gurus can help me in my quest
Thank you for the time you spent reading my post.
My responses/comment below in red font:
tyraek said:
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
(bootloader) version-main: 1.58.502.1
It doesn't appear to have had any OTA updates. Or at most a minor update from 1.54>1.58.
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
Try pressing vol up and power to show the stock recovery menu options. I believe factory reset is one of those options, although if wiping in OS didn't work; I doubt doing so from stock recovery will be any different.
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
Which RUU (exact filename)? There are many, and the RUU has to be intended for your CID version.
What error number, and what error message? This is very important, otherwise we have no idea why it failed.
You're on the right track, by trying to run an RUU. I think its your best bet to fix the issue. But we need to make sure you run the right RUU.
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
You can't flash recovery with a locked bootloader.
- Tried to flash only the zip from the RUU and ends up with the same signature error
Again, which RUU specifically is very important. Can't tell if the RUU is the right one based on the info given.
Also, please verify on the hboot screen, near the top, if it says LOCKED (other possibilities being UNLOCKED and RELOCKED)
Click to expand...
Click to collapse
Thank you so much for your reply.
I have tried the factory reset from the recovery and the result is the same.
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
The update states it will upgrade from 1.58.502.1 to 4.28.502.2. Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.
bump
tyraek said:
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
Click to expand...
Click to collapse
Yes, this is for your model (AT&T) and the version number will work.
tyraek said:
Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
.
Click to expand...
Click to collapse
This is means there is a USB communication issue, usually on the PC side, and there is nothing wrong with the RUU or the phone.
RUU is very finicky, and this issue is common. Try a different cable, different USB port, and try to re-install HTC Sync.
But you may have to resort to using another computer. Win7 and USB 2.0 (USB 3.0 is known to cause issues with RUU) are the best bet to get the RUU to run properly.
tyraek said:
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.
Click to expand...
Click to collapse
Do not unlock the bootloader if you intend to RUU. Unlocked bootloader will actually cause the RUU to fail, by definition. RUU requires the bootloader by LOCKED or RELOCKED (or else you need s-off to run an RUU with the bootloader UNLOCKED).
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.
Hi all,
@THE company I work we found a htc one m8s that when I booted it went straight to bootloader menu.
I want to get it working again so I started reading here on the forums, download some stuff from ruu.lalleman.net that I found in one of the other treads. In the end i'm still stuck and i'm hoping to get some advice through this channel.
Here is my current status
when the devices is connected to the PC it boots ALWAYS straight to bootloader with the following info
software status : Modified
unlocked
m8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
OS-1.16.401.10
eMMC-boot 2048MB
aug 13 2015
Fastboot USB with the normal stuff
when I try to load a RUU through the exe I reboot the device and then keeps waiting with in the end a disconnect (saying I need to connect my device) the device itself is already back in bootloader window.
when I try to use htc_fastboot to flash a recovery it gives me
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 1(s)
but then on reboot it's straight back to bootloader menu no recovery
when I try to lock the device I get
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) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
(bootloader) [INFO] Rebooting device arbiter!!I PMIC arbitery-
FAILED (unknown status code)
Execution time is 1(s)
I did get it unlocked (as it was locked before but relocking is not working)
Also fastboot devices shows me the devices but adb devices shows nothing (tried both htc drives and general android ones)
These are my var all info
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 28(ms)
Hoping on any help from here
Greetings
Tom
Little update:
I kept on trying different versions from recovery / boot / ruu's in the hope that one works but nothing so far.
In another topic somewhere I did found that as long as my device is unlocked it will not work to use RUU, so locking the device again will be my first step.
I did notice that when I ended my adventure yesterday evening I wasn't able to turn the phone off, I always rebooted (in like a millisecond) back to bootloader as long as it was connected to the pc. I had to remove the usb connection and then try couple of times with volume-up / power to turn it off.
I did do the 2 minutes bright licht / volume up + down + power button trick to reset the battery but that didn't change anything.
also as a last minute addition
when I do the fastboot -> image CRC i'm getting a 0X0 on sbl2 - sbl3 - boot and recovery so it seems that what ever I do with htc_fastboot flash is not sticking.
Going to look into trying to get it locked again now first in combination with trying to find out why I can't write to the damn phone (adb isn't working ether so maybe driver problem also ?)
The adventure continues
Tom
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
ckpv5 said:
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
Click to expand...
Click to collapse
That is indeed the RUU i tried, i got it based on the fastboot var all i did.
Still trying to get my Phone locked again as that is holding back the ruu upgrade now from what i see.
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
ckpv5 said:
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
Click to expand...
Click to collapse
Yhea i did it with the htc_fastboot version.
another update,
After some more trial and error while aiming for the locking of my phone i'm still stuck.
Both my boot and my recovery are empty it seems (the 0x0 from the image crc) and all the others still have 0xA.....B or what ever value in them
All the writing I do like
C:\tel>htc_fastboot.exe flash recovery recovery_signed.img
sending 'recovery' (30080 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
seems to be working but that doesn't change the crc value's nether does it allow me to use the recovery from the hboot menu.
also when I type stuff like htc_fastboot oem rebootRUU it brings me straight back to the bootloader menu, no black screen to do htc_fastboot flash zip rom.zip.
What I didn't try yet is using a SD-card and see if that fixes it (I could put that card in my other phone, write stuff to it and use it in the M8s.
Anybody got any expereance for using a sdcard to flash the device back to stock.
@ this moment I will be kind of happy with anything that advances me a step
Tom
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
kruc Ire said:
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
Click to expand...
Click to collapse
How do you mean give up ?
is there no way arround based on your opinion from what i posted above ?
I Always hoped it was my lack of knowledge that was holding me back in fixing it ...
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
kruc Ire said:
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
Click to expand...
Click to collapse
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
TomBrunson said:
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
Click to expand...
Click to collapse
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
I made that video but if the F'N censors won't let me put up the lyrics of a song they HATE in their pinheads then I won't be posting their garbage they WOULD view.
I'll keep putting up large videos though just to chew up this sh!tty world's resources. If it's a world of creeps it's
Music videos mostly. Ooh how they HATE my beautiful music...and I can hear the little b##ch there in her fuzzy chair. Like she spoke directly into my head. And if it hadn't taken me so long to make a thumbnail she wouldn't have been able to install her trick. Literally FFFF youtube.
kruc Ire said:
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
Click to expand...
Click to collapse
Is there a different command to Relock as to Lock ?
I couldn't find anything else then htc_fastboot oem lock
Tom
Ok i'm over it. I attached a different (worse) song and reuploaded it. No censorship now.
HTC M8s firmware flash in photos:
Please note I only started making a video because I noticed that time bar on upper right about 15 minutes into the (uninterrupted) flash. So that took a long time and I was concerned about the messed up and overprinted text and made photos during every new screen between the third or fourth at the start (when I caught up with my camera) up till the time of video starting.
So yeah what I am trying to say is it seemed to take very long, with many seemingly false starts and failures. Only by waiting did it finally achieve correctness.
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
TomBrunson said:
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
Click to expand...
Click to collapse
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
kruc Ire said:
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
Click to expand...
Click to collapse
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
You have never gotten it to lock? I thought you said you couldn't get the zip to work?
---------- Post added at 06:53 PM ---------- Previous post was at 06:38 PM ----------
TomBrunson said:
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
Click to expand...
Click to collapse
What output does your cmd window give u? Can you show a screenshot of what your command is and the output.
I see. You are trying to put a lollipop. Still first ya gotta lock it does anyone remember the rules for firmware flash? Is it going to screw up the phone to flash the MM 60 sense 70 ? Dude are you in Europe? The 60 70 I flashed from my microSd was a EUROPE.