yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] osm0sis:
Woo, big changes in Magisk lately! Time to support 'em. :)

It's also with this last major Nexus Media Installer update we bid a fond farewell to the Nexus 5X and 6P's official support window, and so I've added their final factory image media files so that those interested can keep that Google-y feel on custom ROMs for those devices, or perhaps on something less bootloopy. ;)

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-Busybox.Installer.v1.30.1-ALL-signed.zip:

- update to latest busybox stable official source

- properly enable Unicode in all builds (thanks [MENTION=4487388]jcmm11[/MENTION] and [MENTION=8712251]gdgsdg123[/MENTION])

- support new Magisk v18.0, v18.1 and v18.2+ paths in installer

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

UPDATE-Fla****.Installer.v3.5-signed.zip:

- fix fla**** --restore for Magisk

- update busybox binary (1.30.1) with the latest patches and fixes from my repo

- support new Magisk v18.0, v18.1 and v18.2+ paths in installer and scripts

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

- support new Magisk v18.0, v18.1 and v18.2+ paths in installer and scripts

- add Nexus 5X (bullhead) and Nexus 6P (angler)

- change default media to bullhead

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

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

UPDATE-CMSetup.Fix.For.GApps.Installer-signed.zip;

UPDATE-nano.Terminal.Editor.v3.2-signed.zip;

UPDATE-unSU-signed.zip:

- support new Magisk v18.0, v18.1 and v18.2+ paths in installer and scripts
[Android Software/Hacking General [Developers Only]] gdgsdg123:
Have you checked

this

?.. May be of help.
[Android Software/Hacking General [Developers Only]] jcmm11:
https://xdaforums.com/showthread.php?t=2239421&p=78297828
[Android Software/Hacking General [Developers Only]] osm0sis:
Literally the reason I credited you in the release post. ;)
[Android Software/Hacking General [Developers Only]] Damoedge:
Hi all,

I'm just wondering is the "renice" command for apps outdated?

I remember using it years ago and it did make a huge difference to the app that had been reniced.

Thanks.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah we used to use it on the launcher on the Galaxy Nexus back on KitKat. I'm not sure if it would work the same on Pie, or if it would even make a tangible difference on a modern phone that actually has some horsepower. Feel free to try and report back. ;)
[Android Software/Hacking General [Developers Only]] Damoedge:
Thanks mate,

I used to have an app that I could use to renice an app but I can not remember the name of it...I even forget the command to use lol lol
[Android Software/Hacking General [Developers Only]] gdgsdg123:
;)

Invalid?.. How?

Have you checked the

Config files

("Config.in", "Config.src") in busybox source?..
[Android Software/Hacking General [Developers Only]] osm0sis:
Give a search through the old init.d files in my OPs here, or maybe in the GitHub for DirtyV kernel's ramdisk/AK2 and you should be able to turn it up. :)

Invalid since busybox configs use

CONFIG_NAME=y

or

# CONFIG_NAME is not set

So CONFIG_NAME=n like you have it is not a thing in a normal config.

Quickly searching Google while at work at the time I did not check those files, no. My point was WCHAR=0 has very few hits so it wasn't initially clear what it did. As my edit shows I did find information supporting your proposed Unicode setup and added it in the commit which is now included in the latest builds.
[Android Software/Hacking General [Developers Only]] gdgsdg123:
The legacy way of specifying parameters... and it does work.

"# CONFIG_NAME is not set" style exists for taking advantage of syntax highlight. (syntactically those 2 have different meaning but due to the way it's implemented... the difference can be hardly observed)

The main reason you found almost nothing on Google is likely due to those things already included in the source...
[Android Software/Hacking General [Developers Only]] osm0sis:
Good to know it still accepts that without triggering a reconfig. I wasn't aware that was busybox's legacy method for disabled options since that preceded my involvement.

The outcome of WCHARS=0 didn't readily present itself to me in the source either if I recall correctly, but cool, thanks for coming out man. I gave you credit for finding the proper way to enable Unicode in busybox builds as a courtesy since you translated it from the Chinese you found it in, is there something else you need?
[Android Software/Hacking General [Developers Only]] gdgsdg123:
The

Config files

('busybox-1.30.1/libbb/Config.src', line: 229-257).

Nothing :)

