Database Info

Noob - HTC One S on T-mobile stuck on edge with S-ON

I recently purchased a phone on ebay in great condition. It was locked, and was on stock rom. I decided I liked how my custom rom operated on my other phone so I unlocked, rooted, and added a custom rom (initally Cyanogenmod, then I tried PacMan) using this tutorial - http://forum.xda-developers.com/showthread.php?t=1583427.
Regardless of the ROM, I haven't been able to get anything over edge data speeds. I've checked the APN settings and they are correct. I have an unlimited data T-Mobile plan.
Here are some pieces of information that might prove helpful:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.13.50.05.31
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
I was told that going back to stock ROM would fix this but that can't be the only way to get 4G...help?

The HTC One S
According to the seller, the phone's model is PJ40110.

My phone got stuck on EDGE after updating to the official JB OTA. I've tried a lot of things and have yet to find a fix. Might have to resort to sending it in for warranty, if possible. Looks like yours is on JB. Did you update it, or did you get it like that?
Here's my thread for reference: http://forum.xda-developers.com/showthread.php?t=2251286

dr3amsINdigital said:
My phone got stuck on EDGE after updating to the official JB OTA. I've tried a lot of things and have yet to find a fix. Might have to resort to sending it in for warranty, if possible. Looks like yours is on JB. Did you update it, or did you get it like that?
Here's my thread for reference: http://forum.xda-developers.com/showthread.php?t=2251286
Click to expand...
Click to collapse
I got it like that, then I updated it and still stuck on edge. Once I have tampered with the bootloader can I still use the warranty?

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.13.50.05.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************************
(bootloader) imei: **************************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4168mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Going to try downloading the appropriate RUU to see if that fixes it.

Have you tried forcing it to WCDMA only in *#*#4636#*#*?

There is no RUU yet for t-mobile JB, not that I know of.
Sent from my HTC VLE_U using xda app-developers app

usaff22 said:
Have you tried forcing it to WCDMA only in *#*#4636#*#*?
Click to expand...
Click to collapse
See attachment - when I do WCDMA only I get no data...

I'm beginning to wonder if it was a hardware issue...perhaps a bad antenna?

goosemon said:
I'm beginning to wonder if it was a hardware issue...perhaps a bad antenna?
Click to expand...
Click to collapse
Doubt this will help, but have you thought about trying to S-Off and then running an old RUU (ICS)? It sounds like it could be a hardware issue, though, as you mentioned.

npiper05 said:
Doubt this will help, but have you thought about trying to S-Off and then running an old RUU (ICS)? It sounds like it could be a hardware issue, though, as you mentioned.
Click to expand...
Click to collapse
I'm working on that now, currently getting error: device not found once I type adb shell to get SUPERCID. Looking at other posts to figure out how to get this to work. Phone connected to computer and showing FASTBOOT USB so the computer sees that it is connected. Once I get SUPERCID then I can get S-Off and try going back to ICS.

With adb shell, am I supposed to have my device driver files in the "platform tools" folder so the adb server can identify my phone? HTC Sense and drivers are already installed and work fine.

