yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] shoey63:
Dev Host is just a spam/malware site these days.
[Android Software/Hacking General [Developers Only]] osm0sis:
Huh, yeah, seems you're right. The links all point correctly but then you get an "empty response" error from their download server.

Greedy assholes..
[Android Software/Hacking General [Developers Only]] VeJard:
Could you upload a link of your su uninstaller zip please
[Android Software/Hacking General [Developers Only]] osm0sis:
All my zips are either attached to or linked from the OPs and for those attached the blurb names are kept updated as links to the current download.

They're all easy to find. Take your pick.
[Android Software/Hacking General [Developers Only]] VeJard:
I don't know where to find it. Ive gone through your posts and idk where to find it

---------- Post added at 08:02 AM ---------- Previous post was at 07:59 AM ----------

Nvm found it
[Android Software/Hacking General [Developers Only]] pkgnex:
-

They should still be at the links in this post:

https://xdaforums.com/showpost.php?p=62171319&postcount=372
[Android Software/Hacking General [Developers Only]] mrrocketdog:
2different browsers tried each with "file not found" results. thanks anyways :)
[Android Software/Hacking General [Developers Only]] pkgnex:
I think dropbox changed something with public folders a couple months ago, so maybe they are no longer accessible. Sorry about that.

[MENTION=4544860]osm0sis[/MENTION], what's the best way to get you the files so you can re-post them somewhere? You can PM me if needed or I can e-mail them to you if you want... just not not sure I still have your address.
[Android Software/Hacking General [Developers Only]] osm0sis:
Decided I should show a little love to my other projects again.. ;)

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: v10.5 - fix a couple remounting issues, add new debugging output mode:

- hide some expected but obnoxious stderr from sdcard writable test

- fix remounting issues with Chrome workaround on Lollipop and fallback method on Marshmallow for APKs with no libraries

- introduce new debugging output mode, enabled by changing debugging=0 to debugging=1; outputs some crucial information to /data/local/tmp/debug-gappsint.log to help diagnose integration issues

- move precise freespace check out of Marshmallow fallback library check logic so that one always occurs

- a few clean-ups for readability

https://github.com/osm0sis/gappsintegrator/commit/13758d08f65b5067fb136ad4b6b281c10caf0d7f

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

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

- update to latest nano official source

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

- add uninstall or Uninstall to the filename to instead remove a busybox installation from the target location

- add system to the filename to force a system installation/uninstallation

- fix /su and /magisk unmount post-install

- patched remaining issues so all Android and Android x64 builds now have identical configuration (i.e. enabled IPv6 utils, route, time, hush, ipcrm, ipcs, syslogd, logread)

- fix reboot and poweroff to use the AOSP toolbox/reboot utility code like recovery busybox, but add workaround to set the sys.powerctl prop value (since that's what the system does anyway) directly via command

- fix DNS resolver issue properly by hacking around dietlibc's resolver __system_property_get to get the prop value via command (thanks [MENTION=4470081]topjohnwu[/MENTION] for the help debugging)

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

Those busybox workarounds to read/write prop values result in another couple of firsts for a static busybox (of any I've come across, anyway), since most have poweroff/reboot enabled but they don't actually do anything, and some have followed my lead from my previous patch for the resolver by hardcoding a default fallback nameserver but mine's the first to actually pull in the correct net.dns* nameserver from the system. :cowboy:

Per request, I have rehosted [MENTION=4793042]pkgnex[/MENTION]'s nicely updated (for Lollipop/Marshmallow) "Franco Dev Team" tweak init.d scripts on my BasketBuild for posterity. And lastly, the AIK Build Farm, AnyKernel2 and GN Synapse Injector also saw updates in the last couple weeks! :p
[Android Software/Hacking General [Developers Only]] Zackptg5:
Using the filename for passing options (especially the uninstall one) is a great idea (can't believe I didn't think of it). Far better than having the user create files on /sdcard with specific file names or something like that. Fantastic work as always :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Thanks! Yeah, I like it because then you can take UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip and make it UPDATE-Busybox.Installer.v1.26.2-ALL-system.zip or UPDATE-Busybox.Uninstaller-signed.zip, or UPDATE-Busybox.Uninstaller-system.zip, or use whatever naming conventions you like. :)
[Android Software/Hacking General [Developers Only]] addas4:
Dear [MENTION=4544860]osm0sis[/MENTION],

First, thank you for your amazing work! You are such a unique and talented person for creating all these flashable zips/scripts!

Sadly, I have an issue with your systemless Magisk BusyBox NDK Module, whenever I install it on my Huawei P8 (GRA-UL00) running LineAge OS v13, it optimizes apps (strangely not all the apps) (aka Preparing apps X of X) on every boot/restart, which really takes a lot of time!

Your BusyBox is the only way for me to pass SafetyNet because it is required for Safetynet FIX by [MENTION=4476591]Deic[/MENTION] to work.

The logcat shows that dex2oat failed to create oat file for some of the optimizing app because permission denied.

If you need anything more for debugging just tell me.

Thank you very much in advance!

Regards,

addas
[Android Software/Hacking General [Developers Only]] osm0sis:
Can you give me the recovery log from the install of my latest busybox installer, and if possible the contents of /system/xbin on your device with my busybox disabled as a Magisk module (ie. I want to know the original contents that come with your ROM).
[Android Software/Hacking General [Developers Only]] addas4:
Here you go! :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Well the install appears to have worked correctly, putting it all in /magisk/busybox-ndk/system/xbin, so my only guess is that one of the utilities from /system/xbin being replaced is somehow important to dex2oat on your ROM:

ls
powertop
ps
unzip
wget

With my busybox installed as a Magisk module does simply disabling the module then restore your normal boot sequence?

P.S. Completely unrelated to you, but I feel compelled to say something here; I am completely stunned that I've been tagged as an "Inactive Recognized Developer"... I was not informed beforehand of anything (and still haven't been), and etiquette aside, I'm more active in my project development than I think I've ever been, and anyone who follows or has even glanced at my threads would know that... sigh... :rolleyes::confused:
[Android Software/Hacking General [Developers Only]] the_scotsman:
Don't worry mate, it appears to be a system glitch, as it's happened to others too. We're looking into what happened. It'll be rectified soon :good:

EDIT: Fixed :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Thank you sir! :)

I'm still missing my Recognized Contributor status however. :D
[Android Software/Hacking General [Developers Only]] the_scotsman:
Woops, sorted now :D
[Android Software/Hacking General [Developers Only]] osm0sis:
Ah excellent! Thanks again for the rapid response. :) :highfive:
[Android Software/Hacking General [Developers Only]] addas4:
When I disable your Magisk Module the issue still occur, strangely I uninstalled your Magisk BusyBox and install system [MENTION=1335872]Stericson[/MENTION] BusyBox and the issue still occur, looks like it is a ROM issue, I will try deleting the xbin files that you mentioned and I will update you. Thank you in advance and congratulation on getting back your Recognized Developer/Contributor! :)
[Android Software/Hacking General [Developers Only]] osm0sis:
:p
[Android Software/Hacking General [Developers Only]] DEVILOPS 007:
Oh god. Not again:eek:
[Android Software/Hacking General [Developers Only]] addas4:
FINALLY I FIGURED IT OUT! THANK YOU [MENTION=4544860]osm0sis[/MENTION] !!!! :)

Looks like there was multiple BusyBoxes installed in my system which lead to dex2oat conflict

The BusyBoxes were:

Partial system BusyBox installed on /system/xbin (I removed it manually)

Magisk v12 BusyBox (Which got removed when I updated to the latest Magisk v13.1)

SafetyNet FIX Module BusyBox (Which looks like it has its own BusyBox when I updated to v2 Beta 4)

Your Magisk Module NDK BusyBox (Which sadly I uninstalled it cause it will make a conflict with SafetyNet Module built-in BusyBox)

Finally I can pass SafetyNet with root and Xposed (Although I need to disable (soft reboot) system Xposed manually using Root Switch to pass SafetyNet as there is currently no way to pass it with Xposed enabled other than suhide and systemless Xposed 86.2 which needs a pre-November ROM)
[Android Software/Hacking General [Developers Only]] néonaloj:
Hi,

First, thanks for the great job of an ACTIVE Recognized Dev!!

Second, I'm sorry to ask, I read a few pages and tried a search but didn't find the answer... How do you use the "ADBsync sdcard Backup "?? Just flashing it? And how do you retsore?

Thanks very much!
[Android Software/Hacking General [Developers Only]] osm0sis:
This time they sent a message, but the message says a change wouldn't occur for 10 days. So [MENTION=278202]the_scotsman[/MENTION] [MENTION=6842057]The Flash[/MENTION] [MENTION=1566190]efrant[/MENTION] something is still very broken in your system, and whoever decided I should be on this list definitely didn't look very closely or at all.
[Android Software/Hacking General [Developers Only]] Whiskey103:
Sorry for the trouble, you was victim of the system.

Please accept my apologies ;)

I do blame the Matrix though [emoji14]
[Android Software/Hacking General [Developers Only]] osm0sis:
Looks like you've been affected as well! :eek:
[Android Software/Hacking General [Developers Only]] Whiskey103:
Yap, I suffer from the same virus lol.

No worries, we found a cure ;)
[Android Software/Hacking General [Developers Only]] osm0sis:
It's a Windows batch script. You'd run it from your desktop with your device attached and booted to recovery. Restore is a simple adb push (then probably flashing my sdcard Fix Permissions zip). If you read the blurb for it in the OP and follow any links therein you should have it all well explained.

Crazy! Guess we'll see if it happens again in 10 days. :silly:
[Android Software/Hacking General [Developers Only]] cipri10:
Hi,i installed the adb zip on Mediacom tablet with android 4.1.2 but when tap adb on terminal it says "illegal instruction"
[Android Software/Hacking General [Developers Only]] osm0sis:
Too low an Android version. adb should already be included in a KitKat ROM, it wasn't removed from AOSP until Lollipop.
[Android Software/Hacking General [Developers Only]] osm0sis:
Too low an Android version and/or you're device is x86 or MIPS without the compatibility layer to run ARM binaries. That said, my zip shouldn't even be necessary since KitKat ROMs already have adb; it wasn't removed from AOSP until Marshmallow.
[Android Software/Hacking General [Developers Only]] m0han:
haven't checked all the links, but maybe mentioning the 'booted to recovery' part in the blurb for it in the op would be a good thing. [emoji106]
[Android Software/Hacking General [Developers Only]] osm0sis:
It's adb, it'll work either way.
[Android Software/Hacking General [Developers Only]] m0han:
i found so. [emoji106]
[Android Software/Hacking General [Developers Only]] digitman xxx:
[MENTION=4544860]osm0sis[/MENTION], Thanks for all great and awesome work, just need your help to solve Unroot pre-rooted rom issue.

i try to Unroot my Preroted RR rom 6.0.1 as i have no alternative rom to my device yet. in order to get Magisk(Systemless) with your unSU script https://xdaforums.com/showpost.php?p=63615067

then try to extract boot.img from Rom zip and reflash it. it seems to success to unroot and already flash Magisk and yup got Magisk Manager on App drawer also can give apps root access by magisk. but Magisk itself and rom setting force closed everytime try open them So do u have an idea about why this happened or if i miss something here.?

using Latest Magisk 13.2

RR 6.0.1 rom

SM-G7102

Edit: it's only apps preloaded in rom that got root access and working fine eg.(kernel aditure) but for those i setup got force closed immediately..! what does it mean..!??
[Android Software/Hacking General [Developers Only]] fhLan:
can I use your busybox with the latest magisk? do i need to redownload it?
[Android Software/Hacking General [Developers Only]] osm0sis:
Still probably better in recovery since you'll likely need root access to grab some directories, like the root owned TWRP one.

Maybe the ROM is poorly coded and relies on the pre-rooted stuff? Otherwise, no idea.

Yes. And probably yes, I made a new release not that's long ago with a bunch of better patches.
[Android Software/Hacking General [Developers Only]] Paschfire:
There's also a newer Magisk Manager app available, v5.0.6 . It may not solve your FC issues but maybe worth giving it a try.

Here's the release post discussing the changes/fixes within v5.0.6 Magisk Manager. https://xdaforums.com/showpost.php?p=73029750&postcount=16157

It is available for DL within OP section or recent comments/posts(yesterday I believe) of the Magisk v13.2 Official Thread.

You can also grab a copy of v5.0.6 Magisk Manager at apkmirror.com .
[Android Software/Hacking General [Developers Only]] digitman xxx:
Thanks bro for reply. maybe not clarified in my post as iam already using latest Magisk 13.2 beside latest Magisk Manager 5.0.6
[Android Software/Hacking General [Developers Only]] m0han:
i'm using your release of 3rd july. an app i use - mybackup pro - requires newer busybox, which your release delivers. but, i have a few issues trying to get it working alongside

magisk

. could you check this post and see if you can help me in any way? thanks a lot.

edit: [MENTION=5994172]digitman xxx[/MENTION], could you try the app i have linked to here? thanks.
[Android Software/Hacking General [Developers Only]] ante0:
Works fine for me with My Backup Pro, osm0sis busybox and Magisk v13.2.

If you need to use Magisk v12, make sure you don't have busybox ticked in Magisk's settings as that would conflict with busybox here.

[MENTION=4544860]osm0sis[/MENTION] thanks for these.

Busybox is fine and not detected :D

AIK was a pain to install because my /data is encrypted.

I had to install it manually using terminal.
[Android Software/Hacking General [Developers Only]] m0han:
i used the installer zip by [MENTION=4544860]osm0sis[/MENTION]. busybox does not get detected as can be seen from the screenshot (last under set 1) in this post. how did you install it manually using terminal?.
[Android Software/Hacking General [Developers Only]] ante0:
Busybox installed fine using original script. It's Android image kitchen that didn't. Because it installs to /data but my /data partition is encrypted in TWRP. So I had to write a script that installs when the phone is booted.

Could you try with Magisk v13.2?
[Android Software/Hacking General [Developers Only]] m0han:
yeah, let me see. thanks.
[Android Software/Hacking General [Developers Only]] osm0sis:
Heads up, I just brought the BootUnlocker app back from the dead!

https://xdaforums.com/galaxy-nexus/...r-nexus-devices-version-t1731993/post73055753

I added support for OnePlus 2 and OnePlus X, with more devices to come, and am now accepting Pull Requests and collaborators for further device/design updates.

:cowboy::cool::D
[Android Software/Hacking General [Developers Only]] digitman xxx:
Sorry, but i am not understand what can My Backup Pro do in my case, i am already use Titanium Backup Pro

i know My Backup Pro could work w/wo root access but what's the benefits over that.
[Android Software/Hacking General [Developers Only]] m0han:
omg, i just made a request. disregard. [emoji106]
[Android Software/Hacking General [Developers Only]] Stallio:
Hi, I flashed this zip it flashed successfully but there is no icon of this ie like busybox , is this how it is? How to verify if installed (Though everything went fine while flashing with TWRP)

Thank you.
[Android Software/Hacking General [Developers Only]] robcore:
Busybox itself is a command line tool, the icons you see are for installer apps. To see whether it works, simply type busybox into a terminal or by connecting adb and typing adb shell busybox. If you see info about the program, it's installed.
[Android Software/Hacking General [Developers Only]] jcmm11:
That's correct. No icon. There's only a binary with a bunch of symlinks, no apk, no app, so no icon.

To verify just open a terminal emulator and type in the command "busybox". Look at the first line of output to see what version of busybox you're running. It should reference osm0sis and the version number (v1.26.2-osm0sis to be exact).

Or you can go in with a rooted file explorer and check the directories (exact directory to check depends on rooting method, if any. For systemless SuperSU it's /su/xbin).

Note that some custom ROMs come with a pre-installed version of busybox, usually in /system/xbin. Osm0sis' version will precede the pre-installed version in the system PATH so will take precedence in execution.
[Android Software/Hacking General [Developers Only]] k8563:
After flashing busybox installer zip, in order to verify busybox.

Therefore, I open a terminal emulator and type in the command "busybox".

But it shows busybox not found!

What's problem with my device:confused:

Phone info: op 3t with oos 4.1.6, magisk v13.3 and twrp 3.1.1-0

Thanks all!

Update: Thanks your advice [MENTION=6493997]Sytis[/MENTION]! I have tried to type the other command in the terminal emulator. But, it still didn't work.
[Android Software/Hacking General [Developers Only]] Sytis:
You're not supposed to write "adb shell busybox" on your phones terminal. First type "su" in order to gain root access and then just "busybox". ADB can only be used from within an external computer.
[Android Software/Hacking General [Developers Only]] jcmm11:
Just a note - you don't need su to access busybox. Some of the commands may need it to function correctly but the binary itself is accessible without root.
[Android Software/Hacking General [Developers Only]] osm0sis:
Try `echo $PATH; su -c echo $PATH;`

It sounds like on your root setup /su/xbin isn't in the path.

Edit: Wait, what? Magisk? You still have SuperSU remnants on your device, so my installer detected /su as the correct target. Clean up your device.
[Android Software/Hacking General [Developers Only]] Stallio:
Thank you.
[Android Software/Hacking General [Developers Only]] osm0sis:
A new stable busybox (1.27.1) is out, so I've gotten started on the bring-up today. The existing NDK patches all still work, so that's a plus, but some new ones might be necessary for the added/changed features (or those features may need to be disabled if there are still code errors I can't resolve). So far, there are just some missing header errors. Stay tuned. :good:

https://github.com/osm0sis/android-busybox-ndk
[Android Software/Hacking General [Developers Only]] k8563:
Edit2: THANKS [MENTION=4544860]osm0sis[/MENTION]! After your advice, I install the busybox successfully!

Thanks [MENTION=4544860]osm0sis[/MENTION]

I also tried the command that you mentioned, and the result shows in pic.

What should I do to clean up my device? Delete something?:confused:

I hope data won't lose: (

Edit: whether can I flash "unSU Script zip" ? https://xdaforums.com/showpost.php?p=63615067
[Android Software/Hacking General [Developers Only]] osm0sis:
Yes, flash unSU, then flash your ROM's boot.img (from the ROM zip or Factory Image zip), then re-root by flashing the latest Magisk and things should be properly set up with no SuperSU leftovers. Shouldn't be any data loss.

:good:;)
[Android Software/Hacking General [Developers Only]] Setialpha:
[MENTION=4544860]osm0sis[/MENTION] There's a bug in the nano wrapper script: the line-wrapping is completely broken when the used terminal has less than 16 lines. You can fix this by adding the command

resize

to the wrapper script between the command

clear

and the actual nano invocation.
[Android Software/Hacking General [Developers Only]] osm0sis:
Nice find! I'll add it to the next version. :highfive:

Edit: [MENTION=4187311]Setialpha[/MENTION], hmm adding this to the recovery nano wrapper seems to break nano when running through the TWRP Terminal, any ideas? I'm interested in any insight [MENTION=4878287]_that[/MENTION] could provide as well since TWRP's Terminal was his baby. :)
[Android Software/Hacking General [Developers Only]] tdhite:
crond incorrectly expects: /sbin/sh

