[SOLVED] Patching services.jar causes wifi profiles loss? - Samsung Galaxy S10+ Questions & Answers

Got my phone rooted couple days ago with Magisk (in recovery) and so far its working fine. All green. Yayyy
But when I tried to patch services.jar myself (by having my own magisk module to replace), something weird happened. All wifi profiles reporting "Incorrect password" I have to re-enter the passwords but it always ends up being that after reboot.
I think patching services.jar triggers something that causes the saved data to be corrupted and cannot be decrypted somehow? I think other data like bluetooth paired devices could be corrupted in the same way too.
I tried using the original services.jar without any modifications (just replace the .odex). Still no luck.
Smali Patcher doesnt seems to work on 10. I tried that too.
Im currently on latest stock ROM android 10 in case you wonder.
Any help would be appreciated!

alex.do said:
Got my phone rooted couple days ago with Magisk (in recovery) and so far its working fine. All green. Yayyy
But when I tried to patch services.jar myself (by having my own magisk module to replace), something weird happened. All wifi profiles reporting "Incorrect password" I have to re-enter the passwords but it always ends up being that after reboot.
I think patching services.jar triggers something that causes the saved data to be corrupted and cannot be decrypted somehow? I think other data like bluetooth paired devices could be corrupted in the same way too.
I tried using the original services.jar without any modifications (just replace the .odex). Still no luck.
Smali Patcher doesnt seems to work on 10. I tried that too.
Im currently on latest stock ROM android 10 in case you wonder.
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue with wifi, I haven't patched services.jar though, so it's not that. I never re-entered passwords, just rebooting again did the trick. Not 100% sure yet but I think I solved it by wiping dalvik-cache, haven't had the issue since, touch wood

hinxnz said:
I had the same issue with wifi, I haven't patched services.jar though, so it's not that. I never re-entered passwords, just rebooting again did the trick. Not 100% sure yet but I think I solved it by wiping dalvik-cache, haven't had the issue since, touch wood
Click to expand...
Click to collapse
Got it solved!
I followed you to wipe the davik-cache and cache partition also. It didn't help at first. So I went on re-entering the passwords to some recent wifi profiles and tried to reboot. Voilaaaa the wifi seems to be saved properly now. I will check if it still survives after several reboots.
I think my patched services.jar has something to do with secure storage (since I set the isTimaAvailable() to return true always - more details can be found in Smali Patcher project, which does no longer work properly on Android 10) and that causes the old data to be corrupted and you gotta re-enter. I hope I only need to do it once.
Thanks for the tips!

Related

wifi on cm10 and cm 10.1 not working at all

Hi, maybe someone has a clue:
I seem to be the only one who can't use cm10 because wifi is just not working. On cm10 it's dropping out all the time as soon as data gets transfrerred (i.e. app download) and on cm10.1 its not even dropping. there is no data throughput whatsoever.
If you need more info, just tell me which one and I'll post it. I'm desperate.
Any ideas?
Assuming you have made a clean install, with system and data wiped as well, you should check your router configuration, try changing channel and/or security parameters
Sent from my MB526 using Tapatalk 2
thanks for the suggestion. I don't have access to all the routers settings but I tried to use one even without security and the drop outs still appeared. Working well on m7.
I just realise: At the beginning of a fresh build it sometimes happens that wifi works for a couple of MB and suddenly starts dropping.
Is the Wi-Fi network used by many persons at a time? More than a couple of devices connected may cause problems because the new Wi-Fi drivers starts jamming devices, and sometimes as a result the Wi-Fi network is unable to deliver data.
Sent from my MB526 using Tapatalk 2
I wouldn't say so. Not to many and it didn't work with the old wifi driver on cm10 either. The wifi keeps working for other parties in the network - so it is not jammed.
I might try again with a new build but I'm pretty hopeless...
Here is a long post about what I tried so far:
http://forum.xda-developers.com/showpost.php?p=38869441&postcount=915
measel said:
Hi I'm sorry to bother again.
I tried to figure out whats wrong with the wifi bug I'm having: constant drop outs while using any kind of wifi traffic.
Good news:
it worked well at home with my fritzbox router. (only tried 3-4 app downloads) > after a short while it stopped working
Bad news:
in my studio we got a different router and there I got the drop outs.
What I tried so far without luck (always a reboot in between):
disable Draft-N in wpa_supplicant
compared wpa_supplicant but it's the same as in cm7
delete rgnt from system/bin
change build.prop to use all 14 channels > ro.wifi.channels=14
tried changing PowerSavePowerLevel = 0 to 1
copied tiwlan.ini from cm7 backup because a few settings are different
tried 12-12-05 Quarx build
tried 12-10-18 build (but got a bootloop and stopped trying)
tried newest 13-03-07 build
ADDED tried 13-04-09 build
tried newest build and did another factory reset AFTER installing the ROM.
searched the web and found that maybe it might have something to do with wpa2, but the router at home uses wpa2/wpa (which means it's wpa2 as well or not?) and NO I cannot change the routers settings and I don't think it is a solution because i can use but not access like a dozen routers.
checked dmesg: in the TIWLAN section after the wifi connection it says: "iface_stat: stat_update() tiwlan0 not found
is it in any way possible that some settings change because I plugged usb "charge only" in while trying to download from Playstore? because it seems that dmesg spits somthing out regarding usb... (I'm can't really read/understand the output though)
oh and btw. first connection was fine in my last try: I could update Gmail, then I connected my usb and drop outs began. but I don't think it's related.
ADDED change to static IP
ADDED change regional code in wifi settings (w/o knowing what that actually does)
ADDED tried factory reset from stock, flash sbf and start from scratch.
Things I didn't try (and don't know if it would make any sense):
replace tiwlan_drv.ko
change vsel
[...]
Click to expand...
Click to collapse
It may be something elementary, but I presume Wi-Fi optimization is configured properly right?(IT MUST BE DISABLED)
I have had this issue but setting channel manually fixed it for me. This issue I had only on jb and with a specific router only. All others work properly on every channel.
Sent from my MB526 using Tapatalk 2
Damn I can't just change all the channels in all the wifi networks I'm allowed to use... but I will try that with my own one.
I did not try to change channels, yet but I tried once more to start from scratch: wipe from stock / flash sbf / install cm10 and so on..
Reason: Someone hinted the stock wipe could help. But here is the problem:
Everytime I try to wipe from stock (before or after flashing sbf) I get the old "E:can't mount cache:recovery/..." ERROR. Something seems to be wrong and I wonder if that could prevent my wifi from working (maybe data is still unwiped...)
Any more ideas?
Stock recovery can't handle ext4, hence the read errors.
Stock recovery wipe will not help if custom recovery data wipe does not help. You can also try manually deleting the Wi-Fi folder in the data partition.
You'll have to try changing channels eventually, I think.
Sent from my MB526 using Tapatalk 2
thats a misunderstanding:
I know that stock recovery can't handle ext4. My working system is cm7 so I stockwiped from cm7 and still couldn't get rid of the errors. I even checked the filesystem with e2fsck but everything seems to be ok. And I can install everything so... I don't know.
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
And what misunderstanding are you talking about?
Sent from my MB526 using Tapatalk 2
thekguy said:
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
Click to expand...
Click to collapse
That does sound pretty scary.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Click to expand...
Click to collapse
I can't waste another day on hunting the /cache problem right now because of work, but as soon as I have more time I'll try a little more.
Here is some news from me: I had the chance to try it on another wifi router last night and behold: It worked nearly flawless.. a few hickups I think, but it worked. That means WIFI is not broken, but there must be some software-related problem/ or some network weirdness.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
Click to expand...
Click to collapse
This I will not do!
thekguy said:
And what misunderstanding are you talking about?
Click to expand...
Click to collapse
Just that stock over ext4 thing. Nevermind.
Thank you for helping. I wonder if there is a way to find the problem.
Did you check the channel that particular Wi-Fi router operated at? Same as or different than the problematic routers ? Because if so then we have narrowed the problem down
Sorry for the scary part
Sent from my MB526 using Tapatalk 2

[Q] Wifi problem post-kernel update.

