Database Develop

BusyBox Failed to Install

Hey guys,
Just rooted and installed magisk v12 on my OP3T. I'm still running stock oxygen with no additional modules installed on magisk. I went into ROM Toolbox to modify my CPU to be conservative and was prompted to install busybox. I have busybox pro so I went to install that but it's failing to install. Could this be because DM-Verity was flipped? I see a security warning every time I reboot but I honestly have no idea what the significance of it is so I just wrote it off.
Any ideas why BusyBox would be failing to install?

How is the installation failing?
You could just try enabling Magisk built-in busybox in the Magisk Manager settings.

Not sure how it's failing. In the past I'd open it up and hit install and everything was good to go, but it's saying:
"It looks like the installation was not successful. Try installing to a differently location, that may resolve the issue"
I'd switch it to a different location but again I'm not sure the implications of that either.

Same issue on OP5, "It looks like the installation was not successful. Try installing to a differently location, that may resolve the issue". Not sure where that option is in Magisk

Changed Magisk, now stuck on startup splash

This morning Pokemon Go stopped working on my phone. I found this which said to use the "Hide Magisk Manager" option from within Magisks Settings page, and then delete the MagiskManager folder from the SD card. I did that, restarted my phone, and Go started working again. Oddly though, Chrome wouldn't work, and kept crashing with "Unfortunately, Chrome has stopped." (whether I was actively trying to use it or not). Off of a fresh restart I could open chrome, but if I tried to load any webpages it would stay loading forever.
To try and fix that, I went back into Magisk and hit the "Restore Magisk Manager" option, and restarted my phone. Now, my phone won't boot -- it gets stuck loading on the splash screen. I seem to only be digging myself a deeper and deeper hole with each thing I do. How do I get my phone back up and running?
I'm running the latest RR (I think it's 6.1.0?)

Flash the Magisk uninstaller from here https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post68966662
You should then be back to an unrooted state.
Sent from my [device_name] using XDA-Developers Legacy app

Have you tried reflashing your Rom?
Also, what did you expect to Halen with magisk, after you have decided to delete it's manager folder?
Sent from my ONEPLUS A3003 using Tapatalk

Logue1021 said:
This morning Pokemon Go stopped working on my phone. I found this which said to use the "Hide Magisk Manager" option from within Magisks Settings page, and then delete the MagiskManager folder from the SD card. I did that, restarted my phone, and Go started working again. Oddly though, Chrome wouldn't work, and kept crashing with "Unfortunately, Chrome has stopped." (whether I was actively trying to use it or not). Off of a fresh restart I could open chrome, but if I tried to load any webpages it would stay loading forever.
To try and fix that, I went back into Magisk and hit the "Restore Magisk Manager" option, and restarted my phone. Now, my phone won't boot -- it gets stuck loading on the splash screen. I seem to only be digging myself a deeper and deeper hole with each thing I do. How do I get my phone back up and running?
I'm running the latest RR (I think it's 6.1.0?)
Click to expand...
Click to collapse
Repackaging and restoring the Magisk Manager should not have anything to do with the issues you started experiencing. If you can get your device up an running again (as already suggested, uninstalling Magisk might be a good way), could you recreate the problem and grab a logcat when Chrome crashes and when the phone get's stuck on boot.
RASTAVIPER said:
Have you tried reflashing your Rom?
Also, what did you expect to Halen with magisk, after you have decided to delete it's manager folder?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Deleting the MagiskManager folder from the internal storage is harmless. It's just used to store downloaded Magisk zips, module zips and saved logs. It'll be recreated when needed. Pokemon Go have started to detect this folder and use it as a sign of a rooted device. Deleting it is one way of getting PoGo running again.

I'm trying to keep myself in SuperSU, is easier and compatible with almost any app, I know that development stopped. But I feel that Magisk is a great tool but can be complicated.

First try using your computer to create a file without a name and with disable_.magisk as an extension.
Kinda like. disable_magisk
And use TWRP to copy this to /cache.
See if it boots up.

