The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
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
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
I know there's a few posts on this, but looking for advice specific to my symptoms. The problem started off with Android media process using up a lot of cpu each time the phone was powered on. It gradually got worse and started rebooting when this happened. Started off as once or twice a day. Then got worse and worse. I had been on a bell atrix ROM (2.3.6) for about a year.
Tried flashing a number of roms, and making sure to clear caches and factory reset each time. Tried numerous versions of the CWMRecovery, no good. I notice that it noly seems to restart if it tries to communicate wirelessly (wifi or 3g seemingly). If I just leave it in cwmrecovery, it stays on fine. If I leave it at the first motoblur setup screen, without entering wifi settings, it stays on fine.
So I guessed it may be related to the radio. Installed a UK radio, bell original one and a euro one to no avail
Is there anything else I can do before I give up, or is it hardware?
cruhoortwunk said:
I know there's a few posts on this, but looking for advice specific to my symptoms. The problem started off with Android media process using up a lot of cpu each time the phone was powered on. It gradually got worse and started rebooting when this happened. Started off as once or twice a day. Then got worse and worse. I had been on a bell atrix ROM (2.3.6) for about a year.
Tried flashing a number of roms, and making sure to clear caches and factory reset each time. Tried numerous versions of the CWMRecovery, no good. I notice that it noly seems to restart if it tries to communicate wirelessly (wifi or 3g seemingly). If I just leave it in cwmrecovery, it stays on fine. If I leave it at the first motoblur setup screen, without entering wifi settings, it stays on fine.
So I guessed it may be related to the radio. Installed a UK radio, bell original one and a euro one to no avail
Is there anything else I can do before I give up, or is it hardware?
Click to expand...
Click to collapse
just had a look around and came across this http://forum.xda-developers.com/showthread.php?t=1884381 . Forgetting the Jb reference it might be an idea to follow the steps and see if that helps.
If it were me, I would do a complete system wipe first (CWM>mounts and storage>format system,data,preinstall,osh) and then reinstall a rom (I would recomend CM7.2 to start). I also might be inclined to take the external sd card out as well before restarting phone and see if that helps (going down the corrupt media file route)
Good Luck!
barry_ said:
just had a look around and came across this http://forum.xda-developers.com/showthread.php?t=1884381 . Forgetting the Jb reference it might be an idea to follow the steps and see if that helps.
If it were me, I would do a complete system wipe first (CWM>mounts and storage>format system,data,preinstall,osh) and then reinstall a rom (I would recomend CM7.2 to start). I also might be inclined to take the external sd card out as well before restarting phone and see if that helps (going down the corrupt media file route)
Good Luck!
Click to expand...
Click to collapse
Thanks for this, I never spotted the mounts and storage section for formatting before. Looks to be good to get a clean wipe
Will try now
I managed to get the MROM rom on to it, and it has stayed on for about 30mins now with wifi on.
However, it doesn't boot normally, it says 'Modem did not power up, starting RSD protocol support'. I have to choose Boot Android (no BP) to get it to boot ok. What would make it fail like this?
Is there any way to make the phone always boot android by default?
Another thing to add: I can't add any APN. If I add one and save, it doesn't save.
cruhoortwunk said:
I managed to get the MROM rom on to it, and it has stayed on for about 30mins now with wifi on.
However, it doesn't boot normally, it says 'Modem did not power up, starting RSD protocol support'. I have to choose Boot Android (no BP) to get it to boot ok. What would make it fail like this?
Is there any way to make the phone always boot android by default?
Another thing to add: I can't add any APN. If I add one and save, it doesn't save.
Click to expand...
Click to collapse
I can see that i am missing a boot.img to make it boot properly. Where can I download it?
A boot image always comes with any ROM, and MROM is no exception. If you sucessfully flashed the ROM, you've flashed the boot image too, I'm not sure why you think it's missing. But if you really want to reflash it, you can always extract it from the ROM's zip file.
ravilov said:
A boot image always comes with any ROM, and MROM is no exception. If you sucessfully flashed the ROM, you've flashed the boot image too, I'm not sure why you think it's missing. But if you really want to reflash it, you can always extract it from the ROM's zip file.
Click to expand...
Click to collapse
Alright, looks like I misunderstood the function of the boot.img. Any idea as to why it would not load the OS without me prompting it to boot android with no bp?
What is the best process to follow before flashing a rom?
I was doing factory reset,clearcache and clear dalvik from CWM. And I have started doing CWM>mounts and storage>format system,data,preinstall,osh now too.
Is that sufficient to get a good clean slate to start fresh?
And what's the best way to flash the radio? I have tried moto-fastboot radio radio.img, but that seems to stop the OS from loading. I assume the radio be installed after the ROM?
Tried an older gingerbread Bell rom, and same problem. I can only get it to boot by choosing boot android(no bp).
I also can't add an APN to it. I create it, save it and it doesn't save it to the list.
Found a fix here for the APN problem on ICS, but wondering if there's an equivalent on Gingerbread?
'Settings --> More... -> Uncheck 'Enable alt OEM telephony code' and 'Enable alternate getIMSI code'. Then reboot, and now you can add your own apn. '
No idea really, sorry. Kinda seems to me for some reason it's your bootloader that's having issues, not the ROM.
Still cant get it working, can't add an APN.
Replaced the SIM, same.
Noticed that the IMEI and baseband are listed as unknown, and think it's related. So I tried flashing a few radios.
Bell radio stays on about a min, then reboots phone
UK radio reboots once OS has loaded
French radio reboots once OS has loaded
I am based in Ireland, using a phone that was originally Bell Canada. Which radio should I try flashing?
Have you tried AT&T 36p or 37p radio?
No dice. What is the standard process with the radio zip? I have been extracting to a folder, then using moto-fastboot to clear the cache, then install the radio.
Am I missing a step or 2?
Why were you extracting it? Most radios come in a flashable ZIP, which means you flash it through recovery. No extracting.
I always got an error trying to install the zip in CWM. So installed img from fastboot instead. I'll try the newer zips from CWM.
cruhoortwunk said:
I always got an error trying to install the zip in CWM. So installed img from fastboot instead. I'll try the newer zips from CWM.
Click to expand...
Click to collapse
I get error 'assert failed' ...status 7.installation aborted..'trying to install both ATT radio zips via CWM, and status 0 trying Bell radio zip
Update on this:
I got a new phone a few days ago, and had trouble adding an APN (same problem it wouldn't save). Problem was it was not reading the sim correctly. I had some sellotape on part of the card. Removed this, and I was able to add the APN no problem.
I have cleaned the contacts on the sim card reader, no luck.
I am convinced that this is the faulty part though. When I go to add an APN, it should automatically populate the MCC and MNC from the sim, but it doesn't.
Sorry to bump an old thread but...
I have left this Atrix aside for a few months,and wanted to try it once more before giving up entirely.
It reboots when I use 3g or wifi. If I leave it offline or in cwm mode, it stays on ok.
Any ideas? Is it definitely hardware? (Have tried about 4 different images)
cruhoortwunk said:
Sorry to bump an old thread but...
I have left this Atrix aside for a few months,and wanted to try it once more before giving up entirely.
It reboots when I use 3g or wifi. If I leave it offline or in cwm mode, it stays on ok.
Any ideas? Is it definitely hardware? (Have tried about 4 different images)
Click to expand...
Click to collapse
Does it reboot if you put it in Airplane mode, then connect to WIFI only?
My Atrix randomly reboots if I have the cellular radio on, but if I put it in Airplane and only use WIFI, its very stable. I tried dozens of radios and ROMs, nothing seems to help, so I've chalked it up to some flaky hardware.
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.
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