Database Info

Warranty exchange while rooted?

So I have a problem, my HOS is constantly disconnecting from the network. It'll only stay connected as long as I'm not browsing using the 4G network, on Wifi works fine, never disconnects.
At first I heard it was a problem with the TMO network and they were working on updates, so I waited; then I heard it was a problem with the HOS and the TMOB RUU version, and loading a HTC EU ROM would solve the problem; then I heard that it was a problem with the radio, but no one has a consistent method of flashing an updated radio with S-ON (some say OK to flash with Clockwork, others not so much luck, seen reports of soft bricks).
I havent seen anyone really find a solution for this problem. Seen folks say the build.prop needs to be updated (which I haven't tried), others have fixed with different ROMs, everyone has a different solution that only appears to work for them.
FWIW
HBOOT-1.09.0000
RADIO-0.16.31501S.16_2
Running TrickDroid 7.1.0
So my thought is that it's a problem with my device (I got it the first day it came out) so I assume it has to be a manufacturing defect that hopefully a warranty exchange would resolve.
I'm down for reloading stock, but as I recall the minute the bootloader is unlocked the disclaimer appeared. Anyone know how to lock the bootloader?
My other question is, has anyone done a warranty exchange or know if they care if the device is rooted since more than likely they'll just reflash it to stock and put it in the refurb stock. I've done warranty exchanges with G1, N1 and MT4G while rooted and no one seemed to care. But now that the bootloader has the disclaimer on boot, I fear I'll be on the hook for the device since it's rooted.

You can flash radio zips cuz you hboot is 1.09
Sent from my HTC One S using xda premium

randomnoob83 said:
You can flash radio zips cuz you hboot is 1.09
Click to expand...
Click to collapse
With clockwork or another method?

With TWRP. I had those disconnect issues with T-Mobile stock everything, but unlike you, I ran the RUU, so yes I got an update HBOOT but those issues are gone.
T-MobileUS HTC One S running Stock Rooted 2.21.

I flashed my radio with clockwork.
Sent from my HTC VLE_U using xda premium

thanks guys. very excited to hear that the new radio solved the issue. I was waffling between ditching the HOS for a GNexus but the camera on the HOS and the overall form factor kept keeping me near.
I'll try it as soon as I get back in town.

Please let us know if this works for you.
My girlfriend just bought a T-Mobile one s after seeing how nice my one x was, and she has been plagued with radio problems the entire time. I've ran the latest T-Mobile US RUU hoping it would fix the issues but it has not.
Obviously, I'd like to hold out as long as possible with rooting her phone incase she needs to return it. Anyway, let us know how it goes.

ota update to 4.1.1 bricked my phone.

i had plenty of battery life and was on 2.20 4.0.4 update prior to installing this OTA. now my phone wont even turn on after i did the update nor will it charge and have the light come on.. any ideas?

Let me guess. You had supercid??
Sent from my HTC One X using Tapatalk 2

if supercid gives problems on the at&t ota, then you should of been s-off cause i did ota fine with s-off and supercid.

idk i havent really heard of it but maybe. anyway to fix this now or ?

no fix

ps3kev said:
idk i havent really heard of it but maybe. anyway to fix this now or ?
Click to expand...
Click to collapse
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.

enduser76 said:
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
Click to expand...
Click to collapse
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems. It could be, but given that some people don't have any problems, it could be anything.

tlazarus said:
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems.
Click to expand...
Click to collapse
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.

redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?

romy134 said:
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
Click to expand...
Click to collapse
If you were S-Off and SuperCID then the OTA should not affect you.
But. WHY are people wanting the stock OTA? It's causing issues because some people don't know if it's going to brick their phones. Please just wait until custom ROMs come based on the OTA. It's much much much easier

redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.

I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium

The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
for the other images other then system that get updated, and with s-off now we don't really get screwed by anything so you might as well see if latest gives any improvements.

enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
People never listen or read up till its to late
Sent from my HTC One X using xda premium

enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.

DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
The guy at the service station didn't really ask me anything other than "what's wrong with your phone?" and I replied "it's not turning on." he said ok and plugged it into his machines and said he was going to run some tests and to take a seat. Five minutes later he said it's not turning on and he's going to replace it, I asked him what could've happen and he gave a few examples (including third party roms, etc) but that it could have been anything from a corrupt file to dropping it on the floor.
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
For me personally, I couldn't get most of the ROM's to work properly, if at all. I kept getting errors like " com.google.process.gapps has stopped working" or something similar and I'd have no phone service (for example) which is why I went back to stock.

DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF

c5satellite2 said:
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
at&t customer service and even technical support have been badass for me last few years only issue is 110 bucks for my phone bill which imo should ive me the right to do whatever i want with my service and my phone without having to pay for tethering or getting throttled ever imo and cheaper early upgrades.

[Q] flashed radio, having problems

Hey all, so i decided i wanted to try out some radios (was running viper xl)
and tried flashing a few different radios
from this thread and
http://forum.xda-developers.com/showthread.php?t=1694012
this section
"These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files."
anyways, now i have been problems, phone randomly thinks sim card is being removed/inserted.
and having random reboots
tried flashing the 3.18 ruu
and flashed viper again,
and am still having these problems
so what else can i do?
any suggestions would be great

Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita

timmaaa said:
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
Click to expand...
Click to collapse
4.2.0
which firmware do i need to upgrade to ?
(i do belive my hboot was 2.15 before) but i cant seem to remember which ruu that would be
edit:
think i just found it
http://forum.xda-developers.com/showthread.php?t=2517148
is that the correct version?

Yeah that's the one you need.
Sent from my MID-1040

Thanks it had been forever since I'd run an ruu , completely forgot about the firmware upgrade
Sent from my HTC One XL using Tapatalk

No problems.
Sent from my MID-1040

timmaaa said:
No problems.
Sent from my MID-1040
Click to expand...
Click to collapse
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.

deepsouth06 said:
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
Click to expand...
Click to collapse
Please post your bootloader details, your recovery version, your current ROM and kernel, and the exact problem you're facing.
Sent from my Evita

timmaaa said:
Please post your bootloader details, your recovery version, your current ROM and kerncontinuehe exact problem you're facing.
Sent from my Evita
Click to expand...
Click to collapse
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.

I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita

timmaaa said:
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
Click to expand...
Click to collapse
Ok, I read something similar to what you are saying and I did flash a radio 1.31 from this link with is 2.15 firmware. http://forum.xda-developers.com/show....php?t=2517148. However the same problem was still happening. After flashing the current radio (from the above attachment), what I have noticed is that the No Sim icon only seems to happen when I have WiFi turned on for an extended time, this was just a brief observation from last night and this morning.
I am about to flash a stock RUU (possibly the 5.18) to 1) get the phone up to date with the latest firmware and 2) to see if this will help with my Sim Card problems. Or should I use a different RUU to start from Stock again?
Also When looking at the Radios thread I dont see any radios that are 1.31 and up for ATT. All of them seem to begin with 0.xx. The thread i am looking at is http://forum.xda-developers.com/showthread.php?t=1694012

