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!!

M8 stuck in bootloop(?)

Hey guys,
First off, any help here would be more than appreciated as I am at my wits' end.
So, i shall try and inform you guys as much as I can and hope it suffices. My M8 seems to be stuck in a bootloop. I can get to the bootloader (hboot & fastboot) and that's about it. I tried to flash a new recovery and kernel through fastboot but that doesn't seem to help either. My phone has been unlocked a long time ago but never had any problems until this suddenly happened.
Here is my oem info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA03_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.114.18
(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-MOB003
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS- It is also interesting to note that when my phone is stuck on the white HTC screen, i can hear message notifications and such implying that the phone is still running ( I even mirrored my phone to the pc using USB and I can see my home screen on my laptop but just the HTC screen on the phone.
Thanks a ton in advance

xyzzyx666 said:
I tried to flash a new recovery and kernel through fastboot but that doesn't seem to help either. My phone has been unlocked a long time ago but never had any problems until this suddenly happened.
Click to expand...
Click to collapse
Were you trying to flash anything (such as a custom ROM) to make this happen? If not, why would changing the recovery make a difference? If yes, what did you flash?
Phone was on stock or custom ROM when this started to happen?
Do you have a nandroid backup you can restore?
Also, newer versions of TWRP won't work with your (ancient) hboot, so depending on what TWRP build you flashed, you can just be adding to the problem.

No, I wasn't trying to flash anything which is what baffles me more. My phone just froze all of a sudden and I had to use Power+Volume Up to reboot and it hasn't been starting up ever since.
I'm current;y running a custom ROM (skydragon if I remember well).
The last significant change I remember making was giving the "Clean Master" app accessibility permissions through the settings. Idk why it didn't just ask me to do it through SuperUser there.

As I asked before:
Do you have a nandroid backup you can restore?
If so, try to restore that backup.
Otherwise, try to re-flash the custom ROM.
What version TWRP are you currently on?

Boot loop problem

Hi, I'm in need of some assistance if anyone is willing to help.
Just updated to Marshmallow few day ago through OTA. Since my M8 has only 16GB of internal storage decided to root so that I can move some apps to SD. It's my first time rooting a device so I searched through the forum and followed these steps:
1) I have succesffully unlocked bootloader
2) flashed TWRP 2.8.7.0
3) downloaded and installed SuperSU-v2.67 ( from chainfire's download page ) via recovery
After that the only way to get to bootloader is to hold volume up+power and after screen goes blank press volume down. No way of getting back to TWRP recovery, even tried factory reset via bootloader and no changes. Any advice would be greatly appreciated.
More info on device:
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: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxx
(bootloader) imei: xxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(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

Boot loop problem solved by flashing RUU found HERE . I still have to figure out what went wrong with rooting in the first place
Edit:
Did it! I got stuck to boot loop again when I accepted automatic install of Super Su in TWRP. Everything worked when I manually intalled Super Su v2.67. Got root access finally

0taurus0 said:
I got stuck to boot loop again when I accepted automatic install of Super Su in TWRP. Everything worked when I manually intalled Super Su v2.67. Got root access finally
Click to expand...
Click to collapse
TWRP isn't updated to root MM, so the result is a bootloop.

HTC One M8 - Having trouble updating to 6.0

Hi guys,
I have tried what seems like 10+ ROMS, I have flashed them using TWRP and the closest I have gotten to 6.0 was being stuck on the new google logo screen.
Currently I am running Cyanogenmod cm-12.1-2015090.
my getvar all is as follows,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would be really grateful if someone could please point me in the right direction.

I am now open to the idea of taking it back to stock, except I'm not sure how to do that either

Dramli said:
Hi guys,
I have tried what seems like 10+ ROMS, I have flashed them using TWRP and the closest I have gotten to 6.0 was being stuck on the new google logo screen.
Currently I am running Cyanogenmod cm-12.1-2015090.
my getvar all is as follows,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(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: 55eb39ab
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would be really grateful if someone could please point me in the right direction.
Click to expand...
Click to collapse
You need to update your firmware, and a ROM won't do that for you.
Download this firmware and place it into your fastboot folder. Then hook up your phone to your PC, and enter these commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip M8_6.12.1540.4_DevEd_NoWipe_TWRP3001.zip
The flash will halt at 75% to 90%. That's normal and gives you a chance to check the console output to make sure that it's safe to reboot. With most errors it is. If you get error 90, re-run the zip with the same "fastboot flash zip" command as above. Same goes for error 152.
After you've checked your console, enter fastboot reboot-bootloader to complete the firmware flash

xunholyx said:
You need to update your firmware, and a ROM won't do that for you.
CANNOT POST LINK and place it into your fastboot folder. Then hook up your phone to your PC, and enter these commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip M8_6.12.1540.4_DevEd_NoWipe_TWRP3001.zip
The flash will halt at 75% to 90%. That's normal and gives you a chance to check the console output to make sure that it's safe to reboot. With most errors it is. If you get error 90, re-run the zip with the same "fastboot flash zip" command as above. Same goes for error 152.
After you've checked your console, enter fastboot reboot-bootloader to complete the firmware flash
Click to expand...
Click to collapse
Downloading it right now to try,
Once I update the firmware, is there a specific ROM that is tailored to my phone?
Also is my phone considered "Developer Edition"?
Thank you so much for the reply, I have spent hours on this and it seems I may be nearing the end.

Dramli said:
Downloading it right now to try,
Once I update the firmware, is there a specific ROM that is tailored to my phone?
Also is my phone considered "Developer Edition"?
Thank you so much for the reply, I have spent hours on this and it seems I may be nearing the end.
Click to expand...
Click to collapse
Yes, your MID and firmware are DevEd.
As far as ROMs go, anything in the general M8 development forum (not in the Sprint or Verizon forums) should work for you

xunholyx said:
Yes, your MID and firmware are DevEd.
As far as ROMs go, anything in the general M8 development forum (not in the Sprint or Verizon forums) should work for you
Click to expand...
Click to collapse
Thanks for all your advice, unfortunately no other ROM aside from Cyanogenmod will work.
I have updated the firmware and tried the HD ROM, Skydragon ROM, GPE ROM.. they all say installed but none will boot.
Edit: I had made a stock recovery from a long time ago and when I recover and try to do the OTA update the phone restarts and takes me to TWRP Recovery.