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

[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

 

[zputnyq]

Hi @osm0sis
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.

 

[BillGoss]

Hi @osm0sis
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.

Do you have Magisk installed also, not just the manager?

Sent from my OnePlus 3T using XDA Labs

 

[Didgeridoohan]

Hi @osm0sis
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.

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).

 

[BillGoss]

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).

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.

Sent from my OnePlus 3T using XDA Labs

 

[zputnyq]

@BillGoss
Yes, both magisk & its manager installed. All apps that needs root could work
@Didgerdoohan & @BillGoss
I haven't flashed module much lately, I thought it's about the module. Thanks for your Information.

 

[BillGoss]

@BillGoss
Yes, both magisk & its manager installed. All apps that needs root could work @Didgerdoohan & @BillGoss
I haven't flashed module much lately, I thought it's about the module. Thanks for your Information.

Fyi and @Didgeridoohan 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.

Sent from my OnePlus 3T using XDA Labs

 

[Displax]

@zputnyq @Didgeridoohan @BillGoss
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.

 

[Topser99]

@[email protected]@BillGoss
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.

It works, thank you very much. But I modified util_functions.sh in magisk zip and compressed again and it works fine.

 

[VincentJoshuaET]

Is a newer ADB binary available? The pair command doesn't exist for your binary. Thank you.

Sent from my Google Pixel 4 XL using XDA Labs

 

[osm0sis]

Is a newer ADB binary available? The pair command doesn't exist for your binary. Thank you.

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:

 

[osm0sis]

BTW, I updated the link from a few posts above with a new zip that has arm64 and arm versions of fastboot and adb. I compiled them in 11.0.0_r3 though, so the compatibility issues with older devices might still exist.

I did try getting rid of the missing symbol error, but since I never got it on my end ever it'd be hard for me to say whether the changes and inclusions of some libs got rid of the error or not.

In any case, i can say for sure I'm never compiling fastboot for arm again lol that was a crap fest.

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.


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!

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.

 

[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...

 

[osm0sis]

@osm0sis, I've been using your adbsync sdcard tool for a while now and I'd like to make one suggestion. Change (x2):

bin\adb push bin\.noadbsync %%i

to

bin\adb push bin\.noadbsync %%i/.noadbsync

The reason being that if the target path doesn't exists, then using the original code the file that gets created is a file with the name of the last directory in %%i and not .noadbsync. Mychange properly creates all the directories.
I came across this bug because I've been formatting my sdcard whilst testing new Android 11 roms for my phone that don't support encryption. After restoring the sdcard from my PC, the excluded directories don't exist on the clean sdcard. So the next adbsync run creates the files instead of directories for the excluded folders.

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.

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...

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.

 

[LoganDark]

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.

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.

 

[osm0sis]

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.

I'll take a look at the config and see if I can figure it out.

 

[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.

 

[LoganDark]

Hi, I need to report something, that seems not to be connected as usual, but I experienced that 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.

Perhaps the reboot fixed it

 

[kgursu]

Perhaps the reboot fixed it

Nope, not a chance...

 

[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