Database Develop

Installed Magisk Manager. Got a few questions.

I Installed Magisk Manager and i already had supersu. Well now ive got magisksu installed. So i deleted the supersu. But the busy box app is still on my device. But busy box says not installed. Do i need busy box with magisksu? I'm confused

If you have apps that need busybox you can enable Magisk busybox in the Manager settings. Otherwise you can ignore it.

Didgeridoohan said:
If you have apps that need busybox you can enable Magisk busybox in the Manager settings. Otherwise you can ignore it.
Click to expand...
Click to collapse
Okay thanks. And do you know why the force doze app isnt putting my phone into deep sleep after switching to magisk?

BenClay13 said:
Okay thanks. And do you know why the force doze app isnt putting my phone into deep sleep after switching to magisk?
Click to expand...
Click to collapse
Don't know. Your description of your installation is a bit vague. If you already had systemless SuperSU installed when installing Magisk, Magisk will use SuperSU rather than MagiskSU. In that case you'll still need the SuperSU app for root management.

Didgeridoohan said:
Don't know. Your description of your installation is a bit vague. If you already had systemless SuperSU installed when installing Magisk, Magisk will use SuperSU rather than MagiskSU. In that case you'll still need the SuperSU app for root management.
Click to expand...
Click to collapse
I had SuperSU but when i installed magisk it changed to MagiskSU under the properly rooted tab. I don't know how it happened. I just let magisk do its thing and then when my phone rebooted my kernel was back to stock(previously had FK), and magiskSU was now under the properly rooted tab.

BenClay13 said:
I had SuperSU but when i installed magisk it changed to MagiskSU under the properly rooted tab. I don't know how it happened. I just let magisk do its thing and then when my phone rebooted my kernel was back to stock(previously had FK), and magiskSU was now under the properly rooted tab.
Click to expand...
Click to collapse
In that case your installation of SuperSU wasn't systemless. If you want FK back it's just to install it again. Hm... I have never tried installing FK over Magisk through the FK Manager & Updater. If you get issues, reflash your stock boot image, flash FK and then Magisk.
About your Force Doze issue: does the app ask for superuser access? To keep with the FK theme, I've tested Naptime with MagiskSU and it works well.

WiFi problems caused by Magisk ?

Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11

cl0g said:
Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
Click to expand...
Click to collapse
Remove all modules and reboot into recovery.
Wipe caches and reboot.
I have found that I can end up with WiFi, Bluetooth, SIM issue if something happens with the modules.
Before I figured out what it was, I was re-installing the ROM, etc.
Try just deleting the modules and wiping the caches and rebooting.

@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.

cl0g said:
@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
I actually did read the whole post and was offering a solution that DID NOT require re-installing the ROM.
I'm not 100% sure why the problem persist but I have seen it affect Bluetooth, Wireless and SIM recognition.
Typically it happens after a reboot. Wiping the cache on my phone causes it more than 50% of the time if I don't disable modules first.
I don't know why it happens but you are right, removing Magisk does not solve the problem.
There is something corrupted in the data partition and the only way to clean that up is to remove the modules and wipe the cache or do what you proposed.

Nevermind

I recently had the same problem. I'm currently trying to fix it without reinstalling. I've uninstalled all modules, cleared both caches and still no wifi and I'm getting random crashes. Has anyone found fix a reliable fix?
While posting, I tried resetting my network and everything started working again. If this happens again, I'll try that first.
BTW
Also, it happened after a failed installation of Crossfire and Tethering, both thru Magisk. Tethering actually installed but after the reboot, I've got no wifi.

I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael

mellus said:
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael
Click to expand...
Click to collapse
Ugh. I'm having the same issues after upgrading to canary channel Magisk 20.4 on my Razer Phone 2. My WiFi was rock solid on the previous version, but for some reason my WiFi now flashes on and off like a strobe. Weirdly, it doesn't seem to have the issue at my house, but it constantly craps the bed at my work. The work connection is 5Ghz and my home one is 2.4Ghz, so that could be a difference. However, before my attempted upgrade, both worked perfectly.
I tried uninstalling my Magisk modules, flashing the Razer stock boot image, wiped Dalvik cache, flashed Arter/TWRP boot image, Arter kernel zip, Magisk 20.3 stable and reactivating modules. No change at all. WiFi is still garbage.
Are you telling me I'm going to have to flash the entire stock image and wipe my phone to get back full functionality?

