yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] osm0sis:
Oh cool! This is the first report I've heard that it works on a CM ROM. Thanks! :)

Check the versions in /data/app against the versions integrated into system. A good file explorer app like FX is good for that. If they match then just delete the /data/app version and you should be back to normal working order.

As for logs, nah, I don't think this is something I can figure out. I spent days making changes to /data/app, /system/*app and packages.xml and diffing the resulting changes to packages.xml from the optimization to figure out how to experimentally safely alter it how it might want it to be changed to avoid further breakage, and even now I guess it's not 100% on all ROMs. Like I said, I really need a fresh set of eyes to hopefully figure it out and take it the rest of the way. :eek:

Also, here's where I'm at with busybox if anyone's interested in following along:

https://github.com/osm0sis/android-busybox-ndk

So far I've fixed all the host signing warnings I got during build on Cygwin and it builds for arm. I'm still vetting a few more of the patches from the original tias repo I forked, and bringing some headers over from dorimanx's monster combined busybox source + patches + toolchain repo to see what else I can fix, then of course the other 5 target architectures, but it's coming along. I think it'll be good to have all the required Android patches split out from the main source again. :good:
[Android Software/Hacking General [Developers Only]] rogers11:
Just for the records. I've also got the 000gappsintegrator script working on CM12.1 (Nexus 4 with nightly from 26.11.).

- /system/etc/init.d did not work, /system/su.d did

- chmod 0770 for 000gappsintegrator

First reboot copied the apps and libs and created "integrated"-files in the corresponding folders. Apps an libs were not moved.

Second reboot removed the old apps and libs.

Got now log at all.
[Android Software/Hacking General [Developers Only]] osm0sis:
su.d must be extremely early in the boot. Thanks for the report! Maybe I can figure out a way to make it wait for sdcard, might solve some non-working devices, but could also break some working devices by having it happen too late into the boot... Hmm, or maybe it'd be better to save the log in a buffer until after boot completes then copy it to sdcard, to leave the process alone for those it works for... :good:
[Android Software/Hacking General [Developers Only]] skulldreamz:
Thanks so much for all you do for the community [MENTION=4544860]osm0sis[/MENTION] and hope you have a great holiday season!
[Android Software/Hacking General [Developers Only]] JobSup:
I am trying to get the new version to work in /system/su.d with current SuperSU installed. It just doesn't seem to start at all.

- running cm12.1 on MotoE 2015 (surnia) with older tk-gapps

- flashed UPDATE-SuperSU-v2.46.zip

- created /system/su.d/000gappsintegrator (permissions: 0770)

- cleared cache&dalvik - reboot

No logfile is created in /sdcard, gapps still exist in /data/app after reboot, no indication in 'adb logcat' during boot that the script is running. I can attach or pm a logcat if that helps.

Now I am getting FCs in com.google.process.gapps and Play Services... Guess I need to reflash gapps

Thanks
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah there have been some bad reports on CM, not sure what the deal is there.
[Android Software/Hacking General [Developers Only]] Midomad:
[MENTION=4544860]osm0sis[/MENTION]

It is ok to post you're N5 settings like you were doing for GN here http://xdaforums.com/showthread.php?p=34951507

Thanks for you're work.
[Android Software/Hacking General [Developers Only]] osm0sis:
Sure, it's pretty straightforward. franco.Kernel r76 AK2, defaults but with thermal threshold at 80, fast charge on, and vibrator amp down at 37. Then my color calibration was at 235 245 255 on my first screen (broken glass) and my first replacement (which then had the digitizer break), and my new replacement isn't quite as nice so now it's 205 220 255.
[Android Software/Hacking General [Developers Only]] osm0sis:
One more update to the OP for a little while!

UPDATE-nano.Terminal.Editor.v2.5.0-signed:

- Updated from @bgcngm's nano 2.2.6 to my own quick static ARM compile of nano 2.5.0; seems to work well with no extra patches now, and it's smaller!

- Updated the installer and command wrappers to detect and work in both system and systemless root.

- Scoured the internet for a working terminfo that allows scrolling and enter to work correctly in booted Android Terminal Emulator, AROMA Filemanager's Terminal Console, and recovery/booted adb shell, and managed to find only one: a different pcansi! I replaced the existing pcansi in the package with the working one, made pcansi the default using the command wrappers and just left the others there in case someone wanted to mess around with different ones at some point (they're only like 18kb).

- Added support for nano command line options to the wrappers (--smooth might be helpful to some people).

Happy tweaking!

Edit

: New special zip features

You may add keywords to zip filename or in a file at /data/.nano-ndk:

1) system or System or SYSTEM to force a system installation.

2) uninstall or Uninstall or UNINSTALL to uninstall nano from the zip's detected target location (/su/xbin > /magisk/nano-ndk/system/xbin > /data/adb/su/xbin > /data/adb/modules/nano-ndk/system/xbin > /system/xbin, unless system forced per above).
[Android Software/Hacking General [Developers Only]] rogers11:
Hello and thanks for the update. The script is working on my Nexus 4 with CM12.1 (latest nightly). But still no log-file. So no difference to the former version of the script.

Edit: I was wrong. The new script creates the "integrated"-file but does not replace the installed files in /data/app. So the result after all is a reinstalled older version.
[Android Software/Hacking General [Developers Only]] osm0sis:
You mean it doesn't push them to system? Damn, the only thing I added was a wait really, and I'm not sure why it wouldn't write out to /sdcard now since it waits for that too. :confused:

Oh well, good thing I left the scripts up for copy/paste in the previous release posts if they end up working better for people. I've taken it about as far as I think I can, so hopefully someone will bring a fresh set of eyes to it soon and we can collaborate to work out a few more kinks for everyone. [MENTION=2777334]TKruzze[/MENTION]? ;)
[Android Software/Hacking General [Developers Only]] rogers11:
Yes, unfortunately it does not. But since the former version works for me, even without log, many thanks again.
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
Hey! First of all I must say thanks for your work! I mainly use your AIK installer and love changing the splash screen on my nexus 5 and 7! Now moving on to my question. In your busybox build could you include ADB and Fastboot complied binarys so we may use ADB and Fastboot commands from our devices? I know its a steep suggestion and/or request but your the only one I could find to maybe to ask this to and didn't want to bother you in a pointless PM!

Note: I used the compiled binarys found in the post below to use commands from my device to device over OTG but since marshmallow the ADB commands won't work, Fastboot works perfect.

http://xdaforums.com/showthread.php?t=2586472

Sorry to bother ya! Don't know if your taking request/suggestions such as this one!

Note 2: I am not a developer but am suggest something that may/may not help someone or some developer somewhere along the line.
[Android Software/Hacking General [Developers Only]] osm0sis:
Busybox is its own thing, there's not really any good way to add applets to it like that. I copy a fastboot binary to my devices as well, I posted it to my BasketBuild binaries folder. Didn't realize adb was broken yet. I'll look into getting it working again. Thanks.
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
Thanks! Yeah it's broken in Marshmallow but Fastboot works like a charm. When I use terminal it can't seem to find what ADB references to. If you do find a fix please don't hesitate to notify me via PM or on this post! Lol! Again thanks for all your hard work for the community!
[Android Software/Hacking General [Developers Only]] osm0sis:
Quick search yields a couple options so far:

https://github.com/kosborn/p2p-adb/tree/master/includes (working 1.0.29 static compile)

https://github.com/bonnyfone/adb-arm (broken compile but possibly easy way to build our own)
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
So as in "static" meaning its just for looks and no actions? Sorry but your dealing with a almost complete noob here lol. As for the broken compiled 1.0.31 binary, I have tried a adb binary that was also version 1.0.31 and it worked on Lollipop, but was getting errors in Marshmallow.
[Android Software/Hacking General [Developers Only]] osm0sis:
Google "static binary"; newbies need to read. :)
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
Thank you! I'm aggravated with the whole thing as now I can't get my 2013 Nexus 7 to use adb or to detect my nexus 5 in fastboot sadly. Nexus 5 can find and use fastboot commands to my Nexus 7 (weird but I'm thankful for it) but still after using the 1.0.29 Static ADB compile on it and my Nexus 7, it works on neither. It loads like it would in cmd on a pc but can't get it to recognize each other on bother devices. Regardless thank you for pointing it out to me!
[Android Software/Hacking General [Developers Only]] nicesoni_ash:
Sorry for off topic but can you provide me a link to the micro to micro otg you are using, I couldn't find one and the only one I found doesn't ship to India.

Sent from my "GT-I9300/1+2" powered by Carbon/Blisspop Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Android Software/Hacking General [Developers Only]] osm0sis:
Even in Lollipop (and KitKat!) there were issues with which device would act correctly as host. Following the instructions here helps but since Lollipop still doesn't always work:

http://xdaforums.com/showthread.php?t=1447727
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
I use these http://m.ebay.com/itm/281627123093

They are generic and cheap but they came within one month and they work perfectly for me. The seller is located in China and they shipped them all the way to the US where I live so they should ship internationally. Sorry for off topic.

---------- Post added at 07:51 PM ---------- Previous post was at 07:43 PM ----------

Thanks again osm0sis! I will check this built of Fastboot out and see if I can get my Nexus 7 to work as a host. Been running my devices as root in terminal for Fastboot and ADB. Will edit this if I can get it to work.
[Android Software/Hacking General [Developers Only]] osm0sis:
I couldn't get adb connect to work using that 1.0.29 binary on Marshmallow so I'll have to keep experimenting.
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
Same for both of my devices as well. Also I could'nt get my Nexus 7 to recognize anything using that compile in that thread either. Maybe it's the OTG cable but I don't see how that is a problem either as my Nexus 5 can host just fine using them.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah that was always weird though. Even seeming to depend on which end of the cable was in which device for me since I used a normal micro to usb-a cable with a usb-a to micro adapter (adapted end was dominant/host). Rereading the instructions I linked for you, you need a working adb binary to get fastboot to work by the looks of it.. I've got an idea though. ;)
[Android Software/Hacking General [Developers Only]] osm0sis:
@KentuckyGuy447 check out the attachments in the OP. :)

UPDATE-adb.Installer.v1.0.32-signed:

- installs adb from LMY48Z, the dynamically linked libraries it requires, and a command wrapper so it uses them instead of the current ROM's libraries.

- detects systemless su and installs to /su/bin + /su/lib/adb instead of /system if supported.

- installs static compile of fastboot as well since fastboot's functionality is dependent on adb's.

Since Marshmallow has removed the adb binary from /system/bin and any static compile of adb I've found hasn't worked for some reason, I figured we might as well go as legit as possible, so here's Google's own dynamic compile of adb from the LMY48Z Lollipop factory image, and the libraries it's linked to. The libraries are contained in their own subdirectory so they don't interfere with the ROM, and the command wrapper figures out where that is so the binary can use them. Seems to work as I've tested out adb connect to adb shell into my MX MediaBox (which I have set up to listen for ADB over TCP). :good:

Edit: Since updated with a slightly older adb (1.0.26) static compile to ensure simpler compatibility on x64 devices.

Edit 2

: New special zip features

You may add keywords to zip filename or in a file at /data/.adb-ndk:

1) system or System or SYSTEM to force a system installation.

2) uninstall or Uninstall or UNINSTALL to uninstall adb from the zip's detected target location (/su/xbin > /magisk/adb-ndk/system/xbin > /data/adb/su/xbin > /data/adb/modules/adb-ndk/system/xbin > /system/xbin, unless system forced per above).
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
You sir are the best! ADB and Fastboot are working flawlessly on my Nexus 5! my Nexus 7 was appearing as a unauthorized devices so for anyone that has this problem the fix is killing the server with adb kill-server, then using HOME=/sdcard After that profit. As for my Nexus 7 it's still being as stubborn as ever sadly. I'm getting these errors after installing the zip. I also have your busybox commands installed if that helps.
[Android Software/Hacking General [Developers Only]] osm0sis:
Looks like it's still not linking to the libraries like I told it to.. fastboot, adb and adb.bin seem like they were placed in /system/xbin/ correctly, but can you check /system/lib/ to make sure there's an adb directory there? It should have 5 lib*.so files in it. I installed it on my Nexus 7 systemless to test, but it's pretty straightforward and tested with my nano package, so system should work too. Could you have run out of space in /system?

Edit: Nope. My mistake. Missed renaming a variable in the installer so the libraries weren't getting installed in a system install. Fixing it up now, and adding your HOME=/sdcard trick to the wrapper. :good:
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
I have 163mb free in system. Checked out that directory and didn't see a adb directory In there. This 2013 has given me problems recovery wise since I first got it. When I first installed the latest current twrp it wouldn't mount or read any partitions whatsoever. I latter come to knowledge there was a revision somewhere along the line with the 2013 Nexus 7 flo. I had to installed Tasssadar's multirom twrp just to get the recovery working right. Do you think the revision or that twrp in the problem? Forgot to mention this to ya as I know its probably important info.

Edit: Gotcha ha-ha, this post may still be some info in regards to the problem. Once you updated the zip I'll test for you again and see if the problem persist. Thank you once again osmosis!
[Android Software/Hacking General [Developers Only]] osm0sis:
Nah, as I said, it was just something I missed in the installer. I've reuploaded the zip. Give it a try. :)
[Android Software/Hacking General [Developers Only]] KentuckyGuy447:
Appreciate you! ADB will now show up(Progress!) but my stupid Nexus 7 still can't find my Nexus 5. I have the OTG end plugged into it like I would be if my Nexus 5 was the host but it still cannot find my Nexus 5. Are you using the older model Nexus 7 2013 or are you using the later revised model? You can't really find anything about a revision but I've seen some people mention it around here on xda. Nothing really makes sense as to why it can't find it. Regardless whenever you fell to tell me to take a hike go for it lol! You've definitely done your part and I will respectfully take a hike! :D
[Android Software/Hacking General [Developers Only]] josteink:
Glad to see some of my old and obscure work still being of use :)
[Android Software/Hacking General [Developers Only]] osm0sis:
Just reuploaded the Busybox Installer zip to the OP with a couple fixes to the installer script. The binaries are the same so unless you had an issue there isn't really a need to reinstall.

Changes:

- improve symlink cleaning to work with different recoveries' `ls -al` output formatting.

- make symlink creation more intelligent/futureproof to work with different busybox binaries' included applets list output length.

- make systemless install "smart" by only creating applet symlinks in /su/bin for those applets that don't exist in /system/bin to avoid conflicts with toybox/toolbox versions.

The last item should help users who were seeing WiFi Calling disrupted after they installed Busybox to /su/bin, as well as issues with AdAway's webserver and root explorers like FX File Explorer being unable to remount /system rw, (to name only a few, I'm sure). /su/bin was designed to take precedence over /system/bin whereas /system/xbin does not, so by installing to /su/bin busybox was replacing some system functions it wouldn't in /system/xbin, which understandably can break some things.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
In this installer, do you clean up /tmp at the end of the script? Because after flashing this, I'm missing a large portion of my recovery log :(. I'm wondering if the SuperSU installer does the same thing . . .
[Android Software/Hacking General [Developers Only]] osm0sis:
Nope. Only cleans up what it puts there:

rm -rf /tmp/busybox;
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
Have you noticed any truncation of the recovery log after flashing Busybox?
[Android Software/Hacking General [Developers Only]] osm0sis:
No, I haven't. But I haven't been looking at the logs much lately either. /system/xbin installation or /su/bin installation or both?
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
Currently, /system/xbin, but I haven't checked the log after a systemless installation, so it might be the same. I'm not positive it's the Busybox installer that's doing it, but I haven't had a chance to confirm.
[Android Software/Hacking General [Developers Only]] osm0sis:
Yeah, doesn't make any sense given the script but let me know if you figure out it is related to my installer somehow.
[Android Software/Hacking General [Developers Only]] SpasilliumNexus:
Awesome! This fixed Solid Explorer and FC upon opening Layers Manager.
[Android Software/Hacking General [Developers Only]] osm0sis:
Even better, Chainfire took my suggestion to add /su/xbin and have it near the end of the path so things like busybox can be installed there and not conflict with any /system/bin counterparts. That's starting with the SuperSU 2.65 zip, so flashing that first is a prerequisite to what follows.

Accordingly, I've just reuploaded my Busybox Installer again with systemless support updated for a full install to /su/xbin if it exists, and just to still support any stragglers, it'll fallback to a smart install to /su/bin as well if /su/xbin doesn't exist.

