yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] osm0sis:
Nothing really jumps out at me there.. no ideas without looking into it myself, and I'm sorry, I really don't have time to look into other projects than my own. :(
[Android Software/Hacking General [Developers Only]] Rom:
I finally found the solution to this problem, by looking at the paths I had defined in my variables, they pointed to gcc and not to clang.

So I successfull cross-compile curl for android-x86 but I have another problem now, running the binary on a device with this architecture displays a symbol error.

I will deepen this error this weekend because it seems to me that I didn't correctly point some paths in my variables.

In most of time (as you probably know) all details are in the logfile(s).

Thank you for taking the time to answer me :)
[Android Software/Hacking General [Developers Only]] mkdante381:
How using adb from "adb + fastboot Installer"? This magisk module is installed, but how use it? No detected devices after adb start-server
[Android Software/Hacking General [Developers Only]] osm0sis:
Search the thread. Mileage varies and no guarantees.
[Android Software/Hacking General [Developers Only]] clarkcant:
Nexus Media was just updated, and there's no changelog. Anything new?
[Android Software/Hacking General [Developers Only]] osm0sis:
Have you heard of GitHub? Everything in Magisk Manager is publicly hosted there and it's a literal catalog of changes: https://github.com/Magisk-Modules-Repo/nexusmedia/commits/master
[Android Software/Hacking General [Developers Only]] Estebanium:
After updating a finance app, the app reports the detection of root. When reading the log files it turned out that the detection of busybox in sbin/busybox let it assume that I got rooted.

I downloaded busybox via the download section of Magisk Manager and I thought that it is installed systemless. The log file however stated that it would mount /system..

I use Magisk 19.
[Android Software/Hacking General [Developers Only]] osm0sis:
You misread. Magisk overlays on system. Hide your finance app in MagiskHide, clear the app data and try again. If it doesn't work go open a thread in the Magisk forums, since your app problems don't belong here.
[Android Software/Hacking General [Developers Only]] clarkcant:
Re Nexus Media - I know you have some sort of disclaimer about boot animations. I just wanted to report that after the latest magisk update, the boot animation is back to the default OnePlus animation. Not a big deal, but is there anything to do about that or is that just it?

Edit: I'm using a 6T. Not sure why I didn't mention that. Anyone here a doctor?
[Android Software/Hacking General [Developers Only]] osm0sis:
That's just it for your device unless [MENTION=4470081]topjohnwu[/MENTION] adds a way to mount earlier than post-fs-data to Magisk again.

You can always just do a system install with my zip's filename or /data/.nexusmedia reading feature if you really want the Nexus animation, since OnePlus always does Full OTAs when they detect root modifying system isn't really a big deal. You'll just have to flash it again after each OTA.
[Android Software/Hacking General [Developers Only]] clarkcant:
Got it. For what it's worth though, the Play Store app called "boot animations" (https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations) is able to change the animation on my 6T. Again, not a big deal, I'm just mentioning it because maybe they're doing something that you can replicate. Worth mentioning that they haven't issued an update to their app for around 2 years now.
[Android Software/Hacking General [Developers Only]] osm0sis:
Easy. They're replacing it in system. Which like I said mine also does if a user wants, but I'm not about to force system modifications by default via a Magisk module. Would sort of defeat the whole point of Magisk.

You don't need a specialized app for it. You can do it with root and a file explorer app or even terminal/adb shell if you want. It's not rocket science. It's pretty much the oldest, most widely documented Android system modification in existence.
[Android Software/Hacking General [Developers Only]] edomiredo:
after i updated busybox from you, then reboot my phone it's got stucked in boot animation. what should i do? can you make zip that uninstal this module? because i can only enter recovery mode.
[Android Software/Hacking General [Developers Only]] jcmm11:
What version of Magisk? If it's a recent enough version go, in recovery, to /data/adb/modules and delete the busybox-ndk folder. That will delete the module.
[Android Software/Hacking General [Developers Only]] osm0sis:
And even if it's not, I also created SUmount which lets you do the same. ;)

Your report is useless. It obviously works fine for me and others so I can't recreate it. Give me information about your device and setup, a module install log from Magisk Manager and try installing from recovery and give me /tmp/recovery.log from directly after as well.
[Android Software/Hacking General [Developers Only]] XtraWater:
Regarding to Busybox NDK. I updated Magisk to version 19 on two phones. On the Xiaomi I updated the Busybox NKD module before I updated Magisk.

On the Samsung phone, I just wanted to update Busybox,but installation fails. Unable to extract.... Is this module compatible with the new Magisk version?

Edit: I cleared cache and dalvik. All good now.
[Android Software/Hacking General [Developers Only]] osm0sis:
I bet these boot hang/loop issues being reported by the occasional person are related to the switch to imageless Magisk and that Magisk's support to migrate from magisk.img to imageless is known to only half-work on some devices.

Like [MENTION=4470081]topjohnwu[/MENTION] said in his release notes, be prepared to reinstall all your modules to make sure they all work correctly.
[Android Software/Hacking General [Developers Only]] osm0sis:
AnyKernel 2.0 updated with my own updated image tool native compiles. :D
[Android Software/Hacking General [Developers Only]] trevd:
[MENTION=4544860]osm0sis[/MENTION] Alright Dude....

Ah the old build Android on Android trick. That was one of the reason I got a tablet for, I Failed ... Hard! in my effort however as I didn't have a clue about linux back then :-\ I have seen kbox during my adventures in android but something put me off. I think it's all the chroot nonesene which the author admits is a bit of a hack ( Developer shame, sometime we do things we're not proud of lol ) . Also the whole source code access page is just a bit weird.

Just to confirm kbox does produce native android executables , i.e use /system/bin/linker and bionic as it's libc?

I've generally regarded terminalide as a more elegant take on subject although the GCC is aging a bit now. CppDroid seems to be a new comer to the native toolchain party and looks pretty good, last time I tried installing it I only had and EGDE connection ( yeah that's still a real thing lol ) l, so my d/l's kept failing as it downloads everything on first run.

Linaro has proper native toolchain stuff ( gcc binutils ) without a chroot in sight.

A Couple of bit of randomness.

On my github is the latest version on parted that is linked to bionic which I swiped from the Android-x86 project who swiped it from intels AOSP tree. this is v3.something but is better than using that ancient prebuilt one which is included with cwm and is version 1.8

libhybris [github] looks like a useful project although it seems to have either been superseded or fallen out of favour

Here's a piece of insanity XServer (PlayStore ) as an Android App, Someone had to do it I suppose. Just picture it now as your device grinds to an halt under the weight of running Eclipse.

There's loads of other "interesting" crap ( tools and libraries ) I can throw your way depending on your goals but as far a getting a completely equipped build environment you seem to have most if not all of it covered.... I suppose to only thing as you are missing which is absolutely vital is "sl" but don't worry dude, I've already porting it [ https://github.com/trevd/android_external_sl ] :p

One thing to test. Can you build statically linked binaries ok?

Also does your unzip actually unzip flashable update zip files ( or any zip file for that matter ) most busyboxes don't because of an #ifdef which ifdefs out all of the useful functionality when you're not targeting the desktop ( F**k knows why! )

Hopefully some of that is helpful!

Trevd
[Android Software/Hacking General [Developers Only]] osm0sis:
Hey buddy! Always good to hear from you! :)

I think I ended up building file, xz and mkbootfs statically because otherwise they'd require libraries. lz4, mkbootimg (other than libmincrypt) and unpackbootimg are dynamically linked. Not sure about bionic/libc but they definitely run on my devices. Maybe you can tell me; they're up in the AIK thread. :good:

You're right about the unzip in busybox hating signed zips. This really poses a problem for zips that use shell scripts instead of an update-binary especially, since it can't use minzip like the recovery does. I noticed Chainfire worked around it for SuperSU and (after some pestering) here's how he did it ;):

http://xdaforums.com/showpost.php?p=48199109&postcount=4373

kbox2 comes with gcc 4.7 and 4.8 toolchains, not too sure of any other details there. The chfakeroot seems a pretty functional solution, hack or not. I noticed he had to make a few script wrappers for binaries in his bin directory, but otherwise pretty clean. I'll check out the ones you suggested too!

Thanks as always! :)
[Android Software/Hacking General [Developers Only]] trevd:
Well there's no great mystery to the zip thing, Just fix busybox, which is "exactly" what I did with this one line patch ..... 3 months ago ENABLE_DESKTOP In the unzip applet to Fix the 1 and 8 issue ... sorry dude :o been kinda of busy otherwise I'd have probably noticed. ..

I was going to say I'd get this pushed out to cm and omni but looking at it, setting ENABLED_DESKTOP for an embedded device is not right at all ( I know a dirty hack when I see one, even my own lol ) It might be a case of ... I'd just be guessing so... Anywho that's "A" Fix .

kbox should do you nicely. I've played with cppdroid for a bit it's pretty good but you're not a c programmer are you? Although compiling from source and git are gateway drugs .. it's a slippery slope but for you know it you'll be injecting code into your eyeballs. :silly:

I think I might prod this one with a stick I see I can get to the bottom on it.,It's been that way for a while But first I must sleep

TBC lol

Oh yeah, final thing I figured out how to make proper ota zips not so long back, not really of much use around xda but all good knowledge
[Android Software/Hacking General [Developers Only]] osm0sis:
[MENTION=4179234]trevd[/MENTION] Just discovered the latest busybox 1.22.1 from Stericson doesn't seem to have the 1 and 8 issue for some reason. :good:

And whoa, proper OTA zips how? Did you manage Google signing, or do you mean imgdiff and .p patch files? Either way, very cool and you should make a thread for it, maybe ROMs would want to switch to it from their Delta implementations. :D
[Android Software/Hacking General [Developers Only]] :
[MENTION=4544860]osm0sis[/MENTION] and [MENTION=4179234]trevd[/MENTION]

I can confirm that cppdroid is a good source to have. Only thing I am noticing odd with it is that it focuses more on C++ which causes confliction with some of my work. Though, could be me as I am still playing around with it.

Also, I have tried out c4droid and CCTools. Both are just as good. I use SGit and AIDE for dealing with git repos so that I may work straight from my device.

As for linking c files. In some cases I can pull it off but in other cases I get those stupid redefinition errors. Currently having that problem now as I am wanting to combine mkbootimg, unmkbootimg, mkbootfs, and nbimg all in to one executable. So far, a fail.

But hey, its all for fun and for the learning :) IMHO.

Also noticed that compiling mkbootfs brings lots of errors and warningd using the mentioned apps, and of course using linux it just simply works lol. My guess, its incomplete.
[Android Software/Hacking General [Developers Only]] osm0sis:
To compile mkbootfs I ended up commenting out the things it was complaining about so that it would use the ARM-Linux definitions kbox has in its native headers instead. Worked perfectly. :)

As for combining them, take a look at one of trevd's old projects where he got pretty far with that idea; maybe you could fork and continue it. :good:

https://github.com/trevd/android_external_bootimage_utils
[Android Software/Hacking General [Developers Only]] :
Hmm, not a bad idea to comment them out. Didn't even think to do that. That may also work with the redefinition errors as well which would save me the headache of making header guards (dreading that one lol).

I actually came across that very repo just the other day. Had cloned it to my device so I could review it and see what approaches he took to make it work.
[Android Software/Hacking General [Developers Only]] osm0sis:
He had it working, just needs finishing up. :)
[Android Software/Hacking General [Developers Only]] trevd:
[MENTION=5537766]Modding.MyMind[/MENTION]

If anyone wants to run with those boot image utils feel free ..... It got to a point where it's usable and It's something I use all the time although it doesn't support dtb ... I've got plans/dreams to use libarchive for archive handling which beats the hell out of my ropey custom implementations ...

[MENTION=4544860]osm0sis[/MENTION] You got me started on this compiler thing ... I decided to compile my own gcc using Linaro's work [ https://wiki.linaro.org/Platform/Android/ToolchainOnAndroid ] after a bit of tweaking I got it to compile from within my omnirom sources which is cool is suppose lol

