yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Achi Shukuteki:
Hmm.....I'll order another camera. If not then it might be the motherboard.
[Android Software/Hacking General [Developers Only]] creeve4:
I cannot find the 975experimental init.d script that is "linked above" does anyone have a copy or link?

edit: found a link, but it is dead...
[Android Software/Hacking General [Developers Only]] osm0sis:
Well, the old version is still up on my BasketBuild: https://basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/scripts/975experimental

And anything decent that still worked is still in [MENTION=4793042]pkgnex[/MENTION]'s updated versions: https://basketbuild.com/devs/osm0sis/scripts/
[Android Software/Hacking General [Developers Only]] Paschfire:
[MENTION=4544860]osm0sis[/MENTION]

Just an update on this previous issue..

Using Magisk v14.2 seem to have solved the "the response is invalid" Safety-Net status check bug, Safety-Net status check is now working properly while having the Adreno_GPU_Developer_Preview_Drivers module enabled.

All is good in Nexus land once again. ;)

Thanks! :highfive:
[Android Software/Hacking General [Developers Only]] rizki_Alkaf:
Hi everyone,

I'm on a rooted Nitrogen OS 8.0.0

I have a permission problem with obb files located on internal storage /storage/emulated/obb

Those files inside are owned by root:sdcard_rw and their permission are 660.

But i cannot delete it even as a root with a file explorer.

Using TWRP, /obb folder is not mounted. /storage folder is empty. Is there any script here that can solve my problem? Tried sdcard permission fix zip but it didn't work.

Or maybe anyone here knows how to mount /obb folder from TWRP / terminal?

Thanks
[Android Software/Hacking General [Developers Only]] osm0sis:
The actual location is /data/media/obb and the ownership is media_rw:media_rw, which are correct. Try from that location in a file explorer instead.
[Android Software/Hacking General [Developers Only]] rizki_Alkaf:
It works!!

Thank you, very very much [emoji2]
[Android Software/Hacking General [Developers Only]] Schrotty35:
Can not install Busybox with Magisk 14.2.
[Android Software/Hacking General [Developers Only]] osm0sis:
Boot the device first. Magisk's install zip doesn't make magisk.img during install anymore.
[Android Software/Hacking General [Developers Only]] Surge1223:
What applets is it missing specifically? Im wondering because adding applets to busybox kinda blows especially on aosp, where busybox is built in much the same way as was kernel inlining is done. I just recently rebuilt busybox with bionic and selinux so while it's fresh in my head I might as well add some useful binaries, I think off the top of my head checkpolicy, dispol, sefcontext, getfilecon, and setfilecon are the most useful in addition to the defaults.

I think most people have difficulty building busybox with selinux on aosp is for a few different reasons, the first being that busybox doesn't give much in the way of useful info on how to add it other than "make sure selinux is installed"

Next most selinux stuff we want to use depends on a a libselinux and libsepol minimum, and aosp doesn't contain a Android.mk for generation of the static versions (though the .bp is very useful). And finally it requires linking of the libs, along with references to the includes and its just a mess. Luckily it's not too bad if you have been building selinux and busybox for awhile.

I think I'm just going to fork osm0sis' busybox and see how it is for ndk and aosp.

I'm bored af rn so might as well.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
I've actually been trying to figure out how to build a dynamically linked busybox with the latest busybox and AOSP source with SELinux enabled to use with TWRP. If you can get this working, it would be awesome.
[Android Software/Hacking General [Developers Only]] Surge1223:
Hah ironic I was actually working on that as we speak

Along with...

osm0sis I saw your message about aapt..just built newest on ndk, requires setting the ___ANDROID_API__=21 CFLAG to use non unified headers using the newest ndk.
[Android Software/Hacking General [Developers Only]] Fif_:
That's a long list...

Spoiler content hidden.
[Android Software/Hacking General [Developers Only]] _that:
And which of those are actually useful under Android?
[Android Software/Hacking General [Developers Only]] ahrion:
You forgot wget and zip. Awk would be nice too
[Android Software/Hacking General [Developers Only]] Fif_:
You really enjoy my long lists, do you?

ar can be used to unpack .debs

arping is a network utility

bash doesn't need an introduction

blkdiscard is for blanking flash

chrt is for controlling the real-time scheduler

cksum is a CRC32 checksum utility

du is for disk usage

ether-wake is for wake-on-lan

