My cousins phone will only turn on for the like 5 seconds than keep on turning off and on. He has a locked bootloader ,factory recovery and rom and is s-on. I think there is something wrong with the recovery mode because it boot into it but I can still go into fastboot mode. My question is could I still unlock the bootloader and put a custom recovery because I don't think he put it into usb debugging and if I can't then what else could I do to fix it.
hamugee68 said:
My question is could I still unlock the bootloader and put a custom recovery because I don't think he put it into usb debugging and if I can't then what else could I do to fix it.
Click to expand...
Click to collapse
You don't need debugging to unlock the bootloader and install custom recovery. Those things are done with fastboot, which doesn't require debugging to be on. Only adb needs debugging to be on.
redpoint73 said:
You don't need debugging to unlock the bootloader and install custom recovery. Those things are done with fastboot, which doesn't require debugging to be on. Only adb needs debugging to be on.
Click to expand...
Click to collapse
I tried to unlock the bootloader everything was going well until I confirmed it on the phone and it rebooted to a red triangle and exclamation point like it did when I tried to boot into recovery. I don't know what to do now.
hamugee68 said:
I tried to unlock the bootloader everything was going well until I confirmed it on the phone and it rebooted to a red triangle and exclamation point like it did when I tried to boot into recovery. I don't know what to do now.
Click to expand...
Click to collapse
That is the stock recovery. Try holding vol up (or maybe its vol down, I can never remember) then just pressing and releasing the power button, to show the recovery menu options. From there, just reboot the phone. Or alternately, just hold vol up and power until the phone reboots (may need to hold the buttons for a minute or so).
Reboot into bootloader, and see if the bootloader was successfully unlocked or not.
If so, go into fastboot mode and continue the process (flash TWRP)>
redpoint73 said:
That is the stock recovery. Try holding vol up (or maybe its vol down, I can never remember) then just pressing and releasing the power button, to show the recovery menu options. From there, just reboot the phone. Or alternately, just hold vol up and power until the phone reboots (may need to hold the buttons for a minute or so).
Reboot into bootloader, and see if the bootloader was successfully unlocked or not.
If so, go into fastboot mode and continue the process (flash TWRP)>
Click to expand...
Click to collapse
The recovery menu is frozen and when i boot into bootloader it says locked.
hamugee68 said:
The recovery menu is frozen and when i boot into bootloader it says locked.
Click to expand...
Click to collapse
Enter bootloader-fastboot mode (if its not already) and try to unlock the bootloader again.
redpoint73 said:
Enter bootloader-fastboot mode (if its not already) and try to unlock the bootloader again.
Click to expand...
Click to collapse
I tried to unlock it three time and everytime it was the same.
hamugee68 said:
I tried to unlock it three time and everytime it was the same.
Click to expand...
Click to collapse
Same unlock token every time? If so, try going thru HTCDev.com again, and get a new token, and see if it makes any difference.
Otherwise, if you version has RUU, I'd try RUU and start the bootloader unlock process over again.
redpoint73 said:
Same unlock token every time? If so, try going thru HTCDev.com again, and get a new token, and see if it makes any difference.
Otherwise, if you version has RUU, I'd try RUU and start the bootloader unlock process over again.
Click to expand...
Click to collapse
I tried both when i would try to unlock the bootloader with a different token i got the same result and when i try to use ruu it would just restart the phone.
hamugee68 said:
I tried both when i would try to unlock the bootloader with a different token i got the same result and when i try to use ruu it would just restart the phone.
Click to expand...
Click to collapse
Need more info. Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
And what RUU are you trying (exact file name)?
redpoint73 said:
You don't need debugging to unlock the bootloader and install custom recovery. Those things are done with fastboot, which doesn't require debugging to be on. Only adb needs debugging to be on.
Click to expand...
Click to collapse
I'm on the same boat, can't unlock the bootloader, it goes all fine until it should promp me on the phone screen to confirm bootloader unlock, i simply stay in the bootloader as if nothing happened.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Related
Hello,
I am trying to fix my issue and have done a ton of reading but can't figure out where to go from here. I've had my phone rooted for months and tried to flash a newer custom ROM today and it ended up locking my phone into a boot loop. I was able to get out of it and had to re install a recovery tool (have installed both CWM and TWRP and they work fine). But I can't actually get a ROM back onto my phone because I don't have one on the SD card and I can't get one to it. I just want to put a stock ROM back onto it at this point.
I can't boot into windows to access the SD card because whenever I boot the phone normally it just goes back to boot looping. I have tried ADB push when in recovery to put a ROM on the SD card and I continually get permission denied when I try to do that. I have tried ADB sideloader and I can't get that to work either. How can I go about getting a ROM to my phone so I can flash it via CWM/TWRP?
Fastboot works fine and I can flash recoveries no problem. ADB appear to work but I can't understand why I can't just get push to work. Any help would be greatly appreciated.
HTC One M7 on Verizon.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
NotATreoFan said:
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
Click to expand...
Click to collapse
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
factor00 said:
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
Click to expand...
Click to collapse
What about fastboot?
NotATreoFan said:
What about fastboot?
Click to expand...
Click to collapse
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
factor00 said:
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
Click to expand...
Click to collapse
I haven't done anything RUU in a while, so I don't want to steer you wrong. But I believe you can use decrypted to get everything up and running. Check the general forum for a guide on returning to stock.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Just remember to keep s-off while running the ruu
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).
Hi,
I have an HTC One M8 and its stuck on the bootloader screen. Im trying to flash a stock rom, or a custom rom, anything really to get the phone working again.
I have installed ADB, HTC drivers and Android SDK Tools, but ADB does not detect the phone, and the phone doesnt show in device manager. So I think usb debug option must be unchecked in the phones settings?
I tried the M8 all in one kit, but usb debug needs be be checked for that to work.
I read I can fastboot a custom recovery image without usb debug, but the computer cant see the phone so i cant do fastboot usb?
If I select Recovery from the bootloader screen, the phone reboots back to the bootloader screen.
Can anyone help me get this phone working? Any help greatly appreciated.
when you get stuck on bootloader, you don't need adb but you need fastboot.
Install these two drivers : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
then run fastboot devices .. if it returns a serial no. then it's good
then report fastboot getvar all without serial & imei no.
C:\adb>fastboot getvar all
< waiting for device >
(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.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.295s
You have two options :
if the bootloader is unlocked
1. return to stock 4.16.401.13 with a TWRP nandroid backup
what you need to do :
install TWRP 2.8.7.0 or latest
restore 4.16.401.13 backup
install 4.16.401.13 stock recovery.img
reboot and OTA to the latest 6.12.401.4
You can get the files and how-to, here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2. flash a RUU zip directly to 6.12.401.4
What you need to do if the bootloader is unlocked, relock bootloader with command - fastboot oem lock, then reboot to bootloader again
then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After running the fastboot reboot-bootloader command the phone switched off and now screen is blank?
fastboot oem rebootRUU says waiting on device for past 10 mins.
Maybe your phone is out of battery ... you shouldn't run those command on a black screen .. only on bootloader/fastboot.
Put the phone on a wall charger for a few hours then try again.
I ran fastboot reboot-bootloader command from cmd a few hours ago and the phone switched off and then wouldnt come back on.
I plugged the phone into the wall charger for a few hours, but it still wont boot.
EarIier this morning I selected fastboot from the bootloader screen then power button and the phone did the same thing; it switched off and would not come back on. I only got it back on to bootloader screen by sheer luck pressing power volume up/down combinations until it came on.
finally got the bootloader screen back but now it just says
ramdump
ramdump to sd
ramdump to usb
ramdump to emmc
reboot
If I choose reboot do you thing the phone will reboot back into bootloader with fastboot option or will the phone go dead again?
sl75 said:
finally got the bootloader screen back but now it just says
ramdump
ramdump to sd
ramdump to usb
ramdump to emmc
reboot
If I choose reboot do you thing the phone will reboot back into bootloader with fastboot option or will the phone go dead again?
Click to expand...
Click to collapse
Oh .. that's because you accidentally selected ramdump menu (2nd menu on bootloader). When you select reboot, it will boot but it will get stuck on bootloop.
After it get stuck, press & hold both volume up & power button to force reboot, when the screen turn black, release both buttons but quickly press & hold volume down button only, this will get you to hboot screen. press power once, it will get you to bootloader/fastboot screen
I selected reboot from the ramdump menu and the phone has switched off again and wont come back on, it seems any time I reboot the phone from the bootloader menu or cmd the phone switches off and doesnt reboot.
How do I get it back to the bootloader screen now? Do I do this?
press & hold both volume up & power button to force reboot, when the screen turn black, release both buttons but quickly press & hold volume down button only
That won't work.
I don't know whether you have hardware issue.
You can try this .. usually will fix the battery abnormality
Power off phone. (yours is already power off for now)
Plug phone into HTC charger and charge for two minutes or more
While charging, hold down volume up+volume down+power button and continue holding
Phone will turn on and off repeatedly every 15 seconds or so while continuing to hold all three buttons
Keep this going for 2-3 minutes, then release buttons when phone is ON
Then it will get stuck again ....
After it get stuck, press & hold both volume up & power button to force reboot, when the screen turn black, release both buttons but quickly press & hold volume down button only, this will get you to hboot screen. press power once, it will get you to bootloader/fastboot screen
then install RUU
If this unable to fix it .. most probably it is hardware issue.
I got to go now ... won't be available for 5 hours
Hi, I took a picture of something with my phone and then locked it. After checking it again the screen was flashing between blank and a stock wallpaper. I reset using the power button and volume up. Ever since then my phone will not load past the HTC splash screen, not showing my carrier splash screen and instead just being stuck on a blank black screen. This is a stock phone which I haven't even attempted to modify.
I have tried to clear the cache, factory reset and all of the different combinations of holding both the power button + both volume buttons etc. I've tried booting without a sim, without a memory card or with one of each. Still no dice.
If anyone could provide me with the answer to my issue that would be amazing.
Thanks!
Edit: I should add I've tried using adb/fastboot and it will not detect my device when I type 'adb devices'.
ADB only works when your phone is powered on. Not when you're stuck at a boot screen. You'll have to boot into the BL and type a few fastboot commands.
Turn your phone off completely.
Press the following combo:
Power + Vol Down
That's the HBOOT menu, press the power button once if FASTBOOT is highlighted. It will go to fastboot mode.
Type 'fastboot devices' and if it shows your serial number, proceed to type this command:
fastboot getvar all
Once you get that, copy the result without the IMEI and Serial Number. Post the rest of the stuff here, so we can guide you on which RUU to flash.
Should be a simple fix hopefully.
Beekel said:
Hi, I took a picture of something with my phone and then locked it. After checking it again the screen was flashing between blank and a stock wallpaper. I reset using the power button and volume up. Ever since then my phone will not load past the HTC splash screen, not showing my carrier splash screen and instead just being stuck on a blank black screen. This is a stock phone which I haven't even attempted to modify.
I have tried to clear the cache, factory reset and all of the different combinations of holding both the power button + both volume buttons etc. I've tried booting without a sim, without a memory card or with one of each. Still no dice.
If anyone could provide me with the answer to my issue that would be amazing.
Thanks!
Edit: I should add I've tried using adb/fastboot and it will not detect my device when I type 'adb devices'.
Click to expand...
Click to collapse
I had this happenned to me once and it was due to counterfeit sd card. So I had to RUU back to stock.
bombo_b said:
I had this happenned to me once and it was due to counterfeit sd card. So I had to RUU back to stock.
Click to expand...
Click to collapse
I gathered I had to do an RUU to stock.
murtaza02 said:
ADB only works when your phone is powered on. Not when you're stuck at a boot screen. You'll have to boot into the BL and type a few fastboot commands.
Turn your phone off completely.
Press the following combo:
Power + Vol Down
That's the HBOOT menu, press the power button once if FASTBOOT is highlighted. It will go to fastboot mode.
Type 'fastboot devices' and if it shows your serial number, proceed to type this command:
fastboot getvar all
Once you get that, copy the result without the IMEI and Serial Number. Post the rest of the stuff here, so we can guide you on which RUU to flash.
Should be a simple fix hopefully.
Click to expand...
Click to collapse
Here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's a weird issue, almost like the entire OS imploded.
Beekel said:
I gathered I had to do an RUU to stock.
Here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's a weird issue, almost like the entire OS imploded.
Click to expand...
Click to collapse
Sadly, Three UK RUUs are impossible to find.
Your bootloader is locked I think and you're S-ON. Making things a bit hard for you.
You can try to unlock the bootloader through HTCDev, once you do, flash TWRP recovery, download the 3 UK backup from ckpv5's thread and restore it to your phone. Then flash the stock recovery for your build and re-flash that. Wipe data and reboot. You should be up and running.
Sent from my Nexus 6
murtaza02 said:
Sadly, Three UK RUUs are impossible to find.
Your bootloader is locked I think and you're S-ON. Making things a bit hard for you.
You can try to unlock the bootloader through HTCDev, once you do, flash TWRP recovery, download the 3 UK backup from ckpv5's thread and restore it to your phone. Then flash the stock recovery for your build and re-flash that. Wipe data and reboot. You should be up and running.
Sent from my Nexus 6
Click to expand...
Click to collapse
See bold. What do you mean here? Re-flash with the stock (non recovery) backup?
Beekel said:
See bold. What do you mean here? Re-flash with the stock (non recovery) backup?
Click to expand...
Click to collapse
Think he meant "Then find the stock recovery for your build and re-flash that".
In any case, just flashing the TWRP backup (nandroid) should get the phone back up and running. Restoring the stock recovery is only necessary to get future OTA updates.
In any case, even if you want stock recovery, I suggest waiting on restoring stock recovery until after you've restored the nandroid, rebooted, and confirmed it boots properly into OS. That way, if it doesn't boot for any reason, you still have TWRP and can try to restore again.
Here's the TWRP backup collection, if you haven't already found it: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You'll find the stock TWRP backup (and corresponding stock recovery) for 6.13.771.4 there.
redpoint73 said:
Think he meant "Then find the stock recovery for your build and re-flash that".
In any case, just flashing the TWRP backup (nandroid) should get the phone back up and running. Restoring the stock recovery is only necessary to get future OTA updates.
In any case, even if you want stock recovery, I suggest waiting on restoring stock recovery until after you've restored the nandroid, rebooted, and confirmed it boots properly into OS. That way, if it doesn't boot for any reason, you still have TWRP and can try to restore again.
Here's the TWRP backup collection, if you haven't already found it: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You'll find the stock TWRP backup (and corresponding stock recovery) for 6.13.771.4 there.
Click to expand...
Click to collapse
Oh, makes sense. Just to make sure, I need to wipe data by just using the 'swipe to factory reset' option in TWRP right? Then I should be good to go? As without wiping the phone is still just a moderately heavy paperweight.
Edit: Factory reset via swipe in the wipe menu, rebooted and so far all is good. Currently optimizing apps.
Beekel said:
Just to make sure, I need to wipe data by just using the 'swipe to factory reset' option in TWRP right? Then I should be good to go? As without wiping the phone is still just a moderately heavy paperweight.
Click to expand...
Click to collapse
It tells you exactly what to wipe in the thread I linked, top post, step #8.
Phone is back to normal working condition so far. Thanks guys!
Beekel said:
See bold. What do you mean here? Re-flash with the stock (non recovery) backup?
Click to expand...
Click to collapse
Sorry about that. Wasn't reading what I typed.
Redpoint couldn't have explained it better.
Glad your phone is up and running again.
Sent from my Nexus 6
Hello everyone, The story with my htc is that an error "Unfortunately settings has stopped" popped up so I went into bootloader and formatted the device, now once the device booted I couldn't get trough setup as the same message popped up over and over so couldn't do anything, then I decided to unlock the bootloader and install twrp so that a custom ROM would work, but once I installed twrp I wouldn't boot system or recovery... so I tried to flash stock recovery but that failed so clever and tired me relocked the device and now the device is relocked and when I attempt to unlock it fastboot claimed a "success" but phone still shows relocked and twrp doesn't want to flash
you must me curious why didn't I just flash the ruu? Well... for this device its cid is H3G__001 and if I can't find a ruu for that that would be correct with the details of the device that would be great
(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.12.771.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: H3G__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: ca3c8ca2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Anyone any ideas on what I should do? :crying:
Anyone?
Maybe someone has the h3g uk ruu for the m8s?
0PKVIMG_M8_QL_UL_L50_SENSE60_H3G_UK_1.12.771.10_R [email protected]_15.00_016_F_release_450151 _combined_signed.zip
Or maybe someone with access to ir-file.com?
for RUU: https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If TWRP doesn't want to flash: You need HTC_Fastboot and NOT the regular Fastboot. ==> https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
twrp-3.0.2-0-m8ql.img is confirmed to work: https://basketbuild.com/devs/Captain_Throwback/One (M8S)/Recovery
jeroen_13 said:
for RUU: https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If TWRP doesn't want to flash: You need HTC_Fastboot and NOT the regular Fastboot. ==> https://ruu.lalleman.net/HTC_M8S(QL_UL)/Tools/Fastboot/
twrp-3.0.2-0-m8ql.img is confirmed to work: https://basketbuild.com/devs/Captain_Throwback/One (M8S)/Recovery
Click to expand...
Click to collapse
Thanks for the links but when i googled the first thing that popped up was ruu.lalleman.net and the ruu than im looking for if not there
But if i understand correctly from what your saying is that i can flash twrp with htc_fastboot with the bootloader relocked?
I will also try to flash the unlock_code.bin with the htc_ fastboot and ill reply on how it goes
the_ziom said:
Thanks for the links but when i googled the first thing that popped up was ruu.lalleman.net and the ruu than im looking for if not there
But if i understand correctly from what your saying is that i can flash twrp with htc_fastboot with the bootloader relocked?
I will also try to flash the unlock_code.bin with the htc_ fastboot and ill reply on how it goes
Click to expand...
Click to collapse
I linked ruu.lalleman.net because your were looking for your RUU.
You have to UNLOCK your bootloader again before flashing TWRP with HTC_fastboot
jeroen_13 said:
I linked ruu.lalleman.net because your were looking for your RUU.
You have to UNLOCK your bootloader again before flashing TWRP with HTC_fastboot
Click to expand...
Click to collapse
like the title of this thread and the first post on this thread says the phone doesn't want to unlock and I believe that its because of no recovery and what u are telling me I know from google and other xda threads so if I would really know how to solve this problem I wouldn't have made this thread
the_ziom said:
like the title of this thread and the first post on this thread says the phone doesn't want to unlock and I believe that its because of no recovery and what u are telling me I know from google and other xda threads so if I would really know how to solve this problem I wouldn't have made this thread
Click to expand...
Click to collapse
What error do you get while sending the unlock token?
Can you send me the cmd log ?
jeroen_13 said:
What error do you get while sending the unlock token?
Can you send me the cmd log ?
Click to expand...
Click to collapse
Well thats the thing cmd shows success
And the unlock_code.bin opens on the phone i press vol up to select yes press power than the phone reboots and still shows relocked
the_ziom said:
Well thats the thing cmd shows success
And the unlock_code.bin opens on the phone i press vol up to select yes press power than the phone reboots and still shows relocked
Click to expand...
Click to collapse
Ok so i bought a ir-file 30 day account downloaded the RUU and copied it to a sd card than i booted into bootloader and the process started... And tan the bootloader showed (after flashing the system.img like 6 times) that the process failed but i took my chances and rebooted the phone and now im writing this post from it [emoji2]. Thanks for help and if anyone has a similar problem than pm me withing 30 day and ill get you the RUU
Sent from my HTC One M8s using XDA-Developers Legacy app
Same problem, same RUU
Hi, if you could share the RUU will be great as I am having the same issue and it will be great to have my HTC back on tracks
Many thanks in advance
the_ziom said:
Thanks for help and if anyone has a similar problem than pm me withing 30 day and ill get you the RUU
Click to expand...
Click to collapse
Hi, have you by any chance seen my PM ?