Related
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
okay so last night i was flashing Roms trying them out to see witch one would be my daily driver
but the problems happened when i flashed MIUI. Then I flashed newts one xxx and i had the roaming triangle on my signal bar
now when ever i try to use my phone it says no service and the 4G is pretty slow
I already went to settings > mobile network > and the setting in there and still no luck
im s on
HTC unlocked
any help thanks
is ur radio up2date ?
did u flash the ruu of global rom ?
No i havent how would i go about doing that
what is your hboot?
Option1:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Option2:
Go into mobile network settings and change to Global Mode. If already on global. Change to CDMA/LTE auto
EDIT
I posted in the wrong thread
Thank you all for your help
Flyhalf205 I flashed the recovery and factory reset and that worked. Thanks a lot
Flyhalf205 said:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Click to expand...
Click to collapse
It's many months since Flyhalf's post, but I wanted to report that after getting a replacement unit, I also ran S-OFF and htc dev unlock and pushed the radios forward to the latest and found that I could no longer make or receive calls, send or receive texts, although data/4G/wifi and BT were all functioning nominally. Tech support couldn't solve it; a new SIM card couldn't change things, and when I finally rolled all the way back to the last GB RUU, and FINALLY did a factory reset WITHIN HBOOT that cleared the problem. I then let the handset download the OTA's one by one to bring it up to speed.
I'm putting this here because I didn't find anything else for "no phone service" or "lost cell service" and was about to open a new thread in troubleshooting when I found this thread, followed Flyhalf's advice and I am now fully operational again. Hppefully someone else doing a similar search will see this post.
hgoldner said:
It's many months since Flyhalf's post, but I wanted to report that after getting a replacement unit, I also ran S-OFF and htc dev unlock and pushed the radios forward to the latest and found that I could no longer make or receive calls, send or receive texts, although data/4G/wifi and BT were all functioning nominally. Tech support couldn't solve it; a new SIM card couldn't change things, and when I finally rolled all the way back to the last GB RUU, and FINALLY did a factory reset WITHIN HBOOT that cleared the problem. I then let the handset download the OTA's one by one to bring it up to speed.
I'm putting this here because I didn't find anything else for "no phone service" or "lost cell service" and was about to open a new thread in troubleshooting when I found this thread, followed Flyhalf's advice and I am now fully operational again. Hppefully someone else doing a similar search will see this post.
Click to expand...
Click to collapse
I wanted to 2nd this post with a small addition. After S-offing my rezound and flashing the latest CarbonRom, I ended up losing 4G. I mistakenly though it was related to gaining s-off and performing a full factory restore and update. I was left with a phone that did everything but receive 4G signal. I had reliable 3G data and could make/receive calls/SMS/MMS. I only lost 4G data. After finding this post, thank you hgoldner for talking it up, I flashed the ICS RUU and then performed a factory reset. I probably could have just flashed the stock recovery but the Goo.im servers appear to be acting up and I couldn't download it from Flyhalf's link above. For those of you with signal issues following a custom ROM flash, I'd definitely suggest giving this a try.
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.
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