I can't figure out why my wifi won't work after rooting with magisk, I go into settings and turn on the wifi, and it either won't turn on, or settings crash entirely, please help
And to top it off, if I use adb commands to turn it on, arb crashes
What phone model do you have, and what version are you on? Did you flash the right modified boot image for your device? When I converted my phone to international my WiFi didn't work until I updated and patched the kernel in magisk. Try installing a custom kernel or if youre not updated try updating and follow a guide to keep root after update.
Is the modified boot.img only for the Tmobile variant or all? If its for all, i get some saying you dont have to do that anymore.
explosivequack said:
What phone model do you have, and what version are you on? Did you flash the right modified boot image for your device? When I converted my phone to international my WiFi didn't work until I updated and patched the kernel in magisk. Try installing a custom kernel or if youre not updated try updating and follow a guide to keep root after update.
Click to expand...
Click to collapse
I flashed the correct boot image, because the internet and texting service is still working, just not calling and wifi, i havent done anything with the kernel yet
Did you resolve this issue & magisk working as I have wifi & sim issues when installing magisk, when twrp & 10.0.4 is installed alone everythings fine, just with magisk the issues arise.
NHNXDA said:
Did you resolve this issue & magisk working as I have wifi & sim issues when installing magisk, when twrp & 10.0.4 is installed alone everythings fine, just with magisk the issues arise.
Click to expand...
Click to collapse
This may not be your problem, but when that happened to me I had forgotten to disable all magisk modules before installing an update. I had to restore from backup, disable all magisk modules, and reinstall the update. Then I was able to reenable the modules and everything was fine.
davidk21770 said:
This may not be your problem, but when that happened to me I had forgotten to disable all magisk modules before installing an update. I had to restore from backup, disable all magisk modules, and reinstall the update. Then I was able to reenable the modules and everything was fine.
Click to expand...
Click to collapse
Strangely I installed again & all worked fine, weird but true.
No modules installed but thanks for the reply anyway.
10.0.5 installed, now twrp kills wifi & network icons are a mess, reinstalling stock OOS fixes this, twrp can be installed but everytime it leaves with wifi not turning on & con mess.
Which inturn magisk wont work properly as twrp messed up the network side.
Related
Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...
Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk
Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk
I remember that installing magisk caused a bootloop on my stock 7.0
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse
josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.
For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse
https://developers.google.com/android/images
Still 9.0, but it's starting a new quarterly build so might have some updates. No change log yet
There is this
"All Pixel devices running Android 9 will receive an Android 9 update as part of the May OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices."
i did clean install of the recovery image this morning. all seems fine. nothing visually different
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Atomregen said:
Has anyone already rooted? With me, the carrier service crashes continuously after I installed Magisk 19.1.
Click to expand...
Click to collapse
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
I can't speak to the 3XL since I am on dotOS, but I had no issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
208.9mb too! Quite large for just a small incremental update too!
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
virtyx said:
considering locking my BL and clean wiping...
google pay no longer works and its fustrating.
Click to expand...
Click to collapse
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Atomregen said:
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck. After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
Click to expand...
Click to collapse
I had some issues getting the May update, TWRP 3.3.0-1, Kirisakura 2.3.0, and Magisk 19.1 to play nicely together. Lots of "rescue party" reboots at the "G" logo of booting after trying to install everything together. I basically did what you did to solve the issue too. Installed the May update (removing -w) then installed TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 18.1 and restarted back to system to make sure it all worked (which it did). After that I upgraded to Magisk 19.1 via the Magisk app and everything seems to be fine now. My temp solution until this was just use TWRP 3.2.3-3 which I had been using up until this point. That worked too and allowed everything to play nice from the initial installation.
Aren't you supposed to boot system before flashing magisk?
Atomregen said:
Thanks for replay,
I flashed the factory image (minus -w), booted TWRP 3.3.0-1 and installed magisk 19.1 many times but never had luck.
After that i flashed the factory image (minus -w) again, booted TWRP 3.3.0-1 and installed magisk 18.1 and now it worked, after that I was able to update magisk in the app to 19.1.
hopefully it is written understandably.
Click to expand...
Click to collapse
wangdaning said:
Aren't you supposed to boot system before flashing magisk?
Click to expand...
Click to collapse
I was wondering the same thing about whether you finished booting before installing Magisk. I completely boot after every step (Image, TWRP, Magisk, Kernel - ElementalX installed with EX Kernel Manager) and don't stack installs in TWRP. Been doing that for years, and it has saved me some time long term despite the couple of extra minutes during installs. My other thought was possibly a bad 19.1 file.
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
sstanton86 said:
208.9mb too! Quite large for just a small incremental update too!
Click to expand...
Click to collapse
Looking at new apps to backup in TB, there were about 7 new system apps that I saw and one that had been removed.
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Sent from my Pixel 3 XL using XDA Labs
Atomregen said:
since there is an auto reboot after flashing flash-all.bat, I did a reboot after flashing the factory image.
Click to expand...
Click to collapse
I always reboot to the system after the factory image/monthly update is installed and allow it to finish setup. Then I fastboot into TWRP to install TWRP recovery, my kernel, and Magisk via the "add more zips" option in TWRP. I've been doing this ever since I got the device and never ran into issues until this May update. Doing this with the May update, TWRP 3.3.0-1, Kirisakura 2.3.0 and Magisk 19.1 caused reboots like I described. However, reverting to TWRP 3.2.3-3 instead (my initial solution/fix) or Magisk 18.1 then upgrading Magisk to 19.1 (like @sliding_billy suggested) worked fine. This to me implies a compatibility issue of some type and not an issue with the method of installation.
Tulsadiver said:
Try this first.
Factory reset in TWRP (after installing factory update and rebooting).
You'll have to set up as new but won't lose internal data.
Click to expand...
Click to collapse
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
virtyx said:
magisk and gpay dont work after googleplay services version 16.0.91
if i downgrade to 16091 it works - but i cant let it upgrade otherwise it breaks gpay
im not sure if its on all phones or just pixels with the titan chip that GPS is now interacting with, but if you try to upgrade to 17.x google play service with magisk - it doesnt work and detects root.
just FYI for people with issues with updates let it boot into OS before flashing TWRP / KERNEL / MAGISK otherwise you will get a bootloop.
and personally i flash TWRP/KERNEL/Magisk in that order and ive never gotten a bootloop (but have flashing kernel last a couple times)
my rationale behind flashing magisk last is because if you were on stock kernel, you would just flash magisk, you wouldnt flash magisk then stock kernel over it would you?
Click to expand...
Click to collapse
This is the way Freak recommends flashing his kernel. Did Freak change something?
Freak07 said:
Flash factory image with -w removed (if you want to keep data intact)
Do a reboot
Then you can boot to twrp and flash twrp, magisk and kernel (in that order)
Afterwards all should be fine.
I personally do a reboot after flashing twrp. Then back to twrp and magisk plus kernel...
Click to expand...
Click to collapse
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
I always flash kernel before magisk. I've never had issues.
Homeboy76 said:
This is the way Freak recommends flashing his kernel. Did Freak change something?
Click to expand...
Click to collapse
not saying either way is right or wrong
but it makes sense to flash magisk LAST.
Anyone try to sideload the OTA? I believe the file is too big to sideload?
lucky_strike33 said:
Anyone try to sideload the OTA? I believe the file is too big to sideload?
Click to expand...
Click to collapse
I sideloaded. Worked fine.
Anyone else unable to root the May update? I installed the update, TWRP, and the kernel I use and everything was fine. After installing Magisk 19.1 the phone boots straight to a "System UI has stopped" dialog box. Substratum overlays were uninstalled before updating and uninstalling Magisk fixes the issue, leading me to believe that it is the cause.
I tried installing Magisk 18.1 instead to see if it would work, but oddly it doesn't seem to install at all. When I boot the phone Magisk Manager was installed, but it claims that Magisk is not installed and no apps can get root access.
Hello guys, I have this problem since upgrading to the latest OOS 10.3.2. If I flash Magisk 20.3, device boots without detecting a SIM, so no signal at all. And phone app crashing.
I'm using the latest TWRP (twrp-3.3.1-18-enchilada-Q-mauronofrio).
Anyone experience the same? How to get this to work? I need my Google PAY back
-=zipp=- said:
Hello guys, I have this problem since upgrading to the latest OOS 10.3.2. If I flash Magisk 20.3, device boots without detecting a SIM, so no signal at all. And phone app crashing.
I'm using the latest TWRP (twrp-3.3.1-18-enchilada-Q-mauronofrio).
Anyone experience the same? How to get this to work? I need my Google PAY back
Click to expand...
Click to collapse
bro check ur imei number wheather it is showing or not dial *#06#
Same thing happenned to me. I removed magisk and all modules completely then used local upgrade and reflashed 10.3.2 OTA and flashed twrp img with fastboot. When it booted into twrp recovery I flashed the twrp installer, rebooted to back to recovery and flashed magisk from twrp and rebooted system. Everything was right with the world then. The key was re moving magisk first.
Sent from my ONEPLUS A6013 using Tapatalk
cjcool_123: IMEI is showing correctly because I reflashed ROM back to get networking ability
Hondo71: I'll try that, thanks
Hondo71: I tried that, but unfortunately with the same result.
I re-flashed stock rom to get functionality back, uninstalled magisk app, flashed twrp, rebooted. flashed magisk, booted and nothing :-/
IMEI is not showing when in this state
Might want to stay where you're at until more reports come in with the all clear or maybe there's an issue with the TWRP or the rom itself
I'd try one more time. Make sure magisk and all the modules are uninstalled. Download & Reinstall 10.3.2 full OTA through local upgrade. Then install magisk mamager. Boot to fastboot and boot TWRP recovery img. Then in recovery flash the twrp installer zip, reboot to recovery and install Latest magisk zip. Reboot system. Data and cellular should work. I lost it on both my 6 & 6T but got it back doing it this way on both.
-=zipp=- said:
Hondo71: I tried that, but unfortunately with the same result.
I re-flashed stock rom to get functionality back, uninstalled magisk app, flashed twrp, rebooted. flashed magisk, booted and nothing :-/
IMEI is not showing when in this state
Click to expand...
Click to collapse
Uninstall magisk and modules then reflash 10.3.2 from local upgrade download twrp installer and Magisk zip to internal memory, install magisk manager. reboot to bootloader, then fastboot boot TWRP, in recovery flash twrp installer, reboot recovery and flash Magisk. Reboot system. Just verified it working again on my OP6.
Sent from my ONEPLUS A6013 using Tapatalk
Hondo71: you were right, it is working now. I don't think I needed to do all the procedures you suggested, I figured out there was one module that was causing this - Native OOS call recorder :-/ I feel stupid I haven't thought about this before.
Anyway, all working now. Now I only need to find out new way how to record my calls
-=zipp=- said:
Hondo71: you were right, it is working now. I don't think I needed to do all the procedures you suggested, I figured out there was one module that was causing this - Native OOS call recorder :-/ I feel stupid I haven't thought about this before.
Anyway, all working now. Now I only need to find out new way how to record my calls
Click to expand...
Click to collapse
I reinstalled oos call recorder and it works fine.
Sent from my ONEPLUS A6013 using Tapatalk
How do I root stock os 10.3.2? Which version of TWRP and Magisk I have to use? Please advise. Thanks in advance.
I also lost the function for telephone.
Mobile network ist working, i can recieve calls, but im not able to do calls.
i tried everything...flashes a few times the latest beta...flashed Magisk new...delteted it...i dont know what else can be possible?
yess same problem after got new update > flash twrp > install magisk > NO SIGNAL That because of OOS native call recording delete and reinstall it >DONE Working great.
Hey all, so I iflashed lineageos 17 4.9 kernel by mistake. It slightly heats up my device .
Can I downgrade to 3.18 safely?
If so, how??
Safe to dirty flash this?
https://forum.xda-developers.com/redmi-s2/development/rom-lineageos-17-1-t4042045
One more question:
Some of my apps shows root detection with 4.9 version then crashes but I haven't rooted.
I tried a lotta methods: flashed magisk uninstaller, flashed installer then uninstaller and even use magisk hide feature with magisk installed but none works. Is this because the ROM that I'm using is in Testing Phase? Also it shows SE Linux disabled.
https://forum.xda-developers.com/redmi-s2/development/rom-lineageos-17-1-t4103145
Sorry for not looking properly into description, I'm new to all this stuff
Do clean flash or u can try other roms with 4.9 kernel other rom dosent have this prblm
mohitdabas07 said:
Do clean flash or u can try other roms with 4.9 kernel other rom dosent have this prblm
Click to expand...
Click to collapse
Sorry for late response, i clean flashed n and switched to Cs 3.18, but thanks anway.
So far im liking the os. There is one problem though, Root detection in certain apps problem still persists even though device not rooted. Anyway to solve this problem?
Thanks.
sk971 said:
Sorry for late response, i clean flashed n and switched to Cs 3.18, but thanks anway.
So far im liking the os. There is one problem though, Root detection in certain apps problem still persists even though device not rooted. Anyway to solve this problem?
Thanks.
Click to expand...
Click to collapse
Root it by magisk and use magisk hide
mohitdabas07 said:
Root it by magisk and use magisk hide
Click to expand...
Click to collapse
Ok, i flashed magisk 20.4, then installed magisk manager 7.5.1 and from settings activated Magisk Hide, but root detection still occurs and app crashes after that.
IDK why?
Tapping on safety net check stats on magisk manager shows both ctsprofile n basicintegrity to "true".
Do i have to encrypt my phone to fix this problem? Its disabled atm.
Ok having trouble updating and issue with rebooting
Have XX No limits and phone rooted
So backed up via Twrp and then installed ota update and then Twrp installer. Reebooted to recovery and then flashed Magisk
Re booted and kept getting error
Com. Android.Systems S........Keeps stopping
So rebooted to recovery again and flashed Magisk again and it worked and started ok
Then flashed no limits via magisk and same issue phone would not start
Then rebooted back into Twrp to reninstall back up and got a boot loop
So what is causing this and how can I fix it?
Thanks
funkyirishman said:
Ok having trouble updating and issue with rebooting
Have XX No limits and phone rooted
So backed up via Twrp and then installed ota update and then Twrp installer. Reebooted to recovery and then flashed Magisk
Re booted and kept getting error
Com. Android.Systems S........Keeps stopping
So rebooted to recovery again and flashed Magisk again and it worked and started ok
Then flashed no limits via magisk and same issue phone would not start
Then rebooted back into Twrp to reninstall back up and got a boot loop
So what is causing this and how can I fix it?
Thanks
Click to expand...
Click to collapse
The problem with bootloop can be caused by No Limits xXx ROM. It's exactly like Renovate Ice ROM. After updating Oxygen OS, I need to uninstall/disable Renovate Ice ROM and to wait that RIce to be updated to can use it again.
You can root with Magisk, reboot TWRP, open "Advanced">"File Manager">"data" (folder) >"adb"(folder)>"modules"(folder)>No limits (or something like that... Folder, again) and choose "delete">swipe right and reboot.
If it works, you can wait that NoLimitsxXx ROM to be updated.
P.S. sorry for my English and tell me if it worked
Dragoș2200 said:
The problem with bootloop can be caused by No Limits xXx ROM. It's exactly like Renovate Ice ROM. After updating Oxygen OS, I need to uninstall/disable Renovate Ice ROM and to wait that RIce to be updated to can use it again.
You can root with Magisk, reboot TWRP, open "Advanced">"File Manager">"data" (folder) >"adb"(folder)>"modules"(folder)>No limits (or something like that... Folder, again) and choose "delete">swipe right and reboot.
If it works, you can wait that NoLimitsxXx ROM to be updated.
P.S. sorry for my English and tell me if it worked
Click to expand...
Click to collapse
So everything is working just have not installed no limits
So take it remove all installed modules Reboot and reinstall no limits then install renovate ice?
funkyirishman said:
So everything is working just have not installed no limits
So take it remove all installed modules Reboot and reinstall no limits then install renovate ice?
Click to expand...
Click to collapse
No, I meant that some modules (Magisk ROMs usually) aren't compatible with every new Oxygen OS update, so you need to wait that respectively module to be updated.
I don't use No Limits xXx ROM, but I guess that Renovate Ice is exactly like this.
For example, you have two ways when you receive an update.
1. You can wait that your Magisk ROM to be compatible with the new Oxygen OS and then to install both.
2. You can install new Oxygen OS and wait that your Magisk ROM to be updated.
In case number two, I prefer to download it from settings (or Oxygen Updater app... it's the same size knowing that a unlocked bootloader needs a full update to not born conflicts). Ok, I download new update. I install it from settings. I DON'T REBOOT. Firstly, I go to disable all my Magisk modules, to install Magisk (After OTA to inactive slot). Then I reboot. I go to Magisk, install TWRP and Magisk (directly) and activate all my modules, but not Renovate Ice (or, in your case, No Limits xXx). I reboot and after that I need to wait the next update for Renovate Ice/No Limits xXx to come and to install it.