goosemon said:
With adb shell, am I supposed to have my device driver files in the "platform tools" folder so the adb server can identify my phone? HTC Sense and drivers are already installed and work fine.
Click to expand...
Click to collapse
Nope, just need HTC Sync, then uninstall it (so you're left with only the drivers) and get adb and fastboot files.
Edit: I don't think adb works in fastboot, works while booted only.
Sent from my HTC One S using Tapatalk 2

I've read that people that updated to the T-Mobile JB OTA can't get super CID, which means they can't get S-OFF. Let us know if it works out for you though.

dr3amsINdigital said:
I've read that people that updated to the T-Mobile JB OTA can't get super CID, which means they can't get S-OFF. Let us know if it works out for you though.
Click to expand...
Click to collapse
So I gotta go back to ICS to get SUPERCID...giving that a shot. At this point my sdcard can't be mounted, trying a fix from http://forum.xda-developers.com/showthread.php?t=1630459&page=25

goosemon said:
So I gotta go back to ICS to get SUPERCID...giving that a shot. At this point my sdcard can't be mounted, trying a fix from http://forum.xda-developers.com/showthread.php?t=1630459&page=25
Click to expand...
Click to collapse
I know you mentioned ADB not working when in fastboot. As a poster mentioned before, ADB only works when phone is booted up, not in fastboot. Make sure you have Debugging checked in developer options in the settings menue. I'm almost certain when you SuperCID, you start off with a booted up phone, not in fastboot, so that my be where you are running into an issue.
Also, do you have a custom recovery installed at this point? Just curios. Will your sd not mount in recovery, or just in general.
Keep working. You'll sort it out and learn a ton in the process. That's why I love XDA. Super helpful community.
Nick

npiper05 said:
I know you mentioned ADB not working when in fastboot. As a poster mentioned before, ADB only works when phone is booted up, not in fastboot. Make sure you have Debugging checked in developer options in the settings menue. I'm almost certain when you SuperCID, you start off with a booted up phone, not in fastboot, so that my be where you are running into an issue.
Also, do you have a custom recovery installed at this point? Just curios. Will your sd not mount in recovery, or just in general.
Keep working. You'll sort it out and learn a ton in the process. That's why I love XDA. Super helpful community.
Nick
Click to expand...
Click to collapse
I'll try ADB in regular bootup once I get sdcard to mount. This is in recovery...the latest clockworkmod recovery, I tried running Viperones rom and it happened sometime around 2 this morning, the details are a little fuzzy, I'm pretty sure I saw red and starting hitting my head against the wall and collapsed in tears and anguish

goosemon said:
I'll try ADB in regular bootup once I get sdcard to mount. This is in recovery...the latest clockworkmod recovery, I tried running Viperones rom and it happened sometime around 2 this morning, the details are a little fuzzy, I'm pretty sure I saw red and starting hitting my head against the wall and collapsed in tears and anguish
Click to expand...
Click to collapse
Been there and definitely understand. It can be frustrating, but I feel like most issues can be sorted out. Have you tried a different USB cord or port on your computer. Seems silly, but I've had similar issues, search high and low on xda, and someone suggested to try to different cord and it mounted. These phones can be moody.
Good luck and report back if you need more help.
Nick

Once I can find and flash stock recovery I think I'll be one step close to accessing my sdcard, and from there stock ROM or ICS ROM so I can get superCID, and then S-OFF.

goosemon said:
Once I can find and flash stock recovery I think I'll be one step close to accessing my sdcard, and from there stock ROM or ICS ROM so I can get superCID, and then S-OFF.
Click to expand...
Click to collapse
The first post in this thread has a link for the stock recovery http://forum.xda-developers.com/showthread.php?t=2250573

[Q] Unfixable radio troubles?

I know I'm an idiot. I didn't do a nandroid backup. Basically I got a stock HTC Inspire recently and started messing with it but after flashing the first ROM I lost all radio ability. It currently has a CWM recovery and is running CM7. I've never been able to get s-off to work and some threads make it seem impossible for my model.
After spending way too much time in the IRC chat with attn1 et al, we've come to the conclusion that HTC has gimped this in the OTA update. They've silently closed the eMMC write protect hole that is used in the downgrade ROM with gfree and would have worked with the stock ROM before the OTA update, but we'll have to work a new angle in the OTA updated Inspires.
Click to expand...
Click to collapse
taken from:
http://forum.xda-developers.com/showthread.php?t=1111557
I'm Unlocked but S-on and my radio is 26.17.14.11_M (which I've seen people from the UK and Belgium using...?)
I've tried a few PD98IMG.zip radios from the bootloader but it always says PD98DIAG.zip - no image and PD98DIAG.nbh - no image or wrong image type and at best kicks me out after parsing. I've also loaded Rils some have suggested, but they don't change anything..
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0030
(bootloader) version-baseband: 26.17.14.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main:
(bootloader) serialno: HT11ZT200200
(bootloader) imei:
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 62d2f26e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.003s
My current mainversion is gibberish right now but I'm pretty sure that's fixable.
So am I basically screwed?

bykfiend42 said:
I know I'm an idiot. I didn't do a nandroid backup. Basically I got a stock HTC Inspire recently and started messing with it but after flashing the first ROM I lost all radio ability. It currently has a CWM recovery and is running CM7. I've never been able to get s-off to work and some threads make it seem impossible for my model.
taken from:
http://forum.xda-developers.com/showthread.php?t=1111557
I'm Unlocked but S-on and my radio is 26.17.14.11_M (which I've seen people from the UK and Belgium using...?)
I've tried a few PD98IMG.zip radios from the bootloader but it always says PD98DIAG.zip - no image and PD98DIAG.nbh - no image or wrong image type and at best kicks me out after parsing. I've also loaded Rils some have suggested, but they don't change anything..
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0030
(bootloader) version-baseband: 26.17.14.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main:
(bootloader) serialno: HT11ZT200200
(bootloader) imei:
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 62d2f26e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.003s
My current mainversion is gibberish right now but I'm pretty sure that's fixable.
So am I basically screwed?
Click to expand...
Click to collapse
You are not able to flash radios with S-ON...I don't get what you are trying to do. CM7 does need work with a different RIL, it needs the original one. RILS must be flashed in sense based roms only.
Reflash CM7 without wiping and that should solve the issue.

glevitan said:
You are not able to flash radios with S-ON...I don't get what you are trying to do. CM7 does need work with a different RIL, it needs the original one. RILS must be flashed in sense based roms only.
Reflash CM7 without wiping and that should solve the issue.
Click to expand...
Click to collapse
I've always heard that you can't flash radios without s-off, but I guess the wording of the post below must have made me think there were other ways.
http://forum.xda-developers.com/showthread.php?p=12264291
I'm not really looking to flash a radio, I was mainly worried that something I did may have accidentally flashed a bad radio. I just want my phone to make and receive calls. I guess I could have just had my wires crossed from the beginning. The first ROM I flashed was a Sense ROM but I didn't know to install a RIL so it only sort of worked. I tried CM next and only really installed a RIL out of desperation. I guess the Inspire radio thread makes radio and RIL sound like a necessary combo.
My wife has the SIM right now so I have to wait until I have it to test the CM7 re-install. Thanks for your help and sorry if my post was confusing; I only added the other info in case it was useful to someone.

