Taking a photo caused brick? - One (M8) Q&A, Help & Troubleshooting

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

Related

[Q] Problems in updating (4.0.4 to 4.1.1) and going into recovery mode

I tried to update my HTC One X from 4.0.4 to 4.1.1 by OTA. The phone would download the entire update (around 370 MB), then try to install it, but couldn't. This happened several times. Then I downloaded the OTA update zip file and copied it to my phone memory. But now, it wouldn't go into recovery mode (after pressing volume down and power and navigating to recovery). When I press on recovery, it would go to a black screen, showing a phone with an exclamatory sign over it. After some time (maybe 1 or 2 minutes) it would reboot to normal mode with 4.0.4.
So, I think the problem is my phone cannot simply enter recovery mode. Is there any way to install the update by commands through PC?
I'm not really a fan of custom ROMs. Only the stock ROM of JB 4.1.1 will do.
Thanks!
Try resetting your phone from the hboot. (You'll lose all data including apps and sdcard. So backup first)
Then try ota again.
Sent from my One X
athulele said:
Try resetting your phone from the hboot. (You'll lose all data including apps and sdcard. So backup first)
Then try ota again.
Sent from my One X
Click to expand...
Click to collapse
You mean factory reset? Did that. No improvement. Also I ran the RUU for stock ROM of ICS 4.0.4. Had to do that to unbrick it (long story, was trying to flash custom ROM. Was facing the same problem, couldn't enter recovery option). But still, same story, downloads update for 2 hours, then goes back to 4.0.4. I'm in deep **** man!
khalid_saad said:
You mean factory reset? Did that. No improvement. Also I ran the RUU for stock ROM of ICS 4.0.4. Had to do that to unbrick it (long story, was trying to flash custom ROM. Was facing the same problem, couldn't enter recovery option). But still, same story, downloads update for 2 hours, then goes back to 4.0.4. I'm in deep **** man!
Click to expand...
Click to collapse
Have you unlocked your bootloader?
If yes, I will directly give you instructions to update to 4.2.2
athulele said:
Have you unlocked your bootloader?
If yes, I will directly give you instructions to update to 4.2.2
Click to expand...
Click to collapse
I did, but again relocked to go to stock ROM to unbrick via RUU. I can unlock it again and I would appreciate if you tell me how to update to 4.2.2. But I'm afraid the process won't work if it involves going into recovery mode in the phone.
khalid_saad said:
I did, but again relocked to go to stock ROM to unbrick via RUU. I can unlock it again and I would appreciate if you tell me how to update to 4.2.2. But I'm afraid the process won't work if it involves going into recovery mode in the phone.
Click to expand...
Click to collapse
It does involve the recovery mode.
Can you tell me why it wouldn't work?
Sent from my One X
athulele said:
It does involve the recovery mode.
Can you tell me why it wouldn't work?
Sent from my One X
Click to expand...
Click to collapse
Like I said earlier, when I go to bootloader (by holding volume down and power) and then select recovery from the options, a black screen comes with an android photo in the middle, with an exclamatory sign above it. After a couple of minutes, the screen disappears and the phone is restarted. That's what happens every time, I don't know why.
khalid_saad said:
Like I said earlier, when I go to bootloader (by holding volume down and power) and then select recovery from the options, a black screen comes with an android photo in the middle, with an exclamatory sign above it. After a couple of minutes, the screen disappears and the phone is restarted. That's what happens every time, I don't know why.
Click to expand...
Click to collapse
That's not a problem. What you're seeing is the Stock Recovery from HTC. As far as I know, you can't flash stuff from HTC's recovery.
Give me the output of 'fastboot getvar all'
And also while pasting the output, hide your IMEI and Serial No. it may be used for bad purposes by bad people.
athulele said:
That's not a problem. What you're seeing is the Stock Recovery from HTC. As far as I know, you can't flash stuff from HTC's recovery.
Give me the output of 'fastboot getvar all'
And also while pasting the output, hide your IMEI and Serial No. it may be used for bad purposes by bad people.
Click to expand...
Click to collapse
I found an article in the internet telling that if I copy the OTA update .zip file in my phone's memory, then go to recovery and select that file for update, it will update from 4.0.4 to 4.1.1. Sorry I forgot the link, so can't give you the reference.
Anyway, here is the output of 'fastboot getvar all':
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.2
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3832mV
(bootloader) devpower: 51
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.810s
khalid_saad said:
I found an article in the internet telling that if I copy the OTA update .zip file in my phone's memory, then go to recovery and select that file for update, it will update from 4.0.4 to 4.1.1. Sorry I forgot the link, so can't give you the reference.
Anyway, here is the output of 'fastboot getvar all':
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.2
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3832mV
(bootloader) devpower: 51
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.810s
Click to expand...
Click to collapse
Cool dude! You have a s-off deivce!
Anyway, Backup ALL (Apps, contacts, sdcard) data before you start with the following steps -
1. Keep your bootloader LOCKED.
2. Download this firmware and place it in your fastboot folder. Also download the stock ROM and place it on your device.
3. reboot your phone into fastboot mode
4. Through cmd - fastboot oem rebootRUU
5.You'll have a black screen on the device
6. Just to be sure, flash the firmware zip twice while in RUU mode. (fastboot flash zip firmware.zip)
7. Now go back to fastboot mode ( Power and volume combo)
8. Unlock your bootloader ( please refer HTCDev for instructions)
9. Flash this recovery (fastboot flash recovery recovery.img)
10. Extract the boot.img from the Stock ROM zip and flash it through fastboot (fastboot flash boot boot.img)
11. Go into the recovery. Do a Factory Reset.
12. locate the stock rom and flash it. (if it was erased while unlocking the bootloader, place it again)
13. now reboot
14. If all goes well, you'll boot into stock 4.2.2!
15. if you want to receive further OTA updates (if any)from hTC , flash this recovery.
Hope I helped! Feel free to ask any doubt you have!
athulele said:
Cool dude! You have a s-off deivce!
Anyway, Backup ALL (Apps, contacts, sdcard) data before you start with the following steps -
1. Keep your bootloader LOCKED.
2. Download this firmware and place it in your fastboot folder. Also download the stock ROM and place it on your device.
3. reboot your phone into fastboot mode
4. Through cmd - fastboot oem rebootRUU
5.You'll have a black screen on the device
6. Just to be sure, flash the firmware zip twice while in RUU mode. (fastboot flash zip firmware.zip)
7. Now go back to fastboot mode ( Power and volume combo)
8. Unlock your bootloader ( please refer HTCDev for instructions)
9. Flash this recovery (fastboot flash recovery recovery.img)
10. Extract the boot.img from the Stock ROM zip and flash it through fastboot (fastboot flash boot boot.img)
11. Go into the recovery. Do a Factory Reset.
12. locate the stock rom and flash it. (if it was erased while unlocking the bootloader, place it again)
13. now reboot
14. If all goes well, you'll boot into stock 4.2.2!
15. if you want to receive further OTA updates (if any)from hTC , flash this recovery.
Hope I helped! Feel free to ask any doubt you have!
Click to expand...
Click to collapse
You are freaking awesome dude! I love you!!!!!!!! :laugh:

Unable to flash roms?

Hey there.
I'm fairly new-ish to the Android modification scene. I've had android phones for a while but only recently started rooting etc one my One M8. I've got the Bootloader Unlocked with S-Off and am also on just the stock rom (or I was as I'm in the middle of attempting to get custom roms. :L). My custom recovery is TWRP 2.8.7.0, the latest and the roms I have been trying to install so far are the latest SkyDragon v10 Sense 7 and ViperOne 4.6.0 roms.
In TWRP, when doing this, it will go through the custom installation setup stuff and afterwards it will go into a never ending bootloop for around an hour before I decide to hold volume up and power to switch it off.
Now, before I do the initial installation of the rom, I have wiped data, system, cache and the Dalvik. Regardless, it still causes a boot loop. I have switched the phone off and waited 30 seconds. Still a bootloop. I have gone back into recovery and re-wiped the cache and dalvik and still get this bootloop.
Another thing to note, I have a pending update which is to fix the something which I received at the end of August for the OTA thing and when I put stock recovery back onto the phone to try and do an OTA for that as well, I get the same issue. The only difference is that due to that being the official rom, it also has sound during the bootup but one thing to note (aside from it doing exactly the same and doing a bootloop), the boot animation sound is also delayed by 5 seconds or so, unlike before the update where it plays at the same time as the boot animation.
I am able to successfully restore my TWRP backup of my OS before it attempts something like this and was last working but that's as far as it goes.
I am at a complete loss as I am following any and all tutorials I can find online to the letter and yet I am still having no luck here.
Can anyone assist me on this? It would be much appreciated. Thank you in advance and for reading.
ThatOneJoshy said:
I am able to successfully restore my TWRP backup of my OS before it attempts something like this and was last working but that's as far as it goes.
Click to expand...
Click to collapse
That show your TWRP backup is not stock enough or it is a rooted stock and that is why the OTA failed.
You need a pure non-rooted backup or RUU to successfully update.
What's your device details ?
Run command fastboot getvar all and post here minus the serial & imei no.. maybe someone will be able to point you to right direction.
ckpv5 said:
That show your TWRP backup is not stock enough or it is a rooted stock and that is why the OTA failed.
You need a pure non-rooted backup or RUU to successfully update.
What's your device details ?
Run command fastboot getvar all and post here minus the serial & imei no.. maybe someone will be able to point you to right direction.
Click to expand...
Click to collapse
It's stock firmware that came on the phone, although it is rooted with SuperSU. Whenever I looked online, every forum board said that having a rooted phone wouldn't prevent an OTA, although having a custom recovery would so I would flash the stock recovery back onto the phone and do the update that way which would in turn create this boot loop.
My RUU is/ should be exactly the same as I haven't done anything to change it and also, the updates still come through and are downloaded that way. It also installs (so I think as it goes through the normal process of updating that my phone has always done showing an image of an updating phone with a loading bar at the bottom whilst rebooting a couple of times).
In terms of the details requested, I'm not sure if it will be affected by the rom I just tried installing again for ViperOneM8, but they can be found below:
(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-OFF
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The version I am on on the stock rom is 4.16.401.10. I'm not sure why that is showing, unless it's because of the ViperoneM8 mod I installed which also features the same patch released by HTC apparently.
Yeah, almost everyone say the same thing and those forum are correct for ROMs prior to lollipop.
On lollipop .. root works differently that is why you can't do update on a rooted lollipop stock ROM.
The only suggestion I have is keep your TWRP backup.
Restore a non-rooted 4.16.401.10 TWRP backup and its stock recovery and do the update. After the update, restore your saved data and re-root or install any ROM that you like.
I have one backup in my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Read these thread on how people solved their same problem as yours
http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
http://forum.xda-developers.com/htc-one-m8/help/stuck-boot-ota-update-t3192441

Soft bricked with S-On

I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
xunholyx said:
Download a ROM on your PC and transfer it to an SD card, then flash it in recovery. Wiping everything in recovery doesn't wipe recovery, so you should still have TWRP on your phone.
To get there after you've inserted the SD card with the ROM to flash, power up your phone by holding power+vol down. That will boot you to bootloader. Use the vol keys to navigate to hboot and the power button to select it, and there will be an option to boot to recovery. Navigate to that, then flash the ROM.
Click to expand...
Click to collapse
I tried that, but it doesn't flash the ROM. Instead it starts flashing and then restarts back into TWRP midway. I tried flashing superuser the same way but to no avail.
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
R3dact said:
I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On
Click to expand...
Click to collapse
Are you sure it was ever s-off? S-off isn't need to flash ROMs, root, or a great many other things.
The only way you could have gotten s-off is with the sunshine app ($25); unless you did s-off with firewater before that method was disabled in Dec 2014.
R3dact said:
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Click to expand...
Click to collapse
There is rarely ever a reason to go into the Advanced section. But if you do, its called "Advanced" for a reason. You shouldn't be wiping any partitions on this device without understanding what it means, and what the results will be.
R3dact said:
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part)
Click to expand...
Click to collapse
If you haven't installed a new TWRP version in a year, there is no way its the "latest".
There is also no reason to guess at this. It says the TWRP version number right on the main screen of TWRP. You're always better of giving the specific number, instead of just saying latest. Folks on here often post they have the "latest" TWRP. But once prompted for the actual version number, I often find its something very old, often 2 years old!
R3dact said:
I have an HTC One M8 (International) and I don't remember how, since this happened long ago, but while flashing some ROM I somehow switched my phone back to S-On while the bootloader stayed 'Unlocked' but it showed the 'Tampered' sign.
After an year, my new phone isn't working and I needed to get my old phone back so I took it out and decided to wipe everything because I didn't care about the data inside it and I just wanted all the storage space. Unwittingly I checked every box in the 'Advanced' section of the factory reset menu, including the 'System' checkbox.
Now my phone has no OS, it has an unlocked bootloader with the latest TWRP installed (not completely sure about the latest part) but it shows 'Tampered' below the unlocked text and I've got 'S-On'. I had the Viper ROM on it before if that matters. It wont boot past the HTC screen which has the red text below it that tells us that the version of HTC is for developers.
I really need some help here, I'd greatly appreciate it.
Click to expand...
Click to collapse
Can you plz post fastboot getvar all here without the imei or serial#. We may be able to find you an RUU that may be able to recover your device.
Sent from my Nook HD using XDA Labs
ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
smub said:
===
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================
Click to expand...
Click to collapse
Jesus. 1.54.651.8 OS? That phone has never been updated since forever.
Go to this thread for instructions and links to update your device.
You want the ones that aren't "Harman"
EDIT: You are S-Off, so keep that in mind (security: off from your getvar)
Feel free to send me a PM if you need further instructions.

Stuck on Setup Wizard has Stopped

Hi all,
I had an old M8 that I decided to reflash to stock. Its been a while and clearly I did something wrong. Upon boot up it just pops up with the message " Unfortunately, Setup Wizrd has stopped work". I have read a few post but I cannot access the settings menu. It wont open. Any ideas where I go from here?
Thanks
chigs said:
I had an old M8 that I decided to reflash to stock. Its been a while and clearly I did something wrong.
Any ideas where I go from here?
Click to expand...
Click to collapse
Maybe. If you provide specific details on what exactly you did. Step by step, with file names, version numbers, etc. Also, the state of the device (unlocked bootloader, root, custom ROM, etc.) before you tried to "reflash to stock".
Also, do fastboot getvar all, and post the results. Delete IMEI and serial number before posting.
redpoint73 said:
Maybe. If you provide specific details on what exactly you did. Step by step, with file names, version numbers, etc. Also, the state of the device (unlocked bootloader, root, custom ROM, etc.) before you tried to "reflash to stock".
Also, do fastboot getvar all, and post the results. Delete IMEI and serial number before posting.
Click to expand...
Click to collapse
Unfortunately I don't remember the exact steps I took. I did it a while ago and then after the loop I left the phone in a drawer!
Here are the getvar details.
(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:
(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: 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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
chigs said:
Unfortunately I don't remember the exact steps I took.
Click to expand...
Click to collapse
At least try to remember whatever you can, even if it's not exact. You must remember something. If you don't know what you did, how are we supposed to?
Maybe the file(s) you tried to use to "reflash to stock" is still on your computer? If so, tell us exact version number, and file name.
Was it on a custom ROM and/or root before you tried to "reflash to stock"?
In bootloader, does it say bootloader is LOCKED, UNLOCKED or RELOCKED?
Do you have TWRP installed? And if so, what version?
Maybe the file(s) you tried to use to "reflash to stock" is still on your computer? So I from what I can remember I think I just tried to factory reset the phone. Stupid of me I know.
Was it on a custom ROM and/or root before you tried to "reflash to stock"? I think it was on a Cyanogenmod, rooted,
In bootloader, does it say bootloader is LOCKED, UNLOCKED or RELOCKED? Bootloader says Unlocked
Do you have TWRP installed? And if so, what version Yes I have TWRP v 2.7.0.2
I have tried to do some of my digging but I am not sure what to do as my version-main is blank. I read on a few other posts that I need to flash a stock rom?
My responses below in red font:
chigs said:
Maybe the file(s) you tried to use to "reflash to stock" is still on your computer? So I from what I can remember I think I just tried to factory reset the phone. Stupid of me I know.
Just for your knowledge: Factory reset doesn't reflash anything, or restore the ROM. If a factory reset is actually what you did, all that does is wipe user data. The ROM (system partition) is actually untouched.
Do you have TWRP installed? And if so, what version Yes I have TWRP v 2.7.0.2
This is a horribly obsolete version of TWRP, that isn't compatible with your current firmware (hboot, etc.). But that is just for your info. The TWRP versions is not too relevant, if you choose to follow the next piece of advice:
I have tried to do some of my digging but I am not sure what to do as my version-main is blank. I read on a few other posts that I need to flash a stock rom?
If the intent is to return to stock (and will also be the last version made by HTC, Marshmallow), and which will probably clear up the Setup Wizard issue, you can use the RUU and instructions on the following post. Be aware this will wipe all data from the phone:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks!
Please ignore my last post. Got worried it was stuck again but it just took a very long time to load up. Currently on app optimisation screen. Hopefully all fixed!

HTC one M8

Hope someone can help. My daughter switched on her HTC One M8 after months of not using and it is showing a page with software status modified, locked and s-on. I know nothing about HTC phones. I have spent 2 days trying to get the answer, but it is beyond me. Here is information I have.
(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.206.5
(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: O2___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
all: Done!
finished.
Spontaneously not being able to boot to OS, and "Software Modified" error on a bootloader locked, previously unmodified (far as you know) phone; often means the OS has become damaged/corrupted.
I don't think your version (O2) has an official HTC RUU tool, which would make it pretty easy to get running again. The device can possibly still be recovered, but the process is not trivial. You would need to unlock the bootloader (HTCdev.com process), flash custom recovery TWRP, then install stock TWRP backup 6.13.206.5 from here (with further instructions herein): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
All personal data on the phone will be lost in the process (data on removable SD will remain, if there is one installed). But if your daughter has not used the phone in months, maybe the personal data on it is not important?
redpoint73 said:
Spontaneously not being able to boot to OS, and "Software Modified" error on a bootloader locked, previously unmodified (far as you know) phone; often means the OS has become damaged/corrupted.
I don't think your version (O2) has an official HTC RUU tool, which would make it pretty easy to get running again. The device can possibly still be recovered, but the process is not trivial. You would need to unlock the bootloader (HTCdev.com process), flash custom recovery TWRP, then install stock TWRP backup 6.13.206.5 from here (with further instructions herein): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
All personal data on the phone will be lost in the process (data on removable SD will remain, if there is one installed). But if your daughter has not used the phone in months, maybe the personal data on it is not important?
Click to expand...
Click to collapse
Thank you for your reply, I'll give this a go, and take my time. There is not personal data on the phone that is important, so not a tragedy if I fail. Appreciate your help.
Twinikle said:
Thank you for your reply, I'll give this a go, and take my time. There is not personal data on the phone that is important, so not a tragedy if I fail. Appreciate your help.
Click to expand...
Click to collapse
Hi
I have taken my time and got so far as number 2. I can't find the link to download TWRP backup 6.13.206.5. Where do I access #2,#3, and #4? I have never done this before, and am actually amazed I have got this far! Could you please simplify the procedure for me to complete this?
Twinikle said:
Hi
I have taken my time and got so far as number 2. I can't find the link to download TWRP backup 6.13.206.5. Where do I access #2,#3, and #4? I have never done this before, and am actually amazed I have got this far! Could you please simplify the procedure for me to complete this?
Click to expand...
Click to collapse
TWRP backup 6.13.206.5 is in Post #3 of the same thread (scroll down, third post of that thread), it says that right in the instructions for Step #2.
You don't need stock recovery (step #3). This is only to receive updates, which doesn't apply to this device anymore (updates stopped at Marshmallow) and not useful for what you are trying to so (just restore stock ROM/TWRP backup). So you can skip step #2, as well as stop at Step #9, and just reboot (and hopefully stock ROM will boot). No need to do steps 10 and on. In fact, it is detrimental in doing so, since if you need to use TWRP again, it will be gone if you flash stock recovery.
redpoint73 said:
TWRP backup 6.13.206.5 is in Post #3 of the same thread (scroll down, third post of that thread), it says that right in the instructions for Step #2.
You don't need stock recovery (step #3). This is only to receive updates, which doesn't apply to this device anymore (updates stopped at Marshmallow) and not useful for what you are trying to so (just restore stock ROM/TWRP backup). So you can skip step #2, as well as stop at Step #9, and just reboot (and hopefully stock ROM will boot). No need to do steps 10 and on. In fact, it is detrimental in doing so, since if you need to use TWRP again, it will be gone if you flash stock recovery.
Click to expand...
Click to collapse
Followed all these instructions and it said that the restore was successful. However when I reboot the phone is stuck on the white startup screen. Any further advice?
Twinikle said:
Followed all these instructions and it said that the restore was successful. However when I reboot the phone is stuck on the white startup screen. Any further advice?
Click to expand...
Click to collapse
Some things to try:
- Did you do the wipes as directed in the guide (Dalvik, cache, data, system) before the restore?
- What version of TWRP did you install? If you followed the guide correctly, it should be 2.8.7 (and older versions may not be compatible with your firmware) which is tried and true. But you can also try other versions after 2.8.7 (up to current 3.2.3-1) from here: https://dl.twrp.me/m8/
- Make sure it was the backup version 6.13.206.5 that you restored. Download and restore the backup again, to be sure the files wasn't corrupted. Make sure you restore both system and boot.img partitions.
- After restore, do the default wipe in TWRP (slightly different from what you wiped before: Dalvik, cache, data, but not system), just to be sure.
Twinikle said:
Hope someone can help. My daughter switched on her HTC One M8 after months of not using and it is showing a page with software status modified, locked and s-on. I know nothing about HTC phones. I have spent 2 days trying to get the answer, but it is beyond me. Here is information I have.
(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.206.5
(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: O2___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
all: Done!
finished.
Click to expand...
Click to collapse
How do you get this information. I am a noob.
Sent from my HTC One M9 using Tapatalk
redpoint73 said:
Some things to try:
- Did you do the wipes as directed in the guide (Dalvik, cache, data, system) before the restore?
- What version of TWRP did you install? If you followed the guide correctly, it should be 2.8.7 (and older versions may not be compatible with your firmware) which is tried and true. But you can also try other versions after 2.8.7 (up to current 3.2.3-1) from here: https://dl.twrp.me/m8/
- Make sure it was the backup version 6.13.206.5 that you restored. Download and restore the backup again, to be sure the files wasn't corrupted. Make sure you restore both system and boot.img partitions.
- After restore, do the default wipe in TWRP (slightly different from what you wiped before: Dalvik, cache, data, but not system), just to be sure.
Click to expand...
Click to collapse
I was using TWRP 2.8.7 but updated to 3.2.3-1 and downloaded backup 6.13.206.5 again. I got the same result so continued to your original instructions and followed to number 12 and it worked. Thank you so much for your patience and expertise.
Thabto said:
How do you get this information. I am a noob.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
You need to use HTC fastboot and adb files and then on your pc use command prompt fastboot getvar all
Sorry but I now cannot remember where I got this information, I did a lot of searches on google.
Twinikle said:
I was using TWRP 2.8.7 but updated to 3.2.3-1 and downloaded backup 6.13.206.5 again. I got the same result so continued to your original instructions and followed to number 12 and it worked. Thank you so much for your patience and expertise.
Click to expand...
Click to collapse
You're quite welcome. Glad it worked out for you.
Not sure why it didn't work the first or second time. Maybe you missed a step, or did something slightly incorrect. Of just some glitch, that was not any fault of yours (it happens). Persistence is key, sometimes!

Categories

Resources