Develop Bugs

[Q] HTC One S-Off, and Unlocked boot looping

Hello,
I have accidentally flashed a GSM rom on my CDMA device(I know stupid of me), and I also did not take a nandroid(very stupid of me). I have access to Recovery, Bootloader, Fastboot, and Adb Sideload. I have tried Sideloading a rom, but I get "This package is for "m7wlv,m7vzw" devices; this is a "m7""
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37TS914979
(bootloader) imei: 990004281570899
(bootloader) meid: 99000428157089
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4006mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
I have tried everything, and I'm pulling at straws here. Help would be super appreciated, and I'd owe you for a lifetime!
Thanks,
Have a wonder night!

I would grab one of Hawk's stock Roms and flash it in philz's recovery.
But it sounds like your CID or something is screwed up.

GrayTheWolf said:
I would grab one of Hawk's stock Roms and flash it in philz's recovery.
But it sounds like your CID or something is screwed up.
Click to expand...
Click to collapse
I ended up fixing it with an RUU I found, however, when I try to install Viper 6.1.0 it successfully installs, but just boot loops. It will get to the htc logo, and just reboot.

meatwad63 said:
I have tried Sideloading a rom, but I get "This package is for "m7wlv,m7vzw" devices; this is a "m7""
Click to expand...
Click to collapse
I think you're using the wrong recovery, make sure that you've downloaded the the m7vzw version. I made this mistake the first time I went to download CWM.

meatwad63 said:
I ended up fixing it with an RUU I found, however, when I try to install Viper 6.1.0 it successfully installs, but just boot loops. It will get to the htc logo, and just reboot.
Click to expand...
Click to collapse
Do you mind giving the steps on how you fixed this problem? I am getting the same error you had in your OP and can't seem to get anything to work.
Thanks