bykfiend42 said:
I've always heard that you can't flash radios without s-off, but I guess the wording of the post below must have made me think there were other ways.
http://forum.xda-developers.com/showthread.php?p=12264291
I'm not really looking to flash a radio, I was mainly worried that something I did may have accidentally flashed a bad radio. I just want my phone to make and receive calls. I guess I could have just had my wires crossed from the beginning. The first ROM I flashed was a Sense ROM but I didn't know to install a RIL so it only sort of worked. I tried CM next and only really installed a RIL out of desperation. I guess the Inspire radio thread makes radio and RIL sound like a necessary combo.
My wife has the SIM right now so I have to wait until I have it to test the CM7 re-install. Thanks for your help and sorry if my post was confusing; I only added the other info in case it was useful to someone.
Click to expand...
Click to collapse
That post only made an explanation on how to flash a radio with S-OFF and not ENG S-OFF. Anyway, try reflashing the rom without wiping and see what happens. That should sort the issue out.

glevitan said:
Reflash CM7 without wiping and that should solve the issue.
Click to expand...
Click to collapse
I reflashed CM7 without wiping and it said error while searching for networks. I read in the CM forums that this has been an ongoing problem they were working on so I decided to give up on CM for a while. I wiped the phone, flashed what should have been a rooted stock rom (DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00), flashed a RIL with a version that matched my radio and flashed the boot from inside the rom. It booted up fine and asked for my carrier (AT&T) but I still get no bars. Does it matter that the rom flashed was a DHD rom? I had already tried it without a RIL (it was the first one I fever flashed).

bykfiend42 said:
I reflashed CM7 without wiping and it said error while searching for networks. I read in the CM forums that this has been an ongoing problem they were working on so I decided to give up on CM for a while. I wiped the phone, flashed what should have been a rooted stock rom (DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00), flashed a RIL with a version that matched my radio and flashed the boot from inside the rom. It booted up fine and asked for my carrier (AT&T) but I still get no bars. Does it matter that the rom flashed was a DHD rom? I had already tried it without a RIL (it was the first one I fever flashed).
Click to expand...
Click to collapse
Nope, most DHD roms are compatible with Inspire 4G. Is the back cover on?? the cover were the sdcard is on needs to be on as it is where the antenna is.

glevitan said:
Nope, most DHD roms are compatible with Inspire 4G. Is the back cover on?? the cover were the sdcard is on needs to be on as it is where the antenna is.
Click to expand...
Click to collapse
Actually my back cover has been off this whole time.. After I put it back on it did find the ATT network but when I click on it it says, "Your SIM does not allow a connection to this network." I have a prepaid ATT account but it worked before so I'm not sure what's wrong. Could it be a RIL problem? I'm still on the DHD Rom.

bykfiend42 said:
Actually my back cover has been off this whole time.. After I put it back on it did find the ATT network but when I click on it it says, "Your SIM does not allow a connection to this network." I have a prepaid ATT account but it worked before so I'm not sure what's wrong. Could it be a RIL problem? I'm still on the DHD Rom.
Click to expand...
Click to collapse
No, reboot the device with the cover on. RIL wouldn't do that....I would reflash the stock RUU for Inspire 4G and see what happens....keep the back cover on the whole time.

glevitan said:
No, reboot the device with the cover on. RIL wouldn't do that....I would reflash the stock RUU for Inspire 4G and see what happens....keep the back cover on the whole time.
Click to expand...
Click to collapse
I ran htc_inspire4g_att_RUU_3.20.502.52_US.exe and it successfully installed but at startup it said, "Sim not allowed MM#3."

bykfiend42 said:
I ran htc_inspire4g_att_RUU_3.20.502.52_US.exe and it successfully installed but at startup it said, "Sim not allowed MM#3."
Click to expand...
Click to collapse
Have you tried a different SIM card? maybe what it is flaw is the card and not the device

glevitan said:
Have you tried a different SIM card? maybe what it is flaw is the card and not the device
Click to expand...
Click to collapse
I tried a straight ATT SIM before I ran the RUU and it didn't recognize it. This SIM works in another phone. I can try the ATT card again after the RUU. This is kind of a weird request but I accidentally listed my IMEI on my first post. Can you remove that line from your first reply?

bykfiend42 said:
I tried a straight ATT SIM before I ran the RUU and it didn't recognize it. This SIM works in another phone. I can try the ATT card again after the RUU. This is kind of a weird request but I accidentally listed my IMEI on my first post. Can you remove that line from your first reply?
Click to expand...
Click to collapse
Yes of course. Done..

glevitan said:
Have you tried a different SIM card? maybe what it is flaw is the card and not the device
Click to expand...
Click to collapse
Thanks for the update. I got a new SIM card from ATT and it still gives me the same error. When I Google that error message a lot of forums have been saying either it's the SIM card or your phone is bricked. Is there anything else I can do at this point?

bykfiend42 said:
Thanks for the update. I got a new SIM card from ATT and it still gives me the same error. When I Google that error message a lot of forums have been saying either it's the SIM card or your phone is bricked. Is there anything else I can do at this point?
Click to expand...
Click to collapse
nope..if it is hardware related then you can not fix it with software...

glevitan said:
nope..if it is hardware related then you can not fix it with software...
Click to expand...
Click to collapse
That sucks. Thank you for help though.

[SOLVED][Q] Phone is freezing after few seconds only. Even in Recovery.

