FORUMS
Remove All Ads from XDA

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

13,665 posts
Thanks Meter: 30,150
 
By osm0sis, Recognized Developer / Recognized Contributor on 18th April 2013, 12:37 AM
Post Reply Email Thread
11th July 2019, 04:11 AM |#2421  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,150
 
Donate to Me
More
Quote:
Originally Posted by Trundler

Hi, sorry to bother everyone. I am trying to install the "Busybox for Android NDK" module through Magisk, but after downloading and installing, and even after a reboot, the module does not appear as installed. There are no errors in the installer script that I can see. I'm using a OnePlus 3 and I need Busybox to get systemize to work properly according to a guide I'm following.

Thanks in advance!

With no install log how do you expect any help?
The Following User Says Thank You to osm0sis For This Useful Post: [ View ]
 
 
11th July 2019, 10:03 AM |#2422  
amg314's Avatar
Senior Member
Flag Kharkov
Thanks Meter: 136
 
More
Quote:
Originally Posted by Trundler

Hi, sorry to bother everyone. I am trying to install the "Busybox for Android NDK" module through Magisk, but after downloading and installing, and even after a reboot, the module does not appear as installed.

Run terminal command

which busybox

You will see something like (in my case)

/system/xbin/busybox

If no answer, busybox is not installed.
11th July 2019, 10:33 PM |#2423  
ogisha's Avatar
Senior Member
Thanks Meter: 291
 
More
Hi @osm0sis,

I am using your busybox, especially the Magisk version, which I consider excellent, but I have one problem on one my old tablet.

It is x86 tablet with Android 5.0, SuperSU rooted, without bootloader like TWRP, so I cannot install your busybox.

I used to use YDS's busybox which had .bin script I run from shell after gaining root access to install busybox. But YDS does not develop his busybox anymore and I am stuck with 1.29.1 version.

I would like to switch to yours busybox.

Could you please make .bin version of your busybox installer and busybox cleaner? It would help me a lot.

Thank you very much.
11th July 2019, 11:54 PM |#2424  
Recognized Contributor
Thanks Meter: 3,148
 
More
Quote:
Originally Posted by ogisha

Hi @osm0sis,

I am using your busybox, especially the Magisk version, which I consider excellent, but I have one problem on one my old tablet.

It is x86 tablet with Android 5.0, SuperSU rooted, without bootloader like TWRP, so I cannot install your busybox.

I used to use YDS's busybox which had .bin script I run from shell after gaining root access to install busybox. But YDS does not develop his busybox anymore and I am stuck with 1.29.1 version.

I would like to switch to yours busybox.

Could you please make .bin version of your busybox installer and busybox cleaner? It would help me a lot.

Thank you very much.

Try this. Get a copy of flashfire from the play store. Development stopped at the beginning of 2018 or so, but it should work for your purposes.

One catch - there's a time bomb built into the app so in order to get it to work you'll have to set the system date on your tablet to sometime before March 2018.

If you decide you want to keep the app just for the old device you can buy the pro version, which will disable the time bomb.
The Following 3 Users Say Thank You to jcmm11 For This Useful Post: [ View ] Gift jcmm11 Ad-Free
12th July 2019, 01:33 AM |#2425  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,150
 
Donate to Me
More
Quote:
Originally Posted by ogisha

Hi @osm0sis,

I am using your busybox, especially the Magisk version, which I consider excellent, but I have one problem on one my old tablet.

It is x86 tablet with Android 5.0, SuperSU rooted, without bootloader like TWRP, so I cannot install your busybox.

I used to use YDS's busybox which had .bin script I run from shell after gaining root access to install busybox. But YDS does not develop his busybox anymore and I am stuck with 1.29.1 version.

I would like to switch to yours busybox.

Could you please make .bin version of your busybox installer and busybox cleaner? It would help me a lot.

Thank you very much.

Busybox is also just a binary after all, so you could download the x86 build from my Magisk module GitHub repo to your device then use your SuperSU su root shell to

`cp -f /sdcard/Download/busybox-x86 /system/xbin/busybox`

then

`chmod 755 /system/xbin/busybox`

and

`busybox --install -s /system/xbin`

Boom, done.
The Following 7 Users Say Thank You to osm0sis For This Useful Post: [ View ]
12th July 2019, 05:08 AM |#2426  
Recognized Contributor
Thanks Meter: 3,148
 
More
Quote:
Originally Posted by osm0sis

Busybox is also just a binary after all, so you could download the x86 build from my Magisk module GitHub repo to your device then use your SuperSU su root shell to

`cp -f /sdcard/Download/busybox-x86 /system/xbin/busybox`

then

`chmod 755 /system/xbin/busybox`

and

`busybox --install -s /system/xbin`

Boom, done.

I didn't know about the --install option! Is that relatively new, or did I just never notice it?
Also, looking at --help, it appears that both -s and dir are optional. If dir is missing I assume it'll install in the current directory. What's the -s do? Symlinks? (If that's what it is what's it do without the -s)?
12th July 2019, 03:49 PM |#2427  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,150
 
Donate to Me
More
Quote:
Originally Posted by jcmm11

I didn't know about the --install option! Is that relatively new, or did I just never notice it?
Also, looking at --help, it appears that both -s and dir are optional. If dir is missing I assume it'll install in the current directory. What's the -s do? Symlinks? (If that's what it is what's it do without the -s)?

Install has been there for ages, I just don't use it in my installer because we need to filter out applets depending on the location.