im having the same problem, on miui i tried tp downrage magisk, that worked. currebtly searchin best way to downrage cause i forgot what i did. but if anyone stuck at this problem:
Without data wiping (luck method):
Remove modules
Reboot into recovery
wipe caches
reboot
done
Downrage magisk (maybe not fix):
Uninstall ALL modules
Delete Magisk from the app
flash downrage magisk
(eg. uninstall 24.1, install 23.0)
wipe caches
reboot
done
Data wiping (i forgot about should we flash magisk via magisk app with recovery mod on, if this dont work try enabling recovery mode):
Just Re-install Magisk via recovery
Clean everything BUT leave boot not wiped
flash rom WITHOUT boot
let it 10-30 minutes booting
go to recovery
flash rom's stock boot
reboot
finish rom's installation
install MAGISK APP
confirm additional installation
reboot
done

Fix ColorOS 6.0 Background Apps Killing and Bypass Startup Manager 5 Apps Limit

Requirements:
- ROOTED DEVICE
- Install any root file manager with text editor (I used ES File Explorer Pro)
- Install any system app disabler (I used Disable Application [ROOT])
Steps:
1. Open app Disable Application [ROOT] and disable the app Athena
(this will prevent your apps from force stopping when you clear them from the recent apps. *clear all button won't work, close apps by swiping)
2. Open ES File Explorer, give root permission and open /data/oppo/coloros/startup/bootwhitelist.txt with the text editor
3. Find the package names of the apps you want to run in background and add them at the bottom line of the list
(package names of apps can be easily found in the Disable Application [ROOT] app)
4. Then enter the Phone Manager app > Privacy Permissions > Startup Manager. You will see that the apps which you put on that list will appear as recommended to turn on.
5. Now you just enable those
That is all you have to do. Reboot if you want to, but it is not necessary.
ENJOY!
App links:
https://apkpure.com/es-file-explorer-file-manager/com.estrongs.android.pop
https://play.google.com/store/apps/details?id=com.iamaner.oneclickfreeze&hl=en

your phone already rooted, bro?

Chelyzin said:
your phone already rooted, bro?
Click to expand...
Click to collapse
... how else would i have figured out this fix?

Inquiad Raad said:
... how else would i have figured out this fix?
Click to expand...
Click to collapse
my device can't rooted can you help me?

Chelyzin said:
my device can't rooted can you help me?
Click to expand...
Click to collapse
Do you have twrp flashed?

Inquiad Raad said:
Do you have twrp flashed?
Click to expand...
Click to collapse
I have already flashed TWRP too, but still not rooted.
After I flash magisk, my device cant boot and got error message "boot device destroyed or contact customer service" and I flash supersu then nothing happen.
can you help me?

Chelyzin said:
I have already flashed TWRP too, but still not rooted.
After I flash magisk, my device cant boot and got error message "boot device destroyed or contact customer service" and I flash supersu then nothing happen.
can you help me?
Click to expand...
Click to collapse
First flash your stock boot.img and reboot to twrp. Then flash Magisk 19.4 beta version. Magisk 19.3 stable doesn't work on Realme X.

Inquiad Raad said:
First flash your stock boot.img and reboot to twrp. Then flash Magisk 19.4 beta version. Magisk 19.3 stable doesn't work on Realme X.
Click to expand...
Click to collapse
I thought, I do that yesterday but still doesnt work. Can you give me private link of magisk 19.4 or link magisk you have?
btw , I on 1903 and magisk still affected? or not?

Chelyzin said:
I thought, I do that yesterday but still doesnt work. Can you give me private link of magisk 19.4 or link magisk you have?
btw , I on 1903 and magisk still affected? or not?
Click to expand...
Click to collapse
https://redirect.viglink.com/?key=e164e26dfb5274d06a0fe10b82774dc2&u=https%3A%2F%2Fgithub.com%2Ftopjohnwu%2FMagisk%2Freleases%2Fdownload%2Fv19.4%2FMagisk-v19.4.zip&type=ap&loc=https%3A%2F%2Fforum.xda-developers.com%2Fapps%2Fmagisk%2Fofficial-magisk-v7-universal-systemless-t3473445%2Famp%2F&ref=https%3A%2F%2Fwww.google.com%2F

Chelyzin said:
I thought, I do that yesterday but still doesnt work. Can you give me private link of magisk 19.4 or link magisk you have?
btw , I on 1903 and magisk still affected? or not?
Click to expand...
Click to collapse
Did it work? Were you able to root your phone?

tried it in realme 5 pro and it worked, thanks so much.

Does it work in Realme 3 as well? Also, is it safe to try this out? Just wondering coz I just bought my phone a few months ago.

It also works on Realme UI, thank you, it's very usefull

The easiest was to remove the background Apps Killing is by removing com.coloros.athena
You can remove it through ADB as well.

OnePlus7ProOxygen_21.O.22_OTA_022

Amendments
System
• Optimized power consumption in standby mode
• Optimized advanced screen display
• Optimized Bluetooth connectivity in cars
• Improved overall interaction (network, phone calls, mobile data)
• Optimized charging performance with third-party chargers
• With blank screen
• Fixed animation problem with fingerprint icon
• Fixed volume AirPods problem
• Fixed issue with black stripe during charging or Play Video Denia
• Updated security patch for Android 2.019.10
• Improved system stability and fixes general errors
Camera
• Optimized performance of the Super Stable function in the Video for Camera application.
https://androidfilehost.com/?fid=4349826312261635544

Rooted and good to go

Does Call of Duty Mobile still crash?

Installed since morning. Still October patch but have noticed battery is not draining as fast in use or idle. Notify buddy was working in tandem with Google Assistant in beta 5 but not here. Think it's a cleanup of either beta 3 or 4 with updated security patch from 10.01. Quite happy with it overall.

before install it on 10.01 swiped factory reset , I installed the rom with twrp ,when finished install , I made again factory reset,and install twrp zip (-3.3.1-70-guacamole-unified-installer-mauronofrio.zip )again .
battery not drain as fast in use,no problem about notification and no problem with twrp and magisk

Installed, rooted, TWRP, ElementalX, Gravity Box - Sill passes safety net.

The live wallpaper Is no more working.
Anyone has this problem?

I have the OnePlus launcher constantly crashing with the screen flashing. I have to use another launcher. Any idea how to fix? Tried uninstalling etc. But to no avail.
Also lost TWRP functionality since now it doesn't ask for pattern and can't mount storage. So no flashing Magisk or another rom.
Came from OB5 by disabling all Magisk mods, flashing 10.0.2 in TWRP, flashing TWRP installer script, rebooting recovery and that's when I got stuck with the unusable recovery. Help?

Guys since I've flashed this the play store keeps wanting me to pay for apps I've already bought and doesn't show any apps under update..I've uninstalled my account and reinstalled, also wiped the play stor app itself

tech_head said:
Installed, rooted, TWRP, ElementalX, Gravity Box - Sill passes safety net.
Click to expand...
Click to collapse
How did you get gravity box installed......
I installed core and tried both sandhook and yahfa... They both left me in a bootloop

grinch247 said:
How did you get gravity box installed......
I installed core and tried both sandhook and yahfa... They both left me in a bootloop
Click to expand...
Click to collapse
avid_droid said:
Wondering the same. I have never got any to work and in another thread someone provided a link but that also left me bootlooping
Click to expand...
Click to collapse
There is a beta release for Android 10. That doesn't trip safety net
*See my next post*
Use 0.4.5.5 not 0.4.6.0

If anyone can help, greatly appreciated.
going from 9.5.11:
System update to 10.0.2. Did not reboot on completion.
Flashed TWRP 3.3.72 in Magisk. Did not reboot.
Installed Magisk via direct install. Did not reboot.
Installed Magisk via available slot. Reboot, all good. Still rooted, no data lost.
I just did this but can't boot, just the white circles around the red circle screen

avid_droid said:
Yahfa or sandhook? Riru core and what else?
Click to expand...
Click to collapse
Riru core 19.5
YAHFA 0.4.5.5
Edxposed framework v90
Gravitybox (Q)
It's the only way I got mine to work on any 10 releases
Better link for everything gravitybox with guide
https://forum.xda-developers.com/xp...0-0-0-beta-1-android-10-t3974497#post80381445

avid_droid said:
Twrp.72 is still causing issues. Use twrp.70 and it'll work perfectly fine
Click to expand...
Click to collapse
Recovery will affect booting?
So just flash the 7.0 installer? I can currently boot to 72 recovery.

avid_droid said:
I ran into that problem when flashing with twrp.72
What I had to do is:
flash twrp.70 and reboot back into slot A.
Flash OOS 10.0.2
Flash twrp.70
Format data (you can try a factory reset)
Repeat same sequence on Slot B
Rebooted into system and set everything up and let it finish.
Reboot back into recovery and made sure I was in slot A
Flashed magisk 20.2
Reboot into system
All is good to go.
---------- Post added at 02:09 AM ---------- Previous post was at 01:58 AM ----------
Isn't there anyway to flash a different TWRP to get boot rather than to have to do all that flashing that you did?
Click to expand...
Click to collapse

avid_droid said:
vibrantliker said:
Yeah, just flash twrp.70 and reboot to recovery and it'll be .70
Click to expand...
Click to collapse
Sorry for all the questions, I can boot to .72 recovery now. Should I flash the earlier version from there? If so, can it be the installer or does it have to be the .img.
After flashing the different recovery, should it boot or do I have to do all the flashing like in your post above?
Click to expand...
Click to collapse

tech_head said:
Installed, rooted, TWRP, ElementalX, Gravity Box - Sill passes safety net.
Click to expand...
Click to collapse
So u run Xposed? Do u use Snapchat?

avid_droid said:
vibrantliker said:
Flash twrp.70 and you won't have any flashing issues.
Flash the twrp.70 and if you can't boot into system, like what I experienced with .72, then unfortunately, a clean flash is recommended as I've posted above
Click to expand...
Click to collapse
The installer or the .img
Click to expand...
Click to collapse

avid_droid said:
vibrantliker said:
Installer.zip just flash it through twrp and reboot to recovery and it'll show twrp .70
Click to expand...
Click to collapse
Then try reboot to system?
Click to expand...
Click to collapse

avid_droid said:
vibrantliker said:
Yes. If it doesn't reboot to system, then you'd have to reflash it all like I explained earlier
Click to expand...
Click to collapse
Thanks!
Click to expand...
Click to collapse

Root miui 12 without custom recovery

Hi guys. I have a question.
I updated my Mi9T to miui 12 and now I want to grant root again. I did the same things that I've done with miui 11:
Downloaded the rom
Extract the boot.img
Let magisk patch the boot
flash the patched boot with fastboot
The problem is that I got a WiFi issue: I can't turn it on. I back my boot.img to default e now it work but without root. Any ideas?

Marco2701 said:
Hi guys. I have a question.
I updated my Mi9T to miui 12 and now I want to grant root again. I did the same things that I've done with miui 11:
Downloaded the rom
Extract the boot.img
Let magisk patch the boot
flash the patched boot with fastboot
The problem is that I got a WiFi issue: I can't turn it on. I back my boot.img to default e now it work but without root. Any ideas?
Click to expand...
Click to collapse
Maybe you have ACC installed - uninstall and try without ACC (people did report similar errors for AAC, not dure was it fixed later in the module)

zgfg said:
Maybe you have AAC installed - uninstall and try without AAC (people did report similar errors for AAC, not dure was it fixed later in the module)
Click to expand...
Click to collapse
Sorry, I don't know what is aac. I searched it but I don't understand what I need to uninstall. I deactivated all magisk module but there is still the issue.

Marco2701 said:
Sorry, I don't know what is aac. I searched it but I don't understand what I need to uninstall. I deactivated all magisk module but there is still the issue.
Click to expand...
Click to collapse
Sorry, mistake, I meant ACC, Advanced Charging Controller Magisk module

zgfg said:
Sorry, mistake, I meant ACC, Advanced Charging Controller Magisk module
Click to expand...
Click to collapse
Nope, I haven't this module. Any other ideas?