Develop Bugs

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.

Soft Bricked M8 in need of help badly

Hi there in need of some help. I have really ****ed up my install of twrp and supersu from my htc one m8.
I followed this person tutorial htconeroot com/htc-one-root I followed everything to the letter apart from enabling Dev enable usb debugging.
1st of all I downloaded this twrp file "openrecovery-twrp-2.7.0.2-m8" when I should have downloaded the latest version of twrp. Such a noob mistake I know now : (
2nd I also downloaded a older version of supersu SuperSU-v2.79-201612051815 which I loaded onto my phone and should have downlaoded the latest version.
I followed all the instruction on the video and when I rebooted after instaling supersu my device is now stuck on the HTC startup screen.
I tried to reboot again going into fastboot and recovery and nothing worked. I know I should have just updated supersu to the latest version but I followed some other peoples advice and now I have completelty screwd my phone I think.
I deleted supersu from twrp and wiped the files as well. My computer now does not recognise my phone folder to be able to install any updated version of supersu or install a ROM. My computer OS is windows 10 and it now sees my phone as a cd drive so cannot install anything on the drive at all.
I can get into twrp but nothing seems to work when I try to reset back to factory settings.
Is there a command line way in geting back into my phone and being able to sort this mess that I have made.
In need of some serious help from the experts here at xda developers.
All help is very much appreciated.
Thanks Steve

tartansteve said:
I followed this person tutorial htconeroot com/htc-one-root I followed everything to the letter apart from enabling Dev enable usb debugging.
Click to expand...
Click to collapse
These random "root" websites just copy content from XDA, and have little or no community to help you. All you need is on XDA, so I recommend stick to XDA.
Such "root" websites also don't give enough information, aren't well organized, and don't update it all. So they are very likely to get you into trouble, as you now know.
tartansteve said:
2nd I also downloaded a older version of supersu SuperSU-v2.79-201612051815 which I loaded onto my phone and should have downlaoded the latest version.
Click to expand...
Click to collapse
What version, if it wasn't SuperSU 2.79?
What version of Android was the phone on when you started? Was it Marshmallow?
tartansteve said:
I can get into twrp but nothing seems to work when I try to reset back to factory settings.
Click to expand...
Click to collapse
There is really no such thing as "reset back to factory settings" especially in TWRP. Just going in and wiping things, isn't going to fix the problem.
Try to fastboot flash an updated version of TWRP. If you were on Marshmallow, try current version 3.1.0-0 from there: https://dl.twrp.me/m8/
Once booted into TWRP, see if you can access the internal storage from your PC. If not, make sure internal storage is checked in "Mount".

(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) 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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Sorry was this version SuperSU-v2.37.zip. I do appologise thats the latest version that I posted and was ment to be this version SuperSU-v2.37.zip this is the one that I installed.
Yes it was marshmallow.
I downloaded the latest version of twrp and can I ask how to re install twrp ??
I cannot access my phone internal storage for some reason my computer is not recognising my phone now. It was before as I installed supersu straight onto my phone internal storage and tried to boot the phone from that. It's now coming up as a cd drive and I cannot access to install anything on it.
In mount all I have
System >>> not checked
cache >>> not checked
Data >>> is checked
Micro SDcard >> is checked
USB-OTG >>> not checked
Thanks again for your help
Steve

tartansteve said:
I downloaded the latest version of twrp and can I ask how to re install twrp ??
Click to expand...
Click to collapse
Flash with fastboot. Which I would assume is the same way you did it before. Instructions on TWRP's website: https://twrp.me/devices/htconem8gsm.html
tartansteve said:
I cannot access my phone internal storage for some reason my computer is not recognising my phone now.
Click to expand...
Click to collapse
Let's get the right version of TWRP on the phone first, and see if that helps. If not, we'll go from there.

Updated twrp
Hi just to let you know that I have booted into the new twrp. I am using FWUL and using simple-ADB and it installed it no problem.
Just cannot seem to find how to install supersu onto my device as my phone is not showing up FWUL OS.

Sorry, what is FWUL?

Updatefor you
Hi just to say that I installed supersu as well the latest version SuperSU-v2.79-201612051815. After rebooting I am back to the htc page. I have no ROM installed at all on this and it's saying there no OS installed on my phone.
I want to install kali Linux Nethunter and I have downlaod the correct files to install.
WillI have to install another OS like Marshmallow or kitkat before installing Kali Nethunter.
Thanks again for yourhelp : ))

[LIVE-ISO][FWUL][STABLE] adb/fastboot without any installation and driver issues
[F]orget [W]indows se [L]inux
Did you not send me there to download it lol : ))

tartansteve said:
I have no ROM installed at all on this and it's saying there no OS installed on my phone.
Click to expand...
Click to collapse
You must have at some point in trying to "fix" the problem, wiped system in TWRP. System is same as ROM/OS. So if you wiped it, it's pretty obvious that no ROM is the result.
Flashing old SuperSU in itself doesn't result in no ROM/no OS. It just makes the phone stuck on boot screen, and flashing the proper SuperSU will fix it.
tartansteve said:
WillI have to install another OS like Marshmallow or kitkat before installing Kali Nethunter.
Click to expand...
Click to collapse
I've never used it. But reading the thread, it looks like you need a fully working OS. So pick a ROM, put it on the phone, and flash it. Then flash Kali Nethunter.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
tartansteve said:
[F]orget [W]indows se [L]inux
Did you not send me there to download it lol : ))
Click to expand...
Click to collapse
Ah, I see it's listed as one of the several options for adb/fastboot in the TWRP install instructions. I've never used that specific one, so the acronym confused me. Any fastboot/adb environment will work about the same. You didn't really need to install anything new on your computer. You already had fastboot on your computer to begin with (to unlock the bootloader), and that would have worked fine to install TWRP.

BackUp File
Hi there and thanks very much for your help very much appreciated. Before I did everything I made a back up and have the files on my desktop they are:
0C77AEECE8C258113148C6FB487946BF97B34672
01C669ECF50A775226B15B9F60EEB522AB34BE2F
I have ten of these files and a deafault file as well. Can I restore these to my hpne at all.
I am going to try and install marshmallow on my phone as that was the last OS that I had. Do I have to have the most current and updated version MM.

tartansteve said:
Before I did everything I made a back up and have the files on my desktop they are:
0C77AEECE8C258113148C6FB487946BF97B34672
01C669ECF50A775226B15B9F60EEB522AB34BE2F
Click to expand...
Click to collapse
What did you use to "backup" the phone? Those don't look like TWRP backup folder names. They look like MD5 verification codes?
Individual TWRP backup folders will usually have name format of the date/time the backup was made, such as: 2017-04-22-20-43-56....
tartansteve said:
I am going to try and install marshmallow on my phone as that was the last OS that I had. Do I have to have the most current and updated version MM.
Click to expand...
Click to collapse
There weren't many different official versions (maybe 1 or 2) of Marshmallow for each M8 carrier version. Any version MM should do.

"locked s-on" cant get to unlock and also stuck
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
===
I HAVE DONE THE WHOLE PROCESS OF HTC DEV UNLOCKING WITH CODE AND EVERYTHING BUT STILL IT IS LOCKED
PLZ REPLY ON E-MAIL IF U CAN OR WHATSAPPP +92 333 23 63 968
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
==============================================================

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.

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!