Doing so helps both us.
[Android Software/Hacking General [Developers Only]] PlumptDickins:
Can i use this on s8+ SM-G955U Verizon USA
[Android Software/Hacking General [Developers Only]] DragonFire1024:
Depends what you want to use...
[Android Software/Hacking General [Developers Only]] yass:
With the 'ADB and Fastboot for Android NDK' installed via Magisk.

Is it possible to adb from phone terminal to firetv for sideloading apk? Tried the usual commands from pc, but Im either getting 'connection refused' or 'no route to host'.

Tried with and without ADB debugging enabled in developer options, same wifi network.
[Android Software/Hacking General [Developers Only]] osm0sis:
To quote myself with some edits, call centre style:

The odds that I or anyone else here has tried to adb from the same random combination of X device to Y device that a user like yourself is asking about is pretty much zero.

Sounds like you need to look into properly enabling USB Debugging and adb over WiFi on your FireTV though, if your PC didn't work.
[Android Software/Hacking General [Developers Only]] Nebrassy:
So I've been wondering, would your twrp a/b retention script work as an addon.d script?

It needs to be the first addon.d script to be executed, because for me, the flashing order needs to be twrp then kernel then Magisk or else I get a bootloop

If anykernel2 gets addon.d support, then the retention script would result in a bootloop, no idea why twrp doesn't have addon.d support in their installers, what do you think?
[Android Software/Hacking General [Developers Only]] osm0sis:
addon.d has never properly supported boot.img mods. I have written hacks for this (my FlashAfterUpdate script and Magisk both make use of it), but that makes having multiple simultaneous things flashing tricky. I've been chatting with a couple of the Lineage guys about putting the ROM zip writing the boot.img before addon.d restore in both v1 and v2 and they were agreeable but we'll see what happens.
[Android Software/Hacking General [Developers Only]] denkazzzget:
Getting "nano: not found". in TWRP. TWRP 3.2.3-1. SE 8.0. Magisk 18.1.
[Android Software/Hacking General [Developers Only]] jcmm11:
Is this right after flashing nano?
[Android Software/Hacking General [Developers Only]] denkazzzget:
I downloaded and flashed it from the repository, when typing "nano" in the terminal I get the error above.
[Android Software/Hacking General [Developers Only]] osm0sis:
The instructions do say you need to flash it each time in recovery before using the command in recovery. I just tested it with my latest update from the Magisk module repo and it works fine.
[Android Software/Hacking General [Developers Only]] jcmm11:
The problem is 2 fold.

1 - unless you're running a Canary build of Magisk the nano files are inside magisk.img and are unavailable without mounting the img file.

2 - the PATH variable within recovery doesn't contain the needed directories even if you manually mount the img

If you're running a Canary build #1 isn't an issue since there's no image file but #2 is still relevant. You'd be able to solve #2 by either switching to /data/adb/modules/nano-ndk/system/bin/ and then running ./nano from there or by just running /data/adb/modules/nano-ndk/system/bin/nano (or you could modify the PATH variable)

Flashing the install zip, even if you already have it installed, handles all this for you . Mounts the image (if needed) and modifies PATH. But this all gets reset once you exit recovery which is why you need to flash it each time you boot to recovery and want to use it.
[Android Software/Hacking General [Developers Only]] ImRickHarrison:
A/B TWRP Retention Script Glitched

Hi, so I used your module on my OP6 on a custom rom before installing a OTA and I rebooted and everything was okay in the ROM, but when I rebooted to recovery, I was stuck in the TWRP logo. I reinstalled OOS in fastboot and then booted TWRP, installed again the custom ROM and booted. Then I rebooted to recovery and again. Stuck in TWRP logo. What do I have to do? Should I reflash the module?
[Android Software/Hacking General [Developers Only]] osm0sis:
You did it in the wrong order. Allow OTA to install -> Flash TWRP A/B Script in Magisk Manager -> Magisk Install to Inactive Slot (After OTA) in Magisk Manager.

All of this needs to be done before rebooting. You just need to flash Magisk again to get out of the recovery loop since it sounds like you missed some steps.
[Android Software/Hacking General [Developers Only]] ImRickHarrison:
Thanks for the quick reply, it solved the problem. Next time I'll do that and I hope I don't mess up everything again :D
[Android Software/Hacking General [Developers Only]] osm0sis:
Another day, another rewrite of Magisk. ;)

