yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] DiamondJohn:
I am running Win7 Pro using VirtualBox (haven't tried VMWare). Originally I had about 8GB RAM (And it worked, even compiling ROMs), but I recently upgraded to 24GB RAM:D

He is correct, and I understand the simplification of the statement to avoid a lengthy post, but simply to express my experience, by "up to date" it may not be as vigorous as some may expect. My PC is an i7-2700K which was first released in 2011; ie 7 years old. Although I have upgraded the RAM to 24GB, have multiple drives (some of which RAIDed and some simply USB) and have OC'd the CPU from 3.5GHz to 4.4GHz (3 simple settings in BIOS), this PC is pretty fast, and compiles an Oreo ROM within a VirtualBox env in just over 1hr. ie its pretty fast.;)

Apart from Linux (numerous distributions), I have also run Win2012, XP (32b and 64b), Win7 (32b and 64b) and a few other virtual OS/environments on this Win7 Pro box. I actually had some problems when running Win7 full screen, I accidentally though I was doing stuff on my base/real PC! ie it wasn't too laggy.
[Android Software/Hacking General [Developers Only]] ashyx:
Just to put things in perspective. I run UBUNTU on VMWARE workstation 12 on 64bit Windows 8 Pro. 2.6 mhz dual core cpu, 4gb ram, 8TB HD.

It's pretty ancient, but I don't use it for compiling ROMS.

Main thing is for the CPU to support Virtualization technology. Also more ram the better.
[Android Software/Hacking General [Developers Only]] Pretinaverse:
[MENTION=4544860]osm0sis[/MENTION]

I tried to install busybox v1.28.3 using magisk. After the install, busybox appear in the modules section but needs a reboot to be activated. I reboot the phone and when i checked in modules again i couldn't find it. I tried some program that use busybox but it says busybox isn't installed. So, i downloaded the zip from here and flashed it with twrp. I started the phone after that, but busybox was still not installed.

I have a Moto G 5 (xt1670) with stock rom and android 7.0.

And this is the log from magisk:
[Android Software/Hacking General [Developers Only]] osm0sis:
Your device would appear to have bigger problems than my module not installing. In fact, no Magisk module should be able to install with that error.. the Magisk module template (which nearly all other modules use) does the exact same thing:

TMPDIR=/dev/tmp
INSTALLER=$TMPDIR/install

mkdir -p $INSTALLER

Which would fail with the same "mkdir: can't create directory '': Read-only file system"

What version of Magisk? What's the log from TWRP look like?
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah, seems like your TWRP is broken too if there's no write access to / and it can't mount magisk.img... try updating to Magisk 16.3 and seeing if Magisk Manager installs work then.

Any ideas [MENTION=4667597]Didgeridoohan[/MENTION]?
[Android Software/Hacking General [Developers Only]] Didgeridoohan:
[MENTION=5064104]Pretinaverse[/MENTION]

I don't think it's an issue with the Busybox module. Rather, I believe the important parts of info that has been provided so far are these:

Moto devices are known to have a broken f2fs implementation, causing the Magisk image to mount read-only. There are solutions tough. Here's a module that works around the issue by placing the Magisk image in /cache:

https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875

I would try that...
[Android Software/Hacking General [Developers Only]] jcmm11:
Wouldn't another option be to simply reformat everything as ext4? (Maybe not simply since you'd lose everything on the phone so would have to make sure you had full backups of everything, including user internal storage)
[Android Software/Hacking General [Developers Only]] SirDre:
Win10 has Ubuntu and other Linux OS in there Windows store. Simply download and use it within command prompt. :silly:

I am currently using Win10 pro with Ubuntu in console. :o

I think more Windows developers will appreciate this. Works great. :good:

---------- Post added at 10:34 PM ---------- Previous post was at 10:17 PM ----------

I can't find ( UPDATE-Busybox.Installer.v1.28.3-ALL-signed.zip) compiled link nowhere. :confused:

The build link seems to be broken except for GitHub sources. That's working.

Normally, I would have to wait for someone to realease your compiled version in there ROM.

Please realease the compiled version on GitHub. Thanks. :good:
[Android Software/Hacking General [Developers Only]] Pretinaverse:
[MENTION=4544860]osm0sis[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=4487388]jcmm11[/MENTION]

Thank you so much for taking the time to help me out.

So, in the end is a problem of motorola and the partition's format.

Originally i installed magisk because some games from the play store detect other programs like supersu and can't be played. With magisk i don't have that problem. Well, in the end i tried installing the normal busybox instead of the systemless. So far i didn't have any problem and games like "super mario run" works fine without detecting root, so I'm gonna keep it that way. If in the future i need to use some systemless module, i'm going to try installing magisk in the cache partition and see if it work. For now thanks a lot for the help ;)
[Android Software/Hacking General [Developers Only]] osm0sis:
Did you try... the link in the OP where it's always linked? Or look... in the OP attachments where it always is?
[Android Software/Hacking General [Developers Only]] SirDre:
On my browser it does work. :good:

I was using the XDA App to download the file. :eek:

Thanks.
[Android Software/Hacking General [Developers Only]] osm0sis:
Forum app that doesn't show forum attachments or even links correctly? Sounds useful. :p
[Android Software/Hacking General [Developers Only]] 1v9:
Hi osm0sis !

I used a nonofficial los15.1 rom for my phone and i flashed your nexus media installer by Magisk. Seems sound pack effective but bootanimation failured.

Most of the time it was lineage animation, only a few times nexus animation successed or first is lineage then boot again used nexus.

I found /system/media/bootanimation.zip exactly being replaced, it is different from /sbin/.core/mirror/system/.....

Surely when i replace the really bootanimation.zip by anything else including nexus,it works.

So I'm puzzled, is there any solution for this?
[Android Software/Hacking General [Developers Only]] jcmm11:
What version of Magisk?
[Android Software/Hacking General [Developers Only]] 1v9:
v16.4
[Android Software/Hacking General [Developers Only]] osm0sis:
Magisk changed the timing of the earliest we can replace something (post-fs to post-fs-data), so as you've seen it's not reliably able to replace the bootanim early enough on all devices now to have it work. I've asked [MENTION=4470081]topjohnwu[/MENTION] to take another look and try to make it as quick as possible after post-fs-data.

That said, it's totally device-to-device whether it'll work or not; my Galaxy Nexus has it replaced just fine and shows the Nexus bootanim, but [MENTION=4667597]Didgeridoohan[/MENTION]'s Nexus 6, not so much.
[Android Software/Hacking General [Developers Only]] oreo27:
Same on my device. It doesn't replace it early enough with post-fs-data. I've read somewhere that he'll be enabling something similar with simple_mount but I haven't seen any proper documentation on this?
[Android Software/Hacking General [Developers Only]] osm0sis:
It's already changed/enabled in the Magisk betas (1640+) and supported in my zips (last 2 releases). What you're seeing is magisk_simple mounts still not being early enough for your device, as I said, and hopefully John can make it happen even sooner with post-fs-data to resolve these kinds of inconsistencies.

https://github.com/Magisk-Modules-Repo/Nexus-Media-Installer/commits/master
[Android Software/Hacking General [Developers Only]] jcmm11:
Too slow on my Nexus 5x as well. I posted something with a log somewhere in the Magisk threads.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah, basically, if John can't make it happen any faster when post-fs-data hits, then you won't be able to replace the bootanim (or anything else that might need an early replacement like that) on some devices anymore. That said, a lot are running custom ROMs, hence wanting the stock animation back, so might as well install to /system with the -system keyword added to the zip filename and avoid all this Magisk fuss.
[Android Software/Hacking General [Developers Only]] oreo27:
Ah. Figures. Hopeful he can find a way around it. Thanks for the heads up.
[Android Software/Hacking General [Developers Only]] jcmm11:
True that. It's not like I haven't modified /system to start with. Magisk just makes some things simpler. But then I was also using bind mounts with supersu for some things.
[Android Software/Hacking General [Developers Only]] SkaboXD:
Hey osm0sis, I just want to report that newest busybox 1.28.3 doesn't install at all. 1.28.2 works fine.
[Android Software/Hacking General [Developers Only]] osm0sis:
Sorry but your report is useless without logs.
[Android Software/Hacking General [Developers Only]] SkaboXD:
ok, i will upload log in 1-2 days
[Android Software/Hacking General [Developers Only]] SkaboXD:
Here is the log
[Android Software/Hacking General [Developers Only]] osm0sis:
That's a partial log. You also still haven't told me a single thing about your device or setup. I gather from that snippet that you're using Magisk, so have you tried installing the zip from within Magisk Manager or from the Magisk Modules repo? Seems like your recovery might have some issues; I haven't changed anything in the mounting script since 1.28.1:

