After trying several ROMs that would not connect to VZWs LTE network (Cyanogenmod, LiquidSmooth), I decided to go for a stock-ish ROM: NuSenseSIX-MAX which is an HTC One port. It installed without a hitch and says its on LTE but then after about 10 minutes, switches to 3G and won't go back to LTE unless I reboot the phone, and after 10 minutes, back to 3G. I installed the latest firmware and baseband (1.02.01.0207) so that isnt the issue. Anyone experience this? Have any ideas?
killerroomba said:
After trying several ROMs that would not connect to VZWs LTE network (Cyanogenmod, LiquidSmooth), I decided to go for a stock-ish ROM: NuSenseSIX-MAX which is an HTC One port. It installed without a hitch and says its on LTE but then after about 10 minutes, switches to 3G and won't go back to LTE unless I reboot the phone, and after 10 minutes, back to 3G. I installed the latest firmware and baseband (1.02.01.0207) so that isnt the issue. Anyone experience this? Have any ideas?
Click to expand...
Click to collapse
Any luck finding a fix? I am having the same issue.
You guys need to flash a stock recovery and perform a factory reset with the stock recovery installed.
Many aosp roms corrupt the NV radio partitions and nothing will fix that except stock recovery.
So back up anything important on the device, grab the stock recovery, load it up.
Then either from hboot, or rom settings menu, or from stock recovery (exclamation point/phone image/volume up+power to get menu) factory reset.
That will fix the NV radio partition that corrupt.
Then you can reflash a custom recovery and set back up your rom.
This is the only true fix for this issue.
Yes RUU will fix it too because it does the factory reset with stock recovery as well, but that's not necessary, just having the latest firmware, stock recovery and doing the reset is all it takes. :good:
Same rule applies on the m7 and m8 as well...
santod040 said:
You guys need to flash a stock recovery and perform a factory reset with the stock recovery installed.
Many aosp roms corrupt the NV radio partitions and nothing will fix that except stock recovery.
So back up anything important on the device, grab the stock recovery, load it up.
Then either from hboot, or rom settings menu, or from stock recovery (exclamation point/phone image/volume up+power to get menu) factory reset.
That will fix the NV radio partition that corrupt.
Then you can reflash a custom recovery and set back up your rom.
This is the only true fix for this issue.
Yes RUU will fix it too because it does the factory reset with stock recovery as well, but that's not necessary, just having the latest firmware, stock recovery and doing the reset is all it takes. :good:
Same rule applies on the m7 and m8 as well...
Click to expand...
Click to collapse
Tried this - no love.
Steps done: Flashed stock recovery, chose factory reset from modified hboot, flashed custom recovery and PA 4.6 ROM.
burtonlax said:
Tried this - no love.
Steps done: Flashed stock recovery, chose factory reset from modified hboot, flashed custom recovery and PA 4.6 ROM.
Click to expand...
Click to collapse
Number one cause of the problem: Aosp roms
First thing you went and installed after fixing the issue: Aosp rom
I've been having network issues as well for a couple of months now. I think it's actually a Verizon issue as I just got a certified replacement device that's having the same problems as my old device. The issue seem to have coincided with the latest update/as well as Verizon's switch to xlte for certain phones. My signal strength/bars is a lot weaker than before. I also have a lot of drops to 3g and 1x in a 4g area that seems to have trouble switching back to 4g. When I called to report the issues/get a replacement device they said that they are aware that many DNA users have been having issues since the latest update. Hopefully we get another update to fix these issues. Also I've never loaded anything aosp on this device. Just stock and viper.
Sent from my Nexus 7 using XDA Free mobile app
I had this issue for a very long time. Couldn't stay connected to 4G to save my life. But as Santod said, you need the stock recovery and stock hboot, then do a factory reset from hboot. I have been connected to 4G for the last 3 days since I fixed this prob. Now waiting for my new sim tray. I actually RUU'd to stock 3.06 and still had little to no 4G. Factory reset and instantly connected to 4G. Gave it a whole 24hrs, no issues or disconnects, then weaksauce and firewater. Now back on Viper and I haven't seen 3G or 1X for 3 days and counting. Hope it helps.
--X
I.M.famous XMAN said:
I had this issue for a very long time. Couldn't stay connected to 4G to save my life. But as Santod said, you need the stock recovery and stock hboot, then do a factory reset from hboot. I have been connected to 4G for the last 3 days since I fixed this prob. Now waiting for my new sim tray. I actually RUU'd to stock 3.06 and still had little to no 4G. Factory reset and instantly connected to 4G. Gave it a whole 24hrs, no issues or disconnects, then weaksauce and firewater. Now back on Viper and I haven't seen 3G or 1X for 3 days and counting. Hope it helps.
--X
Click to expand...
Click to collapse
Ok, so I flashed stock recovery and stock hboot and did a factory reset from hboot - however my previous rom still loads... shouldnt the factory reset delete the rom? I'm not sure how to verify the factory reset worked.
burtonlax said:
Ok, so I flashed stock recovery and stock hboot and did a factory reset from hboot - however my previous rom still loads... shouldnt the factory reset delete the rom? I'm not sure how to verify the factory reset worked.
Click to expand...
Click to collapse
Factory reset only erases /data (without wiping /data/media) /cache and resets NV partition.
Sent from my HTC6500LVW using XDA Free mobile app
Related
So I was originally on Gb firmware and decided to upgrade to ICS firmware, the official OTA. I ran the RUU and even did a factory reset and wiped internal/external sd cards. After loading my rom of choice of rom it still have issues switching to 4G so I went all in. I RUU'd back to the latest GB RUU, I went in and did a factory reset, let the phone boot up and went into settings storage and formatted internal/external sd cards. Then I went into settings update and it gave me the 7 mb update, it rebooted and starting installing the ICS update afterwards I booted into hboot and did another factory reset. booted ics up and wiped both internal/external sd cards again, then flashed amon ra recovery via hboot PH98IMG, then restored my backup. I have had no more 4G issues since.
If this thread has no use for you, please leave it alone. Take what you want from it I hope it helps someone. I do ask the trolls to stay away
Thread cleaned.
Do not post unless you want to discuss the topic.
YZ.
Is this for those who have 4G totally disappear, or will this patch also try to solve then issue when moving from 1x back to 4G(not sure if this issue is there with 3G switch back to 4G)? Thanks.
My situation was 4g would totally disappear. Sense roms only. Like my 4g would pop up for half a second only to disappear and 3g took its place. If you try this and are successful please report back. It would be appreciated.
sent from my S-OFF, INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
bigsnack said:
Is this for those who have 4G totally disappear, or will this patch also try to solve then issue when moving from 1x back to 4G(not sure if this issue is there with 3G switch back to 4G)? Thanks.
Click to expand...
Click to collapse
Sometimes when playing around with RUUs and s-off and stuff, it's possible that your phone will lose 4G entirely, like you won't be able to connect to 4G even in a 4G area, I believe that's what the OP is referring to
Edit: ninja'd lol
I had the 4G loss issue as well.
I put in a fresh sim card, and that didn't fix it.
Did the Hboot factory reset trick, a couple of times, and that didn't fix it.
I did a fresh install of the Rom I was on, and that didn't fix it.
I even tried a different Recovery, and that didn't fix it. I put TWRP back on and did a Nandroid.
Then I ran the official ICS RUU that Androidpolice confirmed was the OTA Update. That fixed it.
I put TWRP on again and restored my Rom. Been right as rain ever since.
What happens when you get the 4G loss exactly, and how often does it happen? I've been in my home area for the past few days and haven't lost 4G once.
I ran the .10 ICS ruu while back, not sure if that did anything. I never had drops when I was on GB either. Do you think the problem is on Verizon's end?
It happens because when you ruu, you need to do a factory reset while using stock recovery. Not doing so cant result in data issues
Sent from my ADR6425LVW using Tapatalk 2
It happened to me after messing with Hboot / Radio combinations. It wiped my internal memory, and killed 4G.
So, I was running NeoMax 2.0 for the most part without any problems. I swapped batteries like normal and then the phone started bootlooping, never leaving the HTC screen. I put the regular battery back in and still had the same problems. I had been planning to switch rooms soon anyways, so I decided to flash Neo's AOKP. That ran fine except for that I had no wifi and data would mostly stay on 3G. I tried to do a nand restore to the last working version of NeoMax and the bootlooping continued. I tried to flash the latest ruu and that also had me bootlooping. Going back to AOKP worked just fine but again, no good data connection. Any ideas aside from getting a new phone?
aftafoya said:
So, I was running NeoMax 2.0 for the most part without any problems. I swapped batteries like normal and then the phone started bootlooping, never leaving the HTC screen. I put the regular battery back in and still had the same problems. I had been planning to switch rooms soon anyways, so I decided to flash Neo's AOKP. That ran fine except for that I had no wifi and data would mostly stay on 3G. I tried to do a nand restore to the last working version of NeoMax and the bootlooping continued. I tried to flash the latest ruu and that also had me bootlooping. Going back to AOKP worked just fine but again, no good data connection. Any ideas aside from getting a new phone?
Click to expand...
Click to collapse
going to need some information from you:
are you s-on or off?
what firmware are you on?
what hboot are you on?
question can be answered by turning off the phone. boot the phone up but hold vol- and power. type all the information in the top left corner
synisterwolf said:
going to need some information from you:
are you s-on or off?
what firmware are you on?
what hboot are you on?
question can be answered by turning off the phone. boot the phone up but hold vol- and power. type all the information in the top left corner
Click to expand...
Click to collapse
Current:
S-OFF
Kernel: Snuzzo's Funky v1.3
Rom: Neo's AOKP v1.5 Linaro
Radio: 2.22.10.0801, 2.22.10.0803
HBOOT: 2.27
I am s-off with hboot ver 2.27. The last RUU I flashed was 4.03.605.2 from micromod's thread here. I believe that I used version 1.2. I followed his instructions first flashing the firmware, then recovery, then the ota global plus. This was the same firmware that I was originally on before I left NeoMax2.0. It kept bootlooping so I flashed Neo's AOKP again. Both his AOKP and AOSP work just fine besides the data problem. I also flashed snuzzo's funky kernel v1.3 and it didn't help. So currently I'm stuck in AOKP/AOSP with only 3g data speeds. Should I try flashing an older RUU?
once my phone charges up, i'm going to flash the stock 3.14 ruu. i'll check back and let you know if it worked.
it's a no go. flashed the 3.14 ruu from shippedrom.com and kept boot looping. sometimes it would get to the 2nd htc splash screen but it wouldn't actually get to the rom. fresh out of idea's, could use your magic synister!
hmm sounds like what happened to me i found a thread where they said that when running the .2 global ruu you need to flash it twice in a row ( i did battery pulled when it was ready to reboot then went back into boot loader) and do a factory reset all from the boot loader before you install recovery and then boot rom they say it helps with data problems worked for me anyway
forey79 said:
hmm sounds like what happened to me i found a thread where they said that when running the .2 global ruu you need to flash it twice in a row ( i did battery pulled when it was ready to reboot then went back into boot loader) and do a factory reset all from the boot loader before you install recovery and then boot rom they say it helps with data problems worked for me anyway
Click to expand...
Click to collapse
Thanks for the reply, I'll try it out tonight. I'm thinking that maybe I will try to flash the global that originally came with my phone. I can't remember the exact one, but I think it was the gb version just before ics came out. I'll post an update with the results.
hmm looks like you have the right radios and hboot or anyway its the same as i have but it still wouldn't hurt to start over the only reason i say something is because i skipped the factory reset in boot loader and i had data problems im not the smartest android on the block here...lol so i try not to tell people stuff that i dont know about that well just what worked for me
And flash Neo's CM9 RAGE rom (aka funky symbol rom).
AOKP has issues where you can lose 4G by going into network settings, CM9 apparently does not. Also, make sure your network mode is set to the one that supports several different data modes, even if you don't get them. Trying to use the one that just says CDMA/LTE prevents 4G signal.
And just FYI, you can run neomax 2 on top of the global firmware, you just can't use it as a true global phone since it is an older rom.
Sent from my Rezound using Tapatalk 2
Hey guys! So I moonshined and got S-OFF on my phone. I first backed up my factory ROM after I wiped all the data so I would have it to go back to in the future if needed, this was done through clockwork mod. So I first tried using the NOS M7 ROM, didn't like that as the home screen seemed too Window's 8 phone like to me. I then tried the CyanogenMod 10.1, I noticed that my phone was only getting 3G data at this point. I was using my wife's new Galaxy S4 that was getting 4G as a comparison to mine. We were traveling through town so it's not a tower based issue, as her phone showed 4G.
I then tried to switch to viperDNA1.3.1 and I had all sort of issues with it. Heck this morning it would not even show me my alarm notification when it was going off to shut the phone up. I had to power it off to silence it. It even stopped showing the notification bar on the top of the screen and I couldn't even do the drag down thing to see notifications and settings.
So today at work I downloaded RageDNA to see if an optimized stock app would work for me, no change..... I even formatted my sdcard to blank it and the did an adb push to transfer the ROM.zip back to my phone.
SO.... between each app I would launch into ClockWorkMod and 1. wipe dalvik cache. 2. format system. 3. wipe data/factory reset. 4. choose the zip from the sdcard (haha like we really have a true sdcard) and wait for the install and then launch into the phone and do the basic setup to get the ROM working.
HELP!!!! (me crying) I am afraid I did something to my phone during the flashing that jacked up the radio causing 4G to be broken. Is there something else you need to know from me to help me out, please let me know!
**********UPDATE**********
I double checked all my phones settings with a coworker who also has a DNA, but still S-ON. Everything is setup the same for settings on the APN's. I even recreated a duplicate APN that used the specified "LTE" network instead of the one that was defaulted on both of ours "unspecified". No change, even rebooted.
I also restored my CWM backup I did before making any changes to my phone via switching ROM's. The only difference is the fact that their network typeshows "LTE" where my shows "eHRPD". I am going to look into seeing how to reflash the radio to see if something got corrupt.
If it comes down to it I am going to reset my phone back to S-ON and reflash everything that I can find that I can do.
*********Resolution*********
After reflashing my radio, I did not get any 4G signal any more, I know Verizon towers were down for 4G near my work so not sure if they moved over to the towers by my home as I only live 10 minutes from work. So only after being at work for about an hour my 4G signal started on it's own without anything done by me today.
So as I was on the path to trying to take it back to stock I followed the guide that Phaded posted for getting back to S-ON http://forum.xda-developers.com/showthread.php?t=2293919. I had a few issues with that, as it turns out my phone was not showing anything about being "LOCKED" after running his first set of commands. So I pressed forward after talking with Phaded on this situation. I had even flashed from my CWM recovery back to the stock recovery (also notice when running the RUU that it flashes the recovery.) I ran the RUU and then got the 158 error then had to flash the HBOOT. After that flash the phone showed "***Tampered*** & ***LOCKED***". I then proceeded to run the RUU and it completed at that point with no issues. Then the last few DOS commands for fastboot and back to Locked and S-On. I updated back from 1.15 up through 2.06. Also doing so that made me realize you have to step from 1.15 to 2.04 and finally 2.06. So far the 4G is still working. I will keep it stock for a few days to ensure no further 4G issues then I will be moonshining again!!
Just a guess, you may have to flash the boot image. If so the directions are in the install directions for Viper
RLGL said:
Just a guess, you may have to flash the boot image. If so the directions are in the install directions for Viper
Click to expand...
Click to collapse
I just tried to restore my CWM files from prior to any ROM changes. So far I have 3G data, but I tend to get 3G more so at my house than 4G, so not sure if anything will change.
I am wondering if the SIM card could have anything to do with this issue as well.... could a ROM have written to the card and caused it to not read the 4G data, or whatever is on there.
I also see that my phone's network seems to be "eHRPD" not sure if this had anything to do with it or not.
I double checked all my phones settings with a coworker who also has a DNA, but still S-ON. Everything is setup the same for settings on the APN's. I even recreated a duplicate APN that used the specified "LTE" network instead of the one that was defaulted on both of ours "unspecified". No change, even rebooted.
I also restored my CWM backup I did before making any changes to my phone via switching ROM's. The only difference is the fact that their network typeshows "LTE" where my shows "eHRPD". I am going to look into seeing how to reflash the radio to see if something got corrupt.
If it comes down to it I am going to reset my phone back to S-ON and reflash everything that I can find that I can do.
U need a new SIM card. 99% sure that's ur problem. They r free from any Verizon store. Give it a shot before u go thru the hassle of going back to s on and stock.
Sent from my HTC6435LVW using xda premium
if you download from the play store this app (its free) https://play.google.com/store/apps/...GwsMSwxLDEwOSwibmV0LmFuZGlyYy5sdGVvbmZvZmYiXQ.. open it and scroll down what does it say under set preferred network type? that screen has more crucial settings then the normal one. if you running viper in viper tweaks its the first option under misc. If you need help ill put up a pick when i get back. someones borrowing mine cause they stepped on their phone lol.
EDIT: also if you are running viper 1.3.1 you should download ind flash after the normal rom the ota update(the one that says 1.3.1 to 1.3.3.
reaverclan said:
if you download from the play store this app (its free) https://play.google.com/store/apps/...GwsMSwxLDEwOSwibmV0LmFuZGlyYy5sdGVvbmZvZmYiXQ.. open it and scroll down what does it say under set preferred network type? that screen has more crucial settings then the normal one. if you running viper in viper tweaks its the first option under misc. If you need help ill put up a pick when i get back. someones borrowing mine cause they stepped on their phone lol.
EDIT: also if you are running viper 1.3.1 you should download ind flash after the normal rom the ota update(the one that says 1.3.1 to 1.3.3.
Click to expand...
Click to collapse
Too funny that you pointed me to that app, I just found another one LTE Settings.
So I tried your app also and they had the exact same data listed. So here's the screen shots I took from my app I pointed to. My phone will connect to 4G only and only if I choose "LTE only" if I move it to something else either by changing it through the OS settings, or changing it through this app, it goes back to getting 3G service. So at least this tells me my phone isn't broken, just some setting is F***ed up somewhere.
I have tried Global and CDMA/LTE settings with it always showing 3G.
yup that's freaking weird lol swing by a VZW store and get a free sim card since yours seems like it might be messed up what happnes if you flash something like crpalmers kernel though? your boot image might just be all screwed up. his latest version is June 24th.
reaverclan said:
yup that's freaking weird lol swing by a VZW store and get a free sim card since yours seems like it might be messed up what happnes if you flash something like crpalmers kernel though? your boot image might just be all screwed up. his latest version is June 24th.
Click to expand...
Click to collapse
Yeah weird! I just used the DNA Toolkit v1.0.5, I flashed the 2.06 radio and after it rebooted and what not, I went outside (as I have bad service inside this house) and now 4G won't even connect. Not sure if it's the towers, as the one by work went out around noon today.
So as it's a kernal and not a ROM how do I do that, just the same install from zip file in CWM? Do I need any certain ROM for it? As right now I have the factory one that I backed up with CWM when I did S-OFF. (it was a blank fresh factory reset)
chayos00 said:
Yeah weird! I just used the DNA Toolkit v1.0.5, I flashed the 2.06 radio and after it rebooted and what not, I went outside (as I have bad service inside this house) and now 4G won't even connect. Not sure if it's the towers, as the one by work went out around noon today.
So as it's a kernal and not a ROM how do I do that, just the same install from zip file in CWM? Do I need any certain ROM for it? As right now I have the factory one that I backed up with CWM when I did S-OFF. (it was a blank fresh factory reset)
Click to expand...
Click to collapse
if your using viper it supports only 2.04 as a base for its radios i believe. like I said try flashing crpalmer's one this one http://d-h.st/hu7
OH also yeah your towers by you could be experiencing maintenance try driving to somewhere else id say at least a mile away.
reaverclan said:
if your using viper it supports only 2.04 as a base for its radios i believe. like I said try flashing crpalmer's one this one http://d-h.st/hu7
OH also yeah your towers by you could be experiencing maintenance try driving to somewhere else id say at least a mile away.
Click to expand...
Click to collapse
I flashed palmer's and no change. I just texted a coworker who lives about .25 miles away to see if he's getting 4G.
Again right now I'm on the factory ROM.
chayos00 said:
I flashed palmer's and no change. I just texted a coworker who lives about .25 miles away to see if he's getting 4G.
Again right now I'm on the factory ROM.
Click to expand...
Click to collapse
does the factory restore work like your cwm one i mean?
Click on Mobile Data in your settings, and make your 'preferred' network LTE/CDMA.
I had the very same error with the stock phone, and once I switched it - I started getting 4G almost everywhere.
Amer28 said:
Click on Mobile Data in your settings, and make your 'preferred' network LTE/CDMA.
Click to expand...
Click to collapse
That doesn't work, I have tried that like 30 times with no change.
reaverclan said:
does the factory restore work like your cwm one i mean?
Click to expand...
Click to collapse
I'll try the factory restore in the ROM and see what it does. (haven't setup the rom due to the lack of 4g)
chayos00 said:
I'll try the factory restore in the ROM and see what it does. (haven't setup the rom due to the lack of 4g)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=17145857&postcount=2 found this and it seems like your towers might be experiencing something if they dropped from pure lte to this. like some equipment has failed and it has dropped to a lower communication lvl hardware wise. EDIT: when i meant factory i meant in cwm going to restore and restoring your whole backup(snapshot) of the factory rom that you made not in the rom itself.
chayos00 said:
That doesn't work, I have tried that like 30 times with no change.
Click to expand...
Click to collapse
I don't think you would notice the change instantly. You will see in a few hours, especially if you go somewhere, you will be getting 4G - or if you restart the phone.
Further, what you can do is flash the radio.
Here's the file you need to flash: https://docs.google.com/file/d/0B9yd_oFytDSzUjRpLTZhSFEwWnc/edit
That is a Verizon radio, and it works also with other providers.
Use fastboot to flash:
Code:
fastboot flash radio radio.img
Original thread of the radio: http://forum.xda-developers.com/showthread.php?t=2236633
PS: This is the original verizon radio.
reaverclan said:
http://forum.xda-developers.com/showpost.php?p=17145857&postcount=2 found this and it seems like your towers might be experiencing something if they dropped from pure lte to this. like some equipment has failed and it has dropped to a lower communication lvl hardware wise. EDIT: when i meant factory i meant in cwm going to restore and restoring your whole backup(snapshot) of the factory rom that you made not in the rom itself.
Click to expand...
Click to collapse
When I was at work, I compared a coworkers DNA and he was getting actual LTE signal. So don't think it's that with the eHRDP thing that I keep seeing. But yeah it looks like a "cheaters way" to get their CDMA hardware to work with LTE. lol
Sorry, I feel like a tard and not really following what you are talking about with the "factory" thing. If you mean in the hboot the factory restore, it takes you to the CWM recovery to do that factory restore. Plus the ROM restore seems to almost go through CWM as well, but does it automatically. I'm going to do a full wipe and set this thing back to factory settings. As when it's broke and not working, best thing to do is start fresh.
chayos00 said:
When I was at work, I compared a coworkers DNA and he was getting actual LTE signal. So don't think it's that with the eHRDP thing that I keep seeing. But yeah it looks like a "cheaters way" to get their CDMA hardware to work with LTE. lol
Sorry, I feel like a tard and not really following what you are talking about with the "factory" thing. If you mean in the hboot the factory restore, it takes you to the CWM recovery to do that factory restore. Plus the ROM restore seems to almost go through CWM as well, but does it automatically. I'm going to do a full wipe and set this thing back to factory settings. As when it's broke and not working, best thing to do is start fresh.
Click to expand...
Click to collapse
okay if you do it from hboot it wont do anything cause now cwm will stop that from running but that is the same as running factory reset in cwm, thats not what im talking about though when you first moonshined then booted cwm after getting it, did you run a backup of your factory(stock) ROM? if so it would be in sdcard/clockworkmod/backups it also would have been about 1.5-2GB's. you could also try the radio.img amer is taking about as well, that you need to flash with adb though in fastboot as he stated.
reaverclan said:
okay if you do it from hboot it wont do anything cause now cwm will stop that from running but that is the same as running factory reset in cwm, thats not what im talking about though when you first moonshined then booted cwm after getting it, did you run a backup of your factory(stock) ROM? if so it would be in sdcard/clockworkmod/backups it also would have been about 1.5-2GB's. you could also try the radio.img amer is taking about as well, that you need to flash with adb though in fastboot as he stated.
Click to expand...
Click to collapse
After I noticed my 4G issue, I restore my CWM backup. Yes the CWM backup is what I restored and I am running from right now. It's size is 1.39GB in size.
I will do the radio flash right now.
So this might be a bit convoluted, but here it goes. I was on the OTA path until last week when I decided to flash some kit kat roms. As my title states, I am rooted with s-off, I've flashed several kitkat based sense roms, BSC, Viper, santod, etc...after doing so I lost 4g and 5ghz wifi. When i flash a new rom I will have 4g for several moments but it always drops, additionally I can not see my 5ghz wifi network with wifi set to auto or 5ghz only. I did already have the new radios installed from the recent OTA's, but I thought I would try to see if flashing the firmware santod posted would help. I flashed that through fastboot and it said it installed, although I did not get the same messages that santod mentioned in his post. So I reflashed the stock rooted rom that santod uploaded (santod is a lifesaver by the way), that rom restored 5ghz wifi, but the same issue with 4g. Now, I am having problems with adb and fastboot recognizing my device. I am in it deep here and would greatly appreciate any advice.
Thanks in advance!
Update
micahl88 said:
So this might be a bit convoluted, but here it goes. I was on the OTA path until last week when I decided to flash some kit kat roms. As my title states, I am rooted with s-off, I've flashed several kitkat based sense roms, BSC, Viper, santod, etc...after doing so I lost 4g and 5ghz wifi. When i flash a new rom I will have 4g for several moments but it always drops, additionally I can not see my 5ghz wifi network with wifi set to auto or 5ghz only. I did already have the new radios installed from the recent OTA's, but I thought I would try to see if flashing the firmware santod posted would help. I flashed that through fastboot and it said it installed, although I did not get the same messages that santod mentioned in his post. So I reflashed the stock rooted rom that santod uploaded (santod is a lifesaver by the way), that rom restored 5ghz wifi, but the same issue with 4g. Now, I am having problems with adb and fastboot recognizing my device. I am in it deep here and would greatly appreciate any advice.
Thanks in advance!
Click to expand...
Click to collapse
So, I finally got adb/fastboot to work after about three hours of work including a variety of manually installing adb interface drivers/htc drivers and other misc work. After completing that, I flashed the firmware that santod has uploaded to hopefully resolve 4g issues, but still no 4g :crying: .I have my network settings set to cdma/lte of course...I would love any help.
Thanks
Had the same problem. After flashing the stock rom, you have to flash the stock recovery then proceed to do a factory reset. Make sure to back up all your data first cuz you'll lose it all. That seemed to do the trick for me. Also had problems with texting on kitkat, would get message failed after sending 1 text. Lemme know if that ffixes it.
yesitsneuner said:
Had the same problem. After flashing the stock rom, you have to flash the stock recovery then proceed to do a factory reset. Make sure to back up all your data first cuz you'll lose it all. That seemed to do the trick for me. Also had problems with texting on kitkat, would get message failed after sending 1 text. Lemme know if that ffixes it.
Click to expand...
Click to collapse
I have sent a stock recovery from [Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU] by .torrented on xda, but when I go to boot into the recovery it just reboots to the normal start up...
micahl88 said:
I have sent a stock recovery from [Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU] by .torrented on xda, but when I go to boot into the recovery it just reboots to the normal start up...
Click to expand...
Click to collapse
Go to setting >power (battery) clear fastboot mark.
restart phone asap turn off hold volumen rocker down to enter to stock recovery
do a factory reset*
I'm sure you've seen this by now, but 5Ghz wifi isn't quite working on any kitkat roms. Santo's making progress but hopefully we'll have a stock kitkat kernel, modules, and source soon.
zandarillis said:
I'm sure you've seen this by now, but 5Ghz wifi isn't quite working on any kitkat roms. Santo's making progress but hopefully we'll have a stock kitkat kernel, modules, and source soon.
Click to expand...
Click to collapse
Oh, I actually did not. Thanks for clarifying that for me, I will just keep checking back for rom patches.
Thanks.
finanandroid said:
Go to setting >power (battery) clear fastboot mark.
restart phone asap turn off hold volumen rocker down to enter to stock recovery
do a factory reset*
Click to expand...
Click to collapse
Ok, I followed those instructions, unchecked fastboot, reboot into hboot then selected recovery, the phone goes to the white HTC loading screen that shows "Entering Recovery" on the top for several seconds then just begins a normal boot. I then used adb commands to enter recovery but it did the same thing. I also tried to factory reset from the typical android feature in settings...
Side note, can you explain what happened? I was already on the latest firmware and radio before flashing the rom.
Many continued thanks for the help.
micahl88 said:
Ok, I followed those instructions, unchecked fastboot, reboot into hboot then selected recovery, the phone goes to the white HTC loading screen that shows "Entering Recovery" on the top for several seconds then just begins a normal boot. I then used adb commands to enter recovery but it did the same thing. I also tried to factory reset from the typical android feature in settings...
Side note, can you explain what happened? I was already on the latest firmware and radio before flashing the rom.
Many continued thanks for the help.
Click to expand...
Click to collapse
Ok, I reflashed a recovery from a different source and finally got stock recovery to run then factory reset and then MAGIC 4G reappeared. Thanks. Now, what caused this to happen? Should I not reflash another rom? 4g is more important to me than other roms...
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse