Bounty/Donation

[Dan Tekle]

If anyone can solve my problem, I've got a donation coming your way. I've got a Verizon HTC One M8 and cannot run GPE or AOSP based Roms without having intermittent cellular connectivity issues. Phone works fine on sense based though. I've tried all of the obvious things like RUU and factory reset from both bootloader as well as stock recovery. I also tried new sim cards too. If anyone has new ideas I'm all ears!

Sent from my HTC6525LVW using XDA-Developers mobile app

 

[redpoint73]

Is your firmware up to date?

If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

 

[SeanHacker]

These issues have been posted a ton by users on AOSP based firmware. Not sure about GPE as I've never personally used it on this device. But it's just something that will eventually be fixed upstream.

 

[Dan Tekle]

Is your firmware up to date?

If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Yes, FW is vzw up to date. I'll get other info too.

Sent from my HTC6525LVW using XDA-Developers mobile app

 

[Dan Tekle]

These issues have been posted a ton by users on AOSP based firmware. Not sure about GPE as I've never personally used it on this device. But it's just something that will eventually be fixed upstream.

I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.

Sent from my HTC6525LVW using XDA-Developers mobile app

 

[redpoint73]

I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.

I think in this case, SeanHacker was (confusingly) using the term "firmware" to be synonymous with ROM. There is not such thing as AOSP firmware (such as firmware.zip with hboot, radio, etc.) in the sense you are I are talking about firmware.

I think he basically means its a ROM issue, that will hopefully be fixed.

 

[Dan Tekle]

I think in this case, SeanHacker was (confusingly) using the term "firmware" to be synonymous with ROM. There is not such thing as AOSP firmware (such as firmware.zip with hboot, radio, etc.) in the sense you are I are talking about firmware.

I think he basically means its a ROM issue, that will hopefully be fixed.

Yea, I figured. However I'm in the very small minority (I think) with these issues. Others using cm13 and GPE roms don't have them.

Sent from my HTC6525LVW using XDA-Developers mobile app

 

[SeanHacker]

I think in this case, SeanHacker was (confusingly) using the term "firmware" to be synonymous with ROM. There is not such thing as AOSP firmware (such as firmware.zip with hboot, radio, etc.) in the sense you are I are talking about firmware.

I think he basically means its a ROM issue, that will hopefully be fixed.

Yeah. Not sure why I said firmware. I meant ROM. ?

 

[SeanHacker]

I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.

Sent from my HTC6525LVW using XDA-Developers mobile app

Yea, I figured. However I'm in the very small minority (I think) with these issues. Others using cm13 and GPE roms don't have them.

Sent from my HTC6525LVW using XDA-Developers mobile app

Yep. I meant ROM. Not firmware issue. You're definitely not in a small minority. I have seen tons of posts on twitter, g+, XDA, ect with the same issues. I see the issue every day as I only use AOSP. I've been working on the issue myself trying to resolve the problem.

 

[xunholyx]

I'm on Sense firmware. It's there Roms, not the FW that I'm having issues with.

Sent from my HTC6525LVW using XDA-Developers mobile app

Of course you have Sense firmware. You have a Verizon M8 and can't have GSM.
Have you tried to flash back to stock to see if the problem persists? I'm not sure if there is a Verizon RUU available (there probably is), but running an RUU should fix everything.
If you do a restore after, and you get problems again, then you'll have to suss out the source to get it fixed.

 

[Dan Tekle]

Of course you have Sense firmware. You have a Verizon M8 and can't have GSM.
Have you tried to flash back to stock to see if the problem persists? I'm not sure if there is a Verizon RUU available (there probably is), but running an RUU should fix everything.
If you do a restore after, and you get problems again, then you'll have to suss out the source to get it fixed.

Already done several RUU's and and I was trying to help the previous person understand that the problem wasn't likely my firmware. If you have something to add that might shed some light or might help, lmk.

Sent from my HTC6525LVW using XDA-Developers mobile app

 

[Dan Tekle]

$25 bucks to anyone who figures it out.

Sent from my HTC6525LVW using XDA-Developers mobile app

 

[redpoint73]

Already done several RUU's and and I was trying to help the previous person understand that the problem wasn't likely my firmware. If you have something to add that might shed some light or might help, lmk.

I don't know what "several RUUs" means (be specific and list the file names), but if its non-VZN RUUs, they won't work and its a really bad idea, as they may even radio brick the phone.

Do fastboot getvar all, and post the results so I can see more info about the phone (delete IMEI and serial number before posting).

 

[Dan Tekle]

Yeah. Not sure why I said firmware. I meant ROM. ?

No worries...

 

[Dan Tekle]

I don't know what "several RUUs" means (be specific and list the file names), but if its non-VZN RUUs, they won't work and its a really bad idea, as they may even radio brick the phone.

Do fastboot getvar all, and post the results so I can see more info about the phone (delete IMEI and serial number before posting).

Alright, here you go! And TIA if you figure this one out . As far as the RUU (Rom Update Utility) I use @dottat's VZWM8_S_OFF_SF_6.0_RUU.zip (File Name).

Please let me know if you need anything else.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader

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.14.20.0930
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429334796
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.266s

 

[redpoint73]

As far as the RUU (Rom Update Utility) I use dottat's VZWM8_S_OFF_SF_6.0_RUU.zip (File Name).

If you ran the RUU, and it installed fully and successfully, but you get the same result on AOSP ROMs; I would have to think its a ROM issue, as SeanHacker has already stated.

 

[Dan Tekle]

If you ran the RUU, and it installed fully and successfully, but you get the same result on AOSP ROMs; I would have to think its a ROM issue, as SeanHacker has already stated.

So nothing out of place in the getvar? And yes no issues with RUU. However it's not just AOSP Roms, its also GPE which makes me think it's a device config issue. I'm stumped and frustrated[emoji16]

Sent from my HTC One_M8 using XDA-Developers mobile app

 

[redpoint73]

So nothing out of place in the getvar? And yes no issues with RUU. However it's not just AOSP Roms, its also GPE which makes me think it's a device config issue. I'm stumped and frustrated[emoji16]

Getvar looks okay, except that the OS number is missing. RUU should have normally have fixed that, but I'm not 100% on how the s-off RUU works.

The VZN and Sprint versions (CDMA versions) of the M8 have different kernels and different firmware. I've seen some folks with the CDMA versions have to play around with one thing or another to get the network to work correctly, even on Sense ROMs.

 

[Dan Tekle]

Getvar looks okay, except that the OS number is missing. RUU should have normally have fixed that, but I'm not 100% on how the s-off RUU works.

The VZN and Sprint versions (CDMA versions) of the M8 have different kernels and different firmware. I've seen some folks with the CDMA versions have to play around with one thing or another to get the network to work correctly, even on Sense ROMs.

Yea I'm familiar with those issues and I've been able to fix initial problem on sense based Roms but never had anything work and stick on GPE or AOSP. The OS version normally shows with the RUU installed but goes blank after a custom ROM is loaded. I'm on the most recent OS though.

Sent from my HTC One_M8 using XDA-Developers mobile app

 

[redpoint73]

The OS version normally shows with the RUU installed but goes blank after a custom ROM is loaded. I'm on the most recent OS though.

The bug of OS being blank is usually due to an old version TWRP. Advise to use TWRP 3.0.2