Hello everyone,
My brother bought HTC One X+ so I got his Sensation very recently (though I helped him to Unlock, Root and ViperS it first time)
As a first time HTC user curiously I flashed couple of ROMs and finally settled on ViperS 3.1.2 (full wipe) yesterday
Problem started right after that. Phone started freezing every few seconds. I need to screen off the device for 1-2 minutes and then it will work for another few seconds and then freeze again completely.
Same thing happened in Recovery too. It took 8 battery pulls to flash ViperS again.
Since it is happening in both the Recovery and OS I narrowed it down to either of them
1. Bad SDCard
2. NAND problem
3. Some other hardware problem
Plz advise me as to what I should do to resolve this issue ?
(My brother will laugh at me that I could not handle HTC even for a day )
Thank you so much in advance !!!
UPDATE:
Seemingly re-flashing 4ext Recovery again and re-flashing ROM with full wipe solved the issue.
Thanks to both friends who helped me all the way especially rzr86
UPDATE 2:
Problem came back again. This time even worse
UPDATE 3:
My SDCard was the culprit. So if anyone has same issues first try another card.

try to format sdcard
then reflash vipers rom with full wipe
see how it goes
ddi you try with another sdcard?

rzr86 said:
try to format sdcard
then reflash vipers rom with full wipe
see how it goes
ddi you try with another sdcard?
Click to expand...
Click to collapse
Unfortunately I don't have another SDCard here with me. And Sensation does not have any internal memory or atleast I did not find any.
Should I buy a new SDCard ?

silentvisitor said:
Unfortunately I don't have another SDCard here with me. And Sensation does not have any internal memory or atleast I did not find any.
Should I buy a new SDCard ?
Click to expand...
Click to collapse
no need to buy yet a new sdcard
we didn't even know if it is sdcard's fault
try to format the current one

rzr86 said:
no need to buy yet a new sdcard
we didn't even know if it is sdcard's fault
try to format the current one
Click to expand...
Click to collapse
Ok. Doing a full format now.
Should I re-flash ViperS or try formatted SDCard for sometime ?
Thanks !

silentvisitor said:
Ok. Doing a full format now.
Should I re-flash ViperS or try formatted SDCard for sometime ?
Thanks !
Click to expand...
Click to collapse
Format it once and then put the rom zip in the sdcard and flash it from recovery
Sent from my HTC Sensation Z710e using xda premium

Nice.....!!!!!!!
It seems working fine for now.
Let see.
Thanks rzr86

It froze again now

silentvisitor said:
It froze again now
Click to expand...
Click to collapse
i suggest to use a ruu.exe to return to stock
if you are on S-OFF dont worry you won't lose it
http://forum.xda-developers.com/showthread.php?t=1672425
see if it freezes again

rzr86 said:
i suggest to use a ruu.exe to return to stock
if you are on S-OFF dont worry you won't lose it
http://forum.xda-developers.com/showthread.php?t=1672425
see if it freezes again
Click to expand...
Click to collapse
I'm S-ON and this whole stuff looked quite complicated
Whole phone is working fine except touch screen sometimes, randomly.
Any other ideas/suggestions apart from RUU ?
Thanks !

silentvisitor said:
I'm S-ON and this whole stuff looked quite complicated
Whole phone is working fine except touch screen sometimes, randomly.
Any other ideas/suggestions apart from RUU ?
Thanks !
Click to expand...
Click to collapse
Your phone gets hang or only touch screen becomes unresponsive? I guess you should give a try to touch screen recalibration tool. You can found it in the development section.
Sent from my HTC Sensation Z710e

silentvisitor said:
I'm S-ON and this whole stuff looked quite complicated
Whole phone is working fine except touch screen sometimes, randomly.
Any other ideas/suggestions apart from RUU ?
Thanks !
Click to expand...
Click to collapse
using an ruu we will see if it is a hardware problem
if you still have freezes after ruu then probably it is a hardware issue
once you are on S-ON just relock the bootloader by using the fastboot command
then run the ruu.exe from pc
another suggestion is go to venom tweaks->misc tab->lcd density and change to 250
see how it goes

I flashed ViperS again today morning without wiping and since then it hasn't frozen except once when I was playing music in the background and editing id3 tags of few songs. After few seconds keyboard started typing random letters on its own. Screen off and on and it was good for another few seconds. Except this it has been good all day

Hmm...started again. Keyboard is typing on its own. Otherwise its normal. Virus ?
Which recalibration tool ? Is that safe ?
Is there any way to completely format all the partitions to eliminate any low (system) level virus issue ?
Thanks !

silentvisitor said:
Hmm...started again. Keyboard is typing on its own. Otherwise its normal. Virus ?
Which recalibration tool ? Is that safe ?
Is there any way to completely format all the partitions to eliminate any low (system) level virus issue ?
Thanks !
Click to expand...
Click to collapse
Search the forum where someone succeded to zeroing all partitions
I don't remember the thread unfortunately
But I suggest also to use the ruu
Sent from my HTC Sensation Z710e using xda premium

So after RUUing I will have to re-unlock my bootloader through HTCDev or old token will work ?
Btw, what is this Quick launch thing in Venom Tweaks under Statusbar tab ? What it does ? Found no difference anywhere.
Thanks !

silentvisitor said:
Hmm...started again. Keyboard is typing on its own. Otherwise its normal. Virus ?
Which recalibration tool ? Is that safe ?
Is there any way to completely format all the partitions to eliminate any low (system) level virus issue ?
Thanks !
Click to expand...
Click to collapse
Use this tool to recalibrate your touch screen.
http://forum.xda-developers.com/showthread.php?t=2437293.
It will erase your data to it is advised to make a backup first. Hope this solve your issue.
Sent from my HTC Sensation Z710e

Hey, thanks for the link. Checking it.
I doubt its a screen issue as after this keyboard thing phone hangs too but becomes normal after screen on-off.
@rzr86 Hi, my software version is 3.33 and there is no RUU with this version. What to do?
Thanks guys !