Yeah the "Proper" OTA using .p files .. To do it you need a full set of "target files" to imgdiff against. These are created when you do a full rom build... However what with all the "after market" modding that users do I can see this method being more trouble than It's worth..
[Android Software/Hacking General [Developers Only]] osm0sis:
I managed to get my crosstool-ng Cygwin -> Linux cross-compiling toolchain to build! :D

Steps:

I started here with the top answer (by Ben Voigt):

http://stackoverflow.com/questions/4769968/c-cross-compiler-from-windows-to-linux

But that required more patches/config:

- The _libintl_gettext error patch from the comment (by Duncan Calvert) of the above: http://sourceware.org/ml/crossgcc/2012-05/msg00012.html

- wget has issues with kernel.org certificates so use the .wgetrc method in the accepted answer: http://stackoverflow.com/questions/...s-when-running-wget-on-an-https-url-in-cygwin

- byteshift headers in the downloaded linux kernel src need fixing: https://lkml.org/lkml/2013/4/28/84

- Use make 3.81 that crosstool includes since 4.0 has problems: http://crosstool-ng.org/download/ibot-logs/2013-11-03.html

- If building with a 32-bit target, set the architecture level in crosstool to i686 (defaults to i386 for some reason) to avoid gcc 4.8+ issues explained: https://bugzilla.redhat.com/show_bug.cgi?id=917161#c6

- Patch the elf headers since Cygwin uses JMP and Linux uses JUMP:

--- a/usr/include/sys/elf_common.h
+++ b/usr/include/sys/elf_common.h
@@ +1,1064
#define R_X86_64_JMP_SLOT 7 /* Set GOT entry to code address. */
+#define R_X86_64_JUMP_SLOT 7 /* Set GOT entry to code address. */

Update: In upgrading to the latest crosstool, components and recompiling i686 as well as x86_64 I have discovered a few additional required changes:

- glibc 2.19 needed sunrpc stat64 refs changed to stat to compile, per: https://forums.freebsd.org/threads/...oss-compile-android-kernel.47766/#post-266854

- Workaround an issue with the Cygwin libintl header using solution here: https://mail.gnome.org/archives/gtk-list/2011-November/msg00077.html

The toolchains compile completely, and I've verified the cross-compiled Linux builds of my custom updated mkbootimg and unpackbootimg binaries work! Here are the toolchains if anyone else wants to cheat and build Linux binaries from Windows. :cool: 😄

i686-cygwin-linux-gnu-gcc481-toolchain.tar.gz:

https://androidfilehost.com/?w=files&flid=312867

i686-cygwin-linux-gnu-gcc491-toolchain.tar.gz &

x86_64-cygwin-linux-gnu-gcc491-toolchain.tar.gz:

https://androidfilehost.com/?w=files&flid=312867

Just "tar xzvf" the archive into your home dir, add the toolchain bin dir to your path and you're good to go adding the gcc binary from its bin dir to your Makefiles. :)

Edit

: 11-Jun-2017 - Uploaded a rebuild of i686 gcc 4.9.1 since I hadn't noticed c++ was missing until now! :eek:;)
[Android Software/Hacking General [Developers Only]] tostep:
ADB Screenshot (GN) 1.3 + TWRP 2.7.0.0

osm0sis, thank you for ADB Screenshot!

It seems like TWRP 2.7.0.0 use bgr0 instead of rgb565le.

Incorrect screenshots (pixfmt variable is automatically set to rgb565le by adb-screenshot.bat):

Right screenshot (I manually changed pixfmt variable to bgr0 at adb-screenshot.bat):

Can you fix this issue for TWRP 2.7.0.0?
[Android Software/Hacking General [Developers Only]] osm0sis:
Thanks for the heads up, I'll see what I can do! :)

Edit: That actually brings them into line with CWM, which also uses bgr0. :good:

Anyway [MENTION=4185544]tostep[/MENTION], just change line 27 of the bat file to the new TWRP pixfmt.
[Android Software/Hacking General [Developers Only]] osm0sis:
A couple items.. :)

Android Image Kitchen - Linux Edition (AIK-Linux) up in its thread:

http://xdaforums.com/showpost.php?p=51832571&postcount=290

crosstool-ng Cygwin to Linux cross-compiling toolchain is now uploaded if anyone else wants to play with it:

http://xdaforums.com/showpost.php?p=51726566&postcount=230

Cheers!
[Android Software/Hacking General [Developers Only]] osm0sis:
Yikes! Three in a row. :p

Just uploaded a new updated version of my Kernel Emergency Reset script zip: http://v.ht/KEmR

Added Synapse support, updated f.Ku support for the recent newer versions and updated Performance Control support since that team's been doing great work to improve it. :)

Spread the word in all your favorite kernel and tweaking app threads. ;)
[Android Software/Hacking General [Developers Only]] DexedrineXR:
Bump... This thread is too good to die. I use these tools all the time ;)
[Android Software/Hacking General [Developers Only]] shoey63:
Don't worry Bro, the thread won't die;)

[MENTION=4544860]osm0sis[/MENTION]

Tried your ADB Screenshot tool on Xperia Z and ended up with a pixel salad that had the pet rabbit salivating :p

Good news though, fb2png sources have been recently updated here to support many more devices.

Download

and extract it.

Then, in recovery, you can do

adb push fb2png /sbin
adb shell chmod 0775 /sbin/fb2png
adb shell fb2png /tmp/screen.png
adb pull /tmp/screen.png

Perhaps you can adapt your script to make use of it;)

Here is an example

:good:
[Android Software/Hacking General [Developers Only]] osm0sis:
Nice stuff! Great how it automatically figures out the pixel format for you. :)

Looked into the code a bit and there is source for a PC executable that should do the entire job at once without pushing or pulling anything manually: adb_screenshoot.

Here's the original code/downloads: http://android-fb2png.googlecode.com/

Looks like it's fallen behind PhilZ's updated version on Git though. But there's a Linux Makefile included so it should be easy to build us something current. I'm surprised there isn't an official thread for this already.

Edit: Couldn't get them to compile with MinGW under Cygwin since there were missing headers for some reason, but compiling a newer libpng to replace the prebuilt one included and messing around with the Makefile I got it to work in straight Cygwin. ;)
[Android Software/Hacking General [Developers Only]] :
Hey guys, you have to check out KBox2! That mess is on point hahaha!

Credits for sharing clearly goes to [MENTION=4544860]osm0sis[/MENTION] and to Kevin Boone for piecing it all together.

Can finally relieve myself of my headaches.

Anyways, time for some sleep.
[Android Software/Hacking General [Developers Only]] osm0sis:
What I'm working on right now if anyone's curious:

http://xdaforums.com/showpost.php?p=53141673&postcount=45026

;)
[Android Software/Hacking General [Developers Only]] osm0sis:
I bet these boot hang/loop issues the odd person are seeing are related to the switch to imageless Magisk and that Magisk's support to migrate from magisk.img to imageless is known only half-working depending on the device in question.

Like [MENTION=4470081]topjohnwu[/MENTION] said, be prepared to reinstall all your modules to make sure they all work correctly.
[Android Software/Hacking General [Developers Only]] osm0sis:
Google Keep's staged server-side Dark Mode rollout is painfully slow, and some have posted settings xml root hacks to force it, but I just discovered that Keep will revert those given enough time if you're still on the wrong side of the rollout. Brutal.

Until the rollout is complete here's an easy way to automate reapplying the settings hack:

for i in /data/data/com.google.android.keep/shared_prefs/experiment_prefs*.xml; do
sed -i "s/\(DarkMode.*\)false/\1true/g" $i;
done;

Force Close Keep and your Dark Mode is back.
[Android Software/Hacking General [Developers Only]] osm0sis:
Google Keep's staged server-side rollout is painful, and some have posted settings xml root hacks to force it, but I just discovered that Keep will revert those given enough time. Brutal.

Until the rollout is complete here's an easy way to automate reapplying the settings hack:

for i in /data/data/com.google.android.keep/shared_prefs/experiment_prefs*.xml; do
sed -i "s/\(DarkMode.*\)false/\1true/g" $i;
done;