After updating to the latest Franco Kernel (r150) earlier today, I found that my wifi no longer works:
i.imgur.com / 6LmniGC.png <-- sorry, low post count.
The wifi switch has been disabled, and I cannot turn wifi on.
I tried reverting to an older revision of the kernel, going back to r134 which I was previously using with no problems, and found that I still could not turn on wifi.
Does anyone have any brilliant ideas?
Thanks in advance.
You can try fixing permissions and wiping the dalvik/cache from recovery mode. That probably wont fix it though, it seems like your wifi config is screwed up. Franco does not mess with the wifi in his kernel so it was probably caused by something else.
Holcomb227 said:
You can try fixing permissions and wiping the dalvik/cache from recovery mode. That probably wont fix it though, it seems like your wifi config is screwed up. Franco does not mess with the wifi in his kernel so it was probably caused by something else.
Click to expand...
Click to collapse
Thanks for the suggestion, but unfortunately neither wiping dalvic/cache nor fixing permissions resolved the issue. Wifi is still unavailable.
I don't know for sure that it was the kernel update that caused the issue, but wifi was working before the update, and then wasn't available after I updated, and I didn't do anything else in between.
I don't suppose you know how to 'unscrew' a wifi config?
I had that problem awhile ago, sadly the only way I could fix it was to restore a Nandroid. If you don't have one and can't wait, I suggest you wipe the phone and reflash everything.
Perhaps someone else here has a fix though
Sib3lius said:
Thanks for the suggestion, but unfortunately neither wiping dalvic/cache nor fixing permissions resolved the issue. Wifi is still unavailable.
I don't know for sure that it was the kernel update that caused the issue, but wifi was working before the update, and then wasn't available after I updated, and I didn't do anything else in between.
I don't suppose you know how to 'unscrew' a wifi config?
Click to expand...
Click to collapse
I pulled the wifi config files from AOKP and packaged them as a zip. Install in recovery. Hope it works.
mega. co.nz/#!E1YRRa5R!JeH_UVS-SaaPGGdj5R7bHnxU4DtGm3iq5yiaypnNEVE
remove the space after "mega." I cant post links yet.

[Q] SGS4 WiFi/Bluetooth Death, ZERO working solutions, willing to pay.

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!

RIL disapperaring sometimes

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.

[Help] Can't turn on wifi

Hi there, I got an issue on the OOS 4.5.12 after 3 days of using it. I got the problem , that the button looks stuck. I can click it and it will change its own color, but it doesnt turn on my wifi. Now I know I can clean flash the update again, but In want to know if someone had/has this problem too, and if someone maybe knows a work-around.
Edit: So I tested the device furthermore and found out, that I can't turn my Wi-Fi hotspot on... Wiping dalvic/ART cache didn't work neither...
Strange.... I didn't have this problem at all.
_MartyMan_ said:
Strange.... I didn't have this problem at all.
Click to expand...
Click to collapse
Same until today ? I will try to dirty flash the update, just to see if this will solve the problem. If it doesn't work, then I will be switching back to 4.5.10 OOS
Sent from my OnePlus 5 using XDA Labs
When I got this error I found out it was because I flashed new firmware and used an older kernel which didn't support the new firmware. You should read your logcat and see if there is any clue there.
Hello. Calling for help!
I have the exact same issue except i am able to launch and use WIFI. When i try to enable portable hotspot it gets stuck on "Turning on". The hotspot button in the slider shows enabling but the hotspot never gets enabled. I was on OOS 4.5.15 and upgraded to 5.1.5 after which i restored only the DATA partition from TWRP. I am currently rooted. I tried with editing the build.prop file and restarted but the issue is persistent. Any help would be appreciated.
Thanks
qureshiburhan said:
Hello. Calling for help!
I have the exact same issue except i am able to launch and use WIFI. When i try to enable portable hotspot it gets stuck on "Turning on". The hotspot button in the slider shows enabling but the hotspot never gets enabled. I was on OOS 4.5.15 and upgraded to 5.1.5 after which i restored only the DATA partition from TWRP. I am currently rooted. I tried with editing the build.prop file and restarted but the issue is persistent. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I would recommend a clean flash to test without restore old data.
strongst said:
I would recommend a clean flash to test without restore old data.
Click to expand...
Click to collapse
Thank you for replying. I dug a bit deeper last night. Deleting the entire wifi folder from root and restarting fixed the issue.
I had a lot of problem with wifi after flashed a not stock rom. Nobody could me help until I find the solution. Tell me Jelly do you have mac address or it show 02:00:00:00:00:00?

Categories

Resources