• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

iooxda

Senior Member
Dec 1, 2019
64
33
I tried installing this module today on zippo on LineageOS 18.1, it copies the zip to temp, extracts files successfully but it hangs on "Installing..." and never recovers. If I reboot it shows that that busybox-ndk by " " under Installed however /data/adb/modules/busybox-ndk/system/xbin is empty

I have installed this module before on other phones and I have several other modules installed on this phone successfully already. Any ideas? Has anyone else seen this?
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
I tried installing this module today on zippo on LineageOS 18.1, it copies the zip to temp, extracts files successfully but it hangs on "Installing..." and never recovers. If I reboot it shows that that busybox-ndk by " " under Installed however /data/adb/modules/busybox-ndk/system/xbin is empty

I have installed this module before on other phones and I have several other modules installed on this phone successfully already. Any ideas? Has anyone else seen this?
Logs or nobody can help you.
 

iooxda

Senior Member
Dec 1, 2019
64
33
Logs or nobody can help you.
I have attached the log here : https://pastebin.ubuntu.com/p/zcryPMPZZM/

There isn't much to look at but I tried it again and I got the same results. It starts to install, hangs on Installing... then nothing happens. I waited for 1 full how this time. I rebooted and after rebooting I see:

Installed
busybox-nkd
by

and nothing else. This is for Version 1.33.1

I did have another strange issue, after I rebooted I had a very strange screen flicker that I have never seen before. It went away after another reboot, not sure if it is related or not but I haven't seen it since.

Edit:
I tried it a 3rd time, same result, this time I saw something different, after a reboot I saw the same:

Installed
busybox-nkd
by

same empty folder undre magisk modules however now I see in Magisk busybox is listed under updates.

I click the update button and... same result. I end up hanging on Installing... and nothing installed.
 
Last edited:
  • Like
Reactions: ipdev

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
I have attached the log here : https://pastebin.ubuntu.com/p/zcryPMPZZM/

There isn't much to look at but I tried it again and I got the same results. It starts to install, hangs on Installing... then nothing happens. I waited for 1 full how this time. I rebooted and after rebooting I see:

Installed
busybox-nkd
by

and nothing else. This is for Version 1.33.1

I did have another strange issue, after I rebooted I had a very strange screen flicker that I have never seen before. It went away after another reboot, not sure if it is related or not but I haven't seen it since.

Edit:
I tried it a 3rd time, same result, this time I saw something different, after a reboot I saw the same:

Installed
busybox-nkd
by

same empty folder undre magisk modules however now I see in Magisk busybox is listed under updates.

I click the update button and... same result. I end up hanging on Installing... and nothing installed.
What Magisk are you installing this with? It looks like it's copying and installing it twice at the same time judging by the log entries at the top. Sounds like app bugs to me.
 
Last edited:
  • Like
Reactions: mrrocketdog

iooxda

Senior Member
Dec 1, 2019
64
33
What Magisk are you installing this with? It looks like it's copying and installing it twice at the same time judging by the log entries at the top. Sounds like app bugs to me.
I am using Magisk 23.0 (23000) from here:

When you say app bugs do you mean a Magisk bug or a busybox for Android NDK bug? Any ideas on further actions I can take to troubleshoot?

I only saw the double copying one time, all the other times I tried to install once and it hangs at Installing... then nothing.
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
I am using Magisk 23.0 (23000) from here:

When you say app bugs do you mean a Magisk bug or a busybox for Android NDK bug? Any ideas on further actions I can take to troubleshoot?

I only saw the double copying one time, all the other times I tried to install once and it hangs at Installing... then nothing.
Magisk is the app. Busybox is only a module. Try with latest Canary maybe? I'm on latest and I've had no trouble installing any of my modules on any of my devices. Without more log there's no way to figure it out honestly. What's your device and ROM setup? Other conflicting modules? Try from TWRP recovery or from an app like FKM? FKM might show an empty onscreen log for Magisk modules but there'll be an sdcard log that shows everything.
 
Last edited:
  • Like
Reactions: ipdev

iooxda

Senior Member
Dec 1, 2019
64
33
Where do the apps come from that are included in you release? I am trying to write scripts using some of the GNU coreutils apps and none of them are working in busybox-ndk. For example:
shred su -c /system/xbin/shred -n1 --verbose /dev/block/mmcblk0.

In busybox-ndk this doesn't work. If I run the same command in Debian on PC or Termux on the same device I get a successful execution.

When I do:

shred --help or shred --version I can see this is the tool written by Colin Plumb, version 8.30. If I do a /system/xbin/shred -- help most of the argument flags are missing. It shows the busybox version rather than the app version and it doesn't work. Was this app rewritten or is it a different app all together?

Same thing with mke2fs, several key flags are missing (-t) to specify the filesytem type.
 
Last edited:

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
Where do the apps come from that are included in you release? I am trying to write scripts using some of the GNU coreutils apps and none of them are working in busybox-ndk. For example:
shred su -c /system/xbin/shred -n1 --verbose /dev/block/mmcblk0.

In busybox-ndk this doesn't work. If I run the same command in Debian on PC or Termux on the same device I get a successful execution.

When I do:

shred --help or shred --version I can see this is the tool written by Colin Plumb, version 8.30. If I do a /system/xbin/shred -- help most of the argument flags are missing. It shows the busybox version rather than the app version and it doesn't work. Was this app rewritten or is it a different app all together?

Same thing with mke2fs, several key flags are missing (-t) to specify the filesytem type.
Oh so you figured out how to install it finally but didn't mention what worked or what the problem was? Kinda weird..

Anyway, busybox applets probably shouldn't be referred to as apps, since that's confusing. Also, I didn't invent or develop busybox, so if you have a problem with their conformity to POSIX or GNU or whatever then you can go file a bug report with them at https://bugs.busybox.net
 
Last edited:

iooxda

Senior Member
Dec 1, 2019
64
33
Oh so you figured out how to install it finally but didn't mention what worked or what the problem was? Kinda weird..

Anyway, busybox applets probably shouldn't be referred to as apps, since that's confusing. Also, I didn't invent or develop busybox, so if you have a problem with their conformity to POSIX or GNU or whatever then you can go file a bug report with them at https://bugs.busybox.net
You may have made an incorrect assumption. I have tried again a few times and unfortunately, I did not figure out how to install it which is the reason why I didn't mention what worked or what the problem is.

I had your module running on an older device. I still cannot install on the new device which I originally reported. Other users in a telegram group have reported no issues installing modules with Magisk 23 but none of them were using busybox-ndk.

I'm not sure the busybox applets are buggy they are just different than expected and appear to be missing argument flags, but you are right this is a question for busybox.net

Thanks for the link, I installed the busybox and ran the tools directly from busybox.net, the output does match your output as mentioned.
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
You may have made an incorrect assumption. I have tried again a few times and unfortunately, I did not figure out how to install it which is the reason why I didn't mention what worked or what the problem is.

I had your module running on an older device. I still cannot install on the new device which I originally reported. Other users in a telegram group have reported no issues installing modules with Magisk 23 but none of them were using busybox-ndk.

I'm not sure the busybox applets are buggy they are just different than expected and appear to be missing argument flags, but you are right this is a question for busybox.net

Thanks for the link, I installed the busybox and ran the tools directly from busybox.net, the output does match your output as mentioned.
I've got my busybox module installed on my Galaxy Nexus and my OnePlus 9 Pro, all fine. So again, not sure what the problem is with your specific device, that you still haven't even told us what it is.. I asked you multiple questions and told you multiple things to try and you outright ignored it, so if you aren't going to try to help figure this out then we're done here.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,533
5,267
Sydney
Where do the apps come from that are included in you release? I am trying to write scripts using some of the GNU coreutils apps and none of them are working in busybox-ndk. For example:
shred su -c /system/xbin/shred -n1 --verbose /dev/block/mmcblk0.

In busybox-ndk this doesn't work. If I run the same command in Debian on PC or Termux on the same device I get a successful execution.

When I do:

shred --help or shred --version I can see this is the tool written by Colin Plumb, version 8.30. If I do a /system/xbin/shred -- help most of the argument flags are missing. It shows the busybox version rather than the app version and it doesn't work. Was this app rewritten or is it a different app all together?

Same thing with mke2fs, several key flags are missing (-t) to specify the filesytem type.
Busybox is NOT Linux or Unix. What works on a fully fledge system is different to the cut down world of Busybox. These applets are heavily cut down, and some are almost just shells/place-holders. The real test I personally use of any busybox implementation, is to try a different busybox implementation. If it does not work there either, then as @osm0sis directed you, the busybox maintainers are the oines to speak to. If it does work, @osm0sis can only help if you help him by following his requests.

Additionally, to remove all doubt you are running busybox and not the Toybox implementation on your device (or the relics of some other previous install), i would explicitly prefix all busybox commands with the explicit path & the busybox binary, for my own comfort.
/system/bin/busybox echo "Hello World";
 
Last edited:
  • Like
Reactions: ipdev and osm0sis

ipdev

Recognized Contributor
Feb 14, 2016
1,494
1
1,849
Google Nexus 10
Nexus 7 (2013)
You may have made an incorrect assumption. I have tried again a few times and unfortunately, I did not figure out how to install it which is the reason why I didn't mention what worked or what the problem is.

I had your module running on an older device. I still cannot install on the new device which I originally reported. Other users in a telegram group have reported no issues installing modules with Magisk 23 but none of them were using busybox-ndk.

I'm not sure the busybox applets are buggy they are just different than expected and appear to be missing argument flags, but you are right this is a question for busybox.net

Thanks for the link, I installed the busybox and ran the tools directly from busybox.net, the output does match your output as mentioned.
Use Magisk debug (canary) and grab the install and magisk debug log.
Run an adb logcat at the same time.

One of the logs should show what is failing on the install. ;)

Where do the apps come from that are included in you release? I am trying to write scripts using some of the GNU coreutils apps and none of them are working in busybox-ndk. For example:
shred su -c /system/xbin/shred -n1 --verbose /dev/block/mmcblk0.

In busybox-ndk this doesn't work. If I run the same command in Debian on PC or Termux on the same device I get a successful execution.

When I do:

shred --help or shred --version I can see this is the tool written by Colin Plumb, version 8.30. If I do a /system/xbin/shred -- help most of the argument flags are missing. It shows the busybox version rather than the app version and it doesn't work. Was this app rewritten or is it a different app all together?

Same thing with mke2fs, several key flags are missing (-t) to specify the filesytem type.
You noted using Termux, that is a heavy linux shell port for Android.
It even includes curl
Curl is not included in toolbox, toybox or busybox.
If i remember correctly, Termux only uses it own installed components.
Can be increased/updated by installing additional Termux packages.

Termux is a great terminal for Android but, not the one to test script commands in. ;)

Best to test shell commands using a basic terminal app or use adb shell.
adb can have slightly elevated permissions, best to do final test as regular user.

If you can not find a different way doing what you want to do..

Check the license for Termux and it's binaries.
or see if you can find a different binary that you can use.

If you can, barrow the shred binary and include it in your project.
Remember to give credit where credit is due.
No Kanging!

Then call the shred binary included in your project.

Cheers. :cowboy:
 
  • Like
Reactions: thomasnsr

ipdev

Recognized Contributor
Feb 14, 2016
1,494
1
1,849
Google Nexus 10
Nexus 7 (2013)
I've got my busybox module installed on my Galaxy Nexus and my OnePlus 9 Pro, all fine. So again, not sure what the problem is with your specific device, that you still haven't even told us what it is.. I asked you multiple questions and told you multiple things to try and you outright ignored it, so if you aren't going to try to help figure this out then we're done here.
Might be time to update your installer script. 🙃
# Output device information since I do not have a crystal ball.

---

More honest question..
Is it possible to use the rename feature for magisk modules?
-debugging.zip


Cheers. :cowboy:
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
Got an update release and a minor addition today for you all! :)

00-Recovery.SLAM.Script.zip or "Recovery Simple Legacy Auto-Mount" is for devices that have been updated to SAR, but there are older zips that break because they rely on the mounts occuring a certain way, especially during a ROM OTA. Recovery SLAM mounts them more as the zips would expect, allowing them to proceed. Most useful for premounting /system before a legacy zip in FlashAfterUpdate, which is why I've prefixed the filename with a number so a user can rename it to come before the troublesome zip in your FlashAfterUpdate directory. I currently use it on my Nexus 7 2013 for example, where the old Adreno Beta zip wouldn't flash to system from FlashAfterUpdate until /system was mounted first using this script. It'll live here in this post and I'll link it from the OP. (y)

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 consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thanks for your support!

999-flashafterupdate.sh:
- always use stderr to hide zip ui_print output to avoid legacy update-binary segfaults

UPDATE-Busybox.Installer.v1.33.1-ALL-signed.zip:
- update to latest busybox stable official source

UPDATE-FlashIt.Installer.v3.8-signed.zip:
- update busybox binary (1.33.1) with the latest patches and fixes from my repo
- add vendor_boot.img auto-detect support to scripts and recovery zip

UPDATE-nano.Terminal.Editor.v5.8-signed.zip:
- update to latest nano official source

UPDATE-Nexus.Media.Installer-signed.zip:
- fix addon.d script for ROMs with product/media

UPDATE-ZipSigner.Installer.v3.0-signed.zip:
- add check to ensure running as root
- automatically generate output filename if none supplied

The Payload-Dumper-Go Magisk Module has been updated to the latest build and some wrapper edge-cases fixed. AnyKernel3 also got a big update for simple vendor_boot support. TWRP_A_B_Retention_Script-Magisk(1).zip got some cosmetic fixes as well. Download TWRP A/B Retention Script again from the repo in the Magisk app to obtain the new version. 🤘

Edit: Just uploaded some updated N5X/6P BLOD Workaround AK3 zips to their respective threads as well. ;)
 

Attachments

  • 00-Recovery.SLAM.Script.zip
    1.7 KB · Views: 35
Last edited:

Achsel

Member
Jan 17, 2007
48
25
Hello osmOsis,

I have successfully installed LineageOS 18.1 (Android 11), Magisk 23.0, Busybox Installer 1.33.1 and ADB & Fastboot Installer 1.0.41 (newest version) on a Samsung Galaxy S4 and Tab4 (both with 32Bit ARM architecture). Android 11 has implemented debugging via WLAN. The "adb pair" command is required for the first connection. But I get the "Unknown command pair" error. In the "UPDATE-adb.Installer.v1.0.41.-signed.zip" I could find a "adb.bin" for ARM (959 KB, which is installed) and another "adb.bin" (2,47 MB, probably not for 32Bit ARM). Is there also a version of the "adb.bin" for 32Bit ARM devices that contains the "pair" command?

Thanks in advance!
Axel
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
I have successfully installed LineageOS 18.1 (Android 11), Magisk 23.0, Busybox Installer 1.33.1 and ADB & Fastboot Installer 1.0.41 (newest version) on a Samsung Galaxy S4 and Tab4 (both with 32Bit ARM architecture). Android 11 has implemented debugging via WLAN. The "adb pair" command is required for the first connection. But I get the "Unknown command pair" error. In the "UPDATE-adb.Installer.v1.0.41.-signed.zip" I could find a "adb.bin" for ARM (959 KB, which is installed) and another "adb.bin" (2,47 MB, probably not for 32Bit ARM). Is there also a version of the "adb.bin" for 32Bit ARM devices that contains the "pair" command?
Both binaries sets are 32bit still I think, but the legacy ones are for older armeabi instruction devices where the newer don't work due to segfaults. There's so much tech debt to try to get it working on the older devices that Surge rightly decided it wasn't worth it. If your device is in that category then unfortunately there's not much to be done: old device is old. 😕
 

Achsel

Member
Jan 17, 2007
48
25
Thanks a lot for the response. For test purposes I once dubbed the smaller adb.bin (armeabi) with the larger one. However, as expected, the "Unknown command pair" error remains. I hoped, I can use the LABD.apk for debugging via WLAN directly on the S4 or Tab4. So I have to use debugging via USB.
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,729
33,257
Halifax
GT-i9250
Nexus 7 (2013)
Thanks a lot for the response. For test purposes I once dubbed the smaller adb.bin (armeabi) with the larger one. However, as expected, the "Unknown command pair" error remains. I hoped, I can use the LABD.apk for debugging via WLAN directly on the S4 or Tab4. So I have to use debugging via USB.
Last I heard they just use our binaries, though they didn't request permission or inform us.. 🙄 but maybe that's changed, good luck! 🙂
 
  • Like
Reactions: Achsel

Achsel

Member
Jan 17, 2007
48
25
The current version of LABD is 1.5.1 (2.99 $ at Google play store). But I have no payment account. So I was only able to find and test version 1.4.3 on the Internet. Maybe version 1.5.1 uses its own ADB binary. At GitHub you can legally download the source code and create an APK file from it. But I didn't have the required Android Studio and SDK tools installed on my old PC. Maybe you or another user can compile the attached source code from LADB 1.5.1 into an APK file. So I could test whether version 1.5.1 uses its own command "pair".

https://github.com/tytydraco/ladb

Thanks in advance!
Axel

Another specific question: The 8 years old Samsung S4 has no native ethernet support. On the old stock ROM with Android 4.4.2 I could activate a connected Ethernet adapter via this shell commands (example for Google server):

su
dhcpcd eth0
ndc resolver setifdns eth0 "" 8.8.8.8 8.8.4.4

On LineageOS 18.1 the shell command "dhcpcd" does not exist. Do you have any idea, to activate a connected Ethernet adapter via shell or busybox commands? I found the busybox command "dhcprelay", but I don’t know how to use.
 

Attachments

  • LADB-main.zip
    2.3 MB · Views: 2

Top Liked Posts

  • There are no posts matching your filters.
  • 679
    osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc.

    General Information


    In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller scripts and zips I've created that I don't think merit their own separate threads. This is partially for my own sanity and will hopefully make it easier for others to find some things as well. A lot of the stuff here was developed with the GN, N5, N7s or N5X, OP5/T, OP6/T, OP7Pro/T, OP8Pro/T or OP9Pro (my devices) and Windows in mind, but could generally be applicable to most devices either out-of-the-box or with some slight modification. If you see something that inspires you, go ahead and mod it, just let me know and give me some credit somewhere. If anyone would like to know the specifics of what's in a particular script that I haven't already linked to more information on, just let me know and I'll post that in here as well.

    Note: Older zips with a "cwm-" prefix are NOT only for the now-defunct ClockworkMod Recovery, the prefix was used to denote a flashable zip before I adopted Chainfire's "UPDATE-" prefix. Please use a currently maintained recovery, like TWRP, for all zips to ensure the best compatibility/results.

    My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!


    Misc./Batch Tools

    • AnyKernel3 (many devices) - link
      AnyKernel was a simple template for an update.zip that could apply any kernel to any ROM, regardless of ramdisk to reduce the chance of any issues arising from the custom kernel pairing. The drawback to this is that some kernels require modifications to the ramdisk to enable/set up kernel features, and in the old AnyKernel format there was no way to do this. AnyKernel3 pushes the format even further by allowing kernel developers to modify the underlying ramdisk for kernel feature support easily using a number of included command methods along with properties and variables to customize the install experience.
    • APK-Patcher (many devices) - link
      A proof-of-concept, simplifies APK modification to make it easier for modification creators to keep creating. Using JesusFreke's brilliant bak/smali and iBotPeaches' excellent apktool, modified to run on-device along with the various binaries required, allows on-the-fly APK modifications to be applied via recovery, to whatever ROM APK is present, taking the constant update burden off of the modification creator. The zip is smart and automated, using the APK name to run all the various parts involved for complicated patches and is extensible to any number of APKs in a single zip.
    • Android Image Kitchen (many devices) - link
      A collection of Windows/Android ports of the necessary Linux utilities for Android image (kernel+recovery) mod work, and my own automation script to unpack, edit and repack the ramdisk. Other guides/scripts exist but none of them are universal for target device, compression and/or developed for Windows/Android. Now also Linux builds to bring my improved featureset back to where it came from, recently extended to macOS as well. Has been extremely useful for me in my messing around with kernel ramdisks.
    • ADB Screenshot (many devices) - attached
      Take screenshots while in recovery. Useful for development of recovery apps or error reporting. Original method had lots of different threads around with the general method for various devices but I figured out a couple tricks required for getting it working on the Galaxy Nexus and then automated the process. Tested and confirmed working with both pixel formats of CWM and TWRP. More information in this GN Q&A FFmpeg thread. New method uses fb2png and should work on all ARM devices.
    • ADBsync sdcard Backup (many devices) - attached
      Backs up the entire sdcard so that you can have a complete snapshot of your device when you make periodic backups, and be able to restore things exactly as they were. Automates the sync process of Renate NST's great adbsync utility which makes only newer files get pulled, significantly decreasing backup time for the sdcard compared to "adb pull". Original version posted in the old adbsync thread. Defaults for devices with /data/media/ internal sdcards (Nexus devices, etc.), but is easily customizable to backup other mountpoints or backup via ADB over WiFI.

    Flashable Script Zips
    • TWRP A/B Retention Module script (many devices) - link
      We need an interoperable root ecosystem again. A/B and system-as-root were a big setback to the root community in this respect. To help alleviate this issue, this atypical Magisk script zip "module" will keep TWRP installed to both slots when flashed from Magisk Manager after an A/B OTA has installed in the background, but before you use Manager to install Magisk to inactive slot.
    • Nexus BootUnlocker script (GN, N4, N5, N7 '13, N10) - attached
      I don't know about everyone else but sometimes I find I've rebooted into the bootloader only to realize I've forgotten to unlock it in segv11's excellent BootUnlocker App beforehand. Well, I decided to make a BootUnlocker Script for my Galaxy Nexus so I could just boot to recovery quickly, unlock, then adb reboot-bootloader (or use my Reboot To Bootloader script below) to get back without having to fully boot the OS to make the change. Also extremely useful in the case you aren't able to boot. As with the app there is no data loss like there would be with fastboot, allowing you to relock for safety. Originally posted in the GN EDIFY Scripting thread. Modified for the newer Nexus devices and combined into a single Nexus BootUnlocker zip with tamperbit reset support added using information from the BootUnlocker App Dev thread. For newer devices using Factory Reset Protection (N6 and later), the BootUnlocker Script can't directly toggle the lockstate due to new security tokens, but it does now toggle the ability to use "fastboot oem unlock" without needing a booted device.
    • N7 BootUnlocker script (N7 '12) [creation guide] - link
      The Nexus 7 2012 is a special case. Per-device encryption of an entire partition makes it impossible to support the N7 '12 in a simple root app, or flashable zip as above, however using my guide and included script you can now create a working BootUnlocker Script Zip for your specific device. As with the above scripts there is no data loss like there would be with fastboot, allowing you to relock for safety.
    • sdcard Fix Permissions script (many devices) - attached
      A little flashable zip script to fix ownership and permissions of files and directories on the sdcard to what they would be if Android OS had put them there itself, since some apps can't access pushed files that have root.root as owner/group. This is useful when restoring to your sdcard backup, as with my ADBsync sdcard Backup batch script above, since generally, pushed files get root.root from adb shell and higher permissions than usual. Also a solution for a bug where sdcard files get lower permissions somehow, resulting in similar access problems. Currently written for devices with /data/media/ internal sdcards (Nexus devices, etc.), but could easily be modified for other mountpoints. No longer required on Oreo since it fixes these itself at boot.
    • Recovery SLAM script (many devices) - link
      Recovery "Simple Legacy Auto-Mount" (SLAM!) is for devices that have been updated to SAR, but there are older zips that break in TWRP because they rely on the mounts occuring a certain way, especially during a ROM OTA. Recovery SLAM mounts them more as the zips would expect, generally allowing them to proceed. Most useful for premounting /system before a legacy zip with my FlashAfterUpdate addon.d script.
    • SUmount script (many devices) - attached
      Another tool for the toolkit of anyone using Chainfire's SuperSU or topjohnwu's Magisk systemless root, this simple flashable zip script toggles the mounting of the su.img, magisk.img and magisk_merge.img while in recovery to allow easier access to the /su, /magisk and /magisk_merge filesystems, simplifying manipulating it via ADB shell, AROMA Filemanager or TWRP's terminal/file manager. Especially useful to anyone who uses su.d/post-fs-data.d scripts or can't boot due to some issue with a user addition in /su/su.d, /su/bin or a Magisk module.
    • unSU script (many devices) - link
      While experimenting with Chainfire's brilliant SuperSU systemless root, I discovered that uninstalling the older style system-modifying root through his app (<2.60) didn't restore all of the modified system files correctly, so I wrote this script to do so and aid in people wanting to unroot from recovery. Expanded to support uninstallation of Koush's SuperUser, phh's Superuser, SuperSU Systemless (su.img and BINDSBIN), Magisk, LineageOS addonsu and custom ROM su binaries.
    • Adreno Systemless Installer script (N5, N6, N7 '13) - link
      For use with Qualcomm's official updated preview GPU drivers packages for Adreno 3xx/4xx-powered Nexus stock images, this is technically a script and not an installer because it is only a different frontend to take whatever device zip from Qualcomm is in the same directory as it (also searching /sdcard) and unpack it then install it into the SuperSU systemless root /su filesystem instead of the usual /system, or Magisk if detected.
    • Kernel MultiROM Injector script (many devices) - attached
      Intended for use in Chainfire's excellent FlashFire app to automate re-injecting the current boot image ramdisk with Tasssadar's brilliant MultiROM's trampoline bootmenu; this avoids having to do this as an extra step in MR-TWRP following an OTA, ROM Delta or SuperSU update. Should work for all EMMC devices with MultiROM installed.
    • GN PIT Editor script (GN) - link
      Dumps and alters the Galaxy Nexus' Partition Information Table (PIT) to reclaim unneeded space from the /cache partition and add it to /system to allow for larger ROMs and GApps packages to make continued support for Lollipop+ easier. The resulting file is byte-for-byte identical to those created by external tools like PIT Magic, so that it may be flashed back to the device in Odin Mode to complete the repartitioning.
    • Kernel Emergency Reset script (many devices) - link
      Basically a go-to cure-all for custom kernel users experiencing issues after an upgrade due to old settings left over in a kernel control app (eg. franco.Kernel updater, Trickster, etc.), or problematic init.d/userinit.d scripts. It's also useful if you just want to make sure you're running clean defaults without conflicts.
    • Reboot To Bootloader script (all devices) - attached
      Those who prefer using CWM may have noticed a couple of things missing that the other popular custom recovery, TWRP, has built-in. One of these is a file explorer/manager, which is answered by amarullz' brilliant AROMA Filemanager. Another thing I found myself wanting is a way to reboot back to the bootloader once I'm in recovery, so I created this very very simple flashable zip script. (No longer required on CWM >=6.0.3.5). Note: Once in the bootloader, "Start" will boot you back to recovery. Not sure why, but it's not a big deal, just reboot normally from recovery at that point.

    Flashable Installer Zips
    • Flashlt Installer (many devices) - attached
      Installs my Flashlt script to allow easy flash and dump of boot, recovery and radio/modem (possibly others) EMMC or MTD partitions while booted, and trimming of null characters from files. Also installs a script zip that makes flashing boot.img (kernel), recovery.img, and radio.img/modem.img (baseband) files via recovery simple. It aims to save the average user the hassle of repacking their own image zip, or using the command-line or fastboot to flash it. Place an appropriately named file in the same directory as the zip and flash away! Should work on all devices with normal partition naming ("boot", "recovery" and "radio" or "modem") which accept Android standards-compliant images (including a/b slot devices like Pixel). Extremely handy when used with amarullz' brilliant AROMA Filemanager, and/or my Android Image Kitchen: Mobile Edition (linked above).
    • Busybox Installer (all devices) - attached
      As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well. Please read the release post about applet inclusion and special features.
    • nano Terminal Editor Installer (many devices) - attached
      A simple installer to push my own static Android ARM build of the nano editor binary to /system/xbin/ along with the required files in /system/etc/terminfo/, and a wrapper with optional parameter to choose your terminal. Detects and supports "systemless" install via SuperSU/Magisk as well. It can then be used from Terminal while booted from that point on. Each time you flash it also temporarily enables use in recovery by pushing a script to /sbin/nano with the required environment variables, so you can then trigger it from recovery shell or the console in amarullz' brilliant AROMA Filemanager. Makes it extremely easy and worry-free to tweak and mod on the go, knowing you can edit the faulty build.prop or init.d script if something goes wrong.
    • adb + fastboot Installer (many devices) - attached
      Marshmallow removed adb from the /system/bin directory. For those wanting this functionality back, here's a simple installer to push static compiles of adb and fastboot to /system/xbin and uses a command wrapper to point adb to the correct HOME directory and set TMPDIR for compatibility. Detects and supports "systemless" install via SuperSU/Magisk as well. It can then be used from Terminal while booted from that point on.
    • Nexus Media Installer (many devices) - attached
      Custom ROMs often don't include the Google ringtones/notifications/system sounds and bootanimation, instead including numerous, terrible sounds and often less-than-desirable visuals. This zip installs the Nexus media for recently-retired Nexus devices, using the zip name (also reading from /data/.nexusmedia) to allow user choice, systemlessly installed (SuperSU and Magisk supported) or with an addon.d script to survive a ROM update or dirty flash.
    • mtd-utils Installer (many devices) - attached
      mtd-utils (flash_erase, nanddump, nandwrite) are necessary for mod work on a number of Android devices using mtd/char devices instead of the more standard emmc/block devices, and where the busybox versions have been less reliable in the past (especially where it doesn't include flash_erase), using the official suite is preferable. The older ARM builds available on XDA were about a decade old, so I worked out how to configure and cross-compile from the latest source. Detects and supports "systemless" install via SuperSU/Magisk as well. It can then be used from Terminal while booted from that point on.
    • ZipSigner + Zip Installer (many devices) - attached
      Signing zips and APKs on-device has always been a tricky proposition due to memory requirements of the old SignApk.jar, running a jar on an Android device, and other complications for script-based zips. Android has always been missing a zip binary (for unzip see my Busybox Installer). ZipAlign is also handy if you do APK work. To remedy this once and for all, here's a simple installer to push my dexed version of topjohnwu's brilliant zipsigner.jar and static ARM compiles of zip and zipalign to /system/xbin and uses a command wrapper to run zipsigner with Android's own dalvikvm. Detects and supports "systemless" install via SuperSU/Magisk as well. It can then be used from Terminal while booted from that point on.
    • odex Script Installer (all devices) - attached
      Based on the great work and binaries from this thread, a simple installer to push my odex script along with the required dexopt-wrapper and zip binaries to /system/xbin and set the appropriate permissions. Automates the procedure to odex any apk or jar from the commandline to potentially improve performance. Dalvik runtime (KitKat and below) only. Also uses cut from busybox.
    • N5X/6P BLOD Workaround Injector (N5X, N6P) - link
      When, unfortunately, my Nexus 5X was recently stricken with the abominable Bootloop of Death, I looked into the well-publicized workaround and turns out it was all contained in the ramdisk and cmdline of a Android image. This is the perfect application of AnyKernel2, so I made an AK2 add-on zip to patch both the current boot and recovery partitions with all the current workarounds to help others afflicted by this issue to hopefully regain their data/device as easily as possible. Linked is the Nexus 5X thread, the Nexus 6P thread may be found here.
    • GN Synapse Support Injector (GN) - link
      This AK2 kernel add-on for the Galaxy Nexus injects support for the Synapse tweaking app into the current boot partition ramdisk, including all the Synapse interfaces for the GN I've maintained since the Franco Kernel and DirtyV Kernel days.
    • GN Recovery Color Correction Injector (GN) - link
      The aging screen on the Galaxy Nexus was looking pretty rough in recovery until I discovered the recently added new OMAP kernel color correction was also present in the most recent TWRP recovery versions. So this add-on zip uses AK2 to patch the current recovery partition ramdisk to add the command to reduce that green/yellow SAMOLED nastiness.
    • Kernel init.d Support Injector (many devices) - attached
      An experimental proof-of-concept. Following from great ideas by Captain_Throwback in my AnyKernel2 thread and using script from my Flashlt script above, this AK2 zip will inject basic init.d bootscript support into any kernel ramdisk on any emmc device with normal partition naming and using the Android bootable image standard, without having to bloat a ramdisk using a busybox binary. This zip is also signed, so could potentially be used with non-Nexus stock recovery on a locked bootloader.
    • CMSetup Fix for GApps Installer (many devices) - attached
      Installs a su.d script fix to work around the CyanogenMod/LineageOS 13 ROM issue of a broken Quick Settings pull-down when CMSetupWizard is removed as part of a GApps installation. Removing CMSetupWizard is useful because it allows Google's SetupWizard to grant apps default permissions, so the workaround automatically executes the only required command at the appropriate time following first boot. Requires a SuperSU/Magisk installation (for su.d/post-fs-data.d support). Flash after the SuperSU/Magisk zip and your GApps.
    • Dev Team init.d Pack Installer (all devices) [see "950iosettings, etc." below] - link
      A simple installer I wrote to create the /system/etc/init.d/ directory, extract the latest init.d scripts as published by the "Franco's Dev Team" tuning collective (of which I was a member), then set correct owner, group and permissions to the entire init.d directory. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask.
    229
    Scripts
    • 950iosettings + 875mntsettings + 925vmsettings + 975experimental init.d scripts (all devices) [with Franco's Dev Team] - links
      Also available bundled in an installer. The scheduler tunables have already gained a bit of attention/adoption on various devices and kernels, but this is the init.d script I wrote to set the new custom scheduler tunables values as "default" by an independent loop, sleeping in the background and detecting each time the scheduler is changed. There is no effect on idle drain or deep sleep. The settings included are the complete work of the "Franco's Dev Team" (or "Team Franco") tuning collective, of which I was a member. We strove to perfect the scheduler, vm and various other settings for the smoothest and fastest experience available. The collective was: malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask. Lollipop(+) updated versions now also available through the continued excellent work of pkgnex.
    • 999-flashafterupdate.sh addon.d+addon.d-v2 script (many devices) - attached
      For ROMs that don't have "Flash After Update" support built into their delta/update process. During an upgrade, this script will flash zips from an sdcard directory, with several options (listed in the script header) for displayed output, after all other addon.d backup/restore actions have completed. This can be used to flash SuperSU and then an AnyKernel2 kernel on LineageOS, for example. Only zips that specifically support addon.d-v2 can be supported on A/B devices. See this how to for instructions for use with A/B devices. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
    • 98-twrp_ab.sh addon.d-v2 script (many devices) - attached
      Allows you to keep TWRP installed in a boot partition through A/B OTAs with Magisk installed by copying the TWRP ramdisk from the current slot to the updated one, before Magisk's addon.d-v2 script patches it. Requires a current Magisk installation since we need the tools and Magisk's the only way to ensure a working addon.d-v2 environment across ROMs at the moment. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
    • 97-dumpbootimage.sh addon.d+addon.d-v2 script (many devices) - attached
      For ROMs with boot.img inside an OTA payload.bin or otherwise inaccessible, it dumps the updated boot partition before further modifications (TWRP, Magisk, etc.), saving it to /sdcard/Download/boot.img or to/from other customizable locations at the top of the script. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
    • 00-omnirootfix.sh addon.d-v2 scipt (many devices) - attached
      OmniROM appears to include 69-gapps.sh automatically in its /system/addon.d directory despite not shipping with any GApps; when not rooted this doesn't appear to present a problem, but really this is only because the script doesn't have enough permissions to run how it's supposed to since Omni's sepolicy doesn't let addon.d-v2 work correctly. Once Magisk is installed, providing more privileges to the addon.d-v2 update_engine, Omni's 69-gapps.sh would remove important system files during an A/B OTA when no GApps were installed, so this script will simply prevent that for those wanting to run Omni minimally and with root. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
    • 00-resizesystem.sh addon.d script (many devices) - attached
      One common solution for aging devices is to resize the /system partition so that it can hold newer, larger ROMs and, of course, GApps packages. On devices where the /system partition has been resized to hold larger GApps packages, but the ROM in use has system.dat format zips with no resizing functionality, the extra space would get lost in a ROM delta flash, breaking things when GApps attempted to restore. This script will resize the system partition to its maximum before the GApps restore occurs on EMMC-based devices with standard partition naming. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
    • 10-extract-lineage-kernel.sh addon.d script (many devices) - attached
      Nowadays with systemless root and other boot.img mods out there, it's good to have a backup of your ROM's unmodified boot.img handy in case you want to do a clean flash of your boot partition. Since LineageOS moved their update zips to a /data/data subdirectory that made this harder to get to, I automated the procedure as an addon.d script so that the newest gets extracted on each update. The output directory may be changed by editing the script. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
    • 999-customkernel.sh addon.d script (many devices) - attached
      Addon.d is awesome at restoring your GApps, root app, and other things after a ROM Delta, update, or dirty flash, but of course this can leave a lot of stuff out that you'd also have to re-flash (see below for a personal addon.d script you can modify to cover anything else you want to save). This script aims to help remedy the issue for custom kernel users on EMMC-based devices with standard partition naming by dumping the current kernel as part of the addon.d backup process, and then restoring it after the ROM has flashed its included kernel. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions. This is deprecated by my FlashAfterUpdate addon.d script, above.
    • logohack.sh (GN) - link
      Galaxy Nexus bootloader image replacement hack script. Inspired by bitdomo's brilliant imgdata tool and replicating the functionality of Ezekeel's abandoned, broken paid Logo Me app, this script improves upon the app version by working on all Galaxy Nexus bootloaders and on-the-fly, to allow replacement of the Google logo and lock images within the sbl partition. Remove the .txt extension once downloaded and place in /system/bin/ or /su/bin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
    • flash_image (many devices) - attached
      MTD devices require a little extra finesse when flashing partitions from the command prompt and multiple commands, versus MMC devices, for which we can just use the dd command both ways. I wrote this little script to simplify the process for myself in my MX Box tinkering. It parses /proc/mtd so you only need to enter the partition name. It requires _n0p_'s excellent MTD-Utils compiled for Android, and uses grep and cut from busybox. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
    • getprio (all devices) - attached
      Android doesn't allow you to check the priority (or "niceness") of a process with the getpriority command as you would with normal Linux, and busybox doesn't provide this functionality either, so I wrote this reasonably simple script to allow you to check the niceness of a process. Some kernels have been experimenting with increasing the priority of com.android.systemui for smoothness, so this command can be used for testing different levels and whether the renice command set it correctly. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from Terminal with either the pid (default), class or a class name search string. Uses pidof and pgrep from busybox.
    • gappsintegrator init.d script (many devices) - link
      ROM GApps Auto-Integration of /data/app GApps into /system, complete with libs (unlike Titanium Backup), for Jelly Bean through Marshmallow. It should process things early enough in the boot that afterwards Dalvik will immediately do the cleanup ("Android is upgrading..."), much like following an OTA. An initial GApps installation is one requirement and there are some important notes for support of Lollipop and above. Intended for ROMs with a busybox installation. Can also remove libs from and zipalign the integrated APKs if those binaries are present in the ROM.
    • lmkwhitelist init.d script (all devices) - link
      Users running ROMs or kernels with extremely aggressive custom lowmemorykiller (lmk) driver settings may notice their launcher redrawing frequently. Some kernels/ROMs also include an exclusion for this by making stock (or the included) launcher unkillable, however that still leaves all the 3rd party launchers out there that people use. I wrote this init.d script with a community created list of the most common launchers to make whichever one is installed unkillable. This also has instructions for how to set up init.d scripts. If your launcher isn't included in the list, you can modifiy it by adding the application class name (from the Play Store URL) to the list within quotes, separated by spaces. Also part of the 975experimental Franco's Dev Team init.d script, linked above.
    • dalvik2cache init.d script (all devices) - link
      Bind mounts the dalvik-cache directory to the cache partition. Useful on devices where the cache is sizable and unlikely to be used for OTAs (custom ROM, etc.), and the data partition is not. Every little bit counts!
    • settingsdump.sh (all devices) - attached
      In comparing vm settings from various kernels and ROMs to see what's out there, I wrote this script to generate a list of the values of all the relevant sysfs files and directories. Now expanded to cover cpu and governor as well. Remove the .txt extension once downloaded. To run it, assuming you just put it in /sdcard/, open Terminal Emulator and type: "sh /sdcard/settingsdump.sh" (without quotes). It will output the file to /sdcard/r*-output.txt where * is the revision of the kernel you're running. This makes it easier to compare what's changed between different nightlies, for example.

    Other
    • BootUnlocker app (many devices) [with segv11] - link
      With a number of users researching and contributing the bootloader lockbit and tamperbit offsets in threads around xda and to the development thread for seg11's excellent BootUnlocker app, I have begun making beta builds with these new devices added. With hopes of adding any/all that can be, it now supports all the older Nexus devices, OnePlus devices and several others. We are accepting Pull Requests and collaborators for further device/design updates. Check my original revival post for more details.
    • G-Box Midnight MX2 g18ref ROM, recovery and kernel osmods (MX Box) [with BenniBenassi & relol] - link
      I bought one of these unbranded Android TV boxes and was immediately determined to tweak it as much as possible following my work on the Galaxy Nexus. Flashing the official Matricom stock ROM over the generic included one I also discovered the recovery didn't have any A/V output to my old CRT TV. I set out to dump the kernel and recovery images, fix the recovery images and tweak the kernel defaults for the most performance.
    • Holo Stock Notification Icons for Notification Toggle (many devices) - link
      This was likely my first post ever on xda. It is a "Notificon" pack for j4velin's fantastic Notification Toggle App, bringing a seamless stock look to this indespensibly useful app. Also a great way to get back to Settings easily from the notification shade since Android 4.2, and add shutdown/reboot menu functionality to stock/vanilla ROMs.
    • My GN Kernel Settings + 900colorsettings init.d script (GN) - link
      I was being asked a fair amount for my kernel settings over in the GN f.K thread where I helped out, so I posted them up. I also put up an init.d script for setting color values on boot, which can drastically change the outcome on older panels, and at least makes custom values seamless. Instructions for how to set up init.d scripts are included.
    • Galaxy Nexus Baseband Collection: maguro - i9250 / M420 / SC-04D Radios (GN) [with josteink] - link
      Original thread author josteink moved on to other devices and asked me to take over the thread. Lots of great information on the GN radios, posted alphabetically by region and chronologically by the build string date I found embedded in the images. Huge respect and massive thanks to josteink for seeing the need for a baseband thread almost as soon as the Galaxy Nexus was launched, way back in December 2011, and maintaining it diligently.
    • TK GApps (many devices) [with TKruzze] - link
      After helping TKruzze with some of the concept and script work for his famous Paranoid Android Google Apps packages (PA GApps 2.0), we decided to collaborate again for his return to XDA after a much-needed hiatus, with me doing the thread setup and management with DevDB, and a Q&A section so things don't get overwhelming for those trying to follow along. The main thread remains locked and can be subscribed-to for those wanting notification only when there's a new GApps release, and the Q&A functioned as the main discussion thread where people can help each other. Much of the script is the same from PA GApps but TKruzze has added some impressive new features, made many fixes and revamped a large portion of the documentation. I also continued as an adviser and submitted script when needed.
    • Nexus Louder Audio Improvement Patch (GN, N4, N5, N7 '12, N7 '13) [with Misledz] - link
      One of my earliest forays into EDIFY scripting, I wrote the flashable zip install/revert scheme for this great volume boost mod by Misledz. The scripts check to see if the mod is already installed and if so recommends you flash the version-specific revert that goes with it. More on that in the Intelligent EDIFY thread. During install the script also backs up the ROM files it replaces so that you don't need to reflash your whole ROM if something goes wrong, just use the revert to restore the backups. I eventually rewrote this completely in shell script with a Universal install/revert, that detects which files to backup and leaves a list for itself to revert. I also wrote automation batch scripts for Misledz as the "Louder Build Farm" to simplify his work for all the versions of the mod he maintains for various devices, linked in the knowledge base below. GN/Dev thread linked; Other links can be found there.
    • Payload-Dumper-Go for Android Magisk Module (many devices) [with ssssut] - link
      payload-dumper-go arm compile and wrapper for use extracting from payload.bin on-device.
    • Git for Android Magisk Module (many devices) [with Termux] - link
      Hacked arm64 git commands for use on booted Android.
    • Google Experience XML Magisk Module (many devices) [with Google] - link
      Hacked Google Nexus/Pixel/Android One sysconfig feature xml entries for use on non-Google devices.
    • Xposed Framework Installer Zip (many devices) [with rovo89 & Tungstwenty] - link
      When JB4.3 broke all previous root methods I made this simple frontend script to install rovo89's brilliant Xposed Framework for modding ROMs until they could release a new version themselves. Xposed Framework files and the install.sh used are the work of rovo89 and Tungstwenty; I have only created a recovery flashable zip and shell script to function as an alternative frontend for the framework installation process. Then updated to mimic the APK installation and allow devices with /system write protection like HTC's S-ON to install the framework. (Deprecated as of Xposed 2.5).
    • BBCode for my xda Signature (n/a) - link
      Last and definitely least. A number of people have asked me about the formatting of my signature, so here are some simple BBCode tricks and workarounds I thought others might like too. Keep in mind that my signature can be significantly larger because of my RC status.

    Enjoy!
    Questions, comments and feedback welcome.



    Credits & Thanks: All authors of any included binaries and libraries for their amazing work. Anyone who's helped me with these projects along the way.

    Disclaimer: Naturally, you take all the responsibility for what happens to your device when you start messing around with things.
    157
    Knowledge Base

    Links to information/research posts I've made and other experiments.

    ----

    avbtool-arm (zip package)
    - link
    AOSP's BootSignature.jar for AVB v1 was relatively simple to run on-device for boot.img modifying flashable zips like SuperSU and AnyKernel2 but avbtool for AVB v2 is written in Python, so that makes things a bit trickier. For experimentation I whipped up a little wrapper script to run avbtool on-device with an actual Python interpreter.

    Omni SoundPacks (and Nexus Stock pack) - link
    My suggested expansion to the Omni SoundPacks feature to allow it to cover all SystemUI sounds.

    OnePlus FingerPrint Material Icons (Information) - link
    My preferred fingerprint icon for the in-screen OP6T sensor using Zacharee1's excellent OPFPControl app.

    ----

    Complete Shell Script Flashable Zip Replacement + Signing Documentation (Reference)
    - link
    Using a shell script instead of an update-binary in flashable zips can make them universal for architecture and put a lot more power in the hands of the developer. This reference documents all of the analogous functions myself and others have written to make this easy.

    Booted Zip Flashing Shell Setup Script (Reference/How-To) - link
    My implementation of booted zip flashing, originally for AnyKernel2 in Franco Kernel Updater (now Franco Kernel Manager) and since expanded to support AK3's ability to be flashed from anywhere and support most other flashable zips on devices that allow remounting /.

    Unified ext4/f2fs ramdisk + ROM installer (Reference) - link
    Supporting multiple filesystems like ext4 and f2fs in a custom kernel boot.img ramdisk required some work before custom ROMs were updated to do this themselves and use fallback fstabs. This is the roll-up post gathering all the changes necessary for someone to add this pre-official support to their ramdisk, kernel and ROM installers.

    FlashFire Recipe Book (Reference/How-To) - link
    Just a quick reference of common tasks (OTA flashing, etc.) for people figuring out how to use Chainfire's brilliant flashing app.

    personal addon.d (How-To/Template) - link
    I was tired of having to redo a number of tasks (remove files, backup Nexus sounds and replace the AOSP ones, etc.) to get my device back to where I wanted it after flashing a newer nightly, so I wrote an addon.d script to do it all for me. Provided if anyone wants to modify it for their own personal setups.

    KBox2: Set Up A Build Environment On Android (How-To) - link
    Very cool Linux-like command prompt environment on Android. I originally had it set up as a native build environment with rudimentary git support. You can follow my steps to do the same.

    Keeping SafetyNet Passing With Incremental Google OTA on Virtual A/B Devices (How-To) - link
    Post-reboot checks added to the incremental OTA process for Virtual A/B devices using Google's servers made it impossible to remain rooted throughout the OTA process, but following these instructions you can complete the OTA then re-root without SafetyNet catching you.

    Cygwin-Linux Cross-Compiler (How-To) - link
    Compiling from Cygwin with a Linux target required some fixes to the toolchain, so I detailed them for future reference.


    N4/N5/N7 '13 Qualcomm Optimized Bionic/Dalvik Patch Comparisons (updated zips) - link
    Using Qualcomm optimized files on Snapdragon devices improves performance greatly on KitKat. Especially good on Nexus devices or AOSP ROMs. I took the time to dissect the required files and see what worked best.

    AIK Build Farm (desktop shell script) - link
    The Cygwin shell script "build farm" I wrote for my Android Image Kitchen project to perform all of the cross-compiles required for the mobile and Linux versions. Allows someone to setup the repos from scratch and build.

    Louder Farm (zip packages) - link
    The Nexus Louder project was a pretty massive system file modifcation undertaking. This details my work to make building the patch zips easy for co-dev Misledz, and includes the farm packages at various stages.

    ----

    N7 '13 Bootloader cracking (Information)
    - link
    Sat down with my parents' Nexus 7 2013 (before I got my own) over Christmas and cracked the bootloader for unlock support via my Nexus BootUnlocker Script zip and later the official BootUnlocker App.

    N7 '13 Unbricking (Information) - link
    Instructions I put together for recovering from a hard brick (bad bootloader flash usually), via the exposed Qualcomm/Marshall London "HS-USB Diagnostics 9006" mode.

    Default System Alarm Setting Script (Information) - link
    A script snippet function to allow easily changing the default alarm sound on ROMs that hide this ability, like OnePlus' OxygenOS.

    SELinux Audit2Allow Script (Information) - link
    A script snippet for turning SELinux audits in a logcat into allow statements ready for supolicy or magiskpolicy.

    Partition Dumping Script (Information) - link
    A script snippet for dumping all non-userland partitions from any eMMC device, useful for bootloader lockstate hacking.

    GN Partition Information Table (PIT) Research (Information) - link
    Wanting to push the GN as far as possible, several remaining users came together to discuss how it could be repartitioned to add more space to /system to better support Lollipop+ and I contributed a large amount of R&D over several posts throughout the thread which resulted in the PIT Editor script zip (posted above). Could be useful for other devices using PITs as well.

    GN/N7 '12 tunables post (deprecated) (Reference) - link
    The list of supported basic tunables on franco.Kernel for the Galaxy Nexus and Nexus 7 2012 back when those were my primary supported devices.

    GN scheduler tunables HZ scale (Information) - link
    The Galaxy Nexus scheduler (and other) tunables opperate on an odd scale due to the the device's HZ value in the source being weird. This post experiments with that and finding the method/equation behind it.

    LMK boot timing (Information) - link
    The Android lowmemorykiller module default tunables go through a bizarre sequence during boot, so I experimented and came up with a script to allow setting alternates as soon as possible.

    LMK Launcher Whitelist/Niceness settings reversion (Information) - link
    Setting oom_adj values and changing the niceness on launchers and systemui improved responsiveness and helped avoid these important processes being killed by LMK. Then I noticed sometimes they spontaneously reset; experimentation followed.

    MTD partition flashing (Reference) - link
    My MTD-based MX Box set-top device gave me a few hours of headaches until I figured out how to dump and flash the boot (kernel) partition correctly. This details my experiments and the correct procedure I discovered.

    nano Android static build instructions (Reference) - link
    A little documentation of all the dirty tricks I used to get the nano terminal editor utility to build for Android from the official git repo source.

    mtd-utils Android static build instructions (Reference) - link
    A little documentation of all the dirty tricks I used to get mtd-utils to build for Android from the official git repo source.

    Pixel Launcher bind mount instructions (Reference) - link
    I was annoyed that on stock Nexus 5X and 6P Pixel Launcher wasn't available and when sideloaded lost the Google Feed pane, so I replaced Google Now Launcher with Pixel Launcher using bind mounts.

    Netflix broken DRM workaround instructions (Reference) - link
    Custom Nexus 7 2013 ROMs Nougat+ have all had issues with Netflix due to some peculiarities of the DRM libraries the ROMs use, but some found that intentionally semi-breaking DRM using files from other devices allows Netflix to work again, but this broke Google Play Movies. I did some more testing, resolved the Play Movies issue and wrote up how to install the single needed replacement library either to system or with a systemless bind mount.

    ----

    Thanks for the interest! More to come, I'm sure!
    110
    New addition to the OP. ;)

    Busybox Installer:
    As a byproduct of building my own static busybox compiles in all supported Android architectures for my latest AIK-mobile v2.0 package I figured I might as well offer them up separately as well since there aren't any providers making Android x64 builds, at least not for all of them when I went hunting (to try and save myself some time). The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary to /system/xbin accordingly; it detects and supports "systemless" root installation as well, installing to /su/(x)bin instead. It then cleans up any symlinks from a possible previous installation at that location and cleverly generates new symlinks directly from the output of the installed binary, so they always match.

    My busybox configs and patches are available here: https://github.com/osm0sis/android-busybox-ndk

    I've got a patch submitted to the official busybox mailinglist to resolve some API 21 compatibility, so that will probably be added in a future version to save people time and make it easier for more providers. Anyway, hopefully I got all the applets most people want working. (y)


    Edit: Now the zip will also clean up an installation made to /su/bin and then install to /su/xbin. (y) :)

    Edit 2: New special zip features
    You may add keywords to zip filename or in a file at /data/.busybox-ndk:
    1) system or System or SYSTEM to force a system installation.
    2) uninstall or Uninstall or UNINSTALL to uninstall busybox from the zip's detected target location (/su/xbin > /magisk/busybox-ndk/system/xbin > /data/adb/su/xbin > /data/adb/modules/busybox-ndk/system/xbin > /system/xbin, unless system forced per above).
    3) nolinks or NoLinks or NOLINKS to opt out of symlink creation and only push the busybox binary.
    4) noselinux or NoSELinux or NOSELINUX to force the non-SELinux busybox binary to be installed.


    For those curious, I automate bundling my busybox binaries directly with builds from my AIK Build Farm using the following script.

    ~/bbox-bundle.sh:
    Bash:
    # also this
    
    home=~;
    magisk=$home/Magisk;
    
    bold() { echo -e "\033[1m"[email protected]"\033[0m"; }
    
    cd "$home";
    
    case $1 in
         help) echo "bbox-bundle.sh [verbose] [nocopy]"; exit 1;;
      verbose) stdout=/dev/stdout; shift;;
            *) zipflag=-q; stdout=/dev/null;;
    esac;
    
    rm -f Busybox-*-ALL*.zip UPDATE-Busybox.Installer.*-ALL-signed.zip 2>/dev/null;
    
    ver=$(ls | grep ^busybox- | cut -d- -f2);
    
    if [ -f AIK-build/mobile/arm/busybox -a "$1" != "nocopy" ]; then
      bold "- Copying new Busybox $ver builds ...";
      cd AIK-build/mobile;
      for i in *; do
        cp -fp $i/busybox $magisk/UPDATE-Busybox.Installer.*-ALL/busybox-$i;
      done;
      cd "$home";
    fi;
    if [ -f android/git/ndk-box-kitchen/libs/armeabi-v7a/busybox -a "$1" != "nocopy" ]; then
      bold "- Copying new Busybox $ver SELinux builds ...";
      cd android/git/ndk-box-kitchen/libs;
      for i in *; do
        case $i in
          armeabi-v7a) out=arm;;
            arm64-v8a) out=arm64;;
                    *) out=$i;;
        esac;
        cp -fp $i/busybox $magisk/UPDATE-Busybox.Installer.*-ALL/busybox-$out-selinux;
      done;
      cd "$home";
    fi;
    
    modver=$(grep -o "^version=.*$" $magisk/UPDATE-Busybox.Installer.*-ALL/module.prop | cut -d= -f2);
    modcode=$(grep -o "^versionCode=.*$" $magisk/UPDATE-Busybox.Installer.*-ALL/module.prop | cut -d= -f2);
    if [ "$ver" == "$modver" ]; then
      newmodver="$modver";
      newmodcode="$((modcode + 1))";
      iteration=1;
    else
      newmodver="$ver";
      newmodcode="${ver//.}0";
    fi;
    if [ "$iteration" ]; then
      echo -ne "\033[1m\n*** Update Magisk module version code ($modcode -> $newmodcode) (y/n)? \033[0m";
      read n; echo;
      case $n in
        Y|y) ;;
        *) skipmodprop=1;;
       esac;
    fi;
    if [ ! "$skipmodprop" ]; then
      sed -i -e "s/version=.*/version=$newmodver/" -e "s/versionCode=.*/versionCode=$newmodcode/" $magisk/UPDATE-Busybox.Installer.*-ALL/module.prop;
    fi;
    
    bold "- Packing \"Busybox-$ver-ALL.zip\" ...";
    cd $magisk/UPDATE-Busybox.Installer.*-ALL;
    zip -9 -x .git -r $zipflag "$home"/Busybox-$ver-ALL.zip *;
    curdir=$(basename $PWD);
    cd ..;
    if [ "$curdir" != "UPDATE-Busybox.Installer.v$ver-ALL" ]; then
      mv UPDATE-Busybox.Installer.*-ALL UPDATE-Busybox.Installer.v$ver-ALL;
    fi;
    
    cd "$home";
    bold "- Signing as \"UPDATE-Busybox.Installer.v$ver-ALL-signed.zip\" ...";
    java -jar zipsigner-*.jar Busybox-$ver-ALL.zip Busybox-$ver-ALL-signed.zip;
    mv -f Busybox-$ver-ALL-signed.zip UPDATE-Busybox.Installer.v$ver-ALL-signed.zip 2>/dev/null;
    rm -f Busybox-*-ALL.zip /tmp/signAPK*.tmp 2>/dev/null;
    64
    Here we go again!

    Gotta say, I'm pretty gobsmacked at the 16,252 downloads of my busybox zip in the last month and a half (and that's not counting via Magisk), the 20,966 downloads of my sdcard Fix Permissions script zip and then there's the 158,506 downloads of unSU! :cyclops:

    Thanks for the continued support all! I guess I should sit down and figure out how to write an app or something, huh? ;)

    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!

    10-extract-lineage-kernel.sh:
    - update for new /data/lineageos_updates location

    UPDATE-adb.Installer.v1.0.36-signed.zip;
    UPDATE-nano.Terminal.Editor.v2.8.7-signed.zip:

    - create magisk.img if needed (e.g. clean recovery flash of Magisk 14+)
    - possible fix for stuck Magisk module update message on some devices by ensuring install is to magisk_merge.img
    - bump Magisk template version to 1400

    UPDATE-Adreno.Systemless.Installer-signed.zip:
    - mount /system (ro) in case we need it for e2fsck (e.g. FlashFire)
    - fix su.d script with BINDSBIN SuperSU
    - create magisk.img if needed (e.g. clean recovery flash of Magisk 14+)
    - possible fix for stuck Magisk module update message on some devices by ensuring install is to magisk_merge.img
    - bump Magisk template version to 1400

    UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip:
    - create magisk.img if needed (e.g. clean recovery flash of Magisk 14+)
    - fix forced system installation with BINDSBIN SuperSU
    - possible fix for stuck Magisk module update message on some devices by ensuring install is to magisk_merge.img
    - bump Magisk template version to 1400

    UPDATE-CMSetup.Fix.For.GApps.Installer-signed.zip:
    - update installer to latest versions of set_perm and set_perm_recursive from my Complete Shell Zip Documentation
    - add support for Magisk post-fs-data.d and BINDSBIN SuperSU su.d

    UPDATE-Nexus.Media.Installer-signed.zip:
    - mount /system (ro) in case we need it for e2fsck (e.g. FlashFire)
    - fix su.d script with BINDSBIN SuperSU
    - fix Magisk bootanimation restoration script install
    - add cleanup script for Magisk workarounds when uninstalled
    - create magisk.img if needed (e.g. clean recovery flash of Magisk 14+)
    - fix forced system installation with BINDSBIN SuperSU
    - possible fix for stuck Magisk module update message on some devices by ensuring install is to magisk_merge.img
    - bump Magisk template version to 1400

    UPDATE-sdcard.Fix.Permissions-signed.zip:
    - update installer to latest versions of set_perm, set_perm_recursive and restore_con from my Complete Shell Zip Documentation
    - remove MultiROM paths support since these vary per device and version, better handled by reflashing the MultiROM zip and secondaries

    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

    AnyKernel2 has also seen some improvements in the last few weeks, and GN Synapse Injector AK2 zip has been updated accordingly. If your custom kernel of choice uses an AK2 zip or you have ever enjoyed a kernel packaged with it then please go thank my AnyKernel2 thread OP, it's still not even on my member profile's Most Thanked threads, despite being my most known project. :):good: