Develop Bugs

[Q] Soft bricked, can't boot after flashing any Rom

Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.

n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..

Did you recently do the GPE conversion?

May be you should try to flash the stock rom and stock recovery then flash the ruu.

Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back

According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go

Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone

We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!

Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.

Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...

n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk

n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks

7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?

Bricked to the Max... (Maybe)

Prologue:
So there I was, caressing my shiny and smooth M8.
At the beginning of the year I S-Offed, and added DigitalHigh's awesome Beyond Stock...
Later on, I used a standard RUU GPE Rom.
After repeated Wi-Fi password amnesia, I wanted Beyond Stock Back.
Flashing "GPE_5.1_M8_DH_080215.zip" gives me an "Error 7" even with repeated wipes... hehe... wipes
Searching didn't give me a coherent answer.
So I though, let's update TWRP... and...
Now
The thing's only usable in Bootloader.
If I go to recovery or ANYTHING, the "Google" logo stares at me in disgust.
Odd detail: I'm using fastboot and when it's stuck on the "Google" logo, entering "adb devices" detects the phone in recovery mode.
I flashed TWRP 2.8.7.0, but all I see is the "Google" logo. (I can still feel vibrations on the screen as if I'm hitting a menu button)
I also tried to "fastboot -w" and it gave me the "remote: not allowed" result.
Actually, I tried to fastboot a lot of things and the result came the same.
Anyways, I'll give a detailed log as soon as I remember how, but the reason I post this is 'cause searching for this doesn't give an understandable or reliable result.
Thanks
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.057s

Give the output of :
Fastboot getvar all
But delete the serial and imei before posting ! If you have an old bootloader you have to use the 2.7 series of TWRP. if you have the latest bootloader (3.18-3.19) you have to use 2.8 series of TWRP !

OOOOOOOOOHHHH, Where I get new M8 bootloader?
Hold Up, going to work, will post 'getvar' later today.

It's there, brah.
Take a look if you can.

It's an AT&T device, you are using it with AT&T ? And you fully converted it from sense to GPE ? You could also :
1: run the GPE ruu again. It will get you on GPE stock again and since you are s-off that should not be a problem of any kind.
2: convert back to sense (original AT&T with software number x.xx.502.x)
i am not sure if the AT&T RUU will cover the "back to sense conversion" so this might be interesting too as it involves the standalone flashing of the firmware first (you need a AT&T firmware, NOT the one posted there !!!)
here is more conversion info :http://forum.xda-developers.com/showthread.php?t=2733523
and here you can get firmwares : http://forum.xda-developers.com/showthread.php?t=2701376
if you want number 2 here is more info with a download link to the latest android L RUU : http://www.theandroidsoul.com/download-att-htc-one-m8-lollipop-ruu-4-28-502-1-75822/

Didnt want to start my own thread due to the shame..
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mike

Sheriff1972 said:
Hi,,
I have managed to remove my OS, without making a backup. All i have running is TWRP. Was going to install CM12.1, but didnt update the M8 to the latest software that contains relevant bootloader. From here it went downhill - fast.
Ended up with no OS, no backkups, and no ability to flash other ROMS i think.
If someone could give me a few ideas, i would really appreciate it.
Click to expand...
Click to collapse
Your case is different and you should start your own thread but there are many same case as yours.
Here is one and the solution is in there.. run RUU - http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
Anything you're not sure, ask there. Don't hijack this thread.

UPDATE: Thanks to ckpv5 and the links that were provided i was able to complete the reinstall - thank you so much!!
Opps - sorry - didnt mean to offend!
Will take a look.
Thanks
Mike

The RUU got me an OS and, right now, that is all I need.
Thank you!!

No WiFi after firmware update

Hi all, I seem to be going around in circles on this.
Basically I returned my M8 to stock and it was all working fine however was on an old version of android.
The phone said there was an update which I installed. Ever since the wireless will not turn on.
I have read some posts on here that if I could upgrade it to the next firmware level (2.26.61.1) the wireless would start working.
However you can only update over wifi or the pc link. I have tried to get the pc link to work. The best I got was the connection working and the download started but stayed at 0% so it clearly wasn't working.
I tried to browse the web also but that didn't work either.
I have done three factory reboots not and it will not enable.
Is there another way of tackling this?

Post your fastboot getvar all result without serial & imei no.
We'll see what actually that you need.

ckpv5 said:
Post your fastboot getvar all result without serial & imei no.
We'll see what actually that you need.
Click to expand...
Click to collapse
Thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(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: ORANG001
(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
all: Done!
finished. total time: 0.007s

Your problem is wrong software version that you restored that's why no wifi.
What you need is 4.19.61.2
Install TWRP 2.8.7.0
Restore 4.19.61.2 backup
Install 4.19.61.2 stock recovery
Check OTA
How-to and needed files you can get them here :
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

ckpv5 said:
Your problem is wrong software version that you restored that's why no wifi.
What you need is 4.19.61.2
Install TWRP 2.8.7.0
Restore 4.19.61.2 backup
Install 4.19.61.2 stock recovery
Check OTA
How-to and needed files you can get them here :
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Perfect! Thank you very much

M8 stuck whilst loading recovery mode..

So i accidentally wiped the phone including the internal storage and the OS instead of factory resetting (wasn't paying attention) and tried to re install the android marshmallow OS onto the phone which didn't work..
i managed to flash the twrp by following another forum where someone had the same problem, using the adb process to flash the bootloader etc but now i can't access the recovery at all, it just says entering recovery and remains idle until i get bored of waiting and power off.
Can anyone help me?
i can provide whatever information is necessary for you to help, just need my phone revitalised as i desperately need it for my new job that i should hopefully be starting at the end of the week.
thanks in advance!

@mcg0v
post getvar all after removing serialno and imei
this info will help to know which RUU you need to flash and return your device to stock
any info you can provide is helpful

C:\Users\mcg0v\Desktop\Android\sdk-tools\sdk-tools>getvar all
'getvar' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\mcg0v\Desktop\Android\sdk-tools\sdk-tools>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.318s
Hope this helps, I'm really not that good with anything Android related as of yet, but i really need this phone fixed asap.

@mcg0v
you post your issue in the wrong forum
your device is HTC One m7
this forum is for HTC One m8
go to this thread http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
this is for your device ask there some one will guide you

I have quite the same problem (and i have One M8). Can't enter TWRP recovery, bootloop - just shows an endless loading, i can start the phone without that by pushing pwr button/VOL+/VOL- at the same time (fastboot mode - ok). I want to get the stock back, but it's impossible without entering TWRP. Can someone help me please? It seems that i do not understand this thing anymore.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(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.049s

andreech95 said:
I have quite the same problem (and i have One M8). Can't enter TWRP recovery, bootloop - just shows an endless loading, i can start the phone without that by pushing pwr button/VOL+/VOL- at the same time (fastboot mode - ok). I want to get the stock back, but it's impossible without entering TWRP. Can someone help me please? It seems that i do not understand this thing anymore.
Click to expand...
Click to collapse
Fastboot erase cache, then flash TWRP again in fastboot. Try TWRP 2.8.1.0, which is an older version (more compatible with your old firmware). Then see if you can boot into recovery.
Or flash signed firmware, to update firmware (yours is ancient) then flash TWRP 2.8.7 and restore a newer stock backup (corresponding to the firmware flashed).

redpoint73 said:
Fastboot erase cache, then flash TWRP again in fastboot. Try TWRP 2.8.1.0, which is an older version (more compatible with your old firmware). Then see if you can boot into recovery.
Or flash signed firmware, to update firmware (yours is ancient) then flash TWRP 2.8.7 and restore a newer stock backup (corresponding to the firmware flashed).
Click to expand...
Click to collapse
Thanks a lot. I've tried the first solution and at least TWRP is now working. I've tried the same thing, but it seems, that it was a wrong version of TWRP

Many apologies, turns out i misread the model and its actually the M7 i have. But im glad that this post is helping others with my original problem and thanks to other members who contributed to helping!
-mcg0v

Reverting to Stock Sense, S-ON (never OFF), which RUU?

Hey Everyone,
I'm trying to revert my M8 to stock sense. I've never S-ON'd, though my phone is all kinds of messed up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.11G
(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: 0P6B13000
(bootloader) cidnum: GLOBA001
(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.008s
Click to expand...
Click to collapse
I bought my phone from a Canadian provider known as Wind Mobile (now rebranded as Freedom Mobile). As you can see there's no firmware listed, and the bootloader is a strange 3.19.0.0000 which I can't seem to find anything on. The lack of firmware listing seems to be a common problem, but it leaves me with a few blanks that leave me unsure on how to proceed.
I've found threads that have RUUs for the same CID & MID, but never for the same bootloader version. I'm not really too sure how to proceed from here as I can't seem to find stock files anywhere for my provider. I'm currently using CRDroid 7.1.1.
I'd like to go back to as stock as possible and receive OTA updates. Can anyone give me some advice on what to use? I've been searching for a few hours now and can't seem to find anything for my specific phone. The one thing I did find was a European based RUU which would probably screw up my radios as I'm located in Canada.
Thank you.

Go to my backup thread linked in my signature and restore stock 6.13.1500.7 backup.
If you want the firmware to be shown on bootloader then flash fw_6.13.1500.7 firmware
How-to is explained there.
First thing .. use correct TWRP version 3.0.x not your current one which I believe is 2.7.x

ckpv5 said:
Go to my backup thread linked in my signature and restore stock 6.13.1500.7 backup.
If you want the firmware to be shown on bootloader then flash fw_6.13.1500.7 firmware
How-to is explained there.
First thing .. use correct TWRP version 3.0.x not your current one which I believe is 2.7.x
Click to expand...
Click to collapse
Thank you so much. You're the best. Got my phone running at pure stock with no issues whatsoever.