The latest RUU is probably your best bet.
Sent from my Evita

timmaaa said:
The latest RUU is probably your best bet.
Sent from my Evita
Click to expand...
Click to collapse
With S-Off and my CID all 1s I wouldnt have to worry about doing the root again? After the RUU i should be able to install TWRP again and then a custom rom?

Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita

deepsouth06 said:
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
Click to expand...
Click to collapse
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.

timmaaa said:
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
Click to expand...
Click to collapse
Much thanks. I will be trying this out.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
redpoint73 said:
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
Click to expand...
Click to collapse
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.

deepsouth06 said:
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
Click to expand...
Click to collapse
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.

redpoint73 said:
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
Click to expand...
Click to collapse
No i havent tried taking it out. I will try that out tonight. If all else fails I may end up going for a referb phone, but now with 5.18 I might hold off for as long as i can.
Thanks for your help as well.

To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Sorry for the long post.

deepsouth06 said:
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Click to expand...
Click to collapse
I doubt that Google Play would have that effect on the SIM. I think its just a coincidence (red herring).
deepsouth06 said:
Sorry for the long post.
Click to expand...
Click to collapse
No need to be sorry. More detail is almost always better. Its the short posts that I have a problem with; where people ask for help and don't give any specifics or details. Makes it much harder to help.

[Q] After succesfull RUU, still stuck at bootlogo

Hello guys,
I got this annoying issue and it drives me insane
Here's the deal:
I have a Sensation XE for 2 years now and i use it as a spare phone, rooted/super-cid/S-OFF from day one and installed many different roms past 2 years.
My girlfriend needed a new phone and i just had a kitkat rom installed but it was still full of bugs so i thought......
Let's install a official RUU and get this sucker back to stock so my girl can use this phone for a while :good:
Here all went wrong
I downloaded the latest RUU (europe version) and relocked the bootloader.
I succesfully installed the RUU and rebooted the device.....i see the Htc bootlogo.....and that is it......after an half hour still the same
Did a reset in the bootloader, no effect...
Ok let's take another RUU and try again, this time i had to put the phone in RUU mode thru ADB, no problem....installed an earlier original ICS RUU succesfully.......rebooted and yeahhhhhh......STUCK AT BOOTLOGO AGAIN!!
Anyone any clue what goes wrong??
Now i'm @ Hboot 1.17 (after RUU) and S-OFF (doesn't matter right?)