[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?

[Q] Stock ROM question

I currently have TWRP and CM12.1 installed, but the gps isn't working. I've heard flashing a stock rom then getting a gps lock and flashing back to CM resolves this. My question is, does flashing the stock ruu remove TWRP, or the hboot recovery option? My understanding is flashing the ruu should just flash the stock rom and I can easily flash back to CM12.1 from TWRP, is this correct?

rcb0325 said:
I currently have TWRP and CM12.1 installed, but the gps isn't working. I've heard flashing a stock rom then getting a gps lock and flashing back to CM resolves this. My question is, does flashing the stock ruu remove TWRP, or the hboot recovery option? My understanding is flashing the ruu should just flash the stock rom and I can easily flash back to CM12.1 from TWRP, is this correct?
Click to expand...
Click to collapse
flashing a stock RUU will make your phone full stock, so TWRP will be replaced with the stock recovery, its not a problem, after flashing the RUU, just unlock your bootloader again and reflash TWRP recovery, simple as that.

Seanie280672 said:
flashing a stock RUU will make your phone full stock, so TWRP will be replaced with the stock recovery, its not a problem, after flashing the RUU, just unlock your bootloader again and reflash TWRP recovery, simple as that.
Click to expand...
Click to collapse
Is there such a thing as just the stock ROM so I don't have to unlock the bootloader again? I've only seen stock RUUs.

rcb0325 said:
Is there such a thing as just the stock ROM so I don't have to unlock the bootloader again? I've only seen stock RUUs.
Click to expand...
Click to collapse
depends, are you s-on or s-off ?
there are stock roms but I doubt that will fix your issue, you will probably need to use a full RUU package, if your s-on, you will need to relock the bootloader to flash it, and therefore have to uinlock again after your finished, if your s-off then you can flash it whilst unlocked, no need to re-unlock again.

Seanie280672 said:
depends, are you s-on or s-off ?
there are stock roms but I doubt that will fix your issue, you will probably need to use a full RUU package, if your s-on, you will need to relock the bootloader to flash it, and therefore have to uinlock again after your finished, if your s-off then you can flash it whilst unlocked, no need to re-unlock again.
Click to expand...
Click to collapse
I have S-off. How do you flash with the bootloader unlocked?

rcb0325 said:
I have S-off. How do you flash with the bootloader unlocked?
Click to expand...
Click to collapse
post your fastboot getvar all without imei and serial number and we can start by seeing what you have and which RUU to flash

Seanie280672 said:
post your fastboot getvar all without imei and serial number and we can start by seeing what you have and which RUU to flash
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXX
(bootloader) imei2: XXXXXXXXXXX
(bootloader) meid: 99000499856088
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.166s

rcb0325 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXX
(bootloader) imei2: XXXXXXXXXXX
(bootloader) meid: 99000499856088
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.166s
Click to expand...
Click to collapse
here's your RUU, just run it as normal, after its finishede flashing, you will be full stock, no need to lock the bootloader as your s-off, once finished and booted, you can then reflash TWRP recovery and try your rom again
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
---------- Post added at 03:51 AM ---------- Previous post was at 03:30 AM ----------
make sure the rom your trying to flash also supports Verizon devices and never ever turn this one s-on.

Help!!Bricked HTC ONE M8!!

So I bricked my phone while trying to unroot.I've been advised to flash a RUU but I can't find/don't know which one I need.
Help?!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(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: 0P6B11000
(bootloader) cidnum: HTC__621
(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: d5206dbc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
Software Status: Modified
**Relcoked***
***Security Warning****

u can unlocked again then flash TWRP and flash a custom rom using TWRP,
u can find the custom rom in this fourm.
hope it can help.
CID 621? TW version?

I bricked my m8 after flashing the xposed uninstaller. When I start my phone, the first splash HTC screen are shown, then it goes black. No response, no way to enter bootloader or recovery. Sad story. I have no idea what to do. Lol.
Well, I connected it to my pc, then did a adb reboot-bootloader and from there did a factory reset. So far so good.
To OP you will find the correct ruu on HTC website.

http://www.htcdev.com/devcenter/downloads/P50

rbrandser said:
I bricked my m8 after flashing the xposed uninstaller. When I start my phone, the first splash HTC screen are shown, then it goes black. No response, no way to enter bootloader or recovery. Sad story. I have no idea what to do. Lol.
Well, I connected it to my pc, then did a adb reboot-bootloader and from there did a factory reset. So far so good.
Click to expand...
Click to collapse
Could you have also used hardware buttons to access recovery by holding power/vol. up then once the screen turns black release both buttons and hold vol. down? Same thing happened to me when I was flashing a ROM!

rbrandser said:
http://www.htcdev.com/devcenter/downloads/P50
Click to expand...
Click to collapse
That's source code dude, not RUUs. It isn't going to help him.
---------- Post added at 06:37 PM ---------- Previous post was at 06:32 PM ----------
Lone Vindicaor said:
So I bricked my phone while trying to unroot.I've been advised to flash a RUU but I can't find/don't know which one I need.
Help?!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(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: 0P6B11000
(bootloader) cidnum: HTC__621
(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: d5206dbc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
Software Status: Modified
**Relcoked***
***Security Warning****
Click to expand...
Click to collapse
You need the 4.24.709.2 RUU or higher. The important part is the x.xx.709.x You need that 709 in the third series of numbers. And since you are S-On, it has to be the version I mentioned or higher since you can't go backwards with firmware unless you are S-Off.

Thanks you everyone for your quick replies.In the end I flashed a custom recovery (TWRP),and restored my phone from someone elses backup which brought me back to Kitkat.From there I just flashed Skydragon's Marshmallow Rom and I've had no problem so far!
I hope this helps someone else

Lone Vindicaor said:
In the end I flashed a custom recovery (TWRP),and restored my phone from someone elses backup which brought me back to Kitkat.From there I just flashed Skydragon's Marshmallow Rom and I've had no problem so far!
Click to expand...
Click to collapse
Flashing a Kitkat backup (which your phone was not, it was on Lollipop) was an unnecessary step. It would have been the same if you just installed TWRP and went straight to Skydragon MM.

Where to get latest firmware.zip for htc one m8

I have an htc one m8 ATT phone I want to install the ViperOneM8 5.02 rom on which says I need to update the firmware to a marshmellow firmware I think.
Or the latest.
While I have found some documentation how to do this on the net, I am not sure where I obtain these files.
The firmware.zip I believe it is
Help on this would be appreciated
Right now I am using hboot 3.16 and twrp 2.7

I found this link
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
https://www.androidfilehost.com/?w=files&flid=32780
and grabbed the 4.16.1540.8.zip but want to make sure I am grabbing the correct and latest version. Because I don't want to brick my phone

Post your fastboot getvar all result without serial & imei no.
You may need a different firmware if it's AT&T & S-On and also don't use that outdated 2.7 TWRP.

ckpv5 said:
Post your fastboot getvar all result without serial & imei no.
You may need a different firmware if it's AT&T & S-On and also don't use that outdated 2.7 TWRP.
Click to expand...
Click to collapse
For some devices, TWRP 2.7 is recommended due to how older boot loaders may not take it well.
I like TWRP. When its workable, its array of tools is superior to CWM. But after I tried 2.8.x, I decided CWM or TWRP at or below 2.7.0.2 is safer and less crash prone.
When I attempted to boot to recovery it would boot loop. Please be mindful of boot signing. If you so slightly make your OEM software notice things a fuse will make your phone implode.
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?

furboom1240 said:
For some devices, TWRP 2.7 is recommended due to how older boot loaders may not take it well.
Click to expand...
Click to collapse
Read again what he is trying to do man ... he's going to update to Marshmallow firmware and that outdated TWRP 2.7 won't work for him (he can't even install his intended ViperOneM8 5.02 ROM with that outdated TWRP)
..... that's why I said don't use that outdated TWRP

ckpv5 said:
Read again what he is trying to do man ... he's going to update to Marshmallow firmware and that outdated TWRP 2.7 won't work for him (he can't even install his intended ViperOneM8 5.02 ROM with that outdated TWRP)
..... that's why I said don't use that outdated TWRP
Click to expand...
Click to collapse
Good point. For some odd reason CM pairs ROMs and Recoveries. If you check the Dev Auto update option would that be unnecessary.
It's been an itching question I actually had...
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?

I originally had twrp 2.8 on and tried to install the latest. But it was freezing because I think I need a newer version of hboot. which I have 3.16 on it.
I then downgraded to 2.7 to get it working. I installed ViperOnem8 Rom not reading the website successfully. but have issues with wifi, and 2 minute boot times.
"The 5.0.x ROM is based on HTC’s latest M8 Sense 7 Android 6.0.x base and requires you to update your firmware to at least the 6.0.x (Marshmallow) version! If you don’t you will run into some issues such as Wi-Fi not working or No Boot, etc.
We cannot install the firmware for you during ROM installation so you will need to take the steps to update the firmware on your own."
So I need to update my firmware. I have an ATT S-ON phone. But I have no clue where to get the firmware from, and make sure it is the right one and recent.
I need to update my firmware in order for this rom and a newer version of twrp to work correctly

ok, so
I upgraded to 3.11.1700.5 firmware I found. and that was successful.
Then I upgraded my twrp to twrp-3.0.2-0-m8 and that was successful
Now I am trying to install either Revolution Rom, or ViperOnem8 and both have the same problem. After install they keep booting into twrp and won't load.
I tried Cynamod and that installed and booted fine.
I believe both Revolution and Viper use the Aroma installer. Anyone know what is going on with these and a fix to stop it from booting into twrp?

Need advice
ckpv5 said:
Post your fastboot getvar all result without serial & imei no.
You may need a different firmware if it's AT&T & S-On and also don't use that outdated 2.7 TWRP.
Click to expand...
Click to collapse
This my phone info
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21331147A1.14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.34.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 260ae94e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Which RUU can I use ?

vertigo262 said:
ok, so
I upgraded to 3.11.1700.5 firmware I found. and that was successful.
Then I upgraded my twrp to twrp-3.0.2-0-m8 and that was successful
I believe both Revolution and Viper use the Aroma installer. Anyone know what is going on with these and a fix to stop it from booting into twrp?
Click to expand...
Click to collapse
Wrong firmware. You installed an old version of GPE firmware.
You can't install Sense ROM like Revolution and Viper on GPE firmware.
I asked you to post fastboot getvar all to help you but it seems that you made it harder now because you installed a wrong firmware. If it is S-Off, then it is easy to fix.

ckpv5 said:
Wrong firmware. You installed an old version of GPE firmware.
You can't install Sense ROM like Revolution and Viper on GPE firmware.
I asked you to post fastboot getvar all to help you but it seems that you made it harder now because you installed a wrong firmware. If it is S-Off, then it is easy to fix.
Click to expand...
Click to collapse
sorry, I must have missed your response. was in phone hell world!
here it is.
this is what it was
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
this is now
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

vertigo262 said:
sorry, I must have missed your response. was in phone hell world!
here it is.
this is what it was
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
this is now
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First - remove all serial & imei no. from your above post.
As I said, it is not easy to fix this with S-On device. What you can try is to install the latest AT&T 6.20.502.5 firmware first then run 6.20.502.5 RUU
Read this for the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
You can get the RUU here : http://www.htc.com/us/support/htc-one-m8-att/news/

ckpv5 said:
First - remove all serial & imei no. from your above post.
As I said, it is not easy to fix this with S-On device. What you can try is to install the latest AT&T 6.20.502.5 firmware first then run 6.20.502.5 RUU
Read this for the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
You can get the RUU here : http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse
so your saying, install the ruu, update the firmware, then re install viper?
Can't I just update the firmware like I did before? It was S-On before I updated the firmware

The ruu won't install. it says needs more then 30% battery, yet it is fully charged

vertigo262 said:
so your saying, install the ruu, update the firmware, then re install viper?
Click to expand...
Click to collapse
No .. I don't say that ... read again ...
Flash firmware.zip first then RUU ...
or install ROM first, don't reboot the system, but reboot to bootloader, relock bootloader then flash firmware.zip
As you already flashed a wrong firmware, as I said this may work and may not work but the only way that you can try to fix the wrong firmware installed.
---------- Post added at 02:49 PM ---------- Previous post was at 02:49 PM ----------
vertigo262 said:
The ruu won't install. it says needs more then 30% battery, yet it is fully charged
Click to expand...
Click to collapse
Because you have wrong firmware installed.

but with what firmware.zip? I never got the right firmware.zip to begin with so I don't have any firmware files to update with

vertigo262 said:
but with what firmware.zip? I never got the right firmware.zip to begin with so I don't have any firmware files to update with
Click to expand...
Click to collapse
That show you don't read all the posts that I posted .. the firmware.zip is posted in the post that earlier posted
You have to wait for someone else I guess who can write a post that you can understand .. maybe my English is not good enough ... good luck
ckpv5 said:
First - remove all serial & imei no. from your above post.
As I said, it is not easy to fix this with S-On device. What you can try is to install the latest AT&T 6.20.502.5 firmware first then run 6.20.502.5 RUU
Read this for the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
You can get the RUU here : http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse

ok .. now that I understand what you are saying. because you had the RUU .exe and also were explaining how to update the firmware at the same time while the firmware was burried a couple of levels of posts, I didn't understand what you were saying.
so it looks like the firmware updated successfully
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I unlocked the firmware through the htc website with the Unlock_code.bin
because fastbook oem unlock didn't work.
had to reinstall twrp and that worked after reinstall. although lots of mounting file system errors. with /Data I don't know if that's normal.
seems to be fixed after formatting
Now I will try installing a rom

vertigo262 said:
had to reinstall twrp and that worked after reinstall. although lots of mounting file system errors. with /Data I don't know if that's normal.
seems to be fixed after formatting
Now I will try installing a rom
Click to expand...
Click to collapse
Now you got it.
And yes, after changing from GPE to Sense GSM (AT&T) firmware, you need to reinstall TWRP (the latest 3.0.2-0) and you MUST format data partition, in TWRP - select WIPE, Format Data - yes ... because GPE & Sense data partition is of different size.

Please where can i get compatible firmware for my htc one m8s with S.O 1.12.1405.6 . I have been on this over 3 weeks now but all no avail.