yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] osm0sis:
No, fastboot is basically just low level, offline partition flashing, so there is no way for addon.d to function with the device in that state.

I haven't gotten into the GSI world yet, so hopefully someone else can answer your remaining questions. Maybe [MENTION=453495]JEANRIVERA[/MENTION] would know?
[Android Software/Hacking General [Developers Only]] Mao04:
I've been trying to research writing a couple scripts. One to connect and immediately disconnect a Bluetooth headset and the other to turn on developer options>override force-dark after restart. Just figured I'd ask if these were even possible before investing too much time.
[Android Software/Hacking General [Developers Only]] osm0sis:
If you could find the developer setting in the `settings` command then that one sounds possible, for the headset you could probably turn off BT entirely and turn it back on via command but specific device stuff is probably too deep in. Tasker might be a better thing to look into since it can automate key press stuff and more detailed ROM functions.
[Android Software/Hacking General [Developers Only]] DiamondJohn:
Not sure if you wish to disconnect a specific Bluetooth device only, or would be happy to simply turn Bluetooth off completely? To turn it off / on, my ROM has the setting in the settings (ie "settings list global" for all). something obvious like "bluetooth_on"

I have also historically found a lot of the settings in my ROMs, within the settings (ie maybe your other thing will be there:confused:)

settings list secure;
settings list global;
settings list system;

I normally run it once, then change the setting using the ROMs UI, run it again, and see if any of the above lines give different results.

There is also

sysctl -a;

and to a much lesser extent

am get-config;

all the above can also be run from a UI using my app: TeMeFI in which you can find the above in the menu under "Current State"
[Android Software/Hacking General [Developers Only]] Mao04:
Thanks, sounds like I'll give the settings script a shot first. Yeah, I was thinking tasker for the bt also since it is for a specific device (use a hacked bt headset to open my garage door).

Thanks for pointing me towards the settings lists. Got a place to start now
[Android Software/Hacking General [Developers Only]] techdoctorusa:
view current folder on android

by running this shell script

https://www65.zippyshare.com/v/f0lCEyQn/file.html

run with FX File Explorer: the file manager with privacy

https://play.google.com/store/apps/details?id=nextapp.fx

why is this useful

well some linux programs

require to cd to current folder

now with this script you can

replace print $folder with cd $folder

to cd to current folder

just modify script to your needs
[Android Software/Hacking General [Developers Only]] shadowstep:
[MENTION=4544860]osm0sis[/MENTION] Hey Chris, just wanted to ask, would you know of a way to install split APKs using a script, on device? I know there are third party apps that can do that, but I would like to avoid using them. I know it can be done via adb (using the "adb install-multiple first.apk second.apk third.apk fourth.apk" command) and I tried doing that too (on device, of course, untethered basically) after flashing your adb + fastboot installer, but it still didn't work. Any suggestions will be appreciated. Thanks!
[Android Software/Hacking General [Developers Only]] osm0sis:
Hmm probably didn't work since that's a newer adb command. You could try with one of the new builds Surge linked a few posts back. :good:

You could also investigate what those split apk installer apps do, probably something with pm, but I haven't come across any commands for it myself yet. :confused:

I had hoped to have the new adb tested and added to the module repo by now, but new home owner stuff keeps getting in the way. So much real world stuff to fix! :silly::(

Our painter finishes up this week, so once we get things set back up and get to hanging some things on the walls I can hopefully carve out some time for Android stuff again. :fingers-crossed:
[Android Software/Hacking General [Developers Only]] shadowstep:
Success! It worked. :) Used the binaries compiled by [MENTION=4939386]Surge1223[/MENTION], connected to localhost, ran the adb command to install split apks and got greeted with a beautiful "success" message. The app installed just fine! :good:

Also, yep, the Android world is definitely missing having you around, but real life always comes first. Hopefully you get some time soon to update all-thing-every-thing. Take care!
[Android Software/Hacking General [Developers Only]] Surge1223:
You've officially tested it more than I have lol. I'm glad that works.
[Android Software/Hacking General [Developers Only]] elliwigy:
bro u lazy
[Android Software/Hacking General [Developers Only]] BlueMan_86:
can you add Xiaomi Mi 10T Pro

thx

---------- Post added at 02:42 PM ---------- Previous post was at 02:42 PM ----------

can you add Xiaomi Mi 10T Pro

thx
[Android Software/Hacking General [Developers Only]] zputnyq:
Hi [MENTION=4544860]osm0sis[/MENTION] :)

I got a problem flashing your latest magisk busybox module using twrp. It can't be flashed. I'm using magisk beta 21.1 magisk manager 8.0.3, there was no problem when I used magisk stable 20.4 with its manager 7.5.1 or 8.0.2.
[Android Software/Hacking General [Developers Only]] BillGoss:
Do you have Magisk installed also, not just the manager?
[Android Software/Hacking General [Developers Only]] Didgeridoohan:
It's not the module (I tested with other modules and it's the same). Seems like there's something about the TWRP environment setup in Magisk V21.1 (maybe v21.0 as well, haven't tested).
[Android Software/Hacking General [Developers Only]] BillGoss:
You are correct. I've been on 21.0 for a while and had no problems with flashing modules. I updated to 21.1 and flashing my module now gives the same error 127 caused by xargs.
[Android Software/Hacking General [Developers Only]] zputnyq:
[MENTION=2911853]BillGoss[/MENTION]

Yes, both magisk & its manager installed. All apps that needs root could work

[MENTION=325890]Didge[/MENTION]rdoohan & [MENTION=2911853]BillGoss[/MENTION]

I haven't flashed module much lately, I thought it's about the module. Thanks for your Information.
[Android Software/Hacking General [Developers Only]] BillGoss:
Fyi and [MENTION=4667597]Didgeridoohan[/MENTION] I've submitted an issue for this https://github.com/topjohnwu/Magisk/issues/3493

The workaround is to first flash Magisk and then the module. See my description of the issue in GitHub.

You'll need to uninstall the additional Magisk Manager if it was previously hidden after you rebooted or the hidden manager won't open.
[Android Software/Hacking General [Developers Only]] Displax:
[MENTION=5228018]zputnyq[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=2911853]BillGoss[/MENTION]

Created PR with fix this: https://github.com/topjohnwu/Magisk/pull/3494/files

You can edit /data/adb/magisk/util_functions.sh itself on your devices to fix this locally.
[Android Software/Hacking General [Developers Only]] Topser99:
It works, thank you very much. But I modified util_functions.sh in magisk zip and compressed again and it works fine.
[Android Software/Hacking General [Developers Only]] VincentJoshuaET:
Is a newer ADB binary available? The pair command doesn't exist for your binary. Thank you.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yep it's mentioned recently in this thread so you can manually replace it if you like. I hope to get to my much-delayed testing later this week and update the Magisk module and a couple things here at least. :fingers-crossed:
[Android Software/Hacking General [Developers Only]] osm0sis:
I ended up using the ARM ones that still respect $ADB_HOME and all seems working great here! Only issue is legacy devices get "Illegal Instruction" now for both fastboot and adb (was only fastboot before), so I've left 1.0.39 in the zip as a "legacy" build and it'll attempt to run the latest first and fallback, like I've been doing with fastboot for awhile now. 🙌

Just discovered the trick with USB-C to USB-C cables for knowing which will be the dominant device (on ROMs that don't let you choose) is to have a higher charge on the one you want to be the host, and then reboot the target device last. 🤪

If one uses a conversion dongle (e.g. USB-A to microUSB, or USB-A to USB-C) that might dictate which end is host as well, but at least there are some rules to follow. :p

Edit

: Looks like XDA is going to go read-only to migrate to the new platform before I get the last couple things done for my Odds thread update, but the Magisk modules are all already updated, and I'll see you all on the other side for everything else! :D

Edit 2

: And looks like things are still pretty wonky.. Likes from this and many posts are missing still, I've heard some peoples' attachments have gotten screwed up, etc. I'll wait until they're done restoring all the missing various bits and things have stabilized here more. 🤦‍♂️
[Android Software/Hacking General [Developers Only]] LoganDark:
I can't find anyone else who has asked the question in this thread, so - how should one go about enabling syntax highlighting in Nano? ~/.nanorc (/data/.nanorc for my unprivileged user) doesn't seem to work, and the --rcfile command-line argument doesn't exist...
[Android Software/Hacking General [Developers Only]] osm0sis:
Tested and will include in v2.1! Thanks! :)

Obviously not too many people using it since nobody let me know I mistakenly shipped v2.0 with my test connectIP= value of "tewt" for over 2 years! 😄🤦‍♂️

Another wrinkle in my update plans however.. the new XenForo XDA only allows 10 attachments per post at the moment, so I can't add any updated ones to the OP as it's well over that. :(:rolleyes:

The syntax files aren't included in mine to try and keep it minimal, so I don't believe there's a way. I think Lineage's does syntax highlighting, but of course isn't as quick to update as mine, nor can it be used in recovery.
[Android Software/Hacking General [Developers Only]] LoganDark:
Aww, that's a real shame. I use nano over ADB on my laptop, so I don't have to keep shuffling files around with pull/push. Would be nice to have syntax highlighting support.

I'm not looking for the syntax highlighting files, I'll bring my own. Just for rcfile support, which seems to be missing.
[Android Software/Hacking General [Developers Only]] osm0sis:
I'll take a look at the config and see if I can figure it out. 👍
[Android Software/Hacking General [Developers Only]] kgursu:
Hi, I need to report something, that seems not to be connected as usual, but I experienced that and they are related.

I was having utter slowness and freezes (screen freezes, can't type keys with keyboard, etc.) after enabling 1-click tracker prevention, with both user-only and user and system apps, on Muntashir Akon's App Manager (https://muntashirakon.github.io/AppManager/). Now, my problem seems to be fixed after updating osm0sis' Nano NDK Magisk module.

Could you please tell me why, @osm0sis?

I also reported this to Muntashir Akon.
[Android Software/Hacking General [Developers Only]] LoganDark:
Perhaps the reboot fixed it
[Android Software/Hacking General [Developers Only]] kgursu:
Nope, not a chance...
[Android Software/Hacking General [Developers Only]] KreAch3R:
Regarding the nano Magisk module, v5.4, Pixel 2 XL, latest stock Android 11, no other mods: It seems that the 'resize' command that is being used in the wrapper script isn't included in the stock Google image (maybe it's part of busybox?), so when you exit nano you get the following error:

/system/bin/nano[15]: resize: inaccessible or not found
taimen:/sdcard $

You can easily hide the error if you do resize 2>/dev/null ; in the wrapper but I don't really know why 'resize' is there, so I'll leave it up to you on how you want to deal with this osm0sis
[Android Software/Hacking General [Developers Only]] osm0sis:
Ah you're right.. resize is from busybox, but is still useful there to ensure nano has the correct width and everything within the terminal, if available. I'll just 2>/dev/null for the next revision as you suggest. :p

I'm also tired of waiting for XDA to fix basic .sh or .sh.txt uploading on what's supposed to be a developer forum, so I'm just going to zip them individually to work around it for now and get this update post out before New Year, even though I already "soft launched" and all my thread zip packages have actually been up for about a week! ;)
[Android Software/Hacking General [Developers Only]] osm0sis:
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)

Edit: Added a newer version with the Pixel 6 release date, but discovered the newer entries actually disable some options, so then I commented out a lot of the newer ones (even some from the last version) to give a more optimal experience. 🤘
[Android Software/Hacking General [Developers Only]] zputnyq:
Hi @osm0sis, thanks for your works. I have a problem with your latest busybox module dated January 13, 2021 on magisk v21.2.

There is no problem on flashing either from twrp or magisk manager (v 8.0.5 or magisk 21.2 default manager v 8.0.4) but after I reboot, my device stuck into loop.

Here is the log. Unfortunately, it seems more lines couldn't be grabbed due to still using a stock kernel

(Xperia M4 stock kernel & android 6.0.1)
[Android Software/Hacking General [Developers Only]] osm0sis:
Weird looks like a little loop. Can you give me a Busybox installation log from both Magisk Manager and TWRP?
[Android Software/Hacking General [Developers Only]] zputnyq:
Here they are
[Android Software/Hacking General [Developers Only]] osm0sis:
Well both appear to match, and nothing obviously bad in there on the face of it. Does your device have a /system/xbin normally? Some don't, and the installer is supposed to fallback to /system/bin in those cases and filter out conflicting applets.
[Android Software/Hacking General [Developers Only]] zputnyq:
Yes my device has normal /system/xbin
[Android Software/Hacking General [Developers Only]] osm0sis:
Well I'm really not sure then, I guess your device just has something that conflicts within xbin. My advice would be to uninstall, then use the advanced options file to skip symlink creation during an install by running this command beforehand:

`echo NOLINKS > /data/.busybox-ndk`
[Android Software/Hacking General [Developers Only]] zputnyq:
Ok, I'm gonna try it. Thanks
[Android Software/Hacking General [Developers Only]] wbedard:
Hey there @osm0sis ,

Just a heads-up to you that your Magisk modules ZipSigner (3.0) and Busybox (v1.31.1) fail to install using @topjohnwu latest canary build (21402). Both Magisk and your modules normally install without issue on my device (OnePlus 6T / Android 10). It would surprise me if you weren't already aware of this but just in case. Let me know if I can provide you with anything useful from a diagnostic standpoint.

R/

wbedard
[Android Software/Hacking General [Developers Only]] sigfy01:
Hi @osm0sis ,

Same issue here since latest Magisk update on canary channel but on OnePlus 8T (Android 11).

Looks like something has been removed from the latest release which prevents your modules to install.

You can find more details in attached install log.

I don't who should fix the issue though.

Is it a miss in Magisk or a change you'll have to do in your modules?

Regards.
[Android Software/Hacking General [Developers Only]] ipdev:
Not to spam the thread but..

It is the same with or without Magisk renamed.

Same with Storage and Install permissions granted to Magisk.

If needed, logs are on gDrive.

GoogleDrive - Link

magisk_install_log_2021-01-24T15:16:05Z.log

magisk_log_2021-01-24T15:16:41Z.log

adb logcat. 20210124-mm-nano.log

Cheers. :cowboy:
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah Magisk changed something in its flashing environment.. investigating. 🙄😓
[Android Software/Hacking General [Developers Only]] osm0sis:
Could technically be fixed on both sides since the flashing environment did change but my install script was also operating on a bit of an assumption.

Fixed versions for Magisk 24102+ of all my modules are uploaded now to the repo, and I'll see about improving things on Magisk's side too after I get the chance to look into a few more fixes over there. 😉(y)
[Android Software/Hacking General [Developers Only]] sigfy01:
Looks like fix has been pushed in Magisk as well.

Thanks for the quick work.
[Android Software/Hacking General [Developers Only]] jamesfitzes:
hello everyone,

I just updated to the most recent version of busybox (1.31.1) through the magisk app but now none of my modules are working. I'd like to revert to the previous version but I don't have the previous version of it. Everything was working fine with the previous version. Can someone provide the previous version? Will I be able to revert?
[Android Software/Hacking General [Developers Only]] osm0sis:
I can pretty safely say that has nothing to do with my module. Magisk's internals don't depend on system commands, so the presence of busybox would have zero effect.
[Android Software/Hacking General [Developers Only]] jamesfitzes:
You're right.The issue was something else, but I fixed it now
[Android Software/Hacking General [Developers Only]] {Qhost}:
how to install sony xperia xz premium android 10 update isitorum published sony update file please help.
[Android Software/Hacking General [Developers Only]] {Qhost}:
i have a sony xperia xz premium device and i want to update to android 10 i downloaded the update file from the sony site how can i install please help thanks.
[Android Software/Hacking General [Developers Only]] Lossyx:
And why are you posting here?
[Android Software/Hacking General [Developers Only]] mrjuniork:
Sony Xperia XZ Premium
[Android Software/Hacking General [Developers Only]] osm0sis:
This is not a general help desk, go start a thread in the Q&A forum or the forum for your device.
[Android Software/Hacking General [Developers Only]] {Qhost}:
I'm new and my English is not very good, I'm sorry.
[Android Software/Hacking General [Developers Only]] Homeboy76:
English, please.
[Android Software/Hacking General [Developers Only]] osm0sis:
Welp, figure I'd better publish these before something else breaks. :p

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!

000gappsintegrator;

97-dumpbootimage.sh:

- clean up old `test` style tic

UPDATE-adb.Installer.v1.0.41-signed.zip;

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

UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip;

UPDATE-Fla****.Installer.v3.8-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

- clean up old `test` style tic

UPDATE-nano.Terminal.Editor.v5.5-signed.zip:

- hide error if resize command doesn't exist (thanks @KreAch3R)

- update to latest nano official source

- Diffusion Installer Backend updates

- clean up old `test` style tic

TWRP_A_B_Retention_Script-Magisk(1).zip and AnyKernel3 also saw some significant updates to support newer Magisk, devices and recoveries. Download TWRP A/B Retention Script again from the repo in the Magisk app to obtain the new version. 👌
[Android Software/Hacking General [Developers Only]] HippoMan:
The latest (22.x) version of Magisk no longer supports the A/B Retention Script, which I have been happily using for a year or so, whenever I want to upgrade the OS on my A/B device (OnePlus 7Pro - GM-1917).

I am not upgrading Magisk from 21.4 to the latest 22.x because of this.

But at some point, I'll probably want to upgrade to the later version of Magisk, so i am wondering what steps I can take manually -- if possible -- to emulate the very helpful functionality of the A/B Retention Script under Magisk 22.x.

Or am I simply out of luck?
[Android Software/Hacking General [Developers Only]] osm0sis:
News to me. I had fixed it a little while back for 21402+, but I guess it needs something new again. Can you provide a log of the breakage? I'll take a look. 👍
[Android Software/Hacking General [Developers Only]] HippoMan:
Oh, I'm sorry. I was just going by the Magisk update log where it said that the A/B Retention script is not supported, so I didn't even try to upgrade Magisk and check it out. But I will check now and get back to you.
[Android Software/Hacking General [Developers Only]] HippoMan:
I just now tried upgrading Magisk to 22.0, and indeed the A/B Retention Script is available .. and it works fine!

So again, I apologize for my false alarm.

Here's what I did, for anyone else who might be interested ...

I don't have a new ROM for upgrade, so I just went to Settings->System Update->Settings and selected Local upgrade of the current ROM image that I had previously installed a few weeks ago. This could also be done with any new ROM that has been stored on /sdcard ... perhaps via the Oxygen Updater app, if like me, you happen to be using a OnePlus device.

After the Local upgrade completed, I went through the standard A/B Retention Script procedure:

* DO NOT (!!!) reboot after Local upgrade

* Install the A/B retention Script in Magisk

* DO NOT (!!!) reboot

* Select Install next to Magisk on the main page of the Magisk app

* Select Install to Inactive Slot (after OTA)

* Select LET'S GO

* When that completes, do indeed choose to reboot.

In my case, everything ran and came up fine.
[Android Software/Hacking General [Developers Only]] osm0sis:
Ah, that's not what it says; I believe you're referring to the Magisk Install to Inactive Slot (after OTA) option being unavailable on specifically Virtual A/B devices since it's a different verification process for the new slot which occurs after the reboot and we don't know how to work around it currently.
[Android Software/Hacking General [Developers Only]] HippoMan:
Oh, I've never learned what a "virtual" A/B device is, and that message about it confused me. I guess it must differ somehow from the way my OnePlus 7Pro A/B device is architected.

Well, in any case, I'm just glad that I can still use the A/B Retention Script.

Thank you for clarifying!
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah, Virtual A/B is new. OnePlus only started using it with the 8T I believe.

Virtual A/B overview | Android Open Source Project

source.android.com
[Android Software/Hacking General [Developers Only]] zputnyq:
@osm0sis I decide to downgrade magisk to 20.4 & there's no problem with symlink. But on 21.x to 22.x I should nolink it.