My script already does that on Lollipop, but as I said, there are further issues/changes in Marshmallow that I'm not sure can be resolved.
Okay well the first thing it needs is a working sed, awk, and unzip, which Marshmallow doesn't provide. Flash my busybox zip then make another symlink from /su/xbin/busybox to /su/bin/sed to override the broken /system/bin/sed. Then give the script another shot in /su/su.d/.
## GApps Auto-Integration Script Log
Sun Jan 31 22:52:58 CET 2016
/data/app/com.android.vending-1 /system/priv-app/Phonesky (80430500 > 80420700)
/data/app/com.google.android.GoogleCamera-1 /system/app/GoogleCamera (31021140 > 30039140)
/data/app/com.google.android.apps.docs-1 /system/app/Drive (54742340 > 53270545)
/data/app/com.google.android.apps.gcs-1 /system/priv-app/GCS (56 > 54)
/data/app/com.google.android.apps.maps-1 /system/app/Maps (919100020 > 913012024)
/data/app/com.google.android.apps.messaging-1 /system/app/PrebuiltBugle (16043130 > 14533138)
/data/app/com.google.android.apps.photos-1 /system/app/Photos (133708 > 72908)
/data/app/com.google.android.dialer-1 /system/priv-app/GoogleDialer (20312 > 20210)
/data/app/com.google.android.googlequicksearchbox-1 /system/priv-app/Velvet (300571362 > 300515542)
/data/app/com.google.android.inputmethod.latin-1 /system/app/LatinImeGoogle (23154 > 23104)
/data/app/com.google.android.launcher-1 /system/app/GoogleHome (103001 > 102000)
/data/app/com.google.android.youtube-1 /system/app/YouTube (108959640 > 107560144)
2nd reboot - integrated some apps (log was smaller) and apps like Maps and Photos won't be able to launch, it asks for uninstalling and again installing (but like systemapp they can't be uninstalled) , Play Services was updating from Play Store
3rd reboot - integrating another apps (log was again smaller) same problem with Maps and Photos
4th reboot - systemUI crash
5th reboot - still SystemUI crash
New addition to the OP.
Busybox 1.24.1 Installer:
I just want to note that I tried this on a fresh on my ZenPad S 8 (was clean installing the newest factory image, ZenUI 5.0.1, then flashed SuperSU, then your BusyBox installer) and TitaniumBackup wouldn't work so I checked the BusyBox version and it said 1.16.1. I saw online that 1.24.1 is the most current, so I used another popular BusyBox installer from the Play Store and TiBU reported that 1.24.1 was now installed.
Just wanted to let you know, because in the recovery install script it said x86 detected, and in this quoted post you said that 1.24.1 is the version that would be installed. Not sure if you knew, this was happening.
That doesn't really explain anything unfortunately. TiBU always packages its own busybox which is way back at 1.16.1, so it not working also has nothing to do with my busybox. Is your device x86? System it systemless root? It's sounding to me like everything worked fine, you just didn't know how to check for it.
Thanks for your reply!
Sorry I should have clarified - because my tablet is x86, I read on the TiBU knowledge base that I have to select "force system busybox" in TiBU. I want to say that when I checked thru TiBU it said BusyBox: 1.16.1 (from system) but not entirely sure. I am 100% that I had already checked "force system busybox" though.
And it is system install SuperSU (ya I had problems with TiBU and systemless on my 6P).
TiBU was still showing its internal version, because it's definitely still 1.16.1 for them. When you switched back from systemless root, did you delete /data/su.img? That would definitely fool my installer into believing that you were still systemless and keep it from installing correctly to system. The correct way to test an installation is to open a command prompt and type busybox, and since you didn't do that, I'm still thinking it might have worked just fine.
Looks like 2016 will hold a lot of script breakage and rewrites:
I'm already noticing some weirdness with sed not working at all like it should on my N7 2013.
su -c "ln -s /su/xbin/busybox /su/bin/sed"
|automation, batch, flashable zip, script, tool|
|Thread Tools||Search this Thread|