Hello ! Every time I install BusyBox from PlayStore or Magisk Repository , I go into a bootloop ... I want to try viper audio on Android 10 Miui 11 but he needs BusyBox installed ... So , how to solve this ? I have the latest global stable 11.0.3.0 / 11.0.5.0 MIUI 11
Try to install orange fox recovey -> reinstall magisk -> install busybox from magisk. I have no bootloop when install busybox from magisk. If you bootloop when magisk module install, you easy delete module from orangefox recovey. Sorry for my bad english
mrback007 said:
Try to install orange fox recovey -> reinstall magisk -> install busybox from magisk. I have no bootloop when install busybox from magisk. If you bootloop when magisk module install, you easy delete module from orangefox recovey. Sorry for my bad english
Click to expand...
Click to collapse
Are you sure you don't have bootloop on the last MIUI 11 EEA stable 11.0.5.0 ? I tried 3 times ...
ManDone.vRs said:
Are you sure you don't have bootloop on the last MIUI 11 EEA stable 11.0.5.0 ? I tried 3 times ...
Click to expand...
Click to collapse
Your phone bootloop when install magisk or busybox ?? If bootloop when install magisk try to "format data" not " wipe data" . note " format data" will delete all internal storage
I don't use EEA but every rom i use eg : xiaomi eu, miuimix, lineage os,PE ... No bootloop when install busybox, just bootloop when install magisk
mrback007 said:
Your phone bootloop when install magisk or busybox ?? If bootloop when install magisk try to "format data" not " wipe data" . note " format data" will delete all internal storage
I don't use EEA but every rom i use eg : xiaomi eu, miuimix, lineage os,PE ... No bootloop when install busybox, just bootloop when install magisk
Click to expand...
Click to collapse
It's bootloop after flashing or install BusyBox . The last version of miui 11 and Android 10
same case on me
im on miui 12 android 10, global stable 12.0.1.0, waiting for solution, because i want instal v4a like before when im on miui 11
ManDone.vRs said:
It's bootloop after flashing or install BusyBox . The last version of miui 11 and Android 10
Click to expand...
Click to collapse
This is SAR. Do not install BusyBox app but BusyBox (systemless) Magisk Module from Magisk Manager
zgfg said:
This is SAR. Do not install BusyBox app but BusyBox (systemless) Magisk Module from Magisk Manager
Click to expand...
Click to collapse
That`s works on all SAR devices or not? I have Samsung SM-T510 (all new Samsung`s going with system-as-root) and root it through Magisk app like in official guide from John Wu for Sams devices, but i have any doubts about installing Magisk modules on modified (but still commonly stock) ROM.
vlrgamaley said:
That`s works on all SAR devices or not? I have Samsung SM-T510 (all new Samsung`s going with system-as-root) and root it through Magisk app like in official guide from John Wu for Sams devices, but i have any doubts about installing Magisk modules on modified (but still commonly stock) ROM.
Click to expand...
Click to collapse
Unfortunately, there is no such thing - "works on all devices" or things like that.
Nobody can guarantee you in advance (if not willing to test yourself, afraid of nuclear blast or something, then don't root your phone )
There are differences between vendors, Android version, etc, specially who knows in advance what you might have in your custom ROM xxx on the device yyy and would something work or not
However, if SAR is read only, then any BusyBox installation (like older apps, maybe older modules) that attempt.to write directly to /system will fail.
Therefore suggestion was to use the given BB module, that uses the systemless mechanism provided by Magisk - in that case it SHOULD work no matter if your SAR is read-only or not
Plus, you just later disable the module and reboot, and BB is gone.
Similarly for any other systemless module and all their artefacts they 'install' to the System - hence, the systemless changes are much more 'secure' than old methods that attempt to make hard changes directly to the System (if something ever goes wrong you then have to reinstall the ROM or manually search and revert changes left by those apps)
If you are you are not familiar with the systemless concept, wether your SAR is read-only or not, etc - please google
Related
-This methode is old but working with emui 4 Android MM (6). Not work with Android N (7).
-Xposed not work in systemless mode if your Android security patch is >= november 2016
-Try to search the last version of zip files and apk on google, the version on this tutorial is old.
Hi!
This tutorial will install Magisk, phh's superuser, xposed and busybox on your Huawei P9 lite device!
Tested on a VNS-L31C432B151 version but normally work on all VNS-L31 and VNS-L21.
Magisk will allow you to "hide" the root... not realy just hide because Magisk and phh's superuser systemless edition create the root outside the system folder!
Magisk feature for common user:
-"hide" root (PokémonGo, Androidpay, banking app, ... all work!) work with
-Magisk not only allow you to replace existing file and directories, but also support adding new files and directories into system!
-Update OTA work! (not tested by me)
For more detail visite this post: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Phh's superuser work at 100% on this device
After a lot of Xposed version tested I can say that Xposed systemless edition is by far the best for P9 lite!
DONT install busybox on system folder!
Ok let's go:
1 Update your system on last emui version and swipe data/factory reset to get a clean and untouched device!
2 Unlock your bootloader (see multiple method on this forum)
3 Install TWRP 3.0.2.0 (see multiple method on this forum)
4 Download this files: Magisk V6.zip / phh's superuser 17.zip / xposed-v86.5-sdk23-topjohnwu.zip / Magisk Manager.apk / XposedInstaller_by_dvdandroid.apk. Put all this files on your externalSD.
5 Go to TWRP recovery and flash in order [Magiskv6.zip > phh's_superuser.zip > Xposed-v.86.5.zip] also reboot your device.
6 When you are on the homescreen go reboot again.
7 Install Magisk Manager.apk and XposedInstaller.apk, then go to the playstore download and install Phh's SuperUser app AND Busybox meefik. Reboot after this step.
8 Open your setting app and allow permission SD card to Busybox.
9 Open Busybox >> settings. Remplace the path file /system/xbin/ with /data/busybox/ and check "Remplace Applets". Also go Menu Zip Archive and download this zip.
10 Go on TWRP recovery and flash the busybox zip file.
10 please perform 3 or 4 reboot
DONE!
So, please try to open yours setting app. if it appears you have done! If not, please try again this method
Now, go Magisk Manager (app) and switch root togle off, launch your protected against root app and normally work!
(Dont need reboot between switch root off/on!)(Selinux switch work, but not persist a boot)
Have fun!
Well done. Works perfect.
The are no files any more
Links are dead
deleted
Evas0r said:
Battery draining after the process...
Is this xposed fault?
Click to expand...
Click to collapse
yes u have to flash another version
Did anyone try this on Nougat/Android 7?
Alexander33 said:
Did anyone try this on Nougat/Android 7?
Click to expand...
Click to collapse
TWRP with this [RECOVERY]Revolution Recovery Android Nougat {15-12-16} Beta .9 in Nougat but anything I tried to flash failed.
Is there anything one can do to get Pokémon Go working while having all of these installed?
Alexander33 said:
Did anyone try this on Nougat/Android 7?
Click to expand...
Click to collapse
Hey, man I've tested it on my Huawei P9-LITE B370 and it all works perfectly. To flash Magisk, you need this custom recovery (https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356)
this really helped me thanks
Helped me alot. Still, post is a bit old, so what I did on b380 version:
FLASH RECOVERY twrp-3.1.1-0-venus.img
FLASH KERNEL Elite+Kernel+for+P9+Lite+CxxB3xx+v10.1.zip
ROOT with Magisk-v13.0(96f8efc).zip
INSTALL busybox archive via recovery to /sbin (for me it installed on /system/xbin, still ok.)
REBOOT after each step
Finally works ! :good:
is this Magisk work on Huawei P9?
I have Emui 5.0 and Android 7.0. I flashed everything except xposed but I still can't use Pokémon Go or Snapchat. Is it beacause i can't flash xposed? And when yes, how can I fix it?
Lg ThePrinoob
ThePrinoob said:
I have Emui 5.0 and Android 7.0. I flashed everything except xposed but I still can't use Pokémon Go or Snapchat. Is it beacause i can't flash xposed? And when yes, how can I fix it?
Lg ThePrinoob
Click to expand...
Click to collapse
flash magisk v13
simo255 said:
flash magisk v13
Click to expand...
Click to collapse
Ok, I will test it!
I installed magisk v13 and got the app but it when it check safety net it doesnt work. What should I do?
ThePrinoob said:
I installed magisk v13 and got the app but it when it check safety net it doesnt work. What should I do?
Click to expand...
Click to collapse
enable magisk hide and see if usb debugging is enabled
simo255 said:
enable magisk hide and see if usb debugging is enabled
Click to expand...
Click to collapse
Okey thank you it worked.
Hey,
If I open the camera app or snpachat I cant make any picture so I have a blackscreen. What should I do? And in youtube or Instagram I cant see videos, they dont load and I also cant hear any sound.
Sorry for my bad english.
I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu
Somebody help me...
I am sure it has been mentioned many times in other threads and forums too.
Magisk 14+xposed seem to be incompatible.
This bootloop happened to me also. I just returned to TWRP and reflashed 13.3.
Problem solved.
Unleashed by ONEPLUS 3T rooted
Why don't flash system version of Xposed?
caryle said:
I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu
Click to expand...
Click to collapse
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.
Aneejian said:
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.
Click to expand...
Click to collapse
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?
caryle said:
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?
Click to expand...
Click to collapse
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
I've read the posts before. I just want to know if it caused by anything else.Now I'm going to flash the xposed system.
There is a better solution:
1 Get this zip file (thanks to @LarappsOfDongle)
2 Flash it by using adb sideload or adb push
3 Go to /magisk in recovery using built-in file manager if using TWRP or use Aroma
4 Delete ONLY folder with or similar name as xposed_framework_25 (be careful in TWRP you need to go into the folder first to delete it)
DON'T DELETE ANY OTHER FOLDER
I had the same issue. Tested with Xposed Framework 25 Magisk 14.0 Oxygen OS Open Beta 14 OnePlus 3T.
FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.
Didgeridoohan said:
FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.
Click to expand...
Click to collapse
Which is this 87.3 version?
And which magisk module u need to uninstall before?
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
Which is this 87.3 version?
Click to expand...
Click to collapse
The one in the Magisk repo (Downloads section in the Magisk Manager).
And which magisk module u need to uninstall before?
Click to expand...
Click to collapse
Xposed... (@topjohnwu changed the module id with version 87.2, if you don't uninstall any previous version you'll get conflicts)
Hi
Since PIE roms for santoni are available, some people, including me, can't root their santoni.
I don't know why.
Flash looks ok in recovery, but after reboot, Magisk Manager says that Magisk isn't installed.
I tried every solution found in forums here, but everytime, same result : "magisk isn't installed"...
So sad !
Could you guys (and girls) centralize here your solutions, step by step, from flash the rom to root it...
It would be so nice for helping desperate people...
I also tried SuperSU and am having the same problem. I've tried Magisk 17.1, 17.2 and the Canary build along with the newest SuperSU and the result is always the same. Flashes fine but Magisk Manager and SuperSU apps can't find root.
The weird thing is that Enpass always tells me that my device is rooted and that it's a security risk even though Magisk Manager can't find root.
Also, I'm positive Magisk is patching the ramdisk. The Uninstaller always finds a Magisk-patched image. I'm assuming something has to be happening during boot that's cancelling root.
Two things I don't understand :
- why some people, with same configuration, don't have root problem ?
- why, with same recovery, same flash method, root works with nougat/oreo rom, and doesn't work with pie...?
Just like that : do you think problem could come from the sd card ?
I'm using à 128 gb samsung sd-card. Maybe I should format it before trying again root ?
I'm not sure it's the problem, since I can flash all roms, but I could try...
Or flash Magisk from internal storage ?
Really desperate...
Hi,
I´m in the same situation like you.
Yesterday I made a new experience of that without solution:
- Backuped all
- Uninstalled magisk at twrp
- Installed santoni_twrp_silent 27_treble (recommended from dev to install havoc)
- Rebooted
- Formated data with factory reset
- Wiped vendor, cache, data... (everything)
- Installed havoc (version 2018-09-08)
- Rebooted
- Installed magisk at twrp
- Rebooted
Same issue like before...
If I try to install magisk on magisk manager I get the following log:
Copying image to cache
Device platform: arm64-v8a
Existing zip found
Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu)
Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory!
Installation failed
It seems magisk can´t install correct in cause of failing permissions to create new directories. But why?
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Click to expand...
Click to collapse
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
newbie_or_not_newbie said:
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
Click to expand...
Click to collapse
I don´t think so. Well, if you like you can try, but I think it´s an internal problem, not an external
So,
I tried another wipe of internal storage, made a format data with recovery. Then I flashed another pie rom, then magisk. And after reboot : tada !! still not working...
try with version 16.6 of magisk
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Lemmy554 said:
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Click to expand...
Click to collapse
I just tried this and it didn't work for me either. I tried multiple clean flashes, flashed MIUI then back to Pie and flashing things in different orders last night and nothing worked. I'm tired of messing with it. I don't know how to get logs without root. I've come to the conclusion that for now I either have Pie or root. Not both. lol
Me too. I stop trying every day a solution.
For the moment, no root for pie roms, so I keep staying with oreo roms (nice dot OS...) I can root.
Hope next builds of pie roms will accept to be rooted on our santoni...
You can try this:
1 Flash Magisk v 17.2, Reinica in fast boot mode, turn it off and turn the phone on again
2 Install Magiskmanager V6 APK, do not open and restart in recovery
3 Flash Magisk v 16.6 and ready...
It worked for me... important, do not update magisk... The root is lost again
Best regards
Thanks for your reply.
Did you have root trouble before trying your solution ?
yes, when installing Pie only. In oreo no, I tried it in havoc and pixys
Try OrangeFox recovery for flashing magisk.
hyperkin said:
Try OrangeFox recovery for flashing magisk.
Click to expand...
Click to collapse
That's what I've been using. Also tried TWRP. Neither worked for me. The flash always looks good with no errors but when I boot the ROM Magisk says it's not installed.
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
Sounds like a plan! I'll try it out when I get home from work and let you know how it goes!
Trying asap.
Thanks
neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
This post right here works, thank you so much
Is the new magisk 22.1 stable like the other, 20.4 and the 22.0?
vishy_kaira said:
Is the new magisk 22.1 stable like the other, 20.4 and the 22.0?
Click to expand...
Click to collapse
all the magisk release are stable unless you change your default update channel via magisk app setting
Galaxy M51, Android 11
Magisk 23 installed, done !
AP File patched, done !
AP File flashed, done !
Magisk apk installed, done !
SU works, done !
All looks good, but why not FullRoot, only "HalfRoot", because u havent any acess many Folder like /system ?
Root is for me, if u have FULLacces, not Half
Today I have installed Built-In BusyBox module by zgfg to overwrite meefik's busybox binaries in /system/xbin which I couldn't remove due Resource or Device Busy error.
Then I found out that busybox is one of the ways to detect modified android so I want to remove it but module unfortunately doesn't come with uninstaller so I am stuck with busybox in my /system/xbin directory with no way to remove. All I found on Magisk's docs is to replace files or directories not remove them but 2018's version said that removal is possible, just that it is hassle or something.
Can anyone help?
Additional info: I don't have any Custom Recovery and don't tell me to get one.
Click to expand...
Click to collapse
NOTE! To help others with same problem I am planning to compile answer as Magisk Module so please open PR in this repo:
Click to expand...
Click to collapse
GitHub - UltraStudioLTD/BuiltIn-BusyBox-Uninstaller: Uninstall busybox
Uninstall busybox. Contribute to UltraStudioLTD/BuiltIn-BusyBox-Uninstaller development by creating an account on GitHub.
github.com
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
lemon567 said:
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't have TWRP and I can't install any Custom Recovery.
Please don't tell me to follow that or this instructions to install them, I followed everything and still no luck.
What you could do is enter safmode of your phone (Google how to enter safe mode for your phone) and remove the files manually or use the BusyBox cleaner zip and flash it in magisk manager and if you're lucky it will remove it
Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
Bot to compile, package and release busybox for all android architectures - Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
github.com
Unfortunately safe mode in my phone is kinda broken, I think. Cause every 3rd party app was not only disabled but also disappeared like magic. Also I don't trust unknown ZIPs so I haven't tried that link.
**I solved problem by disabling every Magisk module I had, rebooting and after that it succeed in deletion with no problem**