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

Search This thread

tres_linguas

Senior Member
Apr 27, 2017
211
36
They're just whatever the zip reported when it failed. It shouldn't flash "*.zip" though, that's weird. I've never seen that before.

Can you show me the contents of the directory? And the zip? You should try enabling verbose and logging to see what's going on with the flashing as well, and show me that.
I attached both.
Its gettin strange: I deleted the FlashAfterUpdate folder in main storage so only the one in /data remained. Flashed the Rom again, but this time manually (not through updater app). Now it worked. Dont know what caused this.
What is also strange:
- the deleted folder was automatically restored
- in both folders a 'disabled' folder was created automatically (see screenshot)
[EDIT I just had a closer look at the script and realized the Behavior of the two points above is intentional]
- although I have a verbose file, too, no output of the zip can be found in it (still empty file) [EDIT I'm attaching the relevant part of orange fox recovery log file so you can also see the output of the zip]

Well, in spite of the stuff I don't understand, seems that it works now. Thanks for your answer, anyways 🙂👌🏻
 

Attachments

  • Screenshot_20210419-203249_FX~2.png
    Screenshot_20210419-203249_FX~2.png
    44.1 KB · Views: 36
  • fp2sleep_gary.zip
    128.9 KB · Views: 12
  • log.txt
    1.4 KB · Views: 6
Last edited:
  • Like
Reactions: osm0sis

Spaceminer

Senior Member
Sep 9, 2016
1,232
599
Olympus Mons
Moto E (2020)
@osm0sis

I just wanted to let you know that the most recent magisk adb-ndk works perfectly with the fastbootd that's used in Orange Fox and TWRP. I've been able to unlock the bootloader, and flash custom roms on 3 different devices without any issues via OTG. Stock firmware can also be flashed. I haven't had a PC in 8 months and this has been a blessing to me.

Edit: It also works with stock fastboot and fastbootd! I just tested it.
 
Last edited:
Mar 26, 2021
9
3
Here's a fresh unstripped build in case it's still of use for debugging the issue you're seeing on your device. Let me know what you figure out! :)
Thank you very much! However so far I have just seen that SIGSEGV was triggered here https://git.busybox.net/busybox/tree/networking/netstat.c?h=1_31_1#n468 (call stack was something like strlen/printf/print_inet_line/...)

Maybe I still have to build selinux-enabled binary on my own, otherwise I won't be sure whether this issue is fixed.
 
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
  • Mar 14, 2012
    14,588
    32,851
    Halifax
    GT-i9250
    Nexus 7 (2013)
    Well! Lots done and lots to do. Hope everyone's doing well out there!

    An updated Payload-Dumper-Go Magisk Module resolving out-of-memory issues has been added to its previous post and linked in the OP. The instructions I worked out for retaining passing SafetyNet on Incremental Google OTA Virtual A/B devices has been linked in the Knowledge Base post as well.

    For more on the "Diffusion Installer Backend updates" see any of my module GitHub commit histories, e.g. https://github.com/Magisk-Modules-Repo/busybox-ndk/commits/master (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!

    98-twrp_ab.sh:

    - add support for latest Magisk AVBv1 BootSigner changes

    UPDATE-adb.Installer.v1.0.41-signed.zip;
    UPDATE-Adreno.Systemless.Installer-signed.zip;
    UPDATE-mtd-utils.Installer.v2.1.2-signed.zip;
    UPDATE-Nexus.Media.Installer-signed.zip;
    UPDATE-ZipSigner.Installer.v3.0-signed.zip:

    - Diffusion Installer Backend updates

    UPDATE-Busybox.Installer.v1.32.1-ALL-signed.zip:
    - update to latest busybox stable official source
    - Diffusion Installer Backend updates

    UPDATE-FlashIt.Installer.v3.8-signed.zip:
    - update busybox binary (1.32.1) with the latest patches and fixes from my repo
    - Diffusion Installer Backend updates

    UPDATE-nano.Terminal.Editor.v5.7-signed.zip:
    - update to latest nano official source
    - Diffusion Installer Backend updates

    TWRP_A_B_Retention_Script-Magisk(1).zip and AnyKernel3 have also seen some more improvements for the latest Magisk, and an Android Image Kitchen v3.8 release with boot_img_hdr_v3 and vendor_boot support will be incoming soon once I finish regression testing. Download TWRP A/B Retention Script again from the repo in the Magisk app to obtain the new version. 👌
     
    Last edited:

    rodken

    Senior Member
  • Jan 11, 2010
    446
    93
    Google Pixel XL
    OnePlus 8
    Here's another quick and dirty Magisk module. I don't intend to regularly upkeep it or directly attach it to the OP, but wanted to provide it for any like myself who might find it useful!

    Basically Google gatekeeps a number of Nexus/Pixel/Android One features and apps behind .xml entries, but since the OnePlus 8T switched to Google Dialer and Messages and I didn't need the full Google Dialer Framework module anymore this meant I lost access to things like Google's Recorder app, so I wanted to try a slimmer approach to get them back.

    I just extracted a bunch of .xmls from various Factory Images and compiled them all into one .xml called google_experience.xml (to not conflict with any real ones), and dumped it into a module. There are other modules that bundle similar .xmls but they either a) have a ton of other stuff like APKs, JARs, fonts, etc. or b) have a ton of other .xml files from other non-Google OEMs which I don't care at all about.

    Manually force-stop Play Store and clear its app data a couple times after installing and rebooting, then open Play Store again to see an effect.

    So here we are! The version is the release date of the Pixel 5 since that's the last device I pulled updated .xml files from. ;)(y)
    Can you provide a short list of what Nexus/Pixel/Android One features and apps this module provides?
     

    lebigmac

    Senior Member
    Jan 31, 2017
    745
    400
    Hi @osm0sis thanks for sharing your great tools with the open source community.

    Could you please tell me what could be causing unknown error 255 in this screenshot? It doesn't seem to be caused by my update-binary itself. I know that error 255 in bash is equivalent to -1 in c++

    Do you think it could have anything to do with the missing digest file? This error doesn't seem to occur in recoveries that have the ability to skip the digest file check.

    Could you please share a default digest file template with me? I've got no clue what a TWRP digest file is supposed to look like and more information about it is scarce online.
    Thank you for your assistance. Keep up the great work!

    error_255.jpg
     
    Last edited:

    osm0sis

    Senior Recognized Developer / Contributor
  • Mar 14, 2012
    14,588
    32,851
    Halifax
    GT-i9250
    Nexus 7 (2013)
    Can you provide a short list of what Nexus/Pixel/Android One features and apps this module provides?

    The ones I know/care about are kinda already mentioned: you get access to the Recorder app, and Photos app extra "Pixel exclusive" features. Dialer back when it wasn't widely rolled out. I'm sure there are more apps and features which I haven't noticed. Report back if you find any. 😉

    Hi @osm0sis thanks for sharing your great tools with the open source community.

    Could you please tell me what could be causing unknown error 255 in this screenshot? It doesn't seem to be caused by my update-binary itself. I know that error 255 in bash is equivalent to -1 in c++

    Do you think it could have anything to do with the missing digest file? This error doesn't seem to occur in recoveries that have the ability to skip the digest file check.

    Could you please share a default digest file template with me? I've got no clue what a TWRP digest file is supposed to look like and more information about it is scarce online.
    Thank you for your assistance. Keep up the great work!

    View attachment 5303953
    A Digest file is just a .md5 or .sha2 file with the checksum of the zip in question.

    The only TWRP that "enforced" the Digest check was 3.5.1 I believe, and that was a bug, and why we got 3.5.2 so quickly.

    You could still work around it by going into settings and disabling Digest Verification of backups (since the options were also erroneously tied together).

    No promises that's what your actual issue is, however, since what you really need to post is the /tmp/recovery.log, not a screenshot, to maybe have more of an idea what's going on with a zip error.
     
    Last edited:

    HippoMan

    Senior Member
    May 5, 2009
    1,714
    551
    Hippoland
    I want to find the mapping of my /dev/block partitions into the standard names of /data, /system, /boot, and /vendor.

    On my device, there are system_{a,b}, boot_{a,b}, and vendor_{a,b} in /dev/block/by-name, and I think it's clear that these are mapped to /system, /boot, and /vendor. However, I don't know what items in /dev/block/by-name would end up being mapped to /data.

    Is there some way to determine, on any given device, what exact items that are listed in /dev/block/by-name (or the particular device's equivalent directory) would be mapped to /data, /system, /boot, and /vendor?

    The reason i want to know this is because I want to write my own dd-based backup and restore scripts that can take the place of TWRP's nandroid backup and restore. I want this because TWRP isn't working under Android 11 in many cases, and I'd like to be able to do the equivalent of nandroid backup/restore under A11.

    Thank you for any tips and pointers.
     
    • Like
    Reactions: lebigmac

    DiamondJohn

    Recognized Contributor
  • Aug 31, 2013
    5,227
    4,849
    Sydney
    I want to find the mapping of my /dev/block partitions into the standard names of /data, /system, /boot, and /vendor.

    On my device, there are system_{a,b}, boot_{a,b}, and vendor_{a,b} in /dev/block/by-name, and I think it's clear that these are mapped to /system, /boot, and /vendor. However, I don't know what items in /dev/block/by-name would end up being mapped to /data.

    Is there some way to determine, on any given device, what exact items that are listed in /dev/block/by-name (or the particular device's equivalent directory) would be mapped to /data, /system, /boot, and /vendor?

    The reason i want to know this is because I want to write my own dd-based backup and restore scripts that can take the place of TWRP's nandroid backup and restore. I want this because TWRP isn't working under Android 11 in many cases, and I'd like to be able to do the equivalent of nandroid backup/restore under A11.

    Thank you for any tips and pointers.
    TeMeFI has a heap of partition info under Device Details>Partition Info and Device Details>Block Details
     

    HippoMan

    Senior Member
    May 5, 2009
    1,714
    551
    Hippoland
    TeMeFI has a heap of partition info under Device Details>Partition Info and Device Details>Block Details

    Thank you!

    Maybe I'm missing something, but I haven't found any info in TeMeFI's Partition Info or Block Details that will tell me which item(s) in /dev/block/by-name or /dev/block/mapper point to /data.

    I can do an ls -l in /dev/block/mapper from a root session in a terminal which says that dm-2 points to userdata. Is userdata what gets mapped to /data?

    And anyway, that is only specific to my device and the OS I'm running. Is there some programmatic method that will work on any Android device to figure out how the /dev/block stuff gets mapped to the standard partitions such as /data, /system, /boot, /vendor, etc. on that device? Or does this have to be done manually, by inspection, on every device? Maybe inspection is the only way, and if so, that would explain, in part, why there is not a generic TWRP that runs on all devices.
     
    Last edited:

    BillGoss

    Senior Member
    Sep 2, 2010
    4,568
    3,968
    Sydney
    OnePlus 3T
    OnePlus 8T
    I want to find the mapping of my /dev/block partitions into the standard names of /data, /system, /boot, and /vendor.

    On my device, there are system_{a,b}, boot_{a,b}, and vendor_{a,b} in /dev/block/by-name, and I think it's clear that these are mapped to /system, /boot, and /vendor. However, I don't know what items in /dev/block/by-name would end up being mapped to /data.

    Is there some way to determine, on any given device, what exact items that are listed in /dev/block/by-name (or the particular device's equivalent directory) would be mapped to /data, /system, /boot, and /vendor?

    The reason i want to know this is because I want to write my own dd-based backup and restore scripts that can take the place of TWRP's nandroid backup and restore. I want this because TWRP isn't working under Android 11 in many cases, and I'd like to be able to do the equivalent of nandroid backup/restore under A11.

    Thank you for any tips and pointers.
    The mount command will show you what's mounted and where.
    Backing up /data is problematic because:
    1. It's encrypted, and
    2. It also includes the user data (/data/media/0 aka /sdcard)
     
    • Like
    Reactions: ipdev and osm0sis

    HippoMan

    Senior Member
    May 5, 2009
    1,714
    551
    Hippoland
    The mount command will show you what's mounted and where.
    Backing up /data is problematic because:
    1. It's encrypted, and
    2. It also includes the user data (/data/media/0 aka /sdcard)

    Thank you again. I have already looked at mount, both from the command line and also in TeMeFI. And now I see that I had overlooked the /dev/block/dm-2 => /data mount from both of those sources.

    And now I understand better why /data can be problematic. I am perfectly happy to back up and restore /sdcard, but the encryption/decryption will indeed be a challenge. But maybe I can figure it out.
     

    HippoMan

    Senior Member
    May 5, 2009
    1,714
    551
    Hippoland
    And now I understand better why /data can be problematic. I am perfectly happy to back up and restore /sdcard, but the encryption/decryption will indeed be a challenge. But maybe I can figure it out.

    Hmm ... maybe /data isn't so problematic, after all. If I do the following (given that dm-2 maps to /data) ...
    dd if=/dev/block/dm-2 of=./foobar
    ... will the following work later on to restore /data?
    dd if=./foobar of=/dev/block/dm-2

    I don't care that the foobar file would contain encrypted data, as long as I can successfully write it back to /dev/block/dm-2 at a later date.
     

    BillGoss

    Senior Member
    Sep 2, 2010
    4,568
    3,968
    Sydney
    OnePlus 3T
    OnePlus 8T
    Hmm ... maybe /data isn't so problematic, after all. If I do the following (given that dm-2 maps to /data) ...
    dd if=/dev/block/dm-2 of=./foobar
    ... will the following work later on to restore /data?
    dd if=./foobar of=/dev/block/dm-2

    I don't care that the foobar file would contain encrypted data, as long as I can successfully write it back to /dev/block/dm-2 at a later date.
    I personally wouldn't try that. I've always thought that the dm* partitions weren't actual, physical partitions. It seemed to me that they were dynamic partitions created on the fly.
    But, I may be wrong.
     

    DiamondJohn

    Recognized Contributor
  • Aug 31, 2013
    5,227
    4,849
    Sydney
    Thank you again. I have already looked at mount, both from the command line and also in TeMeFI. And now I see that I had overlooked the /dev/block/dm-2 => /data mount from both of those sources.

    And now I understand better why /data can be problematic. I am perfectly happy to back up and restore /sdcard, but the encryption/decryption will indeed be a challenge. But maybe I can figure it out.
    And I understand that you already know this, but for others, TeMeFI's mounts command is a simple toybox mounts command.
    Hmm ... maybe /data isn't so problematic, after all. If I do the following (given that dm-2 maps to /data) ...
    dd if=/dev/block/dm-2 of=./foobar
    ... will the following work later on to restore /data?
    dd if=./foobar of=/dev/block/dm-2

    I don't care that the foobar file would contain encrypted data, as long as I can successfully write it back to /dev/block/dm-2 at a later date.
    If you are trying to backup your data partition (off your phone) using a script, could you not use pull commands to get each individual files (unencrypted) and a ls -l -R to get the permissions, ownership and group info.

    I would also investigate if you tar the files into a single tar file (part of toybox), that tar file would be un-encrypted, when pulled off the device. I think the tar file would also have the permissions etc stored in the file. Kinda like a live TWRP process. Looking at the GuitHub of TWRP may give you an in-road; even may help with determining the partitions you are interested in.
     

    HippoMan

    Senior Member
    May 5, 2009
    1,714
    551
    Hippoland
    The problem with trying to use the basic tar command for Android backups is it loses capabilities, I think SELinux contexts, and possibly other things. TWRP uses a special updated libtar for backups which keeps all of that important extra info.
    Thank you very much. I'd love to get my hands on that libtar! I'm going to the TWRP github to see if I can find it.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 3
      Thanks. Will check it out.

      Also hypothetically, I am wondering if this process should also work?

      - Uninstall magisk via the app
      - Restart to ensure, I'm unrooted and then do an OTA incremental update to the latest one
      - After the OS has been upgraded, follow the steps to root the boot dump file using fastboot and the broken twrp for Oneplus 8T

      2 things I'm worried about are -
      1) if I uninstall Magisk via the app, does it fully unroot and allows incremental OTA?
      2) will the broken twrp for Oneplus 8T be compatible with the latest OOS 11.0.8.13?

      Thanks!

      @rezapatel I was doing so for quite some time with my pixel 3a ... there is only one disadvantage with unrooting / taking the OTA and rooting again:
      for the time you are unrooted SafetyNet will fail / apps (especially bank apps) may detect that and cache that imformation. This may lead to failing apps even if you root again later ...

      That's why my method then uses airplane mode to avoid SafetyNet ever "seeing" you were briefly unrooted.👌

      My instructions post already says all this. 😛

      It requires flashing it via recovery, unfortunately, no working twrp for the 8T..

      You can flash it in the Magisk app as well using the manual install button on the Modules page. 😉
      1
      @rezapatel I was doing so for quite some time with my pixel 3a ... there is only one disadvantage with unrooting / taking the OTA and rooting again:
      for the time you are unrooted SafetyNet will fail / apps (especially bank apps) may detect that and cache that imformation. This may lead to failing apps even if you root again later ...
      1
      Uh, yes, makes sense .. but I'm ok with that, even if I have to wipe the dalvik/cache once after rooting. Thanks for giving me the confidence to attempt it :)

      Yep, worked like a charm! :)
      1
      I was kind of annoyed I couldn't change the default alarm tone in OxygenOS on my OP5T, so..

      Code:
      set_alarm() {
        local alarmid alarmuri rebootmsg curuser curalarm;
        if [ "$1" ]; then
          alarmid=$(echo "u:r:shell:s0" > /proc/self/attr/current; content query --uri "content://media/external/audio/media" | grep $1 | grep -oE " _id=([0-9]+)," | grep -oE "[0-9]+");
          if [ "$alarmid" ]; then
            alarmuri="content://media/external/audio/media/$alarmid";
          else
            alarmid=$(echo "u:r:shell:s0" > /proc/self/attr/current; content query --uri "content://media/internal/audio/media" | grep $1 | grep -oE " _id=([0-9]+)," | grep -oE "[0-9]+");
            test "$alarmid" && alarmuri="content://media/internal/audio/media/$alarmid";
          fi;
          if [ "$alarmuri" ]; then
            $(echo "u:r:shell:s0" > /proc/self/attr/current; settings put system alarm_alert $alarmuri >/dev/null);
            if [ "$?" != 0 ]; then
              rebootmsg=" Reboot for effect.";
              curuser=$(dumpsys activity | grep CurrentUser | cut -d= -f2);
              curalarm=$(grep 'name="alarm_alert"' /data/system/users/$curuser/settings_system.xml | grep -oE 'value=.*$' | cut -d\" -f2);
              sed -i "s;alarm_alert\" value=\"${curalarm};alarm_alert\" value=\"${alarmuri};" /data/system/users/$curuser/settings_system.xml;
            fi;
            echo "Alarm changed to \"$1\"; \"$alarmuri\".$rebootmsg";
          else
            echo "Alarm \"$1\" not found!";
            return 1;
          fi;
        else
          curalarm=$(settings get system alarm_alert);
          echo "Alarm currently \"$(echo "u:r:shell:s0" > /proc/self/attr/current; content query --uri "$curalarm" | grep -oE " _display_name=.*" | cut -d, -f1 | cut -d= -f2)\"; \"$curalarm\".";
        fi;
        return 0;
      }

      The settings command mysteriously only works via ADB shell on the OP5T, not from a Terminal Emulator app, so there's a fallback to hack the settings xml directly.

      Use (from root prompt): set_alarm <filename>
      E.g. set_alarm interesting.ogg
      Or even
      set_alarm interesting

      I know OOS isn't the only OEM stock ROM out there making this weird choice for users, but you'd think OnePlus would be more on the ball as an enthusiast brand.. :confused:

      Edit: Updated for the content command only working in ADB shell (at least on Pie), resolved by context switching in subshells. Working on my OP6T via Terminal Emulator at a su prompt now. Probably fixes the settings command issue from before too. :cool::good:
      Edit 2: Fixed found external content id being used with internal uri. :eek:
      @osm0sis you just fixed a super annoying issue for me. Thank you!!!
    • 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 or OP8Pro/T (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.
      • 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.
      228
      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.
      156
      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!
      109
      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: