Straight away after rooting 4.7.5. my wifi doesn't work. Like the toggle won't turn on etc and won't find networks. But after a reboot it's fixed until the next reboot which it starts again.
Any idea how to fix it for good or wait for updates?
known problem, Have to wait on update
Lol! It's not a rooting issue at all. Only after flashing a custom kernel you CAN end up with non functioning WiFi but that's only because the kernel-thread hasn't been read properly.
Rooting + WiFi = zero problems :good:
Likely a custom kernel was installed which installed it's own wifi (and other) modules. Then the kernel was changed or reverted back to stock, but system partition is still changed with custom modules for connectivity. If you revert back from a custom kernel, a "dirty" flash of the system partition usually solves the issue.
Maybe it was after magisk. After magisk patches the boot.img it's "sort of" custom kernel Right. I had magisk 14.5 beta and wifi wasn't working and I flash 14.0 and it's seemed to fix it i think.
wifi working- but...
Hi, my wifi works (picks up all networks nearby- including mine)
but-
it won't connect to my network when using passcode.
Any ideas?
Running Lineage current and used magisk to root initially...
HELP!
It's driving me nuts.
Having same issue as above.
Can search for but cannot connect to my WiFi.
First issue I had after rooting was Facebook messenger force closing only while I was writing a message, installed a custom rom and hasn't happened since. I cleared cache and data, tried a full format, reinstalled magisk and tinkered with settings with no luck still.
Related
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
Hello.
I'm experiencing some issues with rooting. My objective: stay stock, but gain root to flash franco kernel in order to get the best out of my device
All this is happening on OOS Open Beta 12 (Android 7.1.1). I was originally on OOS 4.1.1 and done everything I listed below, and then sideloaded OOS Open Beta 12 in hopes that it would resolve the issue.
What I've done: unlock bl > reboot into android> reboot to fastboot> flash twrp> reboot to twrp> reboot to system> reboot to recovery> i notice that the twrp recovery got overriden by the stock one
i then reboot to fastboot> flash twrp again> reboot to twrp> flash supersu> reboot to system
i have root and it works perfectly, but i lose cellular network.
Flashing franco kernel didn't bring the cellular network back. My device is not encrypted as far as I can see, even though the "Encrypt phone" tooltip in settings says "Encrypted". I'm not required to enter a PIN to start booting android nor did I not need to enter it to decrpyt the phone in TWRP.
Root zip I used is: BETA-SuperSU-v2.74-2-20160519174328-forced-systemless.zip
TWRP used: official 3.1.0-0 from official TWRP site, not the one from this guide
TL;DR: As soon as I get root, I lose cellular network. Right now I can't regain cellular network unless I reflash stock OOS.
Any clues on why this is happening and how can I resolve the issue?
Nevermind, resolved the issue using these steps:
Unroot > reflash twrp > flash SuperSU-v2.79-201612051815 > reboot. Also reflashed FrancoKernel and everything seems to be working fine now.
Although everything seems to be working fine, I can't seem to get LTE. 3G is max I can get. My G3 can pick up LTE with no problems. I was able to pick up LTE with OnePlus 3 yesterday, but nothing today. I'm not sure if this is due to root + kernel change.
Is this a known issue?
Edit: I just randomly got back LTE. It was probably just a temporary issue on my side.
I know you have to allow system modifications in order for twrp to stick or flash something besides an ota.
Glad your problem was fixed!
Hey you people!
Clean flashed Android 9 yesterday, rooted with magisk. No more stuff applied. Wifi stopps working on the phone after some time, restart solves it, but not for long. Mobile data doesnt work at all. Wtf is this?
Thanks
xflowy said:
Hey you people!
Clean flashed Android 9 yesterday, rooted with magisk. No more stuff applied. Wifi stopps working on the phone after some time, restart solves it, but not for long. Mobile data doesnt work at all. Wtf is this?
Thanks
Click to expand...
Click to collapse
Sounds like a Charlie Foxtrot to me! Who's your provider? And have you tried removing/replacing your sim card?
Is Mobile data enabled?
Badger50 said:
Sounds like a Charlie Foxtrot to me! Who's your provider? And have you tried removing/replacing your sim card?
Is Mobile data enabled?
Click to expand...
Click to collapse
yea it is enabled, there is "LTE" shown in the status bar, too. switched to 3g mode, same thing with H.
But wifi doesnt work either after some time, has an x shown besides the icon then. how about that?
no problems with 8.1 before.
xflowy said:
yea it is enabled, there is "LTE" shown in the status bar, too. switched to 3g mode, same thing with H.
But wifi doesnt work either after some time, has an x shown besides the icon then. how about that?
no problems with 8.1 before.
Click to expand...
Click to collapse
Have you tried resetting your APN's?
Did you fastboot, side load, or OTA to 9.0?
Idk what caused the problem, but go to Settings > System > Advanced > Reset options > Reset WiFi, mobile & BT.
If no improvement, then get a new SIM card.
If still no improvement, then flash the factory image and don't make any system changes like installing a custom recovery/kernel. Make sure data is back to normal before doing any mods. Good luck!
i think i got it.
after flashing the magisk uninstaller zip, everything works.
so its either just root, or (and that i previousl missed) the adguard module (with root proxy mode).
I updated as usual without doing anything... and everything works. Could it be the extra stuff you do to your phone?
I think it's best that people run this without magisk until they sort out the bugs. Seems to be working fine for me after going straight stock without twrp or magisk. Had major problems before when I was rooted.
xflowy said:
i think i got it.
after flashing the magisk uninstaller zip, everything works.
so its either just root, or (and that i previousl missed) the adguard module (with root proxy mode).
Click to expand...
Click to collapse
wcouri said:
I think it's best that people run this without magisk until they sort out the bugs. Seems to be working fine for me after going straight stock without twrp or magisk. Had major problems before when I was rooted.
Click to expand...
Click to collapse
Right after Android 9.0 was released, I flashed the factory image without "-w" in flash-all.bat, installed TWRP and used Magisk 16.7 to root. Weird stuff started happening: the camera app force closed once, and I couldn't multitask back into Google Keep because the system thought Keep was not available (even though I could open it from the app drawer and it worked fine). So I started from ground zero and reflashed the factory image without editing flash-all.bat, I did *not* flash TWRP or Magisk, and everything worked as it should and no FCs. Today, I flashed TWRP and Magisk 16.7, and everything is still working properly. I am also using Adguard in standard mode (not root proxy), and it has been working flawlessly, and no mobile data or WiFi hiccups so far.
I have been flashing for years, and I am convinced that some stuff doesn't get completely wiped even when you flash a factory image. But usually another clean flash resolves any issues.
sublimaze said:
Right after Android 9.0 was released, I flashed the factory image without "-w" in flash-all.bat, installed TWRP and used Magisk 16.7 to root. Weird stuff started happening: the camera app force closed once, and I couldn't multitask back into Google Keep because the system thought Keep was not available (even though I could open it from the app drawer and it worked fine). So I started from ground zero and reflashed the factory image without editing flash-all.bat, I did *not* flash TWRP or Magisk, and everything worked as it should and no FCs. Today, I flashed TWRP and Magisk 16.7, and everything is still working properly. I am also using Adguard in standard mode (not root proxy), and it has been working flawlessly, and no mobile data or WiFi hiccups so far.
I have been flashing for years, and I am convinced that some stuff doesn't get completely wiped even when you flash a factory image. But usually another clean flash resolves any issues.
Click to expand...
Click to collapse
Good info my friend! As the saying goes...No wipes, no gripes!! :good:
Hello, recently I got the poco f3 (256-8gB) and I have experienced a really weird behavior (I know about random reboots other peooke expperience, but please read what happened to me)
I rooted it with magisk (patching boot image using latest stable apk from official github).
I added smali oatchee module to it.
At some point miui auto-updated to 12.5.1.0 RKHEUXM, I had to get boot image from the update, extract from payload and reparch to get magisk back.
After this I noticed the phone rebooted randomly, it happened like once in 2-3 days, son nothing really anoying, I didn't pay much atention to it since the phone worked flawlessy for everything else. Then I tried to connect to a router wifi (router setup with openwrt) and I noticed EVERY TIME I tried to connect to that specific wifi the phone rebooted. I tried to reconfigure the wifi network but it still happened. No problem with other devices.
Then the next day, I openwd an app which had embedded adds (an app I have been using for a long time, the very same version). 1 second into the add the phone rebooted...and it became stuck in a bootloop in MIUI logo. I couldn't even power off the phone, I could enter recovery/fastboot though.
I used twrp to wipe it without erasing my data, but problem still persisted. Only reflashing boot image (I used stock version) revived my device. I tried to boot it without flashing, phone seemes to boot but with no display.
So I decided to make a full wipe, then reinstall magisk. Phone has been working fine since then, but the occasional random reboot still happens and I'm afraid eqch time my poco f3 will be stuck in bootloop again.
My conclusion is somehow boot image got coreupted, but I can't think of anything I could have done for that to happen, as I only had magisk set up, I didn't even use any app with root permisions yet. Any ideas why that my have happened?
I'm thinking of flashing twrp to recovery so I can reflash boot image from it in case this hapens again...
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Robert314 said:
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
Click to expand...
Click to collapse
How may I get those logs?
Alin45 said:
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Click to expand...
Click to collapse
My phone is already rooted via magisk patching the roms's boot.img, then flashing via fastboot. That's the recommended method for this device afaik.
Try clean flash. Backup all your stuff that you want to keep. Format data in TWRP before booting into system.
OTA auto-update from time to time causes issues.
I tried again and the revoot when connecting to that certain wifi network persists.
Is there anyway I can reflash my current firmware without having to wipe? Can I jast flash my current update with twrp with no data loss? (Basically what happens when a system update is out...)
Just posting to note that update 12.5.3.0.RKHEUXM solved all those random reboots for me.
They were also happenning when trying to share image/links/anything via bluetooth, telegram....only thing that worked without reboot was "copy link" in the share button.
Hey guys,
My Pixel 2XL initially had some reboot issues so I decided to root it, and was able to do that successfully with magisk on stock firmware with some modules installed as well. It regained its functionality for the most part but unfortunately the Wifi stopped working (kept searching, could'nt find any network). It would sometimes randomly work on some reboots but whenever it did, the phone would auto-reboot after a while and lose the function again (but would work perfectly otherwise).
So I decided to unroot and factory reset with stock firmware thinking it might be a partition defect, just to see if that fixes it but it didn't. And what's more, the phone has once again returned to bootlooping like before root. Can anyone help me find out the issue here? And if I can manage to root it again and get it working, is there some way to resolve this issue (maybe through a custom kernel)?