Database Users

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.

busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...

Magiks on Moto Z play

I managed to have magisk and magiskhide working sucessfully, with some manual tricks and workarounds
There is a bug in f2fs that prevents /data/magisk.img to me mounted writable, so the tweek is just moving that file to the /cache partition, which is ext4 and creating a symlink to the original file.
So the steps for a working magisk is.
- Unlock your bootloader
- Install Twrp
- Flash magisk without mounting data partition and boot once.
- Reboot to recovery and open terminal (advanced)
- move magisk.img to /cache partition, changing name ( example: mv /data/magisk.img /cache/magisk_2.img)
- Create a symlink between_files ( ln -s /cache/magisk_2.img /data/magisk.img)
Would be nice if anybody can try to reproduce.

Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.

lpchaim said:
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
Click to expand...
Click to collapse
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.

jblancoperez said:
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
Click to expand...
Click to collapse
Right. I think I'll try this out today and see how things turn out. As for SafetyNet, I though the unlocked bootloader alone was enough reason for it not to work, is this only for some models?
Update: So, @jblancoperez, I've reproduced your steps and Magisk Manager tells me it's installed but root isn't activated and it doesn't let me do anything else as a result.

Things to have a look,
Please confirm in the terminal if /magisk is mounted.
Go back to TWRP terminal and also confirm if the symlink is OK.
Nice to get the output from /cache/magisk.log
It took me a while to have everything right, doing it on TWRP is not the easiest places to move things around.

So, an update. Your method just wouldn't work for me at all, no matter how many times I tried. What worked was following the first part only, as in unmounting data and then flashing Magisk afterwards. I've tried Xposed and Viper4Android; they worked, but both did have to be flashed through twrp as opposed to Magisk Manager, which would throw an error. Not sure if that's on them or on this particular method. I should mention though that SafetyNet wouldn't pass even before xposed and with the hiding settings, not sure why.

You may want to try the kernel where the f2fs bug is fixed, which may be the cause when Magisk hide is not working which would cause Safetynet to fail.

Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?

tag68 said:
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
Click to expand...
Click to collapse
I got bootloop when I install magiks 11.0.

Do you have a logfile of that action in /cache or /cache/recovery which we could show in the Magisk thread?

I was able to upgrade the 10.2 installation.
Will try a new clean installation on the weekend with the f2fs fixed kernel.
I think I got why my procedure is not working for other people. Please try to copy the image instead of moving with the flags preserving de selinux attributes.

jblancoperez said:
Please try to copy the image instead of moving with the flags preserving de selinux attributes.
Click to expand...
Click to collapse
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.

tag68 said:
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
Click to expand...
Click to collapse
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.

jblancoperez said:
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
Click to expand...
Click to collapse
cp -a tries to copy attributes including timestamps. But it only succeeds if you are currently running as root.

Install magisk on Phoenix Os (x86_64)

Hi all,
I'm trying to install magisk on Phoenix Os. Without a recovery I tried to install it via the magisk manager but I can't see the boot partition to patch via the app... So I tried to patch the ramdisk manually but ./magiskboot and . /magisk (from x64) seems not to work... Don't know how to patch it... Does anyone have any idea how to do it?
Thanks.
Ps
No custom recovery are installable (and it is not useful because if Magisk manager can't detect boot partition also the zip can't); Phoenix Os is for common PC, in fact I have in triple boot with windows and ubuntu

Bump
P.S. custom recovery for Phoenix OS running off USB?

Bump

This would be very nice, but I am equally useless at making this sort of thing work.

I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install scripts and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...

[Solved] Lenovo tab 4 (tb-8504x) mount /system as rw = not responding device

I have a problem with rooted tab4 tablet.
When i remount /system to rw, device hangs/freezes (stop responding).
Tested with magisk and SuperSU.
Android 7.1.1
EDIT:
I figured out.
It's necessary to flash through TWRP, a magisk module from dywersant's post.
When module is enabled, it's possible to mount /system as rw, but device will not pass SafetyNet test.
When module is disabled, /system is mounted as ro, any change on this partition will freeze device, but it will pass SafetyNet test.
I use this module only when I Have to.

tgm28 said:
I have a problem with rooted tab4 tablet.
When i remount /system to rw, device hangs/freezes (stop responding).
Tested with magisk and SuperSU.
Android 7.1.1
Click to expand...
Click to collapse
How have got it rooted?

Uqbar said:
How have got it rooted?
Click to expand...
Click to collapse
Just follow instructions in this thread TWRP and ROOT for Tab 4 8/10 (Plus)
Flash magisk, flash magisk module named magisk-remount (from HERE ) - this module is for /system remount (when it is enabled Magisk do not pass SafetyNet test; when disabled it pass)
Probably that's all

tgm28 said:
Just follow instructions in this thread TWRP and ROOT for Tab 4 8/10 (Plus)
Flash magisk, flash magisk module named magisk-remount (from HERE ) - this module is for /system remount (when it is enabled Magisk do not pass SafetyNet test; when disabled it pass)
Probably that's all
Click to expand...
Click to collapse
Thanks. I haven't found any custom ROM (I am looking for a debloated one). Have you?

Uqbar said:
Thanks. I haven't found any custom ROM (I am looking for a debloated one). Have you?
Click to expand...
Click to collapse
No. I use Stock rom with magisk and Twrp.

How bloated is it?

Uqbar said:
How bloated is it?
Click to expand...
Click to collapse
Not heavily like samsung's devices. It's almost clean.

Did you ever find any other ways other than magisk to mount /system as rw without a system freeze?

Does not work.
This method doesn't work, the system is freeze anyway.

arminass said:
This method doesn't work, the system is freeze anyway.
Click to expand...
Click to collapse
What's news? Is there any other way?
I use Magisk 20.3 or 20.4 on my two tablets.
One tablet is under stock Android 8.1.0
and another is under LineAgeOS16 - Android 9 Pie.
Both, give su for applications and ADB, but don't have system root for system folder.

@krchat - did you try installing the zip in this post to see if you could write /system?

drizzle123 said:
@krchat - did you try installing the zip in this post to see if you could write /system?
Click to expand...
Click to collapse
yes, no luck.

krchat said:
yes, no luck.
Click to expand...
Click to collapse
It's a complete pain. I heard its problems with Magisk? Anyhow I installed magisk 19.3 - booted then installed the remount zip, rebooted again - checked the system was RW, then installed magisk 20.4. All seems well for me

arminass said:
Does not work.
This method doesn't work, the system is freeze anyway.
Click to expand...
Click to collapse
Hello, have you found a way to write to the system partition? My los17.1 write system partition will freeze. I'm going crazy!

asphalt73 said:
Hello, have you found a way to write to the system partition? My los17.1 write system partition will freeze. I'm going crazy!
Click to expand...
Click to collapse
Nope.

[SOLVED]9t - stuck in the bootloop with bad magisk module

[Android10 + MIUI 11]
1. Trying to add new module (extra power menu) and... kaboom - phone stuck at boot.
1a. I'm flashing orginal boot.img
2. No working^ TWRP for me - bootloop and/or data folder mounted in the read only mode or listed as complete mess. No chance for removing bad module.
3. ADB method for removing module - not working under Android 10 :/
4. The situation: no magisk, no root, no GPay
The question: is there anyway to prepare magisk boot image w/o modules loading?

https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242

garett76 said:
[Android10 + MIUI 11]
1. Trying to add new module (extra power menu) and... kaboom - phone stuck at boot.
1a. I'm flashing orginal boot.img
2. No working^ TWRP for me - bootloop and/or data folder mounted in the read only mode or listed as complete mess. No chance for removing bad module.
3. ADB method for removing module - not working under Android 10 :/
4. The situation: no magisk, no root, no GPay
The question: is there anyway to prepare magisk boot image w/o modules loading?
Click to expand...
Click to collapse
Use TWRP, its File Manager.
Navigate to /data/adb/modules
Each installed module has its folder - recognize by name which folder corresponds to your errant module.
Put an empty file disable (for disabling) or remove (for removing) into that folder
Reboot but with the patched boot - on that next booting Magisk will find the file and disable or remove the given module
OtangeFox or certain unofficial TWRPs , or modules for TWRP also help to disable or remove Magidk modules by the same mechanism (leaving the file there for Magisk to find on next boot) - this way you can do it manually, not depending on additional tools and knowing how and why it actually works

zgfg said:
Use TWRP, its File Manager.
Navigate to /data/adb/modules
(cut)
Click to expand...
Click to collapse
Thank you!
Solved.
In the /data/adb/ was some folders with unreadable names. But only one included only 3 files, which is the number of my installed magisk modules. After removing them with TWRP file manager and sending patched magisk img phone booted succesfuly. Thank you!

garett76 said:
Thank you!
Solved.
In the /data/adb/ was some folders with unreadable names. But only one included only 3 files, which is the number of my installed magisk modules. After removing them with TWRP file manager and sending patched magisk img phone booted succesfuly. Thank you!
Click to expand...
Click to collapse
Ok, glad you solved.
But if you have stock MIUI 11, then official TWRP (3.4.0)
https://dl.twrp.me/davinci/
or 3.4.0.2 by brigudav (I prefer since it supports backup/restore for practically all partitions):
https://forum.xda-developers.com/showpost.php?p=83090455&postcount=1
should properly see all files and folders on Data and Internal memory.
Don't know for EEA weekly builds or if you flashed DFE (IMO, then specially shouldn't be a problem with unreadable names)