Probably hard links, much like ln vs. ln -s.
The Following User Says Thank You to osm0sis For This Useful Post: [ View ]
12th July 2019, 05:05 PM |#2428  
Recognized Contributor
Thanks Meter: 3,148
 
More
Quote:
Originally Posted by osm0sis

Install has been there for ages, I just don't use it in my installer because we need to filter out applets depending on the location.

Probably hard links, much like ln vs. ln -s.

Yes it's hard links. And not including dir does not install in the current directory. It tries to install in bin/sbin according to the listing you get with --list-full (fortunately bin isn't writable and sbin refreshes on boot 😅 )
The Following User Says Thank You to jcmm11 For This Useful Post: [ View ] Gift jcmm11 Ad-Free
12th July 2019, 08:23 PM |#2429  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by osm0sis

With no install log how do you expect any help?

My apologies. Meant to include it in my original reply but I just forgot.

Code:
- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.30.1.zip
Archive:  /data/user/0/com.WZ1m1tRyuNME5sfT/cache/install.zip
  inflating: install.sh
  inflating: module.prop
 
mount: can't read '/etc/fstab': No such file or directory
Busybox Installer Script
by osm0sis @ xda-developers
 
Mounting...
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
 
Extracting files...
Archive:  /data/user/0/com.WZ1m1tRyuNME5sfT/cache/install.zip
   creating: META-INF/
   creating: META-INF/com/
   creating: META-INF/com/google/
   creating: META-INF/com/google/android/
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
  inflating: README.md
  inflating: busybox-arm
  inflating: busybox-arm64
  inflating: busybox-mips
  inflating: busybox-mips64
  inflating: busybox-x86
  inflating: busybox-x86_64
  inflating: install.sh
  inflating: module.prop
 
Installing...
Using architecture: arm64
umount: can't unmount /dev/tmp/su: No such file or directory
Using path: /dev/tmp/su/xbin
 
Cleaning...
 
Creating symlinks...
 
Unmounting...
umount: can't unmount /system: Device or resource busy
umount: can't unmount /data: Device or resource busy
umount: can't unmount /cache: Device or resource busy
 
Done!
I'm assuming this is some kind of difference in Android filesystems between Android versions but I don't really know enough to fix it myself. FYI this is Android 8.0.0.
12th July 2019, 09:02 PM |#2430  
osm0sis's Avatar
OP Recognized Developer / Recognized Contributor
Flag Halifax
Thanks Meter: 30,150
 
Donate to Me
More
Quote:
Originally Posted by Trundler

My apologies. Meant to include it in my original reply but I just forgot.

Code:
- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.30.1.zip
Archive:  /data/user/0/com.WZ1m1tRyuNME5sfT/cache/install.zip
  inflating: install.sh
  inflating: module.prop
 
mount: can't read '/etc/fstab': No such file or directory
Busybox Installer Script
by osm0sis @ xda-developers
 
Mounting...
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
 
Extracting files...
Archive:  /data/user/0/com.WZ1m1tRyuNME5sfT/cache/install.zip
   creating: META-INF/
   creating: META-INF/com/
   creating: META-INF/com/google/
   creating: META-INF/com/google/android/
  inflating: META-INF/com/google/android/update-binary
  inflating: META-INF/com/google/android/updater-script
  inflating: README.md
  inflating: busybox-arm
  inflating: busybox-arm64
  inflating: busybox-mips
  inflating: busybox-mips64
  inflating: busybox-x86
  inflating: busybox-x86_64
  inflating: install.sh
  inflating: module.prop
 
Installing...
Using architecture: arm64
umount: can't unmount /dev/tmp/su: No such file or directory
Using path: /dev/tmp/su/xbin
 
Cleaning...
 
Creating symlinks...
 
Unmounting...
umount: can't unmount /system: Device or resource busy
umount: can't unmount /data: Device or resource busy
umount: can't unmount /cache: Device or resource busy
 
Done!
I'm assuming this is some kind of difference in Android filesystems between Android versions but I don't really know enough to fix it myself. FYI this is Android 8.0.0.

Nope, you just didn't properly clean your device when you switched from SuperSU to Magisk. Delete su.img from /data and /cache and it should be fine to flash after.
The Following 2 Users Say Thank You to osm0sis For This Useful Post: [ View ]
14th July 2019, 10:07 PM |#2431  
ogisha's Avatar
Senior Member
Thanks Meter: 291
 
More
Quote:
Originally Posted by jcmm11

Try this. Get a copy of flashfire from the play store. Development stopped at the beginning of 2018 or so, but it should work for your purposes.

One catch - there's a time bomb built into the app so in order to get it to work you'll have to set the system date on your tablet to sometime before March 2018.

If you decide you want to keep the app just for the old device you can buy the pro version, which will disable the time bomb.

I tried FlashFire before and it did not work.
Thank you.

---------- Post added at 10:07 PM ---------- Previous post was at 10:02 PM ----------

Quote:
Originally Posted by osm0sis

Busybox is also just a binary after all, so you could download the x86 build from my Magisk module GitHub repo to your device then use your SuperSU su root shell to

`cp -f /sdcard/Download/busybox-x86 /system/xbin/busybox`

then

`chmod 755 /system/xbin/busybox`

and

`busybox --install -s /system/xbin`

Boom, done.

Nice catch.
I guess the last command will create all necessary links, but will it remove the old ones and remove any leftovers?
Thank you very much.
Post Reply Subscribe to Thread

Tags
automation, batch, flashable zip, script, tool

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes