A somewhat similar problem to this one: https://forum.xda-developers.com/ht...soft-brick-t3504692/post69758285#post69758285
I have a HTC one M8 (obviously).
It successfully has TWRP installed, and until today it had both SuperSU (2.78) and x-posed installed and working.
Earlier today, I was struggling with suspected power failure in the device (it said it had 20-30% power left but it shut off as if completely out of power).
As a result of this, once I started charging it, it could boot fine but had forgotten all my personalization options (what start screen icons, alarms, ringtone etc. and even android device-ID changed, according to titanium backup) though the installed apps were untouched.
So, after I reset the device ID back to the original with titanium backup, I shut it off, made a backup in TWRP, and tried to reload the previous backup with the correct personalization settings.
however, it seems unable to boot into any of the backups I have, not even the one I just made, except for the completely untouched backup that I original made before beginning on rooting.
every other one I try to boot into, it gets stuck on the "HTC powered by Android" splash screen, including the backup of a state that worked mere hours ago.
If anyone has an idea what could be going on I would appreciate the help.
What version TWRP?
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
What version TWRP?
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
TWRP is version 2.7.0.2 (upon investigation, this is a bit out of date. but does that matter seeing as the hardware doesn't change?).
getvar all resulted in:
Code:
(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: **##***#####
(bootloader) imei: ###############
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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
Since this, I've been working on it some more. I think something went wrong with the system or boot partitions, since restoring to factory default and then getting the latest backup of the data on did work. Since then I've been working on re-rooting the phone with majisk.
Though it isn't urgent anymore now that the phone is no longer effectively soft bricked, the fact that TWRP backups didn't work is very disturbing to me, so help getting that working is still appreciated. Hopefully it's just something simple/stupid, like an out of date TWRP.
wild_dog said:
TWRP is version 2.7.0.2 (upon investigation, this is a bit out of date. but does that matter seeing as the hardware doesn't change?).
Click to expand...
Click to collapse
TWRP version absolutely matters. Outdated TWRP is known to cause problems due to incompatibility with later firmware/software. It will probably also fail or cause other problems while trying to root, flash custom ROMs, etc.
Also, it's not just a bit out of that. TWRP 2.7 is something like 3 years old!
Latest TWRP is typically recommended. Currently, that is version 3.1.1. You can get it here: https://dl.twrp.me/m8/
redpoint73 said:
TWRP version absolutely matters. Outdated TWRP is known to cause problems due to incompatibility with later firmware/software. It will probably also fail or cause other problems while trying to root, flash custom ROMs, etc.
Also, it's not just a bit out of that. TWRP 2.7 is something like 3 years old!
Latest TWRP is typically recommended. Currently, that is version 3.1.1. You can get it here: https://dl.twrp.me/m8/
Click to expand...
Click to collapse
0_0 welp, lucky me then that it still was able to go back to the old stock backup... just flashed a new TWRP and am now running a new backup. looks like it also backups more, or at least has a finer controlled partitioning in what it does backup. i'll play around with that a bit, caus I now see that a data backup does not include storage, which is something I would want.
Related
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
Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
boomboxie said:
Hey all, i have a bit of problem here.
To days ago my M8 started to randomly turn off , and now it`s happening more and more often , to point where it is impossible to use.
Before it started it got a bit hot, not to hot, regular htc hot.
Tried: Blues GPE,Lypota GPE (was on this one before things happened), Sky dragoon GPE
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
How does this sudden turn off happen:
It`s fine, when it`s plugged in and charging, sometimes not, tried to test GPE maybe one of them fails, it`s random. When i remove phone from power it works for a while if i don`t press any app, but again it`s like a lottery , sometimes it works for longer sometimes it just dies, and i get more or less stuck on system not booting.
Do anybody have any suggestions ?
Click to expand...
Click to collapse
UPDATE: Seems like it`s mostly happening when installing new apps, or recovering them. Tried to remove sdcard , did`t help.
boomboxie said:
H
Things i tried:
*Reflash rom - FAIL
*Flash diffrent rom - FAIL
*Reroot phone - FAIL
*Wipe everything root again - FAIL
*Start fresh without restoring anything - FAIL
Click to expand...
Click to collapse
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
redpoint73 said:
When you say "FAIL" you mean these things actually don't happen successfully (fail to flash, etc.); or that the random power off persists?
Are you converted to GPE by RUU? Maybe try to RUU to full GPE "stock" and see if that helps.
You may be looking at a bad battery or some other hardware failure (emmc).
Click to expand...
Click to collapse
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Will try to convert to stock GPE with RUU and update on results.
boomboxie said:
Depends some rom fail to flash some works. After flashing power off problem persists. As for now, i`m not able to turn on phone without power cord, but once it`s one, works fine unless i do anything (starting an app and so on)
At the beginning i used Hanson2000`s toolkit to root the phone, and after that installed GPE room.
Click to expand...
Click to collapse
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
boomboxie said:
Will try to convert to stock GPE with RUU and update on results.
Click to expand...
Click to collapse
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
redpoint73 said:
The toolkit hasn't been updated since April 2014! It contains woefully obsolete version of TWRP, and that is probably why some ROMs are failing to flash. Highly advise to update to current TWRP 3.0.
How long have you had the phone, how long on GPE ROMs? Is the firmware up to date?
Do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You can only do this if you have s-off.
You may want to try to RUU back to your stock (probably Sense) version, and see if the random power offs persist.
Click to expand...
Click to collapse
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
Click to expand...
Click to collapse
Be careful with your terminology there, to avoid confusion. From your previous post, you stated you just flashed a GPE ROM.
This isn't the same as "converting" to GPE with RUU, which puts you on GPE firmware, GPE partitioning, etc.
boomboxie said:
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
I don't know what that means, if you don't give details on what you did, and the specific results. But I'm assuming you know how to use command prompt to issue adb/fastboot commands, entered the command, and get no response (or device offline)?
If so, check that you are in bootloader-fastboot mode, have HTC drivers installed, or try different cable or USB port.
---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------
bombo_b said:
To me it looks like a hardware fail, most likely a bad battery. OP says it works when plugged in but dies when not.
My guess ,if all else fail ,is to try a new battery
Click to expand...
Click to collapse
I tend to agree that its a hardware problem. But its always a good idea to return to full stock by RUU, to eliminate the possibility its a software issue, before concluding its a hardware problem.
boomboxie said:
I have newest TWRP installed.
For about 2 years for now. Converted to GPE ever since i got the phone. Yes firmware is up to date.
I can`t seem to manage to make "fastboot getvar all" to work, or i don`t know how.
Click to expand...
Click to collapse
1) at first go to bootloader
2) connect device via usb cable into pc
3) confirm you are in fastboot mode
4) install drivers through htc sync manager
5) download the following zip
6) at first create a new folder in desktop. then copy zip into that folder & extract.
7) while press ''shift'' right clik on the new folder & select ''open command window here''
8) on the command prompt type fastboot getvar all
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Disregard this post.Sorry
boomboxie said:
I managed to run command: here are the results.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Click to expand...
Click to collapse
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
umesh.lk said:
You are still with kitkat firmware. Your version is 3.28.401.9. Try to go to a stock. Confirm whether your problem is a hardware problem or not.
Click to expand...
Click to collapse
What would be the best way to do that ?
boomboxie said:
What would be the best way to do that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
boomboxie said:
I have newest TWRP installed.
Yes firmware is up to date.
Click to expand...
Click to collapse
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
redpoint73 said:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Restore stock ROM and stock recovery for 3.28.401.9, then OTA update up to current MM.
---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------
As I've often found to be the case here, folks claim to be "up to date" without providing any specific details or version numbers, and it turns out they are very much not up to date.
Click to expand...
Click to collapse
Thanks, will update on outcome.
EDIT: I thought i was "up to date" i guess i wasn`t lol, my bad.
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failure.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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. total time: 0.049s
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
boomboxie said:
UPDATE:
Flashed stock rom, did all the updates, nothing has changed same issue persists: Turning off, seem like it`s 90% chance of battery failur
https://www.youtube.com/watch?v=F2SetwqZzKE <- Filmed how it happens/
Click to expand...
Click to collapse
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
umesh.lk said:
At first did you calibration the battery? Is your device still Hot? It's amazing as you could install an ota in such a situation. Turn off Wi-Fi and then check. You're still 50% Battery problem, you have more works to do.
Click to expand...
Click to collapse
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
boomboxie said:
Did calibration of battery with Power+vol up/down method, went to safe mode problem still persists.
No problems with booting into boot-loader, dosn`t power off. once i try to access recovery powers off.
https://www.youtube.com/watch?v=5wgC8ST9lU4
Click to expand...
Click to collapse
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
umesh.lk said:
try to flash firmware through hboot. when it flash look whether sensor_hub.img flushing & flashing correctly happen. then reboot.
Click to expand...
Click to collapse
By that you mean: Connecting phone to PC and flashing Newer recovery or OS ?
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.
Hi, I'll keep this short and simple. The phone is locked, with S-ON and everything is stock, it's running Lollipop 5.0 with stock sense. I've had my M8 since Oct 2014, served me well until Dec 2017 when I switched to the HTC 10. At any rate, I've migrated the majority of my content to the new phone except for a few like telegram secret chat etc. Since I made the switch, I usually keep the M8 switched off and I used it like 4-5 times only since December. My last usage was around early March.
Anyway, come last week. I turned it on and it got stuck on the HTC logo (first time ever). So I booted into recovery which is when I noticed that the software status is now modified vs Official despite never tampering with it. I cleared the cache and attempted a reboot and it got stuck on the "HTC One" logo but that' about it. The only way out of this state is power button + vol up which reboots it again and on and on this goes. It just refuses to go past that stage. Occassionally "android is optimising apps" appears for like 2 sec before the htc One logo shows up again and remains there indefinitely.
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
(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) 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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So just an update, it seems that right now, my device goes straight into fastboot regardless if I choose power down (powering it on again boots it back into fastboot) or restart it (again goes into fastboot).
hemingway60 said:
Any idea on what I could do to make it startup? Preferably without factory resetting. Thank you
Click to expand...
Click to collapse
Probably unlikely to get the phone working and keep your data.
It appears your OS has become corrupted or damaged in some way (it happens). This would explain why it goes straight to bootloader instead of booting to OS. It may also explain why it says software "modified" when you haven't done any mods. Although I haven't seen that happen specifically (showing "modified" due to OS damage on an otherwise stock device); but it does seem logical it would say this (it is possibly reading the damage as some unknown "modification").
Your best bet is to restore factory image using RUU, following the instructions on the following post: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe all data on the phone. But in the current condition (as mentioned), I don't think you have much choice anyway.
The RUU should restore the OS, in addition to updating it to Marshmallow (the last version HTC released for this device).
Hey, appreciate the reply. That's disappointing, considering the phone was literally just sitting inside a desk. Anyway, I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Thanks.
hemingway60 said:
I recalled seeing this post : https://forum.xda-developers.com/showpost.php?p=64883695&postcount=6772 and noticed the OTA release code was 464427 vs 464360 on the RUU file. Is there any significance to this? Ironed bugs perhaps? If it's a better build, can I upgrade to that instead?
Click to expand...
Click to collapse
Both are build number 6.12.401.4.
So I doubt there is any actual difference. If there was any change, it would have a different build number (6.12.401.5 or whatever).
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!