New module template changes will break all custom update-binary modules on the module repo, so I've gone ahead and worked around it with haaxxxx. :p

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.39-signed.zip;

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

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

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

- split out a minimal backend script to work around massive Magisk template changes

UPDATE-nano.Terminal.Editor.v4.0-signed.zip:

- update to latest nano official source

- split out a minimal backend script to work around massive Magisk template changes

My TWRP_A_B_Retention_Script-Magisk.zip has also been updated to the new Magisk template, so Download again from the repo in Magisk Manager to obtain the new version.

Edit

: Reuploaded UPDATE-Nexus.Media.Installer-signed.zip since the next Magisk Canary will remove the basic/simple mount feature that we previously relied on for bootanimation support. Good news is post-fs-data module loading seems a little faster on more recent Magisk so the difference is negligible. :good:
[Android Software/Hacking General [Developers Only]] johnlgalt:
Jeez, you're fast - lol!

Thanks, as always!
[Android Software/Hacking General [Developers Only]] aharisi:
I tried running the updated SUMount script ZIP from a TWRP terminal to uninstall a problematic module that was giving a bootloop with the new version of Magisk (v19) but it gives me an error and doesn't mount. Does it work with new Magisk v19? Is there another workaround to uninstall a module? Am I being stupid and overlooking something simple? Thanks in advance...
[Android Software/Hacking General [Developers Only]] guest4711:
No need for any mount script with magisk >=18.2

Use filemanager in TWRP and navigate to /data/adb/modules Then delete the folder of the module in question (or move it out if the way)...

Or use the old method to force magisk into "core-only" mode by touching /cache/.disable_magisk
[Android Software/Hacking General [Developers Only]] yung40oz84:
I keep getting magisk img not mounted when asking the SU Mount to remove modules. This is on latest canary. Is there a zip to work on canary to mount magisk?
[Android Software/Hacking General [Developers Only]] osm0sis:
Literally the posts above yours. Please read. Also if you're going to use Canary make sure you read the release notes, since you would already know the answer by now.
[Android Software/Hacking General [Developers Only]] vinnievegas:
TWRP retention script not working since it was updated. Is the update not compatible with magisk 18.1? Or maybe not compatible with blu_spark TWRP 9.96?

It worked every time before the script was updated. I updated the script yesterday and updated blu_spark TWRP from 9.91 to 9.96 yesterday as well.
[Android Software/Hacking General [Developers Only]] osm0sis:
Should be backward compatible still though not tested. Got install logs or anything?
[Android Software/Hacking General [Developers Only]] vinnievegas:
Not now. Only have this phone so had to go back to stock OOS for oo6.
[Android Software/Hacking General [Developers Only]] osm0sis:
Edit: Whoops I removed the preceding post by mistake... XDA shouldn't have the Submit button directly under the Hide button, a couple mistaken clicks and things go bye-bye.. :eek:

Anyway, at least I've still got the quote here:

Okay. Not a ton of help. All my A/B devices are tied up, so without logs I guess it'll have to wait until I get my next OTA, in which case I'll just be confirming it still works on latest Magisk Canary, which I believe it does from my script updates and dry-running it without an OTA.

Anybody else in here can confirm an issue and is available to help?
[Android Software/Hacking General [Developers Only]] vinnievegas:
It failed at unpacking image if I recall.
[Android Software/Hacking General [Developers Only]] osm0sis:
Interesting. It's definitely able to go through the whole process on my end (without an actual OTA to switch to, of course). Logs will be necessary to figure out why on Magisk 18.1 that might be different. 18.1 Stable, I presume?
[Android Software/Hacking General [Developers Only]] vinnievegas:
Yes. Stable.

---------- Post added at 11:10 PM ---------- Previous post was at 10:43 PM ----------

This time it worked. I'm without a few modules this time. Does this hurt anything testing it without an OTA?

[YOUTUBE]https://youtu.be/A9HZBhZ9xLs[/YOUTUBE]
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah that looks fine to me. Nope, shouldn't hurt anything, it just puts your current ramdisk into the opposite slot, not a big deal since a TWRP zip install installs to both slots as well.