I only went to the letter e, but f-z has plenty of useful stuff too.
[Android Software/Hacking General [Developers Only]] osm0sis:
[MENTION=4939386]Surge1223[/MENTION] Oooh, adb 1.0.39, nice work! Any chance of an updated fastboot to go with it? :)

Edit: Oh also, I tried adding -D__ANDROID_API__=21 to the CFLAGS in every .mk in my aapt repo but it still comes up with the same linking errors. :confused:
[Android Software/Hacking General [Developers Only]] exodius48:
Does you update busybox NDK for magisk? Recently refresh magisk repo and i get update, but the version still 1.26.2, i already installed it, so whats new in latest version?
[Android Software/Hacking General [Developers Only]] osm0sis:
https://github.com/Magisk-Modules-Repo/Busybox-Installer/commits/master

Installer fixes. Thread post here forthcoming; I'm waiting to hear from [MENTION=4939386]Surge1223[/MENTION] to see about adb/fastboot first. :good:

Edit: Well, it's been a few days.. I guess he's too busy for now. I'll update the installer when he updates us.
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
An updated app for editing ramdisks using your tools would be a godsend, or an osm0sisSend :p

I've used an app that was based on your work, but when rebuilding an image the resulting dding into boot partition would always cause a bootloop

Please consider this request!
[Android Software/Hacking General [Developers Only]] osm0sis:
It's a long-term plan of mine, but having never written an app, it'll be a long while yet.

In the meantime, using AIK-mobile with FX File Explorer is very nearly app-like. :)
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
Happy to hear that, but sad it's long term. Alk is app I was referring to. The last successful binaries I used were ModdingMyMind's who is now [MENTION=7662028]shm[/MENTION]
[Android Software/Hacking General [Developers Only]] osm0sis:
Not even SHM anymore, he disappeared. Too bad, he was an awesome help with getting a lot of tricky utilities to compile for Android and did a lot of excellent work. Hopefully he's doing okay.

Anyway, are you saying AIK-mobile doesn't work for your device's images? AIK-Linux with ./unpackimg.sh --sudo should work for everything.

AIK v3.0 will also be badass now that I've figured out how to get rid of mkbootfs, and will work flawlessly booted just like AK2 does in recovery. :cowboy::cool:

More info here: https://xdaforums.com/showthread.php?p=74137304
[Android Software/Hacking General [Developers Only]] KaMyKaSii:
He's probably referring to this app. Were not you aware of his existence?

https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
[Android Software/Hacking General [Developers Only]] osm0sis:
Oh I'm aware. That ass took my "AIK" name for his app to intentionally confuse my users and make them think it's official.. he never asked for permission to use any of my work, plus his garbage work was erasing sdcards for awhile. I've reported it to Google several times for improper use, but they have never taken it down. :(

Piggy mentioned binaries being an issue though, so maybe not referring to that crap. Anyway, everyone should get FX File Explorer. Best file explorer around. AIK-mobile and FX is pretty awesome.
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
Yes I was using his work, I knew his stuff was based on your work, I didn't know it was without your permission. I'm about to root a Samsung device, and will test your AIK 3.0. Where can I get it?
[Android Software/Hacking General [Developers Only]] osm0sis:
Unreleased, I'm still working on it; finding/making something equivalent for Windows to retain all ramdisk ownership/permissions is going to take some work.

Try AIK-mobile v2.9, and if that doesn't work, AIK-Linux v2.9 with ./unpackimg.sh --sudo almost definitely will. See the AIK thread for downloads.
[Android Software/Hacking General [Developers Only]] KaMyKaSii:
To tell you the truth, I first met his app before knowing that the original work is yours. But at least on the beta channel he changed the name of the app, but the update is from May and has not yet become stable, if one day become...
[Android Software/Hacking General [Developers Only]] slimcyril:
UPDATE-SUmount-signed.zip:

- add support for magisk.img and magisk_merge.img

UPDATE-unSU-signed.zip:

- add support for BINDSBIN SuperSU, Magisk and LineageOS addonsu

- add support for suhide and suhide-lite

- add support for /system/system (Pixel) layouts

[MENTION=4544860]osm0sis[/MENTION] please after flashed audio mods like Arise Sound System that includes your SdCard fix permission scripts, root access tends to be lost on Verizon S7 nougat Systemless Supersu, tried different scenarios but to no avail. However, I don't know if there's anything like addon.d backup for systemless supersu or if any of the scripts above resolve these issue?
[Android Software/Hacking General [Developers Only]] osm0sis:
I've repeatedly told them that's not what sdcard Fix Permissions is for, so they shouldn't be including it in mods.

Also it shouldn't have any affect on root because it only touches /data/media and subdirectories.
[Android Software/Hacking General [Developers Only]] slimcyril:
Thanks for the clarification.

Please is there anyway you could make an addon.d backup script for systemless root (systemless supersu) like we had it when we installed supersu in system. As you're the Android Shell Guru! :highfive:
[Android Software/Hacking General [Developers Only]] osm0sis:
I already did. FlashAfterUpdate in the OP. Put the SuperSU zip in its directory. Done.
[Android Software/Hacking General [Developers Only]] RSDamasceno:
I'm using an old Asus Zenfone 5.

I installed UPDATE-Busybox.Installer.v1.27.2-ALL-signed via recovery (without errors), but after restart busybox was not installed.
[Android Software/Hacking General [Developers Only]] osm0sis:
Read the log. It's installed to /su/xbin. Also, that Titanium error had nothing to do with busybox.

If you want busybox force-installed to /system add the word system to your install zip filename.
[Android Software/Hacking General [Developers Only]] unkash:
Hi everybody. I have a problem. Coupé hoy hemos me?

I've flashed Mu online with the lastima firmware avalaible, unlock bootloader, flashed recogerte and by recogerte, flashed magisk.zip and install magisk manager. Works fine. I got root permissions forma greneefy, es Explorer, Link2SD,.. but adaway say Phineas la nota rooteado, same for Titanium backup. Which the problem?

Core only is disable.

This is log of magisk. There are an error mount /Dev/block/loop0

beginning of main

I( 312: 312) Magisk v14.0(1400) daemon started

I( 312: 314) ** post-fs mode running

--------- beginning of system

I( 312: 468) ** post-fs-data mode running

I( 312: 468) * Mounting mirrors

I( 312: 468) mount: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system -> /dev/magisk/mirror/system

I( 312: 468) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 312: 468) bind_mount: /dev/magisk/mirror/bin

E( 312: 468) mount /dev/block/loop0->/dev/source failed with 13: Permission denied

I( 312: 529) ** late_start service mode running

I( 312: 529) * Running service.d scripts

I( 312: 529) * Running module service scripts
[Android Software/Hacking General [Developers Only]] Bludwurst:
It might be for the best if you disable autorrect ;)

Also, if this is a Magisk issue, it should go on the Magisk subforum.
[Android Software/Hacking General [Developers Only]] unkash:
Sorry

Hi everybody. I have a problem. Could you help me?

I've flashed muy phone with the last firmware avalaible, unlock bootloader, flashed recovery and by recovery, flashed magisk.zip and install magisk manager. Works fine. I got root permissions for greneefy, es Explorer, Link2SD,.. but adaway say phone is not rooted, same for Titanium backup. Which the problem?

Core only is disable.

This is log of magisk. There are an error mount /Dev/block/loop0

beginning of main

I( 312: 312) Magisk v14.0(1400) daemon started

I( 312: 314) ** post-fs mode running

--------- beginning of system

I( 312: 468) ** post-fs-data mode running

I( 312: 468) * Mounting mirrors

I( 312: 468) mount: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system -> /dev/magisk/mirror/system

I( 312: 468) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 312: 468) bind_mount: /dev/magisk/mirror/bin

E( 312: 468) mount /dev/block/loop0->/dev/source failed with 13: Permission denied

I( 312: 529) ** late_start service mode running

I( 312: 529) * Running service.d scripts

I( 312: 529) * Running module service scripts
[Android Software/Hacking General [Developers Only]] osm0sis:
Stop. This is not the Magisk support thread. Post in the Magisk forum, like people here and in the AdAway thread have told you many times already.
[Android Software/Hacking General [Developers Only]] unkash:
Ok, thx for all
[Android Software/Hacking General [Developers Only]] xdadroidabc:
Can you please look again?

I have same issue, using Supersu and flashed Busybox Installer 1.27.2 all and no busybox instlled

Attached screenshot and it showing used path - magisk-merge/busybox-ndk/

it created magisk folder in data

Also su/xbin is empty.

or

I am missing something?

Edit : This fixed by following

-Flashed Magisk

-Flashed Supersu again