g-member said:
Hello guys,
I got this annoying issue and it drives me insane
Here's the deal:
I have a Sensation XE for 2 years now and i use it as a spare phone, rooted/super-cid/S-OFF from day one and installed many different roms past 2 years.
My girlfriend needed a new phone and i just had a kitkat rom installed but it was still full of bugs so i thought......
Let's install a official RUU and get this sucker back to stock so my girl can use this phone for a while :good:
Here all went wrong
I downloaded the latest RUU (europe version) and relocked the bootloader.
I succesfully installed the RUU and rebooted the device.....i see the Htc bootlogo.....and that is it......after an half hour still the same
Did a reset in the bootloader, no effect...
Ok let's take another RUU and try again, this time i had to put the phone in RUU mode thru ADB, no problem....installed an earlier original ICS RUU succesfully.......rebooted and yeahhhhhh......STUCK AT BOOTLOGO AGAIN!!
Anyone any clue what goes wrong??
Now i'm @ Hboot 1.17 (after RUU) and S-OFF (doesn't matter right?)
Click to expand...
Click to collapse
try this
after ruu installation change the cid to the original one

What has supercid got to do with this?
Cid is just a region check.....
Sent from my HUAWEI G6-L11 using XDA Free mobile app

g-member said:
What has supercid got to do with this?
Cid is just a region check.....
Sent from my HUAWEI G6-L11 using XDA Free mobile app
Click to expand...
Click to collapse
yeah i know but if i remember well long time ago a few users reported the same issue
and changing the cid to original one solved the boot problem
try it
you have nothing to lose
edit:actually change it to the one corresponded to the RUU

Verizon M8 3G only FIX

There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,

TekGnosis said:
There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,
Click to expand...
Click to collapse
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.

bacon612 said:
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.
Click to expand...
Click to collapse
I have all of the ruu in one thread which is stickied in the general section.

dottat said:
I have all of the ruu in one thread which is stickied in the general section.
Click to expand...
Click to collapse
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...

bacon612 said:
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...
Click to expand...
Click to collapse
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.

dottat said:
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.
Click to expand...
Click to collapse
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box

bacon612 said:
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box
Click to expand...
Click to collapse
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk

dottat said:
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"

bacon612 said:
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"
Click to expand...
Click to collapse
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk

dottat said:
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!

bacon612 said:
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!
Click to expand...
Click to collapse
Yeah. That's always been the old standby as it sets the nv golden config back.
Sent from my HTC6535LVW using Tapatalk

So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.

bacon612 said:
So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.
Click to expand...
Click to collapse
You can use a Java Card to S-OFF your M8 - check out the Verizon M9 Java Card thread.
(@dottat has one, he is my recommendation - but all are very trustworthy and if someone is closer it may be easier on you to go with them)

Been having this issue myself. Tried RUU, flashing all radios from 4.4.2 on up, factory reset, etc. I'm only getting 3G-- not LTE whatsoever. Any ideas?
Edit: Got a new SIM-- no cigar. Unless there are some network settings that I don't know about, the 4G antenna might just be broken or something

dottat said:
Factory reset on stock recovery now?
Click to expand...
Click to collapse
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.

meskibob said:
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.
Click to expand...
Click to collapse
It's not possible to lose s-off? Did you turn it on yourself?
Sent from my Nexus 6 using Tapatalk

dottat said:
It's not possible to lose s-off? Did you turn it on yourself?
Click to expand...
Click to collapse
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).

meskibob said:
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).
Click to expand...
Click to collapse
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Sent from my Nexus 6 using Tapatalk

dottat said:
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Click to expand...
Click to collapse
Sorry for the confusion, and thanks again!

No dice. On any of these fixes. I've gone through all the RUUs that dottat has posted, full back to stock (with root /s-off). I'm at a complete loss. Does anyone have any other suggestions to try and get this fixed?
After I flashed on of the RUUs I have 4G for about 10 mins, then it bumps back down to 3G. I've checked this in three different cities (Home, Work, Friends) so its not the network in my area. I was thinking of stopping at Verizon, maybe get a new SIM, but I'm not sure if that would work.