yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] rignfool:
First... That's backwards thinking...

Second... You can wipe them in recovery... Since you're going there to flash anyway?
[Android Software/Hacking General [Developers Only]] SuperR.:
Thank you very much, I will add the new Busybox in the next update :)

About AIK...I would like to use it instead of what I use now in the kitchen to unpack all boot.img/recovery.img/kernel.elf. You are much better at keeping up with it, and I am already using your tools anyway lol. Is there ever any reason to run it as root? I am currently unpacking/repacking as root if the rom is Marshmallow or higher, but it would be nice not to need to do this. Thanks again for all your hard work :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Nice! Thanks! [MENTION=357342]tobias.waldvogel[/MENTION] developed unpackelf and was able to expand the support very nicely to cover all kernel.elf files I threw at him, but then he disappeared. I'm hopeful he'll return, or at least that it'll be fairly future proof.. since while I learned a lot about kernel.elf in working on unpackelf after his departure, and do think I was able to improve it as well, there's still a lot I don't know. For example certain kernel.elf files have unpacked kernel parts which need gzipping and dtb appended to it before repacking as boot.img, while others are already gzipped and can have the dtb in its own section like the standard boot.img. Crazy stuff like that I looked for cues from tobias' work to implement.

I agree, it would be nice to be able to work without root, but Linux with root is the only platform that can properly unpack and repack with cpio and retain the proper permissions/ownership; mkbootfs can handle a lot on the repack side, but you still can't even unpack 000 permissioned .dotfile hidden folders and files (like Chainfire uses in .subackup) correctly on Linux without root. mkbootfs also doesn't contend with possible OEM files I haven't added to fs_config yet, while cpio can. So root and Linux is still the best way to go to diminish the chance of any issues across all devices.
[Android Software/Hacking General [Developers Only]] blueyes:
[MENTION=4544860]osm0sis[/MENTION] , I just felt the need to thank you for all of your work. I'd say hard work but this pure talent than is probably easy for you. I have been building bliss officially as well as other side projects, often using my phone. And without Juicessh, and your scripts (too many to list), my mobile on-the-go building wouldn't be possible.

I do have one request. ?. Adding the "system_root" as a mountpoint for these darn pixels. Lol
[Android Software/Hacking General [Developers Only]] osm0sis:
How do you mean? In recovery Pixel gets mounted as /system and so /system/system is where the usual system tree is, and I have my zips push to there instead.

What zips are you talking about specifically and what's the issue?
[Android Software/Hacking General [Developers Only]] blueyes:
I can't think of any of your zips that failed to flash. The only issue I've had was the zip looking for BusyBox in. system/xbin when it's actually in su/xbin. And it wasn't one of yours. I jumped the gun on that one. Blame it on a long day at work. ?.
[Android Software/Hacking General [Developers Only]] smeejaytee:
Hi guys could someone tell please adjust script line I would need to edit backlight dimmer found in sys/backlight_dimmer please
[Android Software/Hacking General [Developers Only]] osm0sis:
Depends on your device. Ask in your kernel or ROM thread.
[Android Software/Hacking General [Developers Only]] smeejaytee:
Done it, it was actually quite simple lol
[Android Software/Hacking General [Developers Only]] Regionella:
I installed busybox and magisk manager. and my root has gone. i flashed supersu zip file again with twrp, but it didn't work. i can't do root my oneplus 3t again. please help me.
[Android Software/Hacking General [Developers Only]] nathanchance:
You're in the wrong thread. Either use the Magisk support thread or the appropriate SuperSU thread.
[Android Software/Hacking General [Developers Only]] m0han:
editing build.prop prior to first boot of new rom

there are 2 lines in build.prop of the rom i use that i wanna change (prior to first boot) as:

ro.sf.lcd_density=* (* being 400)

ro.qc.sdk.audio.fluencetype=* (* being none)

how can i achieve this using nano Terminal Editor Installer? do i need to have aroma file manager working? please list the procedure - and commands, if any. the recovery on my usual device is twrp v3.0.3-3. thanks.
[Android Software/Hacking General [Developers Only]] _that:
You can run the editor from TWRP's terminal, or via adb shell.
[Android Software/Hacking General [Developers Only]] m0han:
i was looking for the commands to be executed from the terminal. thanks. :fingers-crossed:
[Android Software/Hacking General [Developers Only]] osm0sis:
Flash the zip during the recovery session you want to edit.

Then `mount /system` and `nano /system/build.prop`
[Android Software/Hacking General [Developers Only]] VincentJoshuaET:
Is the CMSetupFix still working on LOS 14.1?
[Android Software/Hacking General [Developers Only]] osm0sis:
Shouldn't be necessary anymore on LOS.
[Android Software/Hacking General [Developers Only]] smeejaytee:
Can I ask why you want to set fluence to 0

Also you could use tweak prop method to flash them to build prop on initial flash
[Android Software/Hacking General [Developers Only]] m0han:
i know; that's what i'm doing on 2 of 3 devices i get to play with. but, tweak.prop does not work on 1 device. the reason i set fluence to none is i get no in-call audio on nitrogen-os. the alternate workaround is to flash a newer firmware, which i'm vary about.
[Android Software/Hacking General [Developers Only]] smeejaytee:
Oic fishing firmware is usually safe enough though
[Android Software/Hacking General [Developers Only]] laggardkernel:
Line 22 of sbin/nano in UPDATE-nano.Terminal.Editor.v2.7.4-signed.zip,

test $mnt == /magisk && magisk=/nano/system;

The directory for Magisk installation should be /magisk/nano-ndk/system, which you use in the update-binary script.
[Android Software/Hacking General [Developers Only]] smeejaytee:
Can anybody please point me in the direction of a script to set internal swap please
[Android Software/Hacking General [Developers Only]] osm0sis:
I just downloaded the one from the OP and it says magisk=/nano-ndk/system, so you must have an old version? Download again. :good:
[Android Software/Hacking General [Developers Only]] laggardkernel:
Sorry, I guess I didn't make it clear. What I mean is that the directories for Magisk module installation in sbin/nano and /META-INF/com/google/android/update-binary are different. The module will be installed in /magisk/nano-ndk. While the nano script put in /sbin, which is purported to be used in recovery mode, tries to find it in /magisk/nano.
[Android Software/Hacking General [Developers Only]] osm0sis:
Aha! You did say "sbin/nano" but I missed it when I read your post before. I missed that change when I renamed the magisk install directory as well. Good eye and thanks!
[Android Software/Hacking General [Developers Only]] osm0sis:
Some quick fixes!

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

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

- fix recovery shell wrapper on Magisk installs

UPDATE-Flashlt.Installer.v2.6-signed.zip:

- update busybox binary (1.26.2) with my latest build

- add /system/system (Pixel) and basic Magisk (installs to /magisk/flashіt/system/bin) support to installer

- add --uninstall argument to flashіt shortcut to automate package removal
[Android Software/Hacking General [Developers Only]] czecx:
When I try to run "adb devices" I get the error (follow the screenshot)

Any chance to run/fix it?

I try to run it on Nexus 5x with 7.1.1 on board and systemless root.
[Android Software/Hacking General [Developers Only]] osm0sis:
I can't reproduce that on my hammerhead or flo.

Did you use my installer? It includes a wrapper to work around this sort of stuff.
[Android Software/Hacking General [Developers Only]] Surge1223:
Because the adbd server is already in use.

try to stop/close connection first via

stop adbd
[Android Software/Hacking General [Developers Only]] folusmile:
Will Adb installer work on superSu system mode?
[Android Software/Hacking General [Developers Only]] osm0sis:
Read the blurb in the OP and follow the linked info... yes, it will install to /system/xbin/.
[Android Software/Hacking General [Developers Only]] czecx:
Have tried it and unsuccessful, after enter adb devices command I get the same error.

---------- Post added at 08:43 AM ---------- Previous post was at 08:41 AM ----------

Yes of course, I use your installer.

I just install your zip, reboot to system, open the terminal and type:

su

adb devices

And get the error
[Android Software/Hacking General [Developers Only]] osm0sis:
Well, I'm not sure why, but it seems your ROM/shell doesn't correctly set TMPDIR=/data/local/tmp in its environment. Thanks for the report!

I'll add it to the exports in the wrapper for my next update. You can set that first to work around it until then. :):good:
[Android Software/Hacking General [Developers Only]] czecx:
I will waiting for your update.thanx!
[Android Software/Hacking General [Developers Only]] osm0sis:
Fix more things?! Okay!

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

UPDATE-adb.Installer.v1.0.36-signed.zip:

- add new workaround to adb wrapper to export TMPDIR on ROMs/shells that somehow don't already have this set

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

- update to latest nano official source

UPDATE-Adreno.Systemless.Installer-signed.zip:

- add basic Magisk (installs to /magisk/adreno-dev/system/vendor) support to installer

UPDATE-Nexus.Media.Installer-signed.zip;

UPDATE-Flashlt.Installer.v2.6-signed.zip:

- reuploaded with Magisk directory creation fixed

AIK v2.6 (Android Image Kitchen, AIK-mobile and AIK-Linux) was released today adding ChromeOS support (which required getting futility and libcrypto_static to cross-compile!), Bump/SEAndroid footer support and many fixes, and then I brought the same to AnyKernel2. GN Synapse Injector Addon zip saw another minor update to bring the latest AK2 commits to it, and I had a little bit of fun getting [MENTION=2633638]Ziyan[/MENTION]'s excellent AOSP Nougat "Unlegacy" 7.1 builds for the Galaxy Nexus booting today. ;)

Edit

: Just reuploaded nano with the correct updated version number in Magisk's module.prop. :good:
[Android Software/Hacking General [Developers Only]] gr-e:
Can't get my zip to work with 99-flashafterupdate.sh script.

I have another zip with bootanimation in the FlashAfterUpdate folder and it works just fine, no matter if it's flashed before or after my zip.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah, addon.d isn't meant to work this way, it's a pretty big hack, so I've always said your mileage may vary..

You can try to increase or decrease the "sleep 5" on line 35 of the script and see if that helps. Try 2 seconds, or try 10 seconds.
[Android Software/Hacking General [Developers Only]] folusmile:
Can I use nano terminal on my note 4
[Android Software/Hacking General [Developers Only]] blueyes:
[MENTION=4544860]osm0sis[/MENTION], aka shell scripting genius.. Have you attempted to get Synapse ,UKM , working with the Pixels? I've gotten the UKM installed but not familiar with the necessary kernel requirements. Files all placed correctly, with proper permissions, yet Synapse persists on telling me UKM isn't installed. Is it a BusyBox issue, or do I possibly need to adjust the app to reflect the UKM or BB location? Bind or symlink? Kernel requirements? Or am I just pissing in the wind here. Lol Ive managed to get quite a bit of things working with a little script modifications but UKM -Synapse has me puzzled. So I'm swallowing my pride gracefully, lol, and wanted your input. Expert opinion time... If anyone can answer this, I am sure you can.

I do development, officially and unofficially, so I'm not completely stupid, I'm just not carrying the talent that the like of you , dees-troy and chainfire, etc have. ?

Also, what's the best way or proper addition to the installation script on these dual partition devices. Seems like it does what it feels like. I've used the same scripting and had it install in /system/app and other times it creates a new directory in system_root/app. Instead of /system/system_root/system/app. There shouldn't be any app or priv-app directories in system_root as far as I'm aware. Anyway, I'll be patiently waiting for your solution. ?
[Android Software/Hacking General [Developers Only]] osm0sis:
I appreciate your kind words, but really I shouldn't be in the same sentence as Chainfire and Dees! :o

I thought UKM worked from /data and I doubt it's built to work well from /system. My best guess is SELinux denials.. try adb logcat | grep 'avc: denied' directly after boot. You also need something to run the uci service.. so rooted Pixel should have a boot directory in the ramdisk in which you can make that change.

From what I've seen, for installing to system via recovery, the way to go is to just mount /system and then put things in /system/system. To cover both I have something like this:

mount /system;
test -f /system/system/build.prop && root=/system;
target=$root/system/app;

Also, maybe check this out and report your issues here if they persist with their updated fork:

https://xdaforums.com/android/software/zip-ukm-reborn-unified-t3558888
[Android Software/Hacking General [Developers Only]] blueyes:
I'll recreate what I did, but after installation the UCI command run from the terminal. It's the app that's not cooperating. It is an older app that's probably not been updated in a while so I thought may need some help with the new partitions. I'll grab a log.

The issues with apps installing in /system_root/app priv-app have occurred while modifying V4A and TBO gapps. They all use the updater-script, unlike your installation thru the binary file. Which works better. I assume it's because its installing more so as a shell script in twrp which plays best w these AB slotted devices? Rather than an updater script. Updates sometimes wanna flash to the opposite slot. Still learning the ins and out involved there. Not difficult, but different, esp this old dog having to learn new tricks. Lol
[Android Software/Hacking General [Developers Only]] blueyes:
[MENTION=4544860]osm0sis[/MENTION] , i got the TBO Gapps to install but need your scriptpertise. Made the zip straight from my phone, but it wants to creat a new directory in system_root/app, instead of system/app or system/system/app. If you don't mind. I'll link you to the folder, I zipped up the Meta folder as well so you won't have to dload the full zip.

https://is.gd/lFBdmN
[Android Software/Hacking General [Developers Only]] osm0sis:
They use EDIFY and have no support for the Pixel /system/system layout in their updater-script. These GApps don't have anything to do with me.. please report the issues to the creator of the GApps package? :confused:

As for UKM, pretty much the same deal; I linked you to a currently maintained fork, use that and report the issue for them to fix. :good:
[Android Software/Hacking General [Developers Only]] blueyes:
Oh I'm sorry, I realize your not involved with the Gapps. I just wanted your help fixing the script. Lol

Sorry.

---------- Post added at 03:03 AM ---------- Previous post was at 03:00 AM ----------

[MENTION=4544860]osm0sis[/MENTION], I got UKM working btw. Didn't mean to imply anything, I'm just really familiar with your scripting skills.
[Android Software/Hacking General [Developers Only]] Andycar:
ODEX scripts for LP, MM

In fact, I've been searching for the right dex2oat options to make odexed custom ROMs, and finally found it.

This work is based on the previous work of

osm0sis (https://xdaforums.com/showthread.php?t=2239421)

Droidzone (https://xdaforums.com/showthread.php?t=1091508)

Also, in the last script I borrowed some idea from [MENTION=2822871]Wolfbreak[/MENTION].

Thanks to them! That being said,

The installer puts 5 files into /system/xbin and makes them executable

mkboot (script)

odex (script)

dex2oat_system_apk.sh (script)

zipalign (binary)

zip (binary)

How I run these tools to make odexed LP ROM? It's simple.

You have two choices to run dex2oat in the fully stup environment of paths and libs.

Firstly, these scripts could be ran from adb shell after issuing command "stop zygote" in ADB shell,

After odexing was done, one can issue the "start zygote" command or reboot normally.

It's not he fastest or cleanest way, so I prefer the second method.

Another method is to make it in "offline/charging" mode. This requires permissive adbd.

I'm running odexing script in offline (on-charger environment) using the amazing machinex kernel for Galaxy S4

by Robcore (https://xdaforums.com/galaxy-s4/i9505-develop/kernel-t3455219)

This kernel allows runing permissive adbd with mount and all other busbox utils at offline.charging state.

1). run 'mkboot' to assemble all classes in our $BOOTCLASSPATH into /system/framework/arm/boot.oat(art)

2) Run "mount -o remount,rw /system just make sure.

After that run odex /system/framework/*.jar to create rest odex in /arm

(!check that there is no zero-size .odex files made during this process!)

3). If you are in offline/charging more. Run these commands:

mkdir -p /data/dalvik-cache/arm

chmod -R 777 /data/dalvik-cache

chmod -R 777 /data/dalvik-cache/arm

chown 1000.1000 /data/dalvik-cache

chown 1000.1000 /data/dalvik-cache/arm

ln -sf /system/framework/arm/boot.art /data/dalvik-cache/arm/system@framework@boot.art

ln -sf /system/framework/arm/boot.oat /data/dalvik-cache/arm/system@framework@boot.oat

(If you are in "booting" mode with "stop zygote" , you don't need to make those links in /data)

After that, you can execute the final command, which is

"dex2oat_system_apk.sh"

This last script will odex the rest of the apk /system/app and /system/priv-app

That's all folks!

I'd ask for minimal credits when using these scripts in you ROMs. Thanks!

P.S. Currently, two Custom Samsung 5.0.x ROMs published here on XDA were odexed using these scripts and running normally (one is mine and other is well-known ROM for S4).
[Android Software/Hacking General [Developers Only]] jacomail95:
Thank you for your work, but I can't download this, on browser it says error 404, and XDA Labs refuses to download this file specifically, with any other file it works
[Android Software/Hacking General [Developers Only]] rignfool:
I love following this thread... But it's a little over my head...

You're saying that these files will allow on device odexing of any ROM? I assume the + refers to nougat but it is untested?
[Android Software/Hacking General [Developers Only]] Andycar:
Thanks for noting this error 404!

I changed the file name to the simple one (without funny symbols like "+" or ".") and there is no more download problems.

P.S. The previous file (named cwm-odex.Script.Installer—LP_MM+.zip) was downloaded more than 110 times, so all this is really strange)

---------- Post added at 07:08 AM ---------- Previous post was at 07:06 AM ----------

Exactly! I'm saying that you can run these three scripts and odex your LP ROM on the phone.

However, on MM the scripts are producing mixed results, and Nougat is my next target (not even started yet).
[Android Software/Hacking General [Developers Only]] osm0sis:
It's for the best anyway, that cwm- prefix needs to die. :p
[Android Software/Hacking General [Developers Only]] osm0sis:
Had some fun in the last few days ensuring my ROM GApps Auto-Integration script (AKA gappsintegrator) would work correctly on stock Nexus ROMs. These ROMs' system.img files often have minimal free space, which exposed a few edge cases, and required a couple additions. A failed final copy would for example result in it listed in the log as undergoing integration on each boot but the packages.xml would revert to the old system APK information, or, if it was an APK requiring the runtime-permissions.xml rebuild workaround, this issue would even result in a bootloop. :eek: ;)

Should be good for stock ROM + SuperSU setups now. :cowboy:

Remember this is still pretty experimental, so be sure to have a fresh nandroid before setting up the script. Results may vary from device to device or configuration to configuration, but for best results you should have the zip and zipalign binaries installed.

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

gappsintegrator: v10 - add failsafe precise total required space check, fix workarounds:

- fix runtime-permissions.xml backup/restore workaround for multiuser where by mistake the deletion was outside of the loop so only the highest numbered userfile found would get removed, breaking the workaround for all others

- add existence check for the runtime-permissions.xml file before running any actions as with a non-existent path basename and dirname could reduce to only *, which is of course scary

- add a final total required space check for the possibly deflated/possibly library-stripped, altered /data APK, and all other required files versus any /system counterparts, as the pre-integration file size could pass the initial estimate but fail the copy to system due to library inflation (noted in log with "**")

- modify remount and gappintegrator temporary working directory cleanup placement to accomodate the later post-work /data APK space check causing the old placement of these to be skipped

- when using proper Marshmallow+ zip/zipalign integration method check for any libraries along-side /system APKs and remove them since they are unnecessary and conflict with the newer ones inside the post-work /data APK, which most notably broke Chrome on stock Marshmallow

- reduce the free space estimate buffer numbers to allow some more through the faster check, since we've now got the failsafe precision free space check

- improve some script formatting and tag the endpoints of the larger if- and for-statements

https://github.com/osm0sis/gappsintegrator/commit/2eed3067cc3270febfb85255f926fc339c2bc1d5

Download via GitHub's raw copy of the latest version, or extract it from the repo zip. :good:
[Android Software/Hacking General [Developers Only]] Maxr1998:
I don't know if I did anything wrong (placed the script with the EXKM script manager, aka su.d), but I currently am dealing with a crap-ton of fcs while updating my Google apps from the Play Store after a reboot. Nexus 6P, stock Android Marshmallow.. I don't think there are any logs I could supply to you?

EDIT: At least some got integrated, but a few of them still crash although they're on the latest version. I'm currently fixing this by installing the latest apk from apkmirror on top.