silentvisitor said:
Hey, thanks for the link. Checking it.
I doubt its a screen issue as after this keyboard thing phone hangs too but becomes normal after screen on-off.
@rzr86 Hi, my software version is 3.33 and there is no RUU with this version. What to do?
Thanks guys !
Click to expand...
Click to collapse
No need to follow again the procedure from htcdev site
Only use the unlock code.bin
Post the output from this command
fastboot getvar all
Sent from my HTC Sensation Z710e using xda premium

Here it is :
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.720.6
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4180mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
My local friend here suggested me to try ViperS 1.6.3 to see if it is some issue with ViperS 3.1.2

[Q] Phone stuck on 'quietly brilliant' screen

Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!

mfigrs said:
Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!
Click to expand...
Click to collapse
Anybody feel free to correct me if I am wrong, but you phones HBOOT should say this,
Since you are not rooted ignore whatever is in parenthesis.
(***TAMPERED***)
(***UNLOCKED***)
EVITA PVT SHIP (S-OFF) RL
(CID-11111111)
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Now if I am right, the problem should be that your RUU needs updating. You also seem to be running an old radio version. Your OpenDSP is outdated as well. I would suggest updating your RUU and radio version, I think your OpenDSP should be updated with the RUU. @Madcat8686 would probably be better at explaining everything and being able to give you links, but I think that is the main issue.

The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...

mfigrs said:
The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...
Click to expand...
Click to collapse
Do you know if it was running the Android 4.1.1 update or the original android 4.0.4?

ChadMan097 said:
Anybody feel free to correct me if I am wrong, but you phones HBOOT should say this,
Since you are not rooted ignore whatever is in parenthesis.
(***TAMPERED***)
(***UNLOCKED***)
EVITA PVT SHIP (S-OFF) RL
(CID-11111111)
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012, 18:37:14:-1
Now if I am right, the problem should be that your RUU needs updating. You also seem to be running an old radio version. Your OpenDSP is outdated as well. I would suggest updating your RUU and radio version, I think your OpenDSP should be updated with the RUU. @Madcat8686 would probably be better at explaining everything and being able to give you links, but I think that is the main issue.
Click to expand...
Click to collapse
Not exactly true. It should say what the user had first posted. The reason his radio is old is because you can't change radio on an unmodified phone. Nothing really needs updating as you put it, but an RUU should at least get the phone booting.
Sent from my Evita.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
mfigrs said:
The trick is, the phone doesn't take the RUU update - at least not the recent one from HTC website. I have tried other updates though, and they didn't work either. After the 1st reboot the phone gets stuck on 'quietly brilliant' screen and is never recognized again by the computer, so it just times out.
Besides, I really don't care how much it is outdated as long as it works. Meanwhile - it doesn't, and that is the problem I am trying to fix. Factory reset and recovery didn't work either...
Click to expand...
Click to collapse
That 3.07 RUU doesn't exist for our device, that's why it didn't work. Go to androidruu.com and navigate to the Evita section, there you'll find RUU's for our phone. Find one that is at&t/Cingular and try again.
Sent from my Evita.

mfigrs said:
Hi all,
For no reason - overnight - my phone just stopped working. It displays the 'quietly brilliant' screen forever. It is HTC One X ATT version, unlocked and runs on t-mobile. I already bought it unlocked on Amazon and never 'tampered' with it nor anything.
I tired to obtain help from HTC support - they told me to hold the power button for 3 minutes, then all buttons for 2 minutes - nothing helped. Before I send it for repair I thought I would ask here.
I am able to boot into HBOOT by holding the volume- button. Then if I go into FASTBOOT and connect the phone (all drivers installed) the mode changes to FASTBOOT USB. I've downloaded the 3.07 RUU from HTC and tried that. It recognizes the phone while in the ".. USB" mode and does the 1st step: reboot. The phone boots into 'quietly brilliant' screen and the connection times out.
Next, I downloaded the android SDK and tried to connect with fastboot manually - I am able to connect, but unable to flash anything - signature not matching, etc. Clearing cache didn't help either - that was about all I could do with my skill level.
My HBOOT screen shows the following:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMCC-boot
Apr 2 2012,21:08:24
I've tried many tips from this forum but wasn't able to get anything to work. Help please!
Click to expand...
Click to collapse
In fastboot mode (bootloader) with a command prompt type: fastboot getvar all
Post those details and then we can see the bigger picture. Please edit out your IMEI live when posting.
Edit - (just on the off chance you have superCID)

timmaaa said:
Not exactly true. It should say what the user had first posted. The reason his radio is old is because you can't change radio on an unmodified phone. Nothing really needs updating as you put it, but an RUU should at least get the phone booting.
Sent from my Evita.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
That 3.07 RUU doesn't exist for our device, that's why it didn't work. Go to androidruu.com and navigate to the Evita section, there you'll find RUU's for our phone. Find one that is at&t/Cingular and try again.
Sent from my Evita.
Click to expand...
Click to collapse
Right, but wouldn't that be the latest update for the device. He most likely got the international RUU update.

He can run any Evita RUU later than his current firmware version, it doesn't have to be the latest.
Sent from my Evita.