Hello I have the same problem unauthorized_device_lockout
The problem its that i had used super su before. Uninstalled it. Now i dont have any root and still happening (in pokemon go) please help

Logue1021 said:
This morning Pokemon Go stopped working on my phone. I found this which said to use the "Hide Magisk Manager" option from within Magisks Settings page, and then delete the MagiskManager folder from the SD card. I did that, restarted my phone, and Go started working again. Oddly though, Chrome wouldn't work, and kept crashing with "Unfortunately, Chrome has stopped." (whether I was actively trying to use it or not). Off of a fresh restart I could open chrome, but if I tried to load any webpages it would stay loading forever.
To try and fix that, I went back into Magisk and hit the "Restore Magisk Manager" option, and restarted my phone. Now, my phone won't boot -- it gets stuck loading on the splash screen. I seem to only be digging myself a deeper and deeper hole with each thing I do. How do I get my phone back up and running?
I'm running the latest RR (I think it's 6.1.0?)
Click to expand...
Click to collapse
Hi i found a fix, you just need to reflash magisk patched boot.img from your phone(hope you backed it up) and the system.img / custom os (i didnt even have to wipe my data) lol

[Help] CTS Mismatch

Hey,
I tried several times to pass Safety Net so I can use Google Pay, but I get a constant CTS mismatch.
Things I tried:
-Going back to older Firmware
-Locking Bootloader
-Removing USB debugging mode
-Factory Reset (in eRecovery)
I don't know what else it could be.
Firmware I've installed right now is the CLT29 159 C432

you have busybox installed? or magisk?>

RiTCHiE007 said:
you have busybox installed? or magisk?>
Click to expand...
Click to collapse
nope and nope
like I said I already did some factory resets or flashed firmwares

Then try to install magisk and use the magisk hide feature on the system.

RiTCHiE007 said:
Then try to install magisk and use the magisk hide feature on the system.
Click to expand...
Click to collapse
I already did that. Doesn't help. It also should pass if I'm not rooted or anything. But it doesn't pass.
I also tried flashing a different boot.img because I thought it could have been not flashed but nope also doesn't help.

KennyDumah said:
I already did that. Doesn't help. It also should pass if I'm not rooted or anything. But it doesn't pass.
I also tried flashing a different boot.img because I thought it could have been not flashed but nope also doesn't help.
Click to expand...
Click to collapse
There was someone a few days ago that couldn't get google pay to work also and when he joined the play service beta then after a reboot it worked. But it sounds like there are some files on your storage that **** up the whole thing so maybe its good if you did a system format.

RiTCHiE007 said:
There was someone a few days ago that couldn't get google pay to work also and when he joined the play service beta then after a reboot it worked. But it sounds like there are some files on your storage that **** up the whole thing so maybe its good if you did a system format.
Click to expand...
Click to collapse
So I should fastboot format system / data / cache and then go to twrp or eRecovery and flash a new firmware?
Is it OK to do that in a Huawei?
Used to have nexus phones and it was way easier to do stuff

KennyDumah said:
So I should fastboot format system / data / cache and then go to twrp or eRecovery and flash a new firmware?
Is it OK to do that in a Huawei?
Used to have nexus phones and it was way easier to do stuff
Click to expand...
Click to collapse
Well, im more thinking like flashing a PIt file like on the samsung where it formats the whole memory and then flashes the firmware so that its 100% original.

RiTCHiE007 said:
Well, im more thinking like flashing a PIt file like on the samsung where it formats the whole memory and then flashes the firmware so that its 100% original.
Click to expand...
Click to collapse
Is there anything like that for Huawei?
BTW I already tried formating all partitions and reflashing. Still doesn't pass CTS.
So you said this one guy installed Google play services beta?

yea like this https://www.youtube.com/watch?v=v_RzbAhJkOk

RiTCHiE007 said:
yea like this https://www.youtube.com/watch?v=v_RzbAhJkOk
Click to expand...
Click to collapse
Tried that aswell and noticed I'm already in the beta of google play services. So thats also not my problem.

KennyDumah said:
Tried that aswell and noticed I'm already in the beta of google play services. So thats also not my problem.
Click to expand...
Click to collapse
Try this
- In the Magisk downloads section, download and install “MagiskHide Props Config”
- Reboot
- Download a terminal emulator from PlayStore (eg Termux)
- Open terminal emulator
- If using Termux type “su” and grant root access
- Type “props”
- Select option ‘1 edit device fingerprint’
- Select option ‘f
- pick a certified fingerprint’
- Select option ‘4
- Huawei’
- Select option ‘6
- Huawei P20 Pro (8.1.0)’
- Enter ‘Y’ for yes
- Reboot
Should fix CTS

dladz said:
Try this
- In the Magisk downloads section, download and install “MagiskHide Props Config”
- Reboot
- Download a terminal emulator from PlayStore (eg Termux)
- Open terminal emulator
- If using Termux type “su” and grant root access
- Type “props”
- Select option ‘1 edit device fingerprint’
- Select option ‘f
- pick a certified fingerprint’
- Select option ‘4
- Huawei’
- Select option ‘6
- Huawei P20 Pro (8.1.0)’
- Enter ‘Y’ for yes
- Reboot
Should fix CTS
Click to expand...
Click to collapse
Thanks will try that later at home. But shouldn't CTS pass safetynet, when I installed a new firmware without root etc?
Because that's my point. I'm not rooted or anything and flashed just a new firmware with full factory wipe.
Anyways I gonna try that as soon as I get on my pc.

KennyDumah said:
Thanks will try that later at home. But shouldn't CTS pass safetynet, when I installed a new firmware without root etc?
Because that's my point. I'm not rooted or anything and flashed just a new firmware with full factory wipe.
Anyways I gonna try that as soon as I get on my pc.
Click to expand...
Click to collapse
What else is installed?
Are all apps up to date? I had an issue a while back and it was just Google, needed an update.
Once I had and rebooted it worked.
Couldn't finish the Google pay set up, kept halting on the agreement pages.
Updated and all good.

This method worked fine for me. Thanks! I'm on 159 as well.

So I fixed it on my phone now.
I was about to try what @dladz wrote.
I installed TWRP again so I had to remove my fingerprints and screenlock.
after flashing Magisk I suddenly had the CTS passing, I dont really know if its a bug with the screenlock and fingerprints.

Lineage OS 17 getting "Magisk is not installed"

I'm at my wits end trying to get Magisk back!
(The backstory is that I had been running a DirtyUnicorns OS for a year just fine, but then Pokemon Go started failing to login. So it was time to update.)
Using a Samsung Tab 4 (SM-T330NU)
Formatted and installed stock OS/boot
Used Odin to flash "twrp-3.0.0-3"
Used TWRP recovery to update to "twrp-3.3.1-0"
Installed "Lineage OS 17" (and added Gapps) - made sure it booted and all was well
Booted into TWRP recovery and installed the latest "Magisk-v20.4"
Wiped cache and rebooted
Installed the latest "MagiskManager-v7.5.1" and got "Magisk is not installed"
After a great deal of searching I learned how this is supposed to be corrected:
Took the boot.img from the Lineage OS 17 zip,
Used Magisk to patch it, creating "magisk_patched.img"
Used TWRP recovery to install "magisk_patched.img" to the boot section
Wiped cache and rebooted
Still getting "Magisk is not installed"
Booted into TWRP recovery and installed the latest "Magisk-v20.4" just in case
Still getting "Magisk is not installed"
This is all after roadblocks for hours a day for a week trying to pass safetynet using Magisk on Lineage OS 16 for about a week, so I thought this fresh start would be easier and now I'm pulling my hair out.
Any suggestions would be helpful. I just want to be able pass safetynet and my ctsProfile match fails. Which I can't even begin to work on without Magisk core.
Thanks in advance.

First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed

Didgeridoohan said:
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Click to expand...
Click to collapse
Thanks for the quick reply!
How do I check to see where it's installed and/or reinstall it to the proper storage? Because that could be it.
There's no SD card or USB device plugged in and I couldn't find more information online (I even scoured didgeridoohan.com before posting here).

Also, and this may be helpful, it appears the device is not rooted. Fx file explorer and root checker apps confirm this. So it's possible even with the steps I followed that Magisk core really isn't installed and the apk is telling the truth (I'm just at a loss to know how that's possible after flashing the zip and flashing the patched boot file, both in twrp).

If you have no SD card installed adoptable storage won't be an issue.
You can easily verify through TWRP if the core Magisk files have been installed. Check in /data/adb/magisk. It should contain busybox, magisk, magiskboot and magiskinit binaries, together with addon.d, boot_patch and util_functions scripts.
Seeing the recovery log from when you attempt to install the Magisk zip in TWRP might show us something. Also try the could also be a good idea trying the Canary release to see if there's any difference from stable v20.4.

(This thread can be locked/(closed?)/answered)
I tried my damnedest and nothing worked. So I wiped/formatted lineage-17.1-20200512 and installed lineage-17.1-20200419. THIS was the ease with which I was accustomed to installing Magisk (Recovery install and immediately working on boot). Sadly, other problems abound and they are outside the scope of this subforum.
Just in case anyone reads this and cares:
- GPS Joystick was a no-go because apparently Lineage has a not-so-nifty feature that blocks the "draw over apps" android feature if your RAM is below some secret threashhold, which prevents the entire app from functioning.
- Fake GPS can take getting used to, and I'm used to it and love it, but the location and routing keeps crashing in the background, which means pogo closes when I tab back to start it back up again.
- Regardless of which I use I am rubberbanding back to my house... despite using all the tricks I can find or think of (yes, including 'smali patcher', specific app settings, systemizing the GPS app, setting off/on mock locations, etc)... but I think it's because this OS has no unique setting for the GPS data to be "device only".
Problems one and two are due to the ****ty ram on this Samsung tablet, which I've always known was an issue, so I suppose it might just be time to buy a phone specifically for this purpose. From what I read, the best cost effective option is an iPhone SE, and I'm truly not an Apple fan (I certainly would not risk my own phone being bricked or even merely wiped).
Not sure how I used it for the last year without this many issues, but it seems like that's over now unless I want to deal with DirtyUnicorn OS again, and that was it's own nightmare sometimes.
Thanks all for reading, but especially Didgeridoohan for replying and for all the resources on your pages and threads.

Greenify for magisk bootloop

I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?

You need to enter twrp and select the module causing the card machine to be deleted in the twrp advanced options, file management and data / ADB / modules directory

https://lanzoui.com/b03c2iqbi Password: han
This is the self-help brick rescue module generator made by our domestic great God. After you choose to set it, click OK to automatically brush it into the mask manager! However, you cannot select a language! You can translate screenshots by yourself! The general description of the function is to find that the card machine module regrets trying the boot mode several times. If it still fails to boot after reaching the number set above, all modules will be automatically disabled to achieve the boot effect

ruffpl said:
I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
Click to expand...
Click to collapse
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Check from the section "Disabling/uninstalling modules manually". Maybe this will help

Thanks all for help I got it working. I read that all I need to do is just restart phone from safe mode and when phone will boot magisk will be disabled and it worked . I had open magisk app,removed module, flashed magisk boot image and its ok for now. Only problem that still exists is with some modules - when I want to install zip file I got extract error.

Safe mode has side effects. It's better to uninstall and install! After putting on the mask, brush in the automatic brick rescue module provided by me, and you can do it at will

If you don't understand, open the application, click the three vertical bar options on the right and directly click to confirm the default!