Great tools! However, the crond applet is incorrectly expecting sh to exist at: /sbin/sh -- see this logcat excerpt:

07-22 18:26:51.162 3513 3513 I crond : crond (busybox 1.26.2-osm0sis) started, log level 8
07-22 18:27:00.171 4459 3513 E crond : can't execute '/sbin/sh' for user root
07-22 18:27:00.171 3513 3513 I crond : USER root pid 4459 cmd /vendor/skyhigh/cron-scripts/test.sh
07-22 18:28:00.174 12240 3513 E crond : can't execute '/sbin/sh' for user root
07-22 18:28:00.174 3513 3513 I crond : USER root pid 12240 cmd /vendor/skyhigh/cron-scripts/test.sh
07-22 18:29:00.174 13287 3513 E crond : can't execute '/sbin/sh' for user root
07-22 18:29:00.175 3513 3513 I crond : USER root pid 13287 cmd /vendor/skyhigh/cron-scripts/test.sh

It's a very simple fix (patch) for your build, but takes a sledgehammer approach to fix in a ROM or kernel mod (have to unpack the boot image and set a link from /sbin/sh to /system/bin/sh).

Any chance of an update for that? Otherwise I'll just fork and build myself, but it is a general issue for anyone using crond.

Thanks for consideration.
[Android Software/Hacking General [Developers Only]] osm0sis:
Ah wasn't aware. This is all that's in the configs related to cron.d:

CONFIG_CROND=y
CONFIG_FEATURE_CROND_D=y
CONFIG_FEATURE_CROND_CALL_SENDMAIL=y
CONFIG_FEATURE_CROND_DIR="/var/spool/cron"

Anything there we need to change? The sbin stuff must be in the actual busybox code. I'll look into it. Does run-parts work? You'd think it'd have a similar problem.

Edit: [MENTION=4988866]tdhite[/MENTION], I don't see anywhere that sbin is getting hardcoded in miscutil/crond.c; since you seem to know, how about you send me a pull request with the patch on my ndk busybox repo and I'll include it in my next build?
[Android Software/Hacking General [Developers Only]] DEVILOPS 007:
[MENTION=1143630]osmosis[/MENTION] Hi there, could you please tell me what the use of your adb binary is please. I understand that it was in lollipop and removed from marshmallow and nougat but what is the use of the ADB binary on the phone? I'm not sure what use I would have with it so I'd appreciate a little understanding on the mod. Thanks.
[Android Software/Hacking General [Developers Only]] guest4711:
In developer options you can tell the phone to listen for adb connections on network. Using adb you could start a debugging session from terminal/shell to your phone. So you could have root access to your filesystems without any su-binary nor need for computer.
[Android Software/Hacking General [Developers Only]] DEVILOPS 007:
So basically, it allows you to modify your phone's root directory from your phone through ADB without needing root or a pc? That sounds very interesting, I'll have to learn some adb commands to make use of it. Thanks