Related
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Probably a n00b mistake, but I just installed ExROM 2.0 after I had bionix 1.3.1 and my gps is seeing 12 satellites, but won't lock onto any of them. Checking with GPS Test app. It looks like other people report gps works great. Any thoughts on what I messed up or what I could do to fix this? Do I need to reinstall or something? I did choose wipe everything in clockwork before I installed this. Thanks.
Rellik01 said:
Probably a n00b mistake, but I just installed ExROM 2.0 after I had bionix 1.3.1 and my gps is seeing 12 satellites, but won't lock onto any of them. Checking with GPS Test app. It looks like other people report gps works great. Any thoughts on what I messed up or what I could do to fix this? Do I need to reinstall or something? I did choose wipe everything in clockwork before I installed this. Thanks.
Click to expand...
Click to collapse
If I was in your situation, I would first re-flash the ROM, then if that doesn't work, flash the latest SubZero kernel, and then if that doesnt work, go back to stock, flash bionix and test it to see if GPS is software destroyed (like mine was b4, tried every possible solution, nothing, so i waited for a few weeks, didnt touch GPS at all, and then one day, YAY it works again. Sounds like complete BS, but im not kidding). If GPS works again on Bionix, try going to another ICS rom (such as CM9 (it tells you steps and stuff too) or ICSzenwich from rootzwiki.) and then follow the steps from EXrom page. ^.^ Good Luck!
Thanks for the input. I just installed it again exactly as I did the first time and I'm getting gps data now. Weird. Thanks again.
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
I rooted my S3 about a year ago, when I got it first using CF-Root. Had zero problems.
Gave it to the girlfriend a month ago. Did a factory reset etc, but left it rooted. I did however take out my sd card(which probably has something to do with the problem?)
Anyways, 3 days ago, the wifi suddenly stopped working on it all of a sudden. The wifi tab is kind of greyed out and wont turn on or scan for any networks. (see photos below)
I tried turning the phone on/off, taking out the battery etc. Nothing worked.
I then flashed the same ROM back onto it and the problem disappeared for a day, but then all of a sudden reappeared! I thought I had fixed it, but no!
I put back in a sd card,I then downloaded and flashed another Rom(CM 10.2) using Rom manager from the sd card, and the problem disappeared again.
But after 12 hours both the wifi and the 3G stopped functioning
I've no idea what is the problem. Can anyone help me out with this? Could it be the kernel that's causing the problem? I'm not very tech savvy guys. I know how to root the phone, but I've had to deal with any issues.
I'd really appreciate any help, as we need access to the net from our phones. I've included photos below so that you can see the rom and kernal and other details that may help ye decipher the problem.
http://imageshack.com/a/img856/1443/c3ow.jpg
http://imageshack.com/a/img46/1797/euiv.jpg
http://imageshack.com/a/img196/4737/drsa.jpg
Did you check logcat for any clue?
Stop running nighties. Problem solved.
hberntsen said:
Did you check logcat for any clue?
Click to expand...
Click to collapse
No idea what that is?
xclub_101 said:
Stop running nighties. Problem solved.
Click to expand...
Click to collapse
Problem was present before I flashed the CM nighties, so that doesn't mean it's the issue!
chicoelnino said:
I rooted my S3 about a year ago, when I got it first using CF-Root. Had zero problems.
Gave it to the girlfriend a month ago. Did a factory reset etc, but left it rooted. I did however take out my sd card(which probably has something to do with the problem?)
Anyways, 3 days ago, the wifi suddenly stopped working on it all of a sudden. The wifi tab is kind of greyed out and wont turn on or scan for any networks. (see photos below)
I tried turning the phone on/off, taking out the battery etc. Nothing worked.
I then flashed the same ROM back onto it and the problem disappeared for a day, but then all of a sudden reappeared! I thought I had fixed it, but no!
I put back in a sd card,I then downloaded and flashed another Rom(CM 10.2) using Rom manager from the sd card, and the problem disappeared again.
But after 12 hours both the wifi and the 3G stopped functioning
I've no idea what is the problem. Can anyone help me out with this? Could it be the kernel that's causing the problem? I'm not very tech savvy guys. I know how to root the phone, but I've had to deal with any issues.
I'd really appreciate any help, as we need access to the net from our phones. I've included photos below so that you can see the rom and kernal and other details that may help ye decipher the problem.
Click to expand...
Click to collapse
Have you tried flashing it back to a pure stock ROM (or maybe a stock derived ROM like WanamLite or Imperium) ?
hundred_miles_high said:
Have you tried flashing it back to a pure stock ROM (or maybe a stock derived ROM like WanamLite or Imperium) ?
Click to expand...
Click to collapse
No, I haven't. Simply because I'm not sure which ROM is suitable for me.
Could you point me towards a link to that ROM(a version that works on my phone, or does it matter?)
I'm lost with all the different ROM's etc at this stage, and all I want is for the phone to be back working - whether that's with or without root access. It's for my girlfriend, so she hasn't a clue about root etc.
Thanks for any help you can provide.
chicoelnino said:
No idea what that is?
Click to expand...
Click to collapse
Via logcat you can see messages from android's internal logging system. A lot of times the internal errors you don't see can be obtained via logcat. Look at http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise/ and https://www.xda-developers.com/tag/logcat/ for more info.
Can anyone just suggest to me a way to get the phone back to it's original state either rooted or unrooted...I don't care.
I just need to get the phone fixed so that my g.friend has a phone that has wifi working properly.
Do I need a different kernel or something? I'm lost, so any help as to what direction to that is appreciated.
Its all posted in the fff Faqs and Guides .
Please read how to return to stock for warranty post .
This is not a thread about me asking for help, more so opening the door to help others and provide general guidance with GPS issues on Lollipop.
This past weekend, I flashed back to ZV4 from ZV6. I rooted through Stump Root, installed TWRP, took a backup, and flashed two different Lollipop ROMs. I tried CM first, but am now working with Illusion as the SMS button was broke. GPS would not work no matter the fix on any Google Play Apps, be it a gps.conf changer or an AGPS manager. So there is the back story of what exactly I did, and now I will outline what I did to get GPS working.
I took current backup of Illusion and restored from backup to my stock ZV4 ROM. Lo and behold, getting into the ROM -- I found that GPS was disabled. There was also a secondary "enhanced" GPS option in the ROM I enabled from the same screen in the Location settings menu. (if anyone is still on a stock ROM, can you check for the name of that option?). I also enabled that option. I used "GPS Test" from the Google Play Store and was able to get plenty of satellite fixes -- "3D Fix."
I then rebooted to recovery, restored to the Lollipop ROM -- and GPS worked just fine. This is fairly odd, and we used this method to get GPS to work back in the OG Samsung Epic 4G days. I am wondering if its something that the Stock Rom and firmware can do -- aka turn on GPS, that Lollipop can't actually initiate and toggle. I'm sure Lollipop can "turn it off", but I am not terribly sure of this at the moment.
Anyways, I hope this helps someone out.
OMG thank you! I almost gave up on L for now because no rom I tried would give me a GPS fix. The locating icon only even appeared in the status bar for a few seconds and went away. I restored my stock nand, enabled high accuracy (I usually leave it in battery save unless I'm actually using it), flashed back to L, and bam, instant lock.
vaelek said:
OMG thank you! I almost gave up on L for now because no rom I tried would give me a GPS fix. The locating icon only even appeared in the status bar for a few seconds and went away. I restored my stock nand, enabled high accuracy (I usually leave it in battery save unless I'm actually using it), flashed back to L, and bam, instant lock.
Click to expand...
Click to collapse
No problem. Glad I could help.
I can't, for the life of me, get this to work. I've tried instructions to the t, still no GPS on Illusion.
sent from my LG G3
joeyhdownsouth said:
I can't, for the life of me, get this to work. I've tried instructions to the t, still no GPS on Illusion.
sent from my LG G3
Click to expand...
Click to collapse
This has been a long standing fix, but again confirmed working for me. Brand new VS985 (Verizon LGG3 Warranty Replacement). Had booted the phone to register the new sim card and immediately rooted, Bumped, wipe and flashed Illusion 5.0. Tried maps the next day, GPS apps, etc, NOTHING would work..
Backed up that install in TWRP, loaded up Jasmine 4.0, booted in, turned on GPS, downloaded a GPS app, got a lock, immediately loaded TWRP, wiped 3x, restored my Illusion backup, booted it up, loaded my GPS app, and within 5 seconds it found GPS and locked in.
I can't claim to know why the stock rom would make any diff on turning on GPS, locking in, etc when a rom that does similar stuff and what googles phones are primarily based off of don't work.
This worked though and I'm happy!
Hey I have the same issue and tried this workaround twice, but still can't get GPS on lollipop...
NiK- said:
Hey I have the same issue and tried this workaround twice, but still can't get GPS on lollipop...
Click to expand...
Click to collapse
I also still have the issue, and can no longer get a GPS lock on 4.4.2 ROMs after having flashed lollipop
I spent hours looking for a solution on this that would not imply flashing another ROM.
What fixed it for me was updating the gps.conf file with a proper NTP server more suitable for your zone.
The easiest way to do this is using FasterGPS app. You need root, of course. But works very well.
Didn't work for me.
pmaximal said:
I spent hours looking for a solution on this that would not imply flashing another ROM.
What fixed it for me was updating the gps.conf file with a proper NTP server more suitable for your zone.
The easiest way to do this is using FasterGPS app. You need root, of course. But works very well.
Click to expand...
Click to collapse
I tried this method but it did not work for me. I'm hoping to figure this out without re-installing stock firmware.
Yes gps is not working on lollipop roms. I flashed 2 different lollipop roms, and neither gps is working. I restore my previous kitkat version copied the gps.conf file to my sd card, reflashed the lollipop rom and then I replaced the gps.conf file with the one from kitkat. It works. I updated the rom and the gps won't work again. I replaced it again with the gps.conf from kitkat, gps works fine again.
voltz926 said:
Yes gps is not working on lollipop roms. I flashed 2 different lollipop roms, and neither gps is working. I restore my previous kitkat version copied the gps.conf file to my sd card, reflashed the lollipop rom and then I replaced the gps.conf file with the one from kitkat. It works. I updated the rom and the gps won't work again. I replaced it again with the gps.conf from kitkat, gps works fine again.
Click to expand...
Click to collapse
Do you happen to still have that gps.conf file? I'm having the same problem.
anaya1213 said:
Do you happen to still have that gps.conf file? I'm having the same problem.
Click to expand...
Click to collapse
Anaya1213
Can you give me your email address so I can send it to you.
Alias8818 said:
No problem. Glad I could help.
Click to expand...
Click to collapse
Sir,
I am from Pakistan. i have sprint lg g3 ls990 cell phone. I am using 3g cellular network. But when i enable data it always shows Edge not 3g. I switched network mode to cdma/ wcdma from settings menu but nothing. I flash several roms but no result.
Now i am on cloudy g3 2.5. But there is no change in my data service. I am still on edge data mode.
Any one help me what can i do to switch to cdma/ 3g?????
Thanks and waiting some support from u people.
Regards
Abbas
Flash your stock firmware using .tot not kdz file,but you need another lg flash tool that uses .tot and dll files,just search on google,or use files from this site lgg3root i just did that after trying several stock/custom firmware/gpsconfig files
pmaximal said:
I spent hours looking for a solution on this that would not imply flashing another ROM.
What fixed it for me was updating the gps.conf file with a proper NTP server more suitable for your zone.
The easiest way to do this is using FasterGPS app. You need root, of course. But works very well.
Click to expand...
Click to collapse
I realize it's been a while, but I wanted to say thanks for posting this! Using FasterGPS to update my ntp region did the trick perfectly!