If you'd like to switch from /su/bin to /su/xbin then please use the commands I posted in the SuperSU Beta thread, then flash the new zip.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
[MENTION=4544860]osm0sis[/MENTION]

Just tried adb from your installer on my One A9 running 6.0.1, and got this error when trying to connect to a device over wireless:

u0_a419@unknown:/ $ adb connect 192.168.1.149
CANNOT LINK EXECUTABLE: cannot locate symbol "__register_atfork" referenced by "/system/vendor/lib/libNimsWrap.so"...
page record for 0xf740103c was not found (block_size=16)
1|u0_a419@unknown:/ $

Any idea what the issue might be? I'm rooted systemless, with SuperSU 2.65.
[Android Software/Hacking General [Developers Only]] osm0sis:
That's weird, that's a linking issue, but none of the files I've included were linked to those when I checked all the binary and library dependencies.
[Android Software/Hacking General [Developers Only]] osm0sis:
I just added blurbs to the OPs for the unSU zip everyone now seems so fond of (for uninstalling system-modifying SuperSU <2.60, before the APK cleanup routines were fixed) and one of my more recent pet projects, GN PIT Editor to dump the old device's partition table and modify it to give /system more space. Could be useful to other (Samsung) devices that use PITs as well to make it easier for the average end-user to modify their device. My research and work leading up to the PIT Editor script are documented in a GN Dev forum thread, now linked in the Knowledge Post.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
So, any idea on how I can get it working?
[Android Software/Hacking General [Developers Only]] osm0sis:
Since that file shouldn't be called, can you troubleshoot it a bit more by checking whether everything extracted correctly? On systemless there should be /su/lib/adb/ and on system there should be /system/lib/adb/ with a few libs in there as you can see by looking in the zip. Likewise, fastboot, adb and adb.bin should be in the corresponding bin directory. Them not getting installed correctly is the most likely explanation.

If they are there, then there most likely is some kind of odd issue with the script, so following that, edit the bin/adb file (it's a script) and add the line "echo dir=$dir" between the dir=... line and the LD_LIBRARY_PATH=... lines, run adb from the command prompt again and tell me what it outputs dir as being.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
I am running systemless, and the files are all there.

EDIT: here's the ls output:

shell@htc_hiaewhl:/ $ ls su/bin
adb
adb.bak
adb.bin
aik
app_process
daemonsu
fastboot
su
sukernel
supolicy
supolicy_wrapped
sush
shell@htc_hiaewhl:/ $ ls su/lib/adb
libc.so
libcrypto.so
libdl.so
libm.so
libstdc++.so
shell@htc_hiaewhl:/ $

Here's my terminal output, after making the change you mentioned:

shell@htc_hiaewhl:/ $ adb
dir=/su/bin
CANNOT LINK EXECUTABLE: cannot locate symbol "__register_atfork" referenced by "/system/vendor/lib/libNimsWrap.so"...
page record for 0xf70e103c was not found (block_size=16)
1|shell@htc_hiaewhl:/ $
[Android Software/Hacking General [Developers Only]] osm0sis:
adb

adb.bak

adb.bin

What's going on there? That's not my doing.. :confused:
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
I made the change to the adb script and Root Explorer automatically creates a backup. That's nothing (knew I should've done the "ls" first - didn't think it would throw you off).
[Android Software/Hacking General [Developers Only]] osm0sis:
Is your device x64? These are only arm(32) binaries.
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
It is. That explains it. Thanks. Guess I'll have to find a different solution.
[Android Software/Hacking General [Developers Only]] osm0sis:
You should be able to duplicate the process by pulling the binary and libraries from one of the x64 Nexus devices that had Lollipop.

Edit: If I had a arm64 fastboot binary I'd add support to the zip. :good:
[Android Software/Hacking General [Developers Only]] osm0sis:
I finally found a working static adb binary, but it's a little old at 1.0.26. Worth a shot though since as static it might avoid the issues with the compatibility layer on your x64 device.

http://xdaforums.com/showthread.php?p=35677810

Remove adb.bin and adb from /su/bin, remove the adb directory from /su/lib and rename the linked file to adb and place it in /su/bin with 755 permissions. Let me know how it goes. :)