Hello.
I am desperate now...
I was on 1.105.01, and followed this thread to get the update.zip and update to 1.141.
However, now my wifi simply says "error" and does not connect nor work.
Can anyone help me?
Flashing an unsupported whatever broke something? *shock*
Why don't you post in that thread?
I didn't post because I saw noone with problmes related to this there. I tought this might be an isolated incident.
I am trying to pull myself out of this by installing the leaked chinese 3.1, which should have all data... However, being offline, i can't seem to be able to install ClockWorkMod. I am rooted, but i don't know what zip to use.
Please help?
Done. Scaped the situation by downloading the leaked chinese 3.1 and installing it as a update.
You got your wifi working again?
what does this update do?
Wifi is working again, no programs or configs lost.
I was installing the update more as an "learn how to do stuff". Learned.
nerdmore said:
Hello.
I am desperate now...
I was on 1.105.01, and followed this thread to get the update.zip and update to 1.141.
However, now my wifi simply says "error" and does not connect nor work.
Can anyone help me?
Click to expand...
Click to collapse
I had the same thing happen when I updated to 141. The permissions on the wifi modules was set incorrectly. Root + chmod to the module files and wifi worked again.
how did you do to fix this problem with wi-fi ?
I did the update to 1.105.01 > 1141.01 and the same thing happened to me like the top friends over there I do not know what to do have no application because I clicked System Restore now my wifi does not start or can access my files for lack of an explorer apk 1.105.01 someone has to send me the original?
UPDATE - Problem sorted via philos64 thread at the top...
Should've tried that 1st, but posted here hoping someone would confirm that was the route to take, as it wasn't actually bricked... Never mind, all done..
Why??? Was out earlier so I turned my wi-fi off and my mobile on and everything was working fine..
When I got home, I turned the mobile off and tried to turn wifi back on, but it is hanging on 'Turning wifi On.'
Tried rebooted the tablet a few times and rebooting the router, (BT HomeHub 3), but still the same problem.
This N7 is rooted and running 4.2.2.
When I look at the Advanced Wifi the MAC and IP address are unavailable.
When I go into Wifi Analyzer it says the wifi needs to be turned on and tries but gets same hang and retries...
On the left of the analyzer it shows my Wifi ID with a mac address underneath with a yellow triangle and 'No Signal!' in red.
The wifi from the router is working as my phone is connected via wifi.
Any ideas please people ???
:crying:
going for the post with the most views and zero replies is not on my bucket list... So I'm going to reply to myself..
An Update....
The problem is still there, so I went into bootloader - recovery mode....Then I went into Android system Recovery.
I selected cache then wipe dta/factory reset.. Reboot then starts tablet as new with the unlocked symbol, then goes through the initial setup. Select language, then it does Select wifi and displays 'Turning on wifi'.. Hung...
Would flashing it via Nexus root toolkit sort out then problem... If so, any clues what flash and how...
If it wouldn't fix it... Is the tablet now bricked??
Please answer someone if you know..
Cheers
There have been several posts about wi-fi problems if the outer shell of the N7 is separated and not fully locked in. A loose or separated shell can cause a disconnect in the wi-fi antenna. Check for any separation and maybe squeeze the front and back together all the way around the outer edge.
I did read them and a lot of other threads but they were mainly to do with wi-fi looping and not connecting.... I couldn't find any other post regarding just 'turning it on'.... And seeing as it's sorted with just a flash of the stock rom, I can safely assume this problem had nothing to do with hardware...
Hence why I was surprised I was the only 1 with this 'type' of prob.... (but I didn't read every post so I may have missed one).
Same problem too
filking said:
I did read them and a lot of other threads but they were mainly to do with wi-fi looping and not connecting.... I couldn't find any other post regarding just 'turning it on'.... And seeing as it's sorted with just a flash of the stock rom, I can safely assume this problem had nothing to do with hardware...
Hence why I was surprised I was the only 1 with this 'type' of prob.... (but I didn't read every post so I may have missed one).
Click to expand...
Click to collapse
im experiencing the same thing. im using Samsung galaxy S4 i9505 LTE and on android 4.3/ rooted Baseband i9505XXUEMJ5. it happened when i was trying to erase all the bloatware on my phone using Trulyclean by schoolsux. after i flashed the script i started having this problem.so far ive tried to do a factory reset by using custom recovery, tried to download the modem fix and flashed it through odin and do the advanced settings on wifi and uncheck the auto network switch. The problem that i have is yes it say "connecting" for 2-3 minutes then it gives you a list of possible wifi connections and then you connect. another 2-3 minutes then it wont connect. repeat the steps and now i can connect, then if you turn off the wifi you will have to go through the whole process again. it doesnt save any wifi connections you have connected before. there are 2 other ways i havnt tried yet and that is to flash a different kernel. a custom kernel and reflashing my phone again with the android 4.3 then root:laugh: for the nth time already:fingers-crossed:
hammerthumbs said:
im experiencing the same thing. im using Samsung galaxy S4 i9505 LTE and on android 4.3/ rooted Baseband i9505XXUEMJ5. it happened when i was trying to erase all the bloatware on my phone using Trulyclean by schoolsux. after i flashed the script i started having this problem.so far ive tried to do a factory reset by using custom recovery, tried to download the modem fix and flashed it through odin and do the advanced settings on wifi and uncheck the auto network switch. The problem that i have is yes it say "connecting" for 2-3 minutes then it gives you a list of possible wifi connections and then you connect. another 2-3 minutes then it wont connect. repeat the steps and now i can connect, then if you turn off the wifi you will have to go through the whole process again. it doesnt save any wifi connections you have connected before. there are 2 other ways i havnt tried yet and that is to flash a different kernel. a custom kernel and reflashing my phone again with the android 4.3 then root:laugh: for the nth time already:fingers-crossed:
Click to expand...
Click to collapse
i have same issue with htc one x, my wifi doesn't wan't to turn on. it stuck on "turning on...", i tried to flash different roms, etc, now i think about flashing kernel, did you do that? did it help?
Same problem on N4
Have had the exact same problem not once but twice. One day it works perfectly fine. Next day, it just stops at turning on process.
On my N4 the 4.2 was working fine. Along comes the 4.3 OTA update and the wifi stops working. Does not startup or show the mac addr either.
Did factory reset, wipe cache and even reflash binary from google stock images. No relief.
One day, the wife using gmaps started the gps location service and pop the wifi started,
Now after the 4.4 OTA all seemed to work well till yesterday and pop the wifi breaks down. the earlier trick of gmaps does not seem to work. I think one of the google apps update is breaking this.
After rebooting also, the device seems to remember the wifi state and tries to read the previous history and restore for the startup. And that is killing.
Any idea how to debug this or to wipe the wifi logs or to manually start the wifi/bluetooth radio.. ya athe bluetooth is also stuck.
Thanks guys in advance
Where is the fix?
filking said:
UPDATE - Problem sorted via philos64 thread at the top...
Should've tried that 1st, but posted here hoping someone would confirm that was the route to take, as it wasn't actually bricked... Never mind, all done..
Why??? Was out earlier so I turned my wi-fi off and my mobile on and everything was working fine..
When I got home, I turned the mobile off and tried to turn wifi back on, but it is hanging on 'Turning wifi On.'
Tried rebooted the tablet a few times and rebooting the router, (BT HomeHub 3), but still the same problem.
This N7 is rooted and running 4.2.2.
When I look at the Advanced Wifi the MAC and IP address are unavailable.
When I go into Wifi Analyzer it says the wifi needs to be turned on and tries but gets same hang and retries...
On the left of the analyzer it shows my Wifi ID with a mac address underneath with a yellow triangle and 'No Signal!' in red.
The wifi from the router is working as my phone is connected via wifi.
Any ideas please people ???
:crying:
Click to expand...
Click to collapse
Hi Can you please send a link for the solution? i am still stuck with "wifi turning on" screen and cant seem to bypass it. No matter what Stock image i flash through Wug Toolkit.
i have got the same wifi errorrigictsi vanished
initially i had loaded my explorer with fly rom and everything waas working except the internal memory. i'm not even able to download at least an app and then i tried bulletsense rom for increasing the internal memory of my explorer. it's successful, and the memory increased. From there onwards, the problem started. the wifi first said error... but after reboot, it's all the time saying "turning on"..
by typing "ifconfing twlan0" it said no devices found... so i thought it might be some driver error. coueld any one port some other drivers to the below rom so that i can have both internal memory and wifi...
link to bulletsense rom ///d-h.st/xFr//// ( add https before /xxxx/)
here is a screenshot of it...///bit.ly/MMSeam///
any one please help me on this and give me a chance to raise your thanks meter...
sorry that i'm newbie and not allowed to post links.
Hey guys.. I faced similar issue in my AMOI 820 based Indian local device Micromax (rooted + custom kernal)
I fixed this stuck wifi problem by uninstalling Google apps in system by removing them using Titanium back up + and again installing them from playstore if needed.. Hangouts(in my case) if it's a system app after getting updated is the culprit .. Try removing it and reboot and test it yourself..
guess it working now!!
I was going crazy about this stuck wifi issue!!
I tried everything!! I found on the advance panel on the wifi
That the MAC address and the IP address is unavailble.
After many tries i think i fixed it!! Using:
Busybox and MacMan
MacMan changed my MAC address and now the wifi is no longer stuck!!!! Hope it will help you too. Peace
yurashi# said:
I was going crazy about this stuck wifi issue!!
I tried everything!! I found on the advance panel on the wifi
That the MAC address and the IP address is unavailble.
After many tries i think i fixed it!! Using:
Busybox and MacMan
MacMan changed my MAC address and now the wifi is no longer stuck!!!! Hope it will help you too. Peace
Click to expand...
Click to collapse
I have same problem on my nexus 5,
But macman is not working.
Any other solutions
wifi turning on problem
i have a xperia sola mobile ..
wifi is does not work ..please help
when touch the wifi option then it does not turning on ..
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!
Can someone please suggest a ROM that won't give me the WhatsApp time error? FIVE roms I have tried all suffer from this "issue". I know it's a 'known bug" but why? It's it really so hard to fix a time issue?
My clock even resets itself throughout the day.
What should I look out for so not to get this issue again?
Thanks.
Stock?
WhatsApp works fine this end, on stock latest Lollipop
I don't want just 'stock' though. I want a rom that's got features and has been debloated. I'd I wanted stock I wouldn't have rooted my phone.
the problem isn't your rom
there's something wrong with the time_daemon
on a rooted device, turn auto sync time to provider setting off
make a copy of time_daemon from system/bin
reboot your device and set the correct time
then delete time_daemon and reboot
you will have to reboot a couple of times
turn auto sync on again, reboot once more, put time_daemon back in system/bin and reboot one last time
should be fixed now
at least - it worked for me
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!