Hello everyone,
The results of 'getvar all':
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT246W30???? [last 4 digits obscured]
(bootloader) imei: ---
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4126mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Responding to other questions - I think the RUU 3.07 that I downloaded from HTC suport page for ATT phone should normally work. In the filename it says Cingular, however I also tried other RUUs (at least one) that I downloaded from somewhere, and it didn't work as well. I tried flashing just 'boot_signed.img' from one of those ruus - result: failed - because of signature or something like that.
Regards,

Dude, I like I already said, that 3.07 RUU is not for our device, it's for the HTC One. Just because it says Cingular in the filename doesn't mean it's for our device, it just means it's an at&t RUU. Stop trying RUU's from random places, go to this site:
http://androidruu.com/?developer=Evita
That's where you'll find RUU's for Evita.
Sent from my Evita.

Guys, please - that's not the point!
timmaaa said:
Stop trying RUU's from random places, go to this site: (... it doesn't let me keep the link ...)
Click to expand...
Click to collapse
That's exactly the site I got my other RUU from. The first one that I tried was from HTC website and had this filename: "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe". It says "EVITA" as plainly as it could. I am aware of that.
The thing is: both didn't work. OK, I'm going to try another one just for the sake of completeness, but with two previous attempts the story was the same:
1) Turn on the phone holding volume-
2) Select FASTBOOT
3) Connect to USB
4) Launch RUU
5) Click through dialogs, agree to everything
6) Message appears "Verifying information..."
7) New dialog pops up allowing me to select the 3.18.502.6 update
8) I click Next -> Next -> ...
9) The dialog opens with a message that the phone is being "prepared" for update and it will be rebooted to bootloader
10) Phone reboots and goes to the 'quietly brilliant' screen (or more recently - just black screen)
11) Computer shows message "Waiting for bootloader"
12) Computer times out -> the only available option is Exit.
End of story for me. Is there a way to somehow fix that? I'm OK with doing stuff from cmd - it's just that none of the tips I found in this forum actually worked. For example, adb always ends up with error 'device not found' and fastboot only works while the phone is in the fastboot menu, but does not let me flash anything.
Thanks.

Ok, but the only RUU you specifically mentioned up until this point was one that isn't for this device (3.07), which is why I posted that. Maybe you got it from androidruu, but you definitely didn't get it from the Evita section. There's no need to get narky at me for trying to make sure you don't brick your phone after you've already run at least one RUU that isn't for your device.
Perhaps you need to try the 2.20 at&t RUU.
Sent from my Evita.

You could try putting it into RUU mode to try and force it to flash. I had to do that to mine about 5 hours ago. Just go to fastboot, type "fastboot OEM rebootRUU" and try running the RUU from there.
Sent from my HTC One X using xda app-developers app

My apologies for the confusion - the RUU I was mentioning as 3.07 is actually 3.07.2012 - this way it's being referred to on the HTC website, but the software version in it is 3.18. I'm not allowed to post links yet, so it's kind of hard to explain...
I have tried the 'rebootRUU' trick - it didn't do anything. After some experiments I found that letter sizes do matter - when I entered "fastboot oem rebootRUU" the phone actually rebooted. However, it went straight into the 'quietly brilliant' screen and I wasn't even able to go past the "Verifying information" pop-up on the computer - it ended up in 'usb connection timed out' error.
Anyway, I will try 2.20 - if that one doesn't work, I guess I'll have to send it for service.
Thank you all for trying to help.

timmaaa said:
Ok, but the only RUU you specifically mentioned up until this point was one that isn't for this device (3.07), which is why I posted that. Maybe you got it from androidruu, but you definitely didn't get it from the Evita section. There's no need to get narky at me for trying to make sure you don't brick your phone after you've already run at least one RUU that isn't for your device.
Perhaps you need to try the 2.20 at&t RUU.
Sent from my Evita.
Click to expand...
Click to collapse
http :// www htc com /us/support/htc-one-x-att/news (sorry can't post links)
I think the op might be talking about this RUU which i can confirm does indeed work for the One X. If not, try this RUU! You said it was 3.07.2012 but this is 3.07.2013 not sure if just a typo but here's hoping!
As for the phone, if the RUU doesn't work then it might be a hardware issue not letting the phone boot. It's happened to me on the EVO 4G and no amount of software flashing would fix that.
Also, this probably won't make a difference, but make sure to run the RUU as administrator

mfigrs said:
My apologies for the confusion - the RUU I was mentioning as 3.07 is actually 3.07.2012 - this way it's being referred to on the HTC website, but the software version in it is 3.18.
Click to expand...
Click to collapse
3.07.2013 (its not 2012) is neither the RUU number nor the software version, its the date the RUU was posted to the HTC website (March 7, 2013).
The software/RUU number is 3.18.502.6
The software/RUU number is always in the file name.

Stuck on 3G

Long time M8 user with S-OFF and root. Been using GPE H11 (http://forum.xda-developers.com/htc...om-htc-one-m8-gpe-stock-custom-aroma-t3254245) for the last month with no problems until about a week ago when the phone mysteriously got stuck in 3G mode. This weekend tried a lot of things to no avail.
Toggling preferred network from Global and LTE/CDMA
Factory reset via ROM
Full data erase in TWRP 3.0.0.1
New SIM card
Installed mostly stock RUU (DOTTAT_VZWM8_S_OFF_SF_6.0_RUU.zip - http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972)
Restored stock NAND (VZWm8StockNAND.zip - http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972)
HTC Sync Manager - Verizon Software Repair
Both Verizon and HTC support have exhausted all their options and state it must be a hardware issue with the phone. Out of warranty and I dont feel like upgrading, so exploring any other remaining options left. Attached are logcats (captured from syslog) from a stock MM verizon nand (with supersu 2.65), in case you happen to find the smoking gun on the root cause.
Suggestions?
Code:
(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: 6.21.605.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4AHSF0xxxx
(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

BSOD2600 said:
Long time M8 user with S-OFF and root. Been using GPE H11 (http://forum.xda-developers.com/htc...om-htc-one-m8-gpe-stock-custom-aroma-t3254245) for the last month with no problems until about a week ago when the phone mysteriously got stuck in 3G mode. This weekend tried a lot of things to no avail.
Toggling preferred network from Global and LTE/CDMA
Factory reset via ROM
Full data erase in TWRP 3.0.0.1
New SIM card
Installed mostly stock RUU (DOTTAT_VZWM8_S_OFF_SF_6.0_RUU.zip - http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972)
Restored stock NAND (VZWm8StockNAND.zip - http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972)
HTC Sync Manager - Verizon Software Repair
Both Verizon and HTC support have exhausted all their options and state it must be a hardware issue with the phone. Out of warranty and I dont feel like upgrading, so exploring any other remaining options left. Attached are logcats (captured from syslog) from a stock MM verizon nand (with supersu 2.65), in case you happen to find the smoking gun on the root cause.
Suggestions?
Code:
(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: 6.21.605.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4AHSF0xxxx
(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
Click to expand...
Click to collapse
Try flashing the s-on Android 6.0 ruu, then do a factory reset from within bootloader (key is doing this with stock recovery which the s-on ruu has and the s-off one doesn't) to reset NV radio partition.

andybones said:
Try flashing the s-on Android 6.0 ruu, then do a factory reset from within bootloader (key is doing this with stock recovery which the s-on ruu has and the s-off one doesn't) to reset NV radio partition.
Click to expand...
Click to collapse
No offence intended... but have you encountered this situation before and those exact steps were the solution or is this a shot in the dark guess?
Does S-ON really need to be enabled again for a factory reset to reset the NV partition? What's the logic behind that it only gets reset when S-ON vs S-OFF?
Has sunshine been updated so it now can s-off a verizon m8 on MM? Basically not looking to go through all that hassle again, if possible

BSOD2600 said:
No offence intended... but have you encountered this situation before and those exact steps were the solution or is this a shot in the dark guess?
Does S-ON really need to be enabled again for a factory reset to reset the NV partition? What's the logic behind that it only gets reset when S-ON vs S-OFF?
Has sunshine been updated so it now can s-off a verizon m8 on MM? Basically not looking to go through all that hassle again, if possible
Click to expand...
Click to collapse
1) Yes actually I have done this last week, and this is the only known way to reset the radio NV partition.
I wouldn't waste my time posting nonsense.
2) You are not going back to S-ON, did I give you the cmd to set back to S-ON? No... I gave you an S-ON RUU (it's more complete to help your situation). If you don't want help to fix your issue and are going to question a known DEV.. why make a thread asking for help? (I think you can see I am no noob).
3) If you read my post fully... "Try flashing the s-on Android 6.0 ruu, then do a factory reset from within bootloader (key is doing this with stock recovery which the s-on ruu has and the s-off one doesn't) to reset NV radio partition."
I said nothing about going back to S-ON (I said that the S-ON RUU has the stock recovery and the S-OFF one doesn't, and you need to perform the factory reset with the stock recovery). I am not going to make it so you either have to re-pay for Sunshine, or they don't have support anymore without warning you. I told you the key to resetting the NV radio partition, which IMO is your best bet to solve your issue.
Best of luck. It helped me, and many others on GPe ROM with signal/radio issues. I hope it helps you.
If you have a better solution, or even another one, I am all ears and would love to have in on it.
:good:

Gotcha, thanks for taking the time to assist. Much appreciated.
Ok, so did more reading and S-ON also means stock/signed. How can I validate if the various RUU's I'm installing are signed or not instead of guessing? Or happen to have a link for a s-on ruu for MM? I've tried various RUUs from dottat thread...

BSOD2600 said:
Gotcha, thanks for taking the time to assist. Much appreciated.
Ok, so did more reading and S-ON also means stock/signed. How can I validate if the various RUU's I'm installing are signed or not instead of guessing? Or happen to have a link for a s-on ruu for MM? I've tried various RUUs from dottat thread...
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24438995911975645
Use this ruu.

andybones said:
https://www.androidfilehost.com/?fid=24438995911975645
Use this ruu.
Click to expand...
Click to collapse
Done.
Installed DOTTAT_VZWM8_M_S_ON_6_0_RUU.zip via fastboot:
- htc_fastboot oem rebootRUU
- htc_fastboot flash zip DOTTAT_VZWM8_M_S_ON_6_0_RUU.zip
rebooted and waited for android to finish booting past the setup wizard.
Reboot back to HBOOT, selected factory reset. Saw the Phone image with the circle and down arrow, phone rebooted, optimized all the apps again, completed the setup wizard.
Still stuck on 3G.

BSOD2600 said:
Done.
Installed DOTTAT_VZWM8_M_S_ON_6_0_RUU.zip via fastboot:
- htc_fastboot oem rebootRUU
- htc_fastboot flash zip DOTTAT_VZWM8_M_S_ON_6_0_RUU.zip
rebooted and waited for android to finish booting past the setup wizard.
Reboot back to HBOOT, selected factory reset. Saw the Phone image with the circle and down arrow, phone rebooted, optimized all the apps again, completed the setup wizard.
Still stuck on 3G.
Click to expand...
Click to collapse
Very weird, sorry to hear. Maybe someone else has some ideas.
Did you also only get 3g when stock ROM booted?

andybones said:
You are a Verizon user?
Click to expand...
Click to collapse
Yes :/
andybones said:
Did you also only get 3g when stock ROM booted?
Click to expand...
Click to collapse
Yes
In phone info, noticed the CellInfo was showing a lot of xxx for various parameters
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I basically gave up on the stock ruu resetting stuff by now. In reading over the various 'lost LTE' threads, I came across a few who claimed they got it back by installing CM13. Since by now, have nothing to loose, did that... and now its on LTE! CellInfo no longer shows the xxx as before... or is that the default for what it does when not on LTE?
does the order of the text in "preferred network type" actually make a difference in the order the RIL uses? Or purely visual for humans?
'bout to try going back to by NAND GPE backup and see if LTE sticks.

BSOD2600 said:
Yes :/
Yes
In phone info, noticed the CellInfo was showing a lot of xxx for various parameters
View attachment 3744803
I basically gave up on the stock ruu resetting stuff by now. In reading over the various 'lost LTE' threads, I came across a few who claimed they got it back by installing CM13. Since by now, have nothing to loose, did that... and now its on LTE! CellInfo no longer shows the xxx as before... or is that the default for what it does when not on LTE?
View attachment 3744804
does the order of the text in "preferred network type" actually make a difference in the order the RIL uses? Or purely visual for humans?
'bout to try going back to by NAND GPE backup and see if LTE sticks.
Click to expand...
Click to collapse
Glad to see it working again.

BSOD2600 said:
'bout to try going back to by NAND GPE backup and see if LTE sticks.
Click to expand...
Click to collapse
Awesome. GPE restored and LTE is still functional..... except given the speedtest seems 'fake' and more like 3G. Will do more testing tomorrow around town and see if any better speeds than in my basement.
What I really want to know is how CM13 appears to have fixed it. Was a developer a while ago and root analysis is very interesting to me, instead of glossing over the high level summary. I like the meat of the answer Ideas?

BSOD2600 said:
Awesome. GPE restored and LTE is still functional..... except given the speedtest seems 'fake' and more like 3G. Will do more testing tomorrow around town and see if any better speeds than in my basement.
View attachment 3744817
What I really want to know is how CM13 appears to have fixed it. Was a developer a while ago and root analysis is very interesting to me, instead of glossing over the high level summary. I like the meat of the answer Ideas?
Click to expand...
Click to collapse
Might find answers in the thread u found the suggested cm ROM flash to fix. I'm sure others are curious as well.
If you still have the thread ID like to read through it myself. I'm finding that others had luck trying an older radio.img
And yea those are def not 4g speeds

andybones said:
If you still have the thread ID like to read through it myself. I'm finding that others had luck trying an older radio.img
Click to expand...
Click to collapse
Here it is... I think: https://forum.cyanogenmod.org/topic/106195-no-4g-connection/?page=2#comment-569339
Still a shot in the dark though with next to no technical content on WHY this appears to have fixed it
andybones said:
And yea those are def not 4g speeds
Click to expand...
Click to collapse
Once I went outside (and wifi off) did another test and got 28/3 Mbps, which seems a bit better

BSOD2600 said:
Here it is... I think: https://forum.cyanogenmod.org/topic/106195-no-4g-connection/?page=2#comment-569339
Still a shot in the dark though with next to no technical content on WHY this appears to have fixed it
Once I went outside (and wifi off) did another test and got 28/3 Mbps, which seems a bit better
Click to expand...
Click to collapse
Strange, the first post is same suggestion that I gave, then the last vagely explains CM. He was using CM previously 12.1 though (those are the CM forums..) so that makes some sense I guess. We're you ever using CM? I couldn't begin to explain as to why flashing a CM ROM would fix LTE.
Either way it's fixed, and this may hopefully help someone in the future.
Enjoy. :good:

Same problem happened again and same (and faster) solution fixed it.
Went to Europe, so dirty flashed Blues* GPE 5.07.1700.11 MRA58K.H11 over itself selecting GSM instead of Verizon. Phone worked fine with a local SIM a week with HSPA (no LTE since missing bands on phone). Once back in the USA, dirty flashed H11 again, this time selecting Verizon in the installer. Back to stuck on 3G.
Created NAND with TWRP 3.0.0.1, performed a wipe, installed CM13 (cm-13.0-20160507-NIGHTLY-m8.zip), went through the setup, and LTE was now present. Restored the NAND with H11 and still had LTE.
Makes me really curious what CM is doing differently than GPe to 'fix' this. Since a NAND restore doesnt 'break' it, the fix possibly resides in one of the many partitions?

Few months later, same problem, same fix.
No one still has any idea why this works?

BSOD2600 said:
Few months later, same problem, same fix.
No one still has any idea why this works?
Click to expand...
Click to collapse
Could probably tell you how to fix your radios without a factory reset. Just need some time this weekend to double check the syntax.
Sent from my HTC6545LVW using Tapatalk

dottat said:
Could probably tell you how to fix your radios without a factory reset. Just need some time this weekend to double check the syntax.
Click to expand...
Click to collapse
Any ideas on this topic still?
Looks like I went about 6 months before it broke again.