-Flashed Busybox 1.27.2 again and now it correctly installed in su/bin

I wonder why this happened as I have clean installed first time.
[Android Software/Hacking General [Developers Only]] Zackptg5:
The problem is that you're trying to use 2 root solutions. Magisk has its own root (magisksu) built in and quit supporting supersu a while ago. Either use only magisk or only supersu
[Android Software/Hacking General [Developers Only]] GCalzo:
Hi!

First of all thanks because you make life easier for me that I'm not a linux expert at all! :D

Then, I have a question for you: do you have a good reason to keep the folder TWRP owned by root? I use myPhoneExplorer to keep a local copy of my phones and with it I cannot open the internal TWRP directory (because it has no option to run with SU).

So far I have simply used the info from https://xdaforums.com/moto-x/general/psa-twrp-directory-permissions-t3074377 but I decided to give a try to your script which is easier to run just into TWRP!

myPhoneExplorer is still not able to open the folder, so I gave a look and changed as follow, now MPE can open the folder!

if [ -d /data/media/0/TWRP ]; then
ui_print " ";
ui_print "Setting TWRP directory perms...";
set_perm_recursive 1023 1023 0777 0664 "/data/media/0/TWRP";
# set_perm_recursive 1023 1023 0777 0664 "/data/media/0/TWRP/BACKUPS";
# set_perm_recursive 1023 1023 0775 0664 "/data/media/0/TWRP/theme";
fi;
[Android Software/Hacking General [Developers Only]] osm0sis:
I just have it setting them to what TWRP itself does when it creates those directories. Good news is the sdcard Fix Permissions zip becomes entirely obsolete in Android Oreo due to the system now changing all sdcard files/directories to media_rw:media_rw.
[Android Software/Hacking General [Developers Only]] srqrob:
This helps those of us who like to keep a copy of our most recent backup on our PC. Good to see,
[Android Software/Hacking General [Developers Only]] GCalzo:
...but that is not the purpose of your script has detailed in the OP... :D
[Android Software/Hacking General [Developers Only]] osm0sis:
Semantics. It's if what puts them there put them there. Last I checked Android OS doesn't make TWRP directories at all. ;):rolleyes:
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
Please delete my post if it seems off-topic.

Have your modification for Magisk been implemented into Magisk's latest version: v.14.3

Just wondering, because if not, I'm about to root with magisk, and I'll want to add your work
[Android Software/Hacking General [Developers Only]] osm0sis:
That's well on topic. It should all work. Minimum template version is still 1400.
[Android Software/Hacking General [Developers Only]] bdvince:
I flashed the busybox installer from the first post (

UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip

) and cleared Cache/Dalvik Cache, and when I rebooted

ALL

of my apps were force closing by themselves (and I do mean all: Contacts, Touchwiz, Gallery, Enhanced Features, Camera, countless miscellaneous apps, etc..). In addition the phone background went all black.

I rebooted my phone once without changing anything and everything came back to normal. I searched and no one else reported this behavior, so why on earth would that have happened? I have a Samsung Galaxy S7 Edge - G935F.
[Android Software/Hacking General [Developers Only]] jcmm11:
You know you're not supposed to feed them after midnight.
[Android Software/Hacking General [Developers Only]] osm0sis:
Best guess is because you cleared Dalvik/caches pointlessly and things needed to rebuild.
[Android Software/Hacking General [Developers Only]] Tecalote:
[MENTION=4544860]osm0sis[/MENTION] I would like to install your very good Busybox as an Magisk Module during Rom installation. But it installs instead into the classic path system/xbin and after first reboot its not installed as Magisk Module.

In my updater-script I include Magisk installer first and after your Busybox installer (UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip or Busybox_for_Android_NDK-1.27.2.zip - which is the same) - but it wont be installed as module, only in system/xbin. This occurs if added in updater-script (but not if I flash your BB with TWRP after first boot).

Should I change something in my script to get it as Magisk module installed?

ui_print("Installing Magisk by topjohnwu with core modules...");

package_extract_dir("magisk", "/tmp/magisk1");

run_program("/sbin/busybox", "unzip", "/tmp/magisk1/Magisk.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk1");

run_program("/sbin/sh", "/tmp/magisk1/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk1/Magisk.zip");

delete_recursive("/tmp");

package_extract_dir("busybox", "/tmp/busybox2");

