Unable to flash roms? - One (M8) Q&A, Help & Troubleshooting

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

Related

Soft-bricked(i think) HTC M8. Need some help please!?

A friend of mine messed up his phone when trying to root it. He couldn't explain to me what he did exactly but the phone wouldn t boot anymore. He then tried to flash a rom he got from the htc one m8 android development section. Then phone booted into the os but he had all sorts of problems no signal/camera didn t work etc. I tried to help him get his phone back to stock i flashed the stock recovery.img and boot.img from here http://forum.xda-developers.com/showthread.php?t=2694994 then tried to flash the stock rom also from that link, but it didn t work out. With these thing said i later found out that the carrier number was T-MOB009(not a htc cid as he told me) so i don't think what i did was wise.
How can i get his phone back to the stock rom?
i can enter bootloader and recovery(which is stock as i flashed it from that link), i will post more about the phone when i will have it.
Eddy1911 said:
A friend of mine messed up his phone when trying to root it. He couldn't explain to me what he did exactly but the phone wouldn t boot anymore. He then tried to flash a rom he got from the htc one m8 android development section. Then phone booted into the os but he had all sorts of problems no signal/camera didn t work etc. I tried to help him get his phone back to stock i flashed the stock recovery.img and boot.img from here http://forum.xda-developers.com/showthread.php?t=2694994 then tried to flash the stock rom also from that link, but it didn t work out. With these thing said i later found out that the carrier number was T-MOB009(not a htc cid as he told me) so i don't think what i did was wise.
How can i get his phone back to the stock rom?
i can enter bootloader and recovery(which is stock as i flashed it from that link), i will post more about the phone when i will have it.
Click to expand...
Click to collapse
Grab the nandroid backup for T-MOB009 from the Collection thread
Flash custom recovery(TWRP seeing as the backup was made with TWRP).
Boot into recovery and restore the back up.
ROM he downloaded and installed was probably one of the 3.x ROMs and the issues(Radio - wifi, bluetooth, data etc) all came about as a result of outdated firmware...He probably never bothered to read that he should have the latest firmware before taking the latest ROM.
Ty for your answer. I will try this as soon as i get a hold of the phone. I will get back with feedback.
BerndM14 said:
Grab the nandroid backup for T-MOB009 from the Collection thread
Flash custom recovery(TWRP seeing as the backup was made with TWRP).
Boot into recovery and restore the back up.
ROM he downloaded and installed was probably one of the 3.x ROMs and the issues(Radio - wifi, bluetooth, data etc) all came about as a result of outdated firmware...He probably never bothered to read that he should have the latest firmware before taking the latest ROM.
Click to expand...
Click to collapse
Where do i need to copy the backup? If i copy it on the sd it doesn t show up at the restore thingy
Nevermind i have managed to try and restore it, but it fails it says unable to mount
LE: Nevermind i did the backup, it's kind of hard to guide a total noob through skype but i did it. TY VERY MUCH @BerndM14
Ok so i'm back with a new problem. I did the backup and wanted to update to 4.4.3 with the ota because the phone asked to, so i went and flash the stock recovery and let the phone download and install the ota but now the WIFI does not work it's greyed out. How can i fix this?
Eddy1911 said:
Ok so i'm back with a new problem. I did the backup and wanted to update to 4.4.3 with the ota because the phone asked to, so i went and flash the stock recovery and let the phone download and install the ota but now the WIFI does not work it's greyed out. How can i fix this?
Click to expand...
Click to collapse
Hm, it's not supposed to do that, obviously
Check to see if maybe airplane mode isn't selected, try erasing cache, try factory reset(if all else fails) .
I've never had that issue before *touch wood*
Can't get ota update after unrooting
Hi I hope some one can help, I rooted my phone then I wanted the new update which I ccouldn't get while being rooted, so I unrooted with a step by step guide, when it came to the Cid number I couldn't find one to match so I used a different one, now some of the pre-installed apps are in French n when I download the update after its ready to be installed a message comes up saying can't update please revert back to the official htc software or something along them lines! Any help is very greatful, thanks.
gemmmcdonnell said:
Hi I hope some one can help, I rooted my phone then I wanted the new update which I ccouldn't get while being rooted, so I unrooted with a step by step guide, when it came to the Cid number I couldn't find one to match so I used a different one, now some of the pre-installed apps are in French n when I download the update after its ready to be installed a message comes up saying can't update please revert back to the official htc software or something along them lines! Any help is very greatful, thanks.
Click to expand...
Click to collapse
Don't post the same issue in multiple posts, you already made a thread for this. :good:
I tried facotry resetting/erasing cache etc does not work at all. I know it's weird, i mean it's the update from the carrier, wtf!? here is the info for the phone, maybe it will give you a clue about what's happening with this phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader)
(bootloader)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If i revert to 4.4.2 the wifi works just fine.
Eddy1911 said:
I tried facotry resetting/erasing cache etc does not work at all. I know it's weird, i mean it's the update from the carrier, wtf!? here is the info for the phone, maybe it will give you a clue about what's happening with this phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(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: T-MOB009
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If i revert to 4.4.2 the wifi works just fine.
Click to expand...
Click to collapse
Edit your post and remove the serial no and IMEI you don't share those.
your version number is missing but I'm guessing it would be 3.x considering you did the update.
by reverting to 4.4.2 do you mean just restoring a nandroid ? and it fixes the wifi ?
Try manually flashing the kernel after the update
or flash a custom kernel for 3.x if you can't find the stock one
clsA said:
Edit your post and remove the serial no and IMEI you don't share those.
your version number is missing but I'm guessing it would be 3.x considering you did the update.
by reverting to 4.4.2 do you mean just restoring a nandroid ? and it fixes the wifi ?
Try manually flashing the kernel after the update
or flash a custom kernel for 3.x if you can't find the stock one
Click to expand...
Click to collapse
yes restoring the nandroid backup and the wi fi works just fine
Ok so i helped my friend flash the revolution 21 hd rom and everything works just fine. My question is why do i need to flash the latest firmware when installing the latest stock rom, but when installing custom roms that does not seem to be the case?
Eddy1911 said:
Ok so i helped my friend flash the revolution 21 hd rom and everything works just fine. My question is why do i need to flash the latest firmware when installing the latest stock rom, but when installing custom roms that does not seem to be the case?
Click to expand...
Click to collapse
You need latest firmware for latest custom ROMs as well. Especially as far as the radio is concerned, if you don't have latest firmware you might experience problems with everything related to the radio i.e Data connectivity, wifi, bluetooth
Thank you for this!
BerndM14 said:
You need latest firmware for latest custom ROMs as well. Especially as far as the radio is concerned, if you don't have latest firmware you might experience problems with everything related to the radio i.e Data connectivity, wifi, bluetooth
Click to expand...
Click to collapse
An explanation of these things are always helpful to understand!

I maybe bricked my phone. HELP

Hey guys,
My HTC arrived just hours ago and Ive maybe bricked it already.....
Goal is: Bootloader unlock, s-off, root, custom rom
Ive got the toolkit from Hasoon2000 v2
i62.tinypic.c o m/2rmpnqr.jpg
I have done everything as it said in the instruction, bootloader was unlocked and the twrp version 2.7.0.2 got with success on the phone.
And then Ive tried to flash the MaximusHD Rom without S-off....Wlan didnt worked (I think its because of a wrong firmware) and by every restart there was the disclaimer in a red font in the lower bottom (as if I try to get in recovery) and a restart takes 3-4 minutes.
Then Ive tried to get S-ON via firewater but without successs... I stuck on the adb command "su"...at that point the phone should get a message from supersu..but It doesnt.
Then I flashed the Stock Nand-Backup "TWRP_VODAP001_M8_STOCK_2014-05-01_1.54.161.5_KOT49H.zip" and right after that I got in fastboot and installed the "stock recovery 1.54.61.5 recovery.img". Than Ive done a fullwipe.
Right after that the phone booted without the red disclaimer, but after the boot the display didnt worked...the computer realized it as my HTC, but i saw nothing.
Fastboot works. My phone has a vodafone branding
What should I do? I can spend more and more time downloading gigabytes of data, but that would take days...and I need a phone
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.000
(bootloader) version-baseband: 1.15.2133156
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.349s
Thanks for reading. Pls help
(English is not my mother tongue...im sorry for misunderstandings)
And then Ive tried to flash the MaximusHD Rom without S-off
Click to expand...
Click to collapse
Don't need S-OFF to flash custom ROMs
Wlan didnt worked (I think its because of a wrong firmware
Click to expand...
Click to collapse
Definitely wrong firmware. You're still on 1.54.xxx.x firmware, most of the ROMs out there already updated to 3.x. Unless you specifically downloaded an older ROM version you most likely downloaded the latest one that requires 3.x firmware on the device. Which is why Wlan didn't work. It requires the latest radio firmware in order for data, wifi, bluetooth etc to function properly on the device.
Then Ive tried to get S-ON via firewater but without successs... I stuck on the adb command "su"...at that point the phone should get a message from supersu..but It doesnt.
Click to expand...
Click to collapse
In adb shell? If you're rooted you should have seen the request. I don't see you mentioning that you actually rooted the device, only that you unlocked it and flashed a custom recovery. That being said, odds of Firewater working is pretty slim, you'd have a better chance with Sunshine S-OFF(Same developers) but it's $25. It'll tell you before hand whether it'll work or not, if it works it'll have you pay for it, if it doesn't work it'll tell you and you won't have to pay a thing.
Then I flashed the Stock Nand-Backup "TWRP_VODAP001_M8_STOCK_2014-05-01_1.54.161.5_KOT49H.zip" and right after that I got in fastboot and installed the "stock recovery 1.54.61.5 recovery.img". Than Ive done a fullwipe.
Right after that the phone booted without the red disclaimer, but after the boot the display didnt worked...the computer realized it as my HTC, but i saw nothing.
Fastboot works. My phone has a vodafone branding
What should I do? I can spend more and more time downloading gigabytes of data, but that would take days...and I need a phone
Click to expand...
Click to collapse
Try to restore the nandroid backup again afterwards don't go and do a full wipe(Why you did that in the first place I don't know... )
jjfo said:
(English is not my mother tongue...im sorry for misunderstandings)
Click to expand...
Click to collapse
Your typed English is excellent, please don't apologize.
First off, this phone is not bricked if the screen comes on. You just flashed a ROM that mismatches your firmware, resulting in extremely long boot times (10 minutes or more). Red text on the boot screen is normal once you have flashed custom recovery. So the red text in itself does not mean anything is wrong.
Just flash an older base ROM (HTC software 1.x based) and your phone should boot fine.
Stock ROM and stock kernel (possibly even stock recovery) are best when trying to s-off by firewater (and sunshine as well). Some folks have mentioned success with firewater on past Maximus builds, but I don't know about the latest (Maximus 21) and kind of doubt it. The firewater exploit was patched some time ago. But seeing as your device's bootloader number and radio number indicate a fairly old handset, I'd still hold out some hope that firewater will work. But as mentioned, sotck ROM and stock kernel give you the best chances. Failing that, sunshine is your only option to s-off, as mentioned by another.
I flashed the "TWRP_VODAP001_M8_STOCK_2014-05-01_1.54.161.5_KOT49H.zip" again with all checkboxes checked...and then it worked. After that I go through the instruction step by step and now it works perfectly with venom rom
Thanks for helping out.

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.

Bootloop problem; can't restore to TWRP backup with root.

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.

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