https://github.com/Magisk-Modules-Repo/Busybox-Installer/commits/master
[Android Software/Hacking General [Developers Only]] SkaboXD:
nvm, i solved the problem, it was problem with TWRP, tnx for response.
[Android Software/Hacking General [Developers Only]] osm0sis:
Finally found some time to revive this beauty and try out my idea for getting 000gappsintegrator working with Magisk and, except for a couple of unexpected extra tricks I had to add, it works! :cowboy::cool:

I've tested it on my Galaxy Nexus running LOS13 (Marshmallow) with Magisk, and my Nexus 5 running LOS14.1 (Nougat) with su.img SuperSU, but it should also work just fine on sbin SuperSU. Remember this is experimental, so not for the faint of heart nor lacking of nandroid, but it seems to still be working pretty flawlessly in my testing! :D

I work on these projects in my limited time off, so if you like the progress I'm making, or enjoy anything else I've done on xda, please do hit the donate link from my profile. Thanks for your support!

gappsintegrator: v11 - add Magisk support, fix free space estimate fallback:

- add support for /magisk/.core/post-fs-data.d (up to Magisk v16.2) and /sbin/.core/img/.core/post-fs-data.d (Magisk v16.3+) by altering the untouched mirror of actual system

- work around unreliable /system in PATH during a Magisk boot by adding mirror bin/xbin and testing for actual working mount and date commands before proceeding

- work around occasional lib ownership/permissions issues from some files in Magisk mirror of system being weirdly linked back to /system

- fix some cases of broken free space estimate when no zip/zipalign binaries are found

https://github.com/osm0sis/gappsintegrator/commit/1bc2789d283d113398493dfc0222052958365fa4

Download via GitHub's raw copy of the latest version, or extract it from the repo zip. :good:

zip and zipalign binaries to be unzipped and placed in /system/bin or xbin (/sbin/.core/mirror/system/bin or xbin when booted with Magisk) for full integration are available from my BasketBuild: http://basketbuild.com/devs/osm0sis/binaries

Don't forget to set the correct 755 executable permissions for the script and binaries. Have fun! ;)
[Android Software/Hacking General [Developers Only]] VincentJoshuaET:
Thanks! Will this work on a Lineage OS 15.1 installation without root access? It doesn't have busybox.
[Android Software/Hacking General [Developers Only]] osm0sis:
No no and no. First, it's untested on Oreo, (but I'd be happy to have testers), second it's an init.d/su.d/post-fs-data.d script which alters your system partition - so VERY root, and last your ROM probably has busybox (and Magisk does too for scripts), but it's generally also necessary for a proper script environment.
[Android Software/Hacking General [Developers Only]] ashyx:
Questions like this amuse me. I don't understand why anyone runs a custom OS without root? :confused:

It seems a half hearted effort after going through the whole procedure of going custom.
[Android Software/Hacking General [Developers Only]] IronTechmonkey:
With apologies for a bit of OT:

Better feature set with higher security, the likes of which a support tech might want to provide to a population of users, or a parent might want to provide to a child. In such cases I would do this for things like the left/right keyboard cursor buttons in the navbar in LOS, (IIRC derived from AOKP years ago) among many other non root dependent tweaks in custom ROMs.
[Android Software/Hacking General [Developers Only]] Surge1223:
Amen. I feel like I'm in the minority now. Most of the devs Im friends with don't root either, it's beyond me. Good lord, they're called "custom" roms for a reason.

I don't buy the security argument either, I feel like I have way less chances of fixing things if I cant be root. Imagine the outrage if Windows removed admin prompt...

I can't believe the amount of devs who don't experiment and just stay on stock and give their users security updates monthly
[Android Software/Hacking General [Developers Only]] VincentJoshuaET:
I always have issues with Magisk passing SafetyNet. Sometimes it does, most of the time it doesn't. Being rootless, I have no issues.
[Android Software/Hacking General [Developers Only]] IronTechmonkey:
Custom features and administrative access to the system may be part and parcel of the same usage scenario for you and me, but they're definitely not the same thing. Many people use custom ROMs unrooted, in fact that is the default condition for LOS which does offer features beyond stock without leaving users with an "uncertified" device that cannot install Netflix from Playstore. Also, some (understatement) developers may want their apps to work on non-rooted devices. ;)

As to security; I would not allow root level access to the inquisitive pre-teens in my family (nephew is the worst, never hand that kid your phone unless the allowed app is pinned), but I myself, just as you, would not dream of not being rooted. :)

I cant believe the amount of system admins who allow their users to do all kinds of unsafe stuff and don’t just give them security updates. :silly:

Careening back on topic, I've not checked in on this thread in a while but my goodness those are some nice toys, so I'll busy myself exploring them instead of typing more (crowd roars).
[Android Software/Hacking General [Developers Only]] osm0sis:
In b4 "osm0sis bro, busybox 1.28.4 came out DAYS ago! DAYS! I look forward to/demand your next update!" ! :silly:;):p

Point updates for your enjoyment! :D

I work on these projects in my limited time off, so if you like the progress I'm making, or enjoy anything else I've done on xda, please do hit the donate link from my profile. Thanks for your support!

UPDATE-Busybox.Installer.v1.28.4-ALL-signed.zip:

- update to latest busybox stable official source

See the related commits here: https://github.com/osm0sis/android-busybox-ndk

UPDATE-nano.Terminal.Editor.v2.9.7-signed.zip:

- update to latest nano official source
[Android Software/Hacking General [Developers Only]] davidzam:
Busybox NDK MODULE.

Hello just wanted to report that after installing via magisk manager the latest update of this module, when I reboot to complete installation, the screen went black and the device went into boot loop. I'm on Android 6.0.1 Samsung stock firmware. So I took the battery out and restart again. It went into the building system app screen, and boot normally, check manager and the installation was complete. Just to let you know guys about the behavior of the installation process, didn't went so smoothly. Thank you for the module.

Enviado desde mi SM-G550T1 mediante Tapatalk
[Android Software/Hacking General [Developers Only]] osm0sis:
Busybox installer doesn't do anything that could cause that. Probably just Magisk and Samsung being Samsung and Magisk. ;)
[Android Software/Hacking General [Developers Only]] davidzam:
Sure! everything is good. Thanks you for clarifying.
[Android Software/Hacking General [Developers Only]] Sheetzie03:
I personally would dream of it :laugh: actually, it's a must for me, honestly. While that might change in the future, as of right now, it's a must. Agree to disagree I guess :p
[Android Software/Hacking General [Developers Only]] KaMyKaSii:
Should the "adb" command work on a terminal with superuser permission, or is it really necessary to use the full path? It was the only way it worked here. Running AOSP 7.1.1 with SuperSU v2.82-SR5 in SBIN mode. Anyway, I needed your binary to install twrp on another device using an otg + usb cable connection. Thank you!
[Android Software/Hacking General [Developers Only]] jcmm11:
Termux sets it's own, unique, environment. Compare the $PATH from Termux with $PATH from a regular terminal emulator https://play.google.com/store/apps/details?id=jackpal.androidterm
[Android Software/Hacking General [Developers Only]] osm0sis:
SuperSU SBIN also alters the $PATH when in a su prompt to add the stuff in /sbin/supersu/bin and xbin, so yeah, probably need to be in a root prompt unless you're on Magisk. Also yeah, whatever tricky nonsense Termux is up to, su prompt might still remedy it.
[Android Software/Hacking General [Developers Only]] BillGoss:
The su script that comes with Termux doesn't set up the environment variables properly. Install the tsu package and then run "tsu" as the command instead of "su" and you'll find it works a lot better.
[Android Software/Hacking General [Developers Only]] KaMyKaSii:
I have confirmed that in this terminal emulator the adb command works normally.

I tested tsu in Termux but the result remains as not found
[Android Software/Hacking General [Developers Only]] BillGoss:
Did you add the ADB bin directory to your initial path?

export PATH=$PATH:/data/adb/su/bin

Hint: add that line to the .profile file in your Termux home directory.
[Android Software/Hacking General [Developers Only]] adikri:
Noob question.. But do you have any script that may zipalign /data/app, /system/app, /system/framework and /system/priv-app ?
[Android Software/Hacking General [Developers Only]] osm0sis:
Those should all already be zipaligned... That said, search the thread for zipalign, you'll find the binaries and some scripts which may help with whatever it is you're trying to do.
[Android Software/Hacking General [Developers Only]] osm0sis:
No rigmarole, just another hit for the point update junkie.

I also took some time to rewrite a much less ****ty nano build script, automating downloading the source, patching it for Android, configuring it, building and bundling it into a flashable zip (including updating the Magisk module.prop): http://xdaforums.com/showpost.php?p=66486572&postcount=671

I work on these projects in my limited time off, so if you like the progress I'm making, or enjoy anything else I've done on xda, please do hit the donate link from my profile. Thanks for your support!

UPDATE-nano.Terminal.Editor.v2.9.8-signed.zip:

- update to latest nano official source
[Android Software/Hacking General [Developers Only]] manos78:
Hi [MENTION=4544860]osm0sis[/MENTION],

To the list of "ADB & Fastboot" and "Busybox" for Android NDK, please create one for "SQLite3".

See one example at: https://xdaforums.com/apps/magisk/mod-sqlite3-v3-8-11-1-binary-t3673388

Thank you! Your modules are very good! :good:
[Android Software/Hacking General [Developers Only]] osm0sis:
Nah I'm good, and one clearly already exists so why?

Edit: Just read your post on that thread. So, you want it in the repository, and the newer template, well wait for him to respond to your question in his thread, plus also @ mention him to get his attention, you can also try to PM him.

If none of that works, then I'd suggest you look into updating the zip's module template yourself, it's extremely simple and you'll benefit more from doing it yourself. Then upload it to that thread (and the repository if you please, just remember to credit that OP when you do it).
[Android Software/Hacking General [Developers Only]] daniel_m:
[MENTION=4544860]osm0sis[/MENTION] Thank you very much for your systemless busybox!

Unfortunately I can't get it to work properly on my two Moto Z Play phones. On one, it is working, but the installation seems to break other Magisk modules. On the other, I see the busybox links in /magisk/busybox-ndk/system/xbin/, but the other module files (readme and automount) are missing, and busybox is not linked to /system/xbin/.

Right now, I am too tired to look for logs ... I didn't see anything suspicious during installation of the module. One thing that might cause trouble though it the F2FS loopback bug on Moto Z phones. Therefore I am using Magisk with the "F2FS loopback Bug Workaround" from VR25, that copies the Magisk images to /cache/ and links them to /data/...

I could imagine that this might interfere with the busybox installation script. There might also be size constrictions of the magisk image file?
[Android Software/Hacking General [Developers Only]] jcmm11:
The other problem with that module is the sqlite version. It's 3.8.11 (which I suspect was obtained from another, old, XDA thread). Current version is 3.24. I had a 3.21 version that I found somewhere but have now managed to find 3.22, 64bit ? (extracted from APK from play store)

The bottom line is it's not easy to find precompiled binaries for sqlite. The sqlite site has precompiled stuff for download, but the Android version is "A precompiled Android library containing the core SQLite together with appropriate Java bindings, ready to drop into any Android Studio project", with no command line tools. (Windows, x86 Linux, Mac all have cli available)

If I had a system I could build on I'd do it myself. I don't.
[Android Software/Hacking General [Developers Only]] osm0sis:
I have a hunch you're right, but why would it only work on one? Same device. Maybe something about your setup with the loopback fix being semi-broken on one. Maybe your cache is just full. Hard to know anything without a log. See about it when you're rested.

You could bundle your newer 3.22 binary (or give it to manos78) then and make a Magisk module for it at least. Of course it'd be better to build the latest, but many still will be happy with a recent version, I'm sure.
[Android Software/Hacking General [Developers Only]] daniel_m:
My Magisk image was screwed up, e2fsck reported "clean, 512/512 files, ...". No idea how this happened. Deleting everything and starting from scratch gave me an image file with a less restrictive limit of 4096 files ...

Sorry for causing a fuss :)
[Android Software/Hacking General [Developers Only]] Wolfcity:
......

installed your busybox on my Moto G5+ running stock android 7.0, magisk 16 and the result looks like in screenshot nr.1. Also weird is the fact that after the installation an update is available but after flashing and rebooting it still shows up in the magisk manager.

Also the busybox isn't uninstallable anymore.

Other modules install correctly.

Attached: magisk log, screenshots.

Any way to install it correctly or at least uninstall it?
[Android Software/Hacking General [Developers Only]] osm0sis:
Using path: /dev/tmp/magisk_merge/busybox-ndk/system/xbin
touch: /magisk/busybox-ndk/update: No space left on device
cp: can't create '/magisk/busybox-ndk/module.prop': No space left on device

Something was up with your magisk.img but it looks like it got fixed by the merge with magisk_merge.img on reboot, so should be installed just fine.