Maybe before you tried with an old copy of the zip but now it's working with the new updated one.
[Android Software/Hacking General [Developers Only]] m0han:
i tried a clean install of rr-06apr rom & gapps on my x00td device (pie beta firmware flashed earlier) after a full wipe (cache, dalvik-cache, data, system, vendor). after the phone booted fine, i went back into recovery for flashing other files like magisk permissive, busybox, magisk etc., but nothing works now. the zips don't get flashed; updater process ended with error: 1 see screenshot: https://ibb.co/vHRSFSb. i've been using the same twrp for a while now, so, i presume it can't be an issue with the twrp. the rom is selinux enforcing. can you help me out, please?

see my earlier post here: https://xdaforums.com/showpost.php?p=79297489&postcount=6
[Android Software/Hacking General [Developers Only]] alecxs:
what happen if you change it from TWRP Terminal before flashing?

getenforce
setenforce 0
getenforce
[Android Software/Hacking General [Developers Only]] _that:
Where's your recovery.log?
[Android Software/Hacking General [Developers Only]] m0han:
getting the error even with 'getenforce' giving 'Permissive' result.

---------- Post added at 16:11 ---------- Previous post was at 15:45 ----------

saw this late. will post in a bit. hope the couple of attempts i made thereafter wouldn't make a difference.
[Android Software/Hacking General [Developers Only]] m0han:
would this do?
[Android Software/Hacking General [Developers Only]] Didgeridoohan:
Since it isn't from an instance where you actually tried installing a module, no. Error 1 is just a generic "installation failed" message. To see what really happened you have to save the log right after the error.
[Android Software/Hacking General [Developers Only]] Surge1223:
I was interested in this log with more info as well..
[Android Software/Hacking General [Developers Only]] m0han:
fwiiw:

busybox downloaded from the attachments in OP (last edited by osm0sis; 28-03-2019 at 23:29) and through the link in post details give md5: 1e135e0fbc796c1db85391f2b24c05a1. i was using this zip for installing busybox till a couple of days back, iirc.

since i noticed the zip file installed from inside magisk manager app was getting installed correctly and things were fine, i checked the md5 and find it is different from the one above: 8db745ff82ac60793d58e86188894e29.

this morning when i re-installed the rom, gapps, busybox (magisk module) and magisk - all in one go, there were no errors.
[Android Software/Hacking General [Developers Only]] Didgeridoohan:
The different checksums is because the Manager repackages the zip with a new update-binary.

Other than that, there's no difference. In other words, it sounds like the issue was with your setup (but again, it's impossible to know without proper logs).
[Android Software/Hacking General [Developers Only]] m0han:
since there was no error the last time i installed stuff, no logs saved/posted. will do the next time errors are thrown up.

p.s.: no idea about what's wrong with the setup. all i can recall is it all started when i switched to a rom that had selinux enforcing and/or required pie firmware to be installed prior to flashing the rom zip. i did follow the instructions posted by the rom dev, though.
[Android Software/Hacking General [Developers Only]] DragonFire1024:
Just wanted to let you know [MENTION=4544860]osm0sis[/MENTION] now that we are unlocked, your AIK installer works perfectly on unpacking and repacking the boot.img for the Amazon Fire HD 10. Thank you for this awesome tool. Also did you create the Android app on the play store?
[Android Software/Hacking General [Developers Only]] osm0sis:
Great to hear! And nope. Any apps you find there currently are intentionally misleading people by using my AIK/Android Image Kitchen name and should not be used or trusted.
[Android Software/Hacking General [Developers Only]] DragonFire1024:
It's not the same name. https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
[Android Software/Hacking General [Developers Only]] jcmm11:
Apparently the author does give you credit.

"BOOT/RECOVERY: Use this tool to unpack/repack a boot/recovery image. This part is built on top of osm0sis's Android image kitchen but added support for some MTK devices. You can use "dd" or apps such as "Flashify" to flash image back."

However it's also not been updated since October of 2017.
[Android Software/Hacking General [Developers Only]] osm0sis:
Right but "Image Kitchen for Android" with an app icon that clearly shows AIK... Come on. That's intentionally muddying the waters.

The author has a history of taking open source projects, slapping a basic UI on them and then charging money if you look at his other apps. He might not be charging for his knock-off, out of date "AIK", but I don't trust it. They and he seem like shady sh*t.