run_program("/sbin/busybox", "unzip", "/tmp/busybox2/Busybox_for_Android_NDK-1.27.2.zip", "META-INF/com/google/android/*", "-d", "/tmp/busybox2");

run_program("/sbin/sh", "/tmp/busybox2/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/busybox2/Busybox_for_Android_NDK-1.27.2.zip");

delete_recursive("/tmp");

package_extract_dir("selinux", "/tmp/selinux3");

run_program("/sbin/busybox", "unzip", "/tmp/selinux3/magisk-permissive-script_v1.1.zip", "META-INF/com/google/android/*", "-d", "/tmp/selinux3");

run_program("/sbin/sh", "/tmp/selinux3/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/selinux3/magisk-permissive-script_v1.1.zip");

delete_recursive("/tmp");

package_extract_dir("huawei", "/tmp/huawei4");

run_program("/sbin/busybox", "unzip", "/tmp/huawei4/Huawei-Prop-Fix-v1.2.zip", "META-INF/com/google/android/*", "-d", "/tmp/huawei4");

run_program("/sbin/sh", "/tmp/huawei4/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/huawei4/Huawei-Prop-Fix-v1.2.zip");

delete_recursive("/tmp");

Magisk, Selinux Permissive and Huawei Prop Fix are installed as Magisk Modules after first booting the Rom...

Thanks for your great work and support :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Are you sure you're using my latest busybox zip? It fixes clean Magisk install support where the magisk.img isn't created by the Magisk installer anymore: https://github.com/Magisk-Modules-R...mmit/443a5bff14460f0ab8e5a6ec820b4e2c54230a1b

Here's a test: If you switch the order so the other modules are installed first, does my busybox zip then install correctly?

The only other possibility is when it looks for /data/magisk.img and will try to create magisk.img if it doesn't exist and /data/magisk does, that if for some reason the creation failed it would fall back to a system install because there is still no magisk.img. That's entirely possible if the ROM lacks (or lacks a working) make_ext4fs binary.
[Android Software/Hacking General [Developers Only]] Tecalote:
Thanks for your answer! I'll try tomorrow after work and tell you the result
[Android Software/Hacking General [Developers Only]] osm0sis:
Make sure you download the latest busybox zip from the OP and try it as-is first, you might have been using an old one.
[Android Software/Hacking General [Developers Only]] davidk21770:
Sorry if this had been asked - but my search didn't show it...

I am trying your busy box via the magisk install script.

My question is how are updates managed?

Will I get a notice of an update in magisk module downloads?

Do I have to check here? And if here, where here (1st page - the update busybox installer?) and how is the systemless / magisk compatible update accomplished?
[Android Software/Hacking General [Developers Only]] osm0sis:
Updates are any time there's a critical update to the installer that can't wait, if I make a new patch to the busybox source to fix something for Android, and of course with every official version bump to busybox that's tagged as stable (x.yz.0 releases are tagged as unstable).

If you're using Magisk then any update will show up in Magisk Manager under Downloads. If you're using SuperSU or force install to system using the installer filename keyword then you can subscribe to this thread, since I make changelog posts when I update things, and the latest versions of everything are attached or linked from the OPs of this thread.
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
I had problems on my Samsung as well, installing busybox from op caused boot loop
[Android Software/Hacking General [Developers Only]] osm0sis:
You are having a much different issue than the post you quoted.

A log would be cool. Also any details wouldn't hurt. It doesn't really make any sense if it was a systemless install, since busybox only goes into xbin, so it'll never come before a /system/bin utility in the path. Perhaps it installed to system on your device, tripping some kind of verity or Knox stuff? Again, logs, from recovery install that triggered the issue and from the bootloop itself would help a lot.
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
You're right, it is different.

It was the problem though, happened twice, both times it stood on splash screen, wasn't actually looping, I should've grabbed logs. n00bish of me, I just read a hilarious article here on xda about noobs/n00bs

As I recall, it installed into /sbin

I'm not familiar with Knox, this is my first Samsung device, you may be right
[Android Software/Hacking General [Developers Only]] osm0sis:
/sbin isn't a possible install location option.. It would require unpacking the boot.img. Did you have Magisk or SuperSU installed? If SuperSU then in su.img mode or SBINBIND?
[Android Software/Hacking General [Developers Only]] PiggyFlooper:
Maybe it was /su/bin??

Yes, SuperSU installed

I just noticed the 96MB su.img on /data moments before viewing your post, what is SBINBIND?