Hey there guys, I apologize if this has been covered, as I feel its related to an "efs" folder type of issue. I'm just not quite sure where the hell to even begin searching.
I've been on 4.3 since the leak and have been using Cataclysm 4.3 JWR ROM for a while now, problem free. All was running great until yesterday I was downloading some media and transferring it to my laptop (~10gb of traffic before I noticed the problem), and my WiFi shut off and restarted itself. My mobile data kicked in at that point for all of 10 seconds until the WiFi reconnected and within 30 minutes my signal bars suddenly dropped to zero and calls couldn't be made. "Mobile network not available." message appears. So I figured i'd pull the SIM, replace and reboot. When that didn't work I tried rebooting without the SIM, to see if it would detect no SIM card and prompt me to put one in and reboot to be able to connect to mobile network. Well nothing was detected. A full wipe, reflash of identical ROM, reflash of updated ROM, reflash of original JWR deodexed & rooted backup, all with the same outcome. I have tried everything short of downloading the stock image and flashing that but I haven't got around to it since I haven't had time to backup my internal SD before losing all data. I should note that I'm on baseband .84/4.3 bootloader and have been since Google pushed JWR & JSS. I haven't tried flashing a new modem, I figured that wouldn't been an issue. I suppose I'll try flashing .48 and update.
Edit: I forgot to mention that yes, WiFi is in fact working. Mobile signal seems to be the only thing affected.
Edit: Reflashing baseband .84 and .48 didn't work.
I really appreciate any ideas guys, I'd like to sort this out rather than having to flash stock and RMA it or something :/
All settled, it was an issue with the frequency band my provided operates on. Mod can lock/delete thread thanks.
Sent from my Nexus 4 using xda app-developers app
[Q] Stuck between two "handicapped" results of flashing PA through diff. recoveri
http://forum.xda-developers.com/show....php?t=2020336 This is where i got all the zip which i flashed (radio, bootloader, PA ROM, and GApps)
So there are two problems I have noticed after flashing my nexus with paranoid android.
The biggest one is that my phone cannot get any cellular service. The phone just shows No Service, and when i tried to set mobile network manually it told me to insert sim and restart while already having a sim card in the phone. I tried removing and inserting it again to no avail.
The second one is that I can't use my camera, it opens the app for like half a second then it shows "Can't connect to camera" and quit abruptly.
Everything works just fine when I flashed the backup stock ROM, including the mobile data and camera
UPDATE :
I tried using TWRP instead as the recovery that I use to flash the exact same 4 zip files (radio, bootloader, PA ROM, and GApps, all from the official PA account on XDA developer). It indeed solved the No Service problem, it now has fully functioning HSDPA connectivity, but then two problems emerged.
The first being the unavailability of keyboards. The phone would just show the microphone icon for voice typing and no keyboard is found in settings.
The second problem being there is no Camera app, so I can't decide whether the "Can't connect to camera" issue is solved.
So I am stuck in between two "handicapped" results of flashing PA through different recoveries. (keep in mind that I used the same exact 4 zip files to flash)
1. I can flash it through Clockwork Recovery but then the phone wouldn't recognize the SIM card although everything else would work perfectly.
2.I can flash it through TWRP and the phone would have perfect mobile connectivity, but then the phone would have no keyboard showing up and no Camera app. I had assumed this would be an easier problem to solve by googling, but it seems like this problem is rather unique/specific.
Is there a way i can install the keyboard and camera by itself?
Remember that there is no keyboard so I really can't type in anything including signing in on the Play Store. I attempted installing Google Keyboard through the desktop play store, but since the one on my phone isn't connected to my Google account, the download won't start on the phone.
wolverine060 said:
http://forum.xda-developers.com/show....php?t=2020336 This is where i got all the zip which i flashed (radio, bootloader, PA ROM, and GApps)
So there are two problems I have noticed after flashing my nexus with paranoid android.
The biggest one is that my phone cannot get any cellular service. The phone just shows No Service, and when i tried to set mobile network manually it told me to insert sim and restart while already having a sim card in the phone. I tried removing and inserting it again to no avail.
The second one is that I can't use my camera, it opens the app for like half a second then it shows "Can't connect to camera" and quit abruptly.
Everything works just fine when I flashed the backup stock ROM, including the mobile data and camera
UPDATE :
I tried using TWRP instead as the recovery that I use to flash the exact same 4 zip files (radio, bootloader, PA ROM, and GApps, all from the official PA account on XDA developer). It indeed solved the No Service problem, it now has fully functioning HSDPA connectivity, but then two problems emerged.
The first being the unavailability of keyboards. The phone would just show the microphone icon for voice typing and no keyboard is found in settings.
The second problem being there is no Camera app, so I can't decide whether the "Can't connect to camera" issue is solved.
So I am stuck in between two "handicapped" results of flashing PA through different recoveries. (keep in mind that I used the same exact 4 zip files to flash)
1. I can flash it through Clockwork Recovery but then the phone wouldn't recognize the SIM card although everything else would work perfectly.
2.I can flash it through TWRP and the phone would have perfect mobile connectivity, but then the phone would have no keyboard showing up and no Camera app. I had assumed this would be an easier problem to solve by googling, but it seems like this problem is rather unique/specific.
Is there a way i can install the keyboard and camera by itself?
Remember that there is no keyboard so I really can't type in anything including signing in on the Play Store. I attempted installing Google Keyboard through the desktop play store, but since the one on my phone isn't connected to my Google account, the download won't start on the phone.
Click to expand...
Click to collapse
Have you tried re downloading the zips again? maybe one is corrupt? make sure you do a full wipe before flashing ( also do advanced wipe and wipe all except sdcard and usb)
You could also try Wugs root tool kit, http://www.wugfresh.com/ im pretty sure it has a feature to allow you to push apps to your system,
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Wexberg said:
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Click to expand...
Click to collapse
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
DeadlySin9 said:
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
Click to expand...
Click to collapse
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Wexberg said:
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Click to expand...
Click to collapse
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
DeadlySin9 said:
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
Click to expand...
Click to collapse
Wexberg said:
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
Click to expand...
Click to collapse
I don't know why that would work. At this point I'm not sure what else you could do. I know I used to have WiFi issues after some flashes with my Inspire but i never really had a fix even then.
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Been there, done that.
It's not a hardware problem. It is, I believe, problems with the restrictive 4.3 update not playing nicely with some system settings. In short your system drivers or configuration settings are getting messed up to to bugs in how Knox and the bootloader are interacting with the modem.
I had your exact symptoms after installing certain custom ROMs, also noted that the problem could be temporarily "fixed" if the boot process was interrupted or by specific sequences of modem changes. The situation is not helped by Bell being more restrictive than other Canadian carriers e.g. Rogers, something that also caused me problems when I was enabling AWS on a Bell firmware.
The effective solution was to install a custom recovery to facilitate a complete wipe of files, then flash a Rogers stock image. Cured. And continuing to work properly if subsequently returned to a Bell stock image. Although, frankly you'd have a more stable and flexible platform if you you kept the Rogers image in the end. If the build properties edit doesn't solve your issue, then here is a path for you to pursue.
.
1/2 Lit Toggles - build.prop editing issue
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
jrwebdev17 said:
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
Click to expand...
Click to collapse
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
DeadlySin9 said:
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
Click to expand...
Click to collapse
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Editing build.prop is a plausible workaround if the OP has root access. If he doesn't wish to root his phone, then he can clean up his system configuration by reinstalling as I described earlier in the thread without requiring root. Two approaches to the same result.
And yes, you can add the entry if it doesn't already exist in your configuration.
.
jrwebdev17 said:
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Click to expand...
Click to collapse
UPDATE: I didn't have any luck using the build.prop fix, nor with the wpa_supplicant.conf fix that some of you may have seen mentioned. I ended up Recovering to stock MF3, (I was already on MF3). This gave up my root access, and I didn't take any additional steps to hide busy_box or anything like that, after my MF3 recovery it looked like I was safely unrooted and I contacted AT&T support via web-chat, and they asked some questions and sent me to a nearby AT&T device center. I took it there, they didn't ask a single question about how it happened, whether I had rooted it, etc(although I was paranoid that there would be traces left behind and they would turn me away). Long story short, they replaced the phone no questions asked!
In my opinion it would seem that while this problem could in some cases be caused by rooting and tinkering, it's enough of a known issue to AT&T that they would replace it under warranty. Hopefully Bell or other carriers would do the same. My advice is to try your carrier, particularly if you are with AT&T.
Just to help people who are searching for a solution. I had flashed a T-Mobile rom and my wifi stopped being togglable on my AT&T S4. That is, I couldn't turn on wifi. The button would get stuck on. After trying to flash what I thought was the right MK2 modem and still having the same issue, I thought I was out of luck. However, I found this one here: http://forum.xda-developers.com/devdb/project/dl/?id=3275 and hit paydirt. Flashing it using Safestrap and then wiping cache and delvik worked. The file is called jflteatt-MK2-modules.zip.
Only for WIFI, for me what worked was I had to open a litte bit the one side of the phone and close it again (removing a little the plastic, like if you were going to open the device) Wifi started working again, no need to flash any roms, it seemed to be something related with pressure, humidity or something inside the phone.
Regarding bluetooh I had no luck still not working, only keeps saying activating and never gets activated.
does anyone find a solution for this yet?
I have had the same issue for months. Started after warranty was up. I have AT&T on nc1. I tried everything mentioned here but nothing worked. Even left it with the phone repair guys for a week with no luck. It first started after I flashed Hyperdrive ROM. A reboot helped for a while. It actually came back for a week on Kevp's ROM, but then had an error that reboot the phone and lost it again. Phone is now on Craigslist and I am back to my S2. On a high note it's nice to not have a unlocked bootloader again.
you need to flash the exact same model/firmware's modem file atleast thrice before giving up.... i have a simalar issue the thing is my model number is 1377z and google doesnt have a working flashable modem file for it so basically i am screwed too wifi calling and video recording doesnt work....
update :: saw that you got it replaced !!
smoooth .....
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
Just tried this on my sgh-i337m that was having the same wifi issues after rooting and flashing a kernel. Rebooted and wifi is up and running. So far so good. Thanks a lot!
Hi guys, I have to clear my mind on a problem:
I have a XT1562 european mono-SIM Moto X Play, and I've upgraded it to Marshmallow (the indian dual-SIM firmware) after unlocking the bootloader and flashed Squid kernel some weeks ago (and then updated to the last build, of course).
Sometimes I'm experiencing an annoying thing: after a reboot RIL dies, and on the best, on the next reboot it reappears; on the worst, after multiple reboots with no luck, I have to do a wipe cache to see it again.
I have root and Xposed (and so, also busybox).
Is anyone experiencing something similar?
There's a way to fix it that maybe I didn't find here on XDA?
Nobody?
have u tried flashing the modem for ur rom?
anks095 said:
have u tried flashing the modem for ur rom?
Click to expand...
Click to collapse
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
nplezka said:
Yes.
But it's strange, because I see it's not modem fault or similar. I see it's something software related because sometimes when I reboot, I also have the stock wallpaper (the green material one).
Now I flashed Marshmallux rom with the exact configuration (apps, modules, etc) and for now all is ok.
But, I still wanna follow this thread because it's too strange and I want to see if someone will expose a pearl.
Click to expand...
Click to collapse
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
anks095 said:
Ok..good...but may be u can do a full wipe and then flash factory image and then check it out if the problem sill exist..if not then that should something with software with ur last OS.
Click to expand...
Click to collapse
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
nplezka said:
Hi guys, I'm back to inform you that I'm on Marshmallux and the problem is still the same. I get randomly "emergency calls only" until reboot (maybe).
I don't understand...
Click to expand...
Click to collapse
I don't know if this is the same thing as you but I had "Emergency Calls Only" sporadically as well but it would come back either after a short period of time or after a reboot. I also had random reboots too (didn't matter which ROM I was on at the time).
I lived with this for a bit but then upgraded my SD card (it was old) and I haven't had either problem since.
My guess is that my SIM card might not've been seated properly in the little carrier and/or the SD card I had was mucking things up somehow. I wasn't using it as internal storage either.
Anyways, if you haven't tried this already, might be worth taking out your SIM card and re-seating it (and maybe give the contact part a careful wipe). If you still have the problem and you have an SD card remove it and see what happens. Good luck!
Hi guys! I'm here with news:
after several tests in these days, I discovered the problem was every module that can modify the systemUI.
I tried activating and disabling those modules one by one (I'm talking about GravityBox first, then little modules like Advanced Power Menu or a newer one called NeoPowerMenu), and I saw that without them, I had network at every reboot. The only exception in systemUI is SignalIconsAOSP (I really hate that big "4G" icon next to the signal indicator) and it works at every reboot I did. The other modules (like Xposed GEL Settings, Lolistat, YouTube AdAway) don't annoy the system.
So, I don't know, Moto seems dislike too much modifications on the UI or it's a strange bug. Maybe a bug.
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Unroot, lock and take it back for repairs? Sorry, not very XDA-style answer.
Edit: are you completely sure that you flashed the right stock ROM for your device?
Try again
Alvaro Luna said:
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Click to expand...
Click to collapse
I have a Retla and received official 9.0. download the 89-2 stock firmware. You can find it here. Use the .bat
File, place inside extracted firmware click & when it restarts you should get a notification to download 89-5.. once it completes the next notification will appear.. that's 116-11 9.0..
mod edit - telegram chat spam removed