I believe it started out as just slapping a UI on AIK (v2.2 or something) and now he "supports" a couple more - which were among the many I later added - like MTK, and apparently some system images in a beta (which also hasn't been updated in over a year).

Last I heard about it on the AIK thread his app had a nasty habit of wiping people's sdcards/internal storage, however, and of course people come and blame me for it because he has "AIK" as his icon and the name is misleadingly close, pretty clearly to try and drum up users from people searching for my work...

Of course he never asked my permission to use the name, or any of my work (my full scripts are used in the APK as assets)... Anyway, long story short, f*ck that guy.
[Android Software/Hacking General [Developers Only]] ianmacd:
Thank you for providing today's belly laugh.
[Android Software/Hacking General [Developers Only]] DragonFire1024:
Thanks for the heads up. I know how hard all you guys work to put these things together for us. Such a shame some people have to ruin it for everyone else.
[Android Software/Hacking General [Developers Only]] clarkcant:
Edit: so you know the guy who calls the pizza store complaining that the pie has no cheese, only to discover that he opened the box upside-down? Well, that guy's on XDA ?. I just noticed that my data toggle had somehow been switched to off ??. I'm leaving this post up in case by some miracle there's another moron out there. Thanks for developing the mods! Really enjoying Nexus Media ?.

Original post:

TL;DR: does the Nexus Media Magisk module write to any files that would have any bearing on network connectivity on an unlocked OnePlus 6T using Verizon?

Hey, love this mod! Weird question: I downloaded the Nexus Media Magisk module on my unlocked 1+6T last night. Today I realized that I have no Verizon data connection. For the life of me I can't imagine how this module would affect that, but I have no idea what files this module writes to, so who knows..

Would there be any reason this would affect network connectivity?

PS: here's the weird thing. The 6T doesn't have CDMA bands. It connects to Verizon with just LTE. I can call and text, which means that my phone is connected to the Verizon LTE network. So why wouldn't I be able to use the internet? So weird. Again, I know that this isn't a Verizon thread. I'm only posting this here because the issue only occurred after I installed this Magisk module.

So my question essentially is: does this module write to any files that would have any bearing on network connectivity on an unlocked OnePlus 6T using Verizon? Thanks!
[Android Software/Hacking General [Developers Only]] gyj1109:
Flash After Update Script unable to work properly with Magisk v19.0-8d4c4072 (19004) because it no longer uses /sbin_tmp. Can you update it with some new methods?
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah, I'm aware. It's on the to-do. I'll have to look for some other hallmark of a Magisk addon.d installation in progress..

Frustrating that Magisk would take my method for allowing boot.img modifications from addon.d, then has repeatedly changed things to break the originating script coexisting with it. :rolleyes:

Edit: Found something that works. :cool:

Change:

while [ -d /sbin_tmp ]; do
sleep 1;
done;

To:

while [ "$(ps | grep 'magisk/addon.d.sh' | grep -v 'grep')" ]; do
sleep 1;
done;
[Android Software/Hacking General [Developers Only]] Rom:
@osm0sis

Hello, I don't know if you can help me, but why not try after all.

I have already compiled curl-7.50.0 via Ubuntu 16.04 LTS in a static way for arm32 and arm64 via NDK, both binaries work correctly.

I'm now trying to compile curl to static for x86 devices, but I have a compilation error.

As a prerequisite:

- compilation openssl-1.1.1.1b in static OK

- compilation zlib-1.2.2.11 in static not OK

- curl-7.50.0 compilation in static pending

You can find the variables I use as well as the log file of the defective compilation as an attachment.

I tried to find solutions left and right on the web, but without success.

Already, when ordering:

./configure --prefix=/usr --static "$@" $CONFIGURATION_OPTIONS &&
make -j8 && make DESTDIR="/home/rom" install

The following error appears:

Checking for snprintf() in stdio.h.... No.
WARNING: snprintf() not found, falling back to sprintf(). zlib
can build but will be open to possible buffer-overflow security
vulnerabilities.

Considering the little information I found about this error, it could be that one of my variables is defective compared to what should be linked behind, or something could be missing on my vm, I let you tell me what you think.

Since you know the compilation well, you may have an idea about it, terminal and vm already restarted few times.

(ah, and before i forget, i have install the libc6-dev-i386 package)