yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] osm0sis:
Most ROMs still don't give you root just from adb, so you'd still need to type su, but yes, the idea is having adb shell access to your devices for debugging on the go, either by adb connect <ip> or directly tethering, without the need for a PC.
[Android Software/Hacking General [Developers Only]] _that:
https://github.com/omnirom/android_external_busybox/blob/android-7.0/console-tools/resize.c#L54

TWRPTerm doesn't support most of these control sequences - I stopped adding more code when busybox vi worked.

Also, TWRPTerm's implementation of the scrollback buffer is quite hacky: There is no difference between the scrollback buffer and normal terminal lines - mostly because I don't know how a proper solution that still works with very small terminals.

I suggest checking if TERM is set in the environment - if not, you're not running on a proper terminal :)
[Android Software/Hacking General [Developers Only]] Stallio:
Good Luck keep us posted here so we can try it. Thank you.
[Android Software/Hacking General [Developers Only]] osm0sis:
The build itself is complete as of my last commit on GitHub (there were a few patches required), now I'm just finishing off testing a number of installer changes that make it flashable from within Magisk Manager. ;)

I'm on night shift at work for the next three days, so maybe on the weekend, but early next week for sure.
[Android Software/Hacking General [Developers Only]] mkhcb:
I understand this is an old thread. However, I am interested in this addon.d script: https://dl.xda-developers.com/4/1/1....txt?key=xUIo4_w_BzziaMlJWsHt0g&ts=1501030381

Is it possible for the zip to install the newest (based on download date) of a file that start with [static name]-[wild card]?

Example, I would like this script to see that FK-50.zip is newer than Fk49.zip.

The downloads always starts off as FK. So I would like a script that will install the newest of all files that starts with FK in a folder.

Is that possible?

Ideally, I would like to apply this to my kernel and magisk. Problem with magisk addon.d script is that when I update my kernel, I need to reflash magisk. So I cannot relay on magisk addon.d in favor of flashing the zip all over again.
[Android Software/Hacking General [Developers Only]] osm0sis:
Not an old thread at all!

Magisk's new addon.d ability used my work on FlashAfterUpdate, which is cool, but it does now make for unpredictable results when used together since it uses the same wait time as mine so both could be trying to modify the boot.img simultaneously.

I've got an updated FlashAfterUpdate to work around that (1 second longer wait, and continue to wait if it's detected that Magisk's addon.d is in the middle of doing its thing). I'll have it out when I put out the new busybox and some other updated goodies.

As for your idea, no.. way overcomplicating things. Rename the files under /sdcard/FlashAfterUpdate with 01- 02- etc. to dictate the order is the most obvious solution.

And for your reflashing Magisk issue, I'd suggest your kernel use AnyKernel2 so the Magisk changes remain intact through updates. If it's official Franco Kernel that should already work.
[Android Software/Hacking General [Developers Only]] mkhcb:
So my problem is that if I flash an updated version of FK, I will lose root (irregardless of magisk's addon.d, which makes sense since I am not updating the system). The only way to fix this is by reflashing Magisk.

So now, when I have CyanDelta install FK kernel, I must have it install Magisk.

However, it gets tiresome constantly renaming both files and moving it into the CyanDelta folder, since both are not on the same release schedule (understandably) .

I can always use the addon.d you made to keep my current kernel and use the magiskSU addon.d to keep that as well. However, if a new kernel is released, I need to flash that and magisk again manually (nothing is automated).

Essentially, I would like a way that I can have Magisk and FK updater to download the newest file when it comes out and when I hit install in CyanDelta, everything new gets installed. I'd like to do this without having to rename and manually moving the files (the kernel and magisk) into they cyandelta folder.
[Android Software/Hacking General [Developers Only]] rignfool:
This sounds to me more like an excellent job for Tasker... It can move files and so forth with root... And rename them as well
[Android Software/Hacking General [Developers Only]] osm0sis:
Can you point me to the exact FK zip? Sounds like it just needs to be fixed somehow, AK2 zips are supposed to stack and leave existing changes untouched. Does it make any difference if it's flashed in recovery or via FKU?
[Android Software/Hacking General [Developers Only]] mkhcb:
https://kernels.franco-lnx.net/OnePlusOne/7.1.2/anyKernel/

Flashing from the update app also undoes magisk. Seems like the AnyKernel zip replaces the kernel with a new one, rather than stack on-top of....

If this can be fixed by fixing the AnyKernel, it be awesome cause I don't mind updating the kernel or magisk via the update app and let the addon.d keep the current versions installed with each ROM update.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah it's an AK2 issue for sure. Must be something Magisk does with the ramdisk files that mkbootfs is undoing.

Please flash the latest FK zip via recovery over working Magisk root, but rename the zip file first to fk-r51-anykernel2-debugging.zip. After flashing send me the debugging zip it creates in the zip directory.
[Android Software/Hacking General [Developers Only]] mkhcb:
Sent via PM.

Thanks :)
[Android Software/Hacking General [Developers Only]] atarek:
Hello [MENTION=4544860]osm0sis[/MENTION],

sorry i know it might be off this thread but i ask if u have any clarification or description.

i have a strange behavior with magisk but i noticed change when installed ur latest update-busybox systemless.

here is issue full details

i flashed new rom:nxteam magma. With magisk 13.3 flashed and without busy box after boot magisk manager log still empty which is my main issue then i flashed "UPDATE.Busybox.Installer.v1.26.2-ALL-signed" after boot manager start log successfully, magisk.log and magisk_last.log created in /cache.

After that i flashed unfied hosts from magisk and reboot then manager stoped logging again. I tried to flash kernel then magisk but same result busybox system or systemless no results also.

Could this info guide anyone to relate any troubleshooting approach. or what is busybox did in cache folder i don't know but for somehow my issue fixed.

any advice.

Regards,

Ahmed
[Android Software/Hacking General [Developers Only]] osm0sis:
Definitely sounds more like a Magisk issue, no ideas from my end about what could be going on there.
[Android Software/Hacking General [Developers Only]] mkhcb:
Just wanted to make sure you got my PM. Obviously, take your time but, please let me know if you got what you needed.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yup I should be able to figure it out from that debug archive; precisely why I added that feature. ;)
[Android Software/Hacking General [Developers Only]] str8str:
So will this make it system less
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
It's already systemless if you use Magisk.
[Android Software/Hacking General [Developers Only]] jcmm11:
Also if you use systemless SuperSU (installs to /su/xbin)
[Android Software/Hacking General [Developers Only]] oux:
I tried to install stericsons busybox to install v4a driver but the driver won't install.. I want to try your BusyBox but do I need to uninstall it in some way? the stericsons BusyBox won't let me uninstall via the app
[Android Software/Hacking General [Developers Only]] osm0sis:
Yep, mine will handle that. :)
[Android Software/Hacking General [Developers Only]] oux:
ok so I just need to flash your zip? cool thanks!
[Android Software/Hacking General [Developers Only]] Mezabaru:
Not noticing any issues with latest busybox! Thanks for maintaining such a great collection of skilled work!
[Android Software/Hacking General [Developers Only]] JohnCorleone:
I am trying to give you more than one thanks but I hit my daily limit! I can't believe that between Magisk 13.3 and your Busybox I am passing Safety Net (and I changed a LOT of stuff).. Netflix doesn't even show up in Play Store if you trip Safety Net. Many thanks!!
[Android Software/Hacking General [Developers Only]] Shtiff1:
Module says to reboot to activate, but have done that multiple times, no luck.

Magisk 13.3,manager 5.1.1,only module installed is this one.

XT1254, 6.0.1, stock rom
[Android Software/Hacking General [Developers Only]] osm0sis:
Try installing it again? Working fine for myself and several others so far. [MENTION=4667597]Didgeridoohan[/MENTION], any ideas?

P.S. to everyone, I guess this lets the cat out of the bag a little early - I put my new busybox (and several other of my zips) on the Magisk module repo yesterday. Enjoy! :cowboy:

Proper post and thread zip attachment updates to follow once I finish a couple of things on one more project. :good:
[Android Software/Hacking General [Developers Only]] Shtiff1:
I tried again through manager twice and twrp once. Still saying reboot to activate. When I look in logs, it looks like there is Alot of busy box related logs in there, so I guess it installed? But module section is just not updating? When I click on the save option in logs to save, it does, creates folder, but when I try to post it it doesn't attach.
[Android Software/Hacking General [Developers Only]] osm0sis:
While booted look in /magisk/busybox-ndk, is there system/xbin/ with busybox and all the symlinks? If so then yeah it's installed correctly, and it sounds like a Magisk issue. Just delete the "update" file from that same directory and that notice will go away.
[Android Software/Hacking General [Developers Only]] Shtiff1:
Yes.

Deleted update file, notice is gone
[Android Software/Hacking General [Developers Only]] Shtiff1:
Here was the logs just in case. ☺️
[Android Software/Hacking General [Developers Only]] Didgeridoohan:
Hm... That one's interesting. There is a bug where modules don't install properly through the Manager, mainly on Samsung devices. The magisk_merge.img file doesn't get created.

See here for reference: https://github.com/topjohnwu/Magisk/issues/297

That doesn't seem to be the case here though...

[MENTION=5359721]Shtiff1[/MENTION] If you could reproduce the issue (uninstall the module and install it again) it'd be interesting to see the Magisk log from the first reboot and also the magisk_debug.log from /data.
[Android Software/Hacking General [Developers Only]] Shtiff1:
I'll have to do it this evening.
[Android Software/Hacking General [Developers Only]] kwanthenewbie:
SafetyNet failed with the latest busybox, 1.26.2 worked fine. Please take a look at it.
[Android Software/Hacking General [Developers Only]] osm0sis:
Unrelated. SafetyNet has never looked for busybox. Your issue is elsewhere.
[Android Software/Hacking General [Developers Only]] loner.:
I can't get the new BusyBox to install through Magisk. Can you post a TWRP flashable zip please?
[Android Software/Hacking General [Developers Only]] nguyentankiet:
Delete
[Android Software/Hacking General [Developers Only]] Paschfire:
You think maybe you should have asked [MENTION=4544860]osm0sis[/MENTION] for permission first before sharing this here?(Pardon me if you have already, my apologies if this is the case)

The 1.27.1 Busybox installer, a build he even has yet of Officially releasing within his own Thread.

Imho... Just saying, that's all.
[Android Software/Hacking General [Developers Only]] nguyentankiet:
You right. Please edit your mention to remove my link
[Android Software/Hacking General [Developers Only]] Shtiff1:
Now I can no longer find this folder/directory. I wanted to remove the update folder like I didn't before. But no I don't have"/magisk "folder. I can now only see the symlinks in magisk logs.
[Android Software/Hacking General [Developers Only]] osm0sis:
..Download the zip in Magisk and then flash it in recovery?

People need to chill. I said early this week for my post and that is what it will be.
[Android Software/Hacking General [Developers Only]] loner.:
I did download the zip 2 times and couldn't find it. Lol
[Android Software/Hacking General [Developers Only]] osm0sis:
Doesn't it end up in /sdcard/Download? That or like /sdcard/Magisk Manager.
[Android Software/Hacking General [Developers Only]] loner.:
Not on this device. I may look into Magisk permissions in Android 7.1.1

Edit: The BusyBox.zip downloads to /sdcard/Magisk Manager/ now. Weird!
[Android Software/Hacking General [Developers Only]] Shtiff1:
Nevermind on this one
[Android Software/Hacking General [Developers Only]] Didgeridoohan:
From those logs it looks like the TWRP installation was successful. Was it? The Manager installation does not seem like it created the magisk_merge.img file. So, you're likely affected by the Manager installation bug I talked about earlier.
[Android Software/Hacking General [Developers Only]] Shtiff1:
Yes it is installed, thank you guys
[Android Software/Hacking General [Developers Only]] danmaman:
installed busybox 1.27.1 via magisk manager on Ogygen os -oneplus 3T

all good here...installed without probs

thanks osmOsis
[Android Software/Hacking General [Developers Only]] osm0sis:
Well! I still have an update for Flashlt cooking, but I decided that I'd better not rush it, since it adds Pixel support (a/b slot and /system/system support) and those are some pretty big changes. In the meantime, without further ado, here are all the other goodies I've been working on the last couple of weeks.. :)

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:

- a new addon.d script to automatically extract the boot.img from a Lineage ROM update zip to /sdcard

99-flashafterupdate.sh:

- increase wait time by 1 second (now 6 seconds total) to try and catch Magisk's addon.d script, which also uses my method, and avoid conflicts

- detect if Magisk's addon.d script is currently active (by /sbin_tmp presence) and wait until it's done

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

- update installer to latest versions of set_perm, set_perm_recursive and file_getprop from my Complete Shell Zip Documentation

- update Magisk support for full online installs in Magisk Manager

- fall back to /sdcard for finding target Adreno zip to accommodate direct Magisk Manager installations

- fix Magisk module.prop version replacement with Adreno release name

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

- fix parameters with spaces being passed from wrapper

- update Magisk support for full online installs in Magisk Manager

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

- update to latest busybox stable official source

- fix for zip being renamed with spaces

- update Magisk support for full online installs in Magisk Manager

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

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

- update to latest nano official source

- fix line-wrapping on undersized terminals with booted wrapper script (thanks [MENTION=4187311]Setialpha[/MENTION])

- fix support for paths/filenames with spaces

- update Magisk support for full online installs in Magisk Manager

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

- update installer to latest versions of set_perm, set_perm_recursive and file_getprop from my Complete Shell Zip Documentation

- fix for zip being renamed with spaces

- update Magisk support for full online installs in Magisk Manager

- work around Magisk Manager PATH issue by ensuring busybox tar is used to unpack (if available)

- fix common files merging issues under some circumstances

- allow override of filename media choice using contents of /data/.nexusmedia to accommodate direct Magisk Manager installations

- add work around for bootanimation.zip mounting under Magisk
[Android Software/Hacking General [Developers Only]] Gigobaito:
Flashed "UPDATE-Busybox.Installer.v1.27.1-ALL-signed.zip"; SafetyNet check results in ctsProfile: false. Any idea how to go around it?
[Android Software/Hacking General [Developers Only]] BelzIgoh:
I think it is not the busybox zip issue. Mine still passed safetynet.
[Android Software/Hacking General [Developers Only]] 24imelqui:
Install the latest usnf test version, disable/enable magisk hide, restart and check again.
[Android Software/Hacking General [Developers Only]] Ikkuh84:
Xposed Framework Installer (Flashable Zip) v2

Will this also work with the latest version of Xposed, or do I have to wait for an update? :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Wait for tonight. The new one's got to contend with detecting x86 etc. so it isn't as easy as dropping in the new files. Just wrapping up a holiday here in Canada, but I'm hoping to get it working once I get home.
[Android Software/Hacking General [Developers Only]] nicesoni_ash:
This is strange, I remember posting here but couldn't find that post so here it goes again.

I tried to backup my sd card and I added media/0/android/data folder to ini file, all went fine except in the end I didnt get any zip file and the script threw an error that no zip file found. What could be the problem?

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Android Software/Hacking General [Developers Only]] osm0sis:
Probably that the directory is enormous and not something you should block and try to zip. It contains a lot of semi-important app data, but if you do want to exclude it you should put a .noadbsync file in it. Trying to zip something too large for your free space probably caused the zip to not be made, which then caused the error you saw when it tried to adb pull a nonexistent file.

Edit: That or you didn't supply the correct path so there was nothing to zip and nothing to pull.

media/0/android/data is incorrect. It would be /data/media/0/Android/data/ as far as I know. So either way, something not quite intended being done on your end. ;)
[Android Software/Hacking General [Developers Only]] nicesoni_ash:
Yup, I used /data/media/0/Android/.. This is the post I made which cleared that I made a mistake posting at wrong place.

and yes, that folder has about 3gb of data or may be more than that so it could be the same reason as you said that it's too big. Will try to put .noadbsync file in it.
[Android Software/Hacking General [Developers Only]] osm0sis:
That error looks like it couldn't push zip to /tmp which I've only seen happen when you don't have root or the binary got deleted. Are you running it from custom recovery or USB Debugging? It's only meant to run from custom recovery (ie. root).

And yeah.. you don't want to zip that. It'd be a monster, so .noadbsync is the only way to correctly exclude it; doing so sort of defeats the purpose of a sdcard backup though, considering that directory is the bulk of it.
[Android Software/Hacking General [Developers Only]] nicesoni_ash:
Indeed, without it seems to be have an uncomplete backup and yes, I was running it through usb debugging, my bad. Will work it through recovery now. :)

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Android Software/Hacking General [Developers Only]] dirtyreturn:
[MENTION=4544860]osm0sis[/MENTION] . I use the xposed framework and flash cyanogen nightlies for some reason.. the flashable zip you prepared for recovery installation includes the xposedbridge.jar . Is there a way to include app_process? A request maybe.
[Android Software/Hacking General [Developers Only]] osm0sis:
Eh? It's in there. ;)
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Yes, its probably my mistake anyway. I had xposed v.2.3.1 installed granted root and everything to system I guess. I went ahead and dirty flashed a rom along with the zip. And the only green number was the xposedbridge.jar.
[Android Software/Hacking General [Developers Only]] osm0sis:
The jar is stored in /data/data/ now, and app_process is still in /system/bin/; so I assume you flashed the zip after the ROM?

If so, give me the log from /data/local/tmp/ and I'll take a look.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Yes, I flashed you're zip after the rom. Is the init.rc log sufficient? If that doesn't work please excuse my ignorance...

edit; @osm0sis ...again.. the zip I attached adds the app_process after I flash a rom.If needed I will repeat the process to get that log for you. I have, since posting went back to v.2.2 of xposed.
[Android Software/Hacking General [Developers Only]] osm0sis:
That's not my zip. Please remove it. If you flashed my zip it leaves a log in /data/local/tmp/xposed.log or something close to that.

Give me that log or there's absolutely no way I can know what's going on. I'm no mind-reader..
[Android Software/Hacking General [Developers Only]] osm0sis:
It's UPDATE ALL THE THINGS day here for me I guess!

Nexus BootUnlocker Script Zip latest version added to the OP!

- Switch from EDIFY to shell script. Vastly decreases the size and complexity of the script. This also makes it far easier to add new devices and so...

- Support the Nexus 5 (hammerhead)!

- Add support for the recently discovered "tampered bit" on newer "lk-based" bootloaders (so far, just mako and hammerhead have been shown to use one). My script will always reset tampered to false.

Also, just wanted to share that segv11's BootUnlocker app was recently featured on Android Police, so congrats to him for the recognition. My N7 BootUnlocker Script Zip thread got an honorable mention too. ;)

My combined Nexus BootUnlocker zip version is still largely unknown, despite how useful it is when your device won't boot and you want to fastboot flash an image to recover, so please, tell your friends! :p

nano Terminal Editor v2.2.6 Installer Zip added to the OP!

- Flash to install nano to /system/xbin/ along with the required files in /system/etc/terminfo/. It can then be used from Terminal when booted.

- Also (temporarily) enables use in recovery by flashing a script to /sbin/nano with the required environment variables, so you can then trigger it from recovery shell or the console in AROMA File Manager for that recovery session. You could also add this script into the recovery image /sbin/ of your choice with my Android Image Kitchen. ;)

/sbin/nano:

#!/sbin/sh
# nano: set up and run nano from recovery/terminal
# osm0sis @ xda-developers

export TERMINFO=/system/etc/terminfo;
export TERM=linux;
mount /system 2> /dev/nul;
/system/xbin/nano "$1";

Perfect for the tweaker-on-the-go, now you can edit files from AROMA Filemanager's terminal/console and never need access to a computer if something goes wrong! Thanks to [MENTION=455439]bgcngm[/MENTION] for his great work porting the nano binary over to Android. :)

flash_image script also added to the 2nd post, automating some tedious command work for flashing to NAND/MTD partitions from shell, like I've been doing on a MX Box I recently purchased, that doesn't have a USB adb connection, accessible bootloader, nor a working recovery on my TV.

Hack hack hack. :D :good:
[Android Software/Hacking General [Developers Only]] VivaErBetis:
There's an omission in your nexus bootunlocker script.

It says “ For GN, N4 & N10 bootloaders ONLY“... Where is the N5?

BTW: thanks again for the script!
[Android Software/Hacking General [Developers Only]] osm0sis:
Ah sh*t. :p

Cosmetic, but good catch! Reuploaded. Those 10 people that downloaded it overnight can feel free to get it again. ;)

Edit: I also went ahead and added my threads to the DevDB. :D

Not sure if I want to bother going live with the Downloads section in this thread though.