Related
I am working on a custom jb4.2.2 rom for the A13 SOC and wanted to add some features, ROOT By default - I added the su Binary and the SuperSU.apk however it does not work by default. If you boot into CWM Recovery then Reboot the device it offers to fix Root, when I select yes it proceeds and works fine... I would Rather make the ROM Rooted without having to do that any Ideas On what Im doing wrong ?
I am also interested in adding features to the ROM automatic Zipalign would be desirable as well as the ability to use a swap / zram. I am using a Stock JB 3.0.8+ Kernel and in at least one prior iteration I could use zram and activate swap... I would Like to make those features user selectable.
I currently have init.d working in the rom set in the init.rc using busybox run-parts. I do not have run-parts installed by default, is there a simple way to include the full busybox install as well ?
Assistance on any of these questions is appreciated.
Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v2.30!
(complete, with knox 0x0 reference! hehe)
This script/toolbox allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
(aroma installer and other magic like that gets ignored, but the aroma mods can usually be installed manually on a second run)
On top of that it allows you to create and restore backups of your system and data partition. (for "online" restore without needing custom recovery).
As we (hopefully) all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel....
But let me start with a few words of warning:
Dont do anything obviously stupid...there are no safe-wheels for most commands.
(for example: dont "clean-base" or use "rom-install" without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom the system ui gets stopped, so better do it over adb!
kn0x0ut toolbox is 100% safe for your device - no hardbrick or efs clear possible by using it!
The worst thing that can happen when using the kn0x0ut toolbox is that you have to factory reset or flash again with odin, so keep the odin file close. (at best this is a custom made RDLV odin.tar.md5 you used to upgrade your rom version with - or for people who have to use other methods because of the new bootloader - keep the last odin file close you used to upgrade also.. and the root method that worked for you)
This whole thing "programmed" on/for a N9005 but in theory it should work for all samsung devices - including the other knox enabled devices and even on many other devices. (but it might need some adjustments, so be careful and have a way to restore your stock rom before you try anything fancy with other devices)
If your knox warranty is already void aka 0x1 then you can still use the toolbox and its mods (some could actually be useful to anyone..) but it won't bring back the warranty.
I didn't really create this thing for me actually - I already did the all steps the toolbox can do by hand with adb terminal on my device (and perfected my method with lots of trial and error..), but I wanted you guys to also be able to enjoy custom roms while keeping your knox warranty intact and show samsung a big FU for putting us through this BS in the first place...
If you like the toolbox and appreciate the work I put into this please consider buying me a beer or hitting the thanks button at least.
---
This kn0x0ut toolbox itself requires root access (if you want to be able to install mods and files you need to be able to mount system writable)!
You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
IF YOU GET "PERMISSIONS DENIED" ERRORS, PLEASE TRY THE FOLLOWING COMMANDS TO REMOUNT YOUR SYSTEM WRITABLE:
(please try them all, and report back in the thread which one works, and which fail or get permission denied)
Code:
mount -o rw,remount /system
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
mount -o rw,remount /dev/block/mmcblk0p23 /system
---
How to use:
Extract the download from below to the root of your internal or external sd card.
The script will try to detect the folder first on the external and then on the internal sd.
(/mnt/extSdCard/kn0x0ut or /sdcard/kn0x0ut)
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
and you will get all the commands supported currently.
---
You can then use the command
Code:
sh kn0x0ut.sh kn0x0ut
to install the script to your system's xbin folder and create a symlink to "/system/xbin/knoxout" as well.
(if you want to upgrade kn0x0ut from an older version, make sure you delete all the duplicate old files from the kn0x0ut folder - basically everything but the "processed" and the backup folders if you have them, and replace them with the files from the latest versions download. Then re-run the "sh kn0x0ut.sh kn0x0ut" command to update the kn0x0ut script in your system/xbin folder as well)
From then on you can just type
Code:
kn0x0ut <command>
or even easier:
Code:
knoxout <commands>
The script will automatically detect the kn0x0ut folder on the external or internal sd. (external has higher priority if both present)
To install a zip file meant to be flashed in CWM, you put in into the "put_files_folder". You can put zip, tar, tar.gz or already extracted files and folders into there.
---
To actually work, the files/folders must be in a certain stucture. The script expects already extracted files which get placed into the put_files_here folder to be in the structure like they would appear on the device.
Think of the "put_files_here" folder as the root folder - files get placed on the system in the same structure as if the put_files_folder was the rootfs "/". So if you got a subfolder system/app inside the put_files_here folder, the files inside it will get pushed to /system/app... Hope this makes any sense, else someone else pls try to explain it better.
(NOTE: The script will only install files, it wont do additional magic if there is any contained inside the zip like aroma installer - its mainly meant to speed up the process of installing mods and/roms that require system files to be replaced. (and some things might need to be done by hand, if you want enhanced functionalities from aroma installer)
If you have a zip that does not fully install, check out if there are any scripts inside etc. - and also check the "not_installed" folder which gets created after each installation.
If you want to install a rom, make sure you are on the same base version as the rom you are trying to install. So if you want to flash rom "xyz" based on MK2 then you gotta have stock, but rooted MK2 installed (with odin and RDLV for example). If you want to mix versions, you can try - but I can't tell if that actually works or causes problems - I just would skip the BS and make sure you got the right base rom installed with odin before tying to install a custom rom with kn0x0ut...
---
See 2nd post for current command list.
See 3rd post for current list of available mods.
See 4th post for more detailed command explanation.
See 5th post for download.
Code:
>>> commands <<<
Help:
-----
help - Display help
listmods - Display a list of all available mods
Backup:
-------
backup-base - Backup system app and framework files
backup-efs - Backup efs partition
backup-system - Backup system partition
backup-data - Backup data partition
backup-full - Backup system and data partition
Installation / Restore:
-----------------------
install - Install contents of "put_files_here"
(place backup tar's there for restore)
For System Restore use "rom-install"!
For Data Restore run "clean-data" then "install"!
rom-install - As above but clean system apps, framework
and dalvik-cache before
Mod Installation:
-----------------
mod=[mods] - Install specified mods (for multiple seperate with ',')
Special:
--------
supersu - Install supersu v1.80 to xbin (incl. init.d support for all kernels)
busybox - Install busybox v1.21.1 to xbin (incl. symlink-redirect)
kn0x0ut - Install kn0x0ut v2.30 to xbin
fix_perm - Install fix_permissions v2.10 to xbin
backup_perm - Install backup_permissions v2.00 to xbin
Cleaning:
-----------------------
clean-dalvik - Clean dalvik-cache
clean-base - Clean system apps and framework (MAKE SURE YOU INSTALL NEW BEFORE REBOOT!)
clean-data - Clean data partition to restore from backup (leaves sdcard content alone)
Bloatware Removal:
------------------
removebloat-cooolboy - Remove most bloatware (based on CoOoL_BoY's bloatware remove script)
removebloat-zroice - Remove bloatware hardcore mode (beware - most google stuff gone except playstore)
>>> commands END <<<
Code:
>>> available mods <<<
Mod: acid
Description: ACID Audio Engine v5 (optimised for samsung)
Mod: acid_awesomebeats
Description: ACID Audio Engine AddOn - Awesome Beats
Mod: acid_noozxoide
Description: ACID Audio Engine AddOn - Noozxoide
Mod: aosp_browser
Description: AOSP Browser (with Google, Startpage & Startpage Mobile)
Mod: aosp_clock
Description: AOSP Clock (deinstall ClockPackage.apk if you want to use this)
Mod: bash
Description: BASH Shell
Mod: busybox
Description: busybox v1.21.1 (busybox.net) + special default symlink fixes
Mod: chronus
Description: Chronus Clock Widget
Mod: forcelte
Description: Init.d script to force lte on
Mod: onandroid
Description: onandroid script v9.20 + necessary binaries (mkyaffs2image, dedupe)
Mod: onandroid_n9005
Description: onandroid partition layout for N9005
Mod: openvpn
Description: openvpn binary v2.1.1 (statically linked, no libs necessary)
Mod: sqlite3
Description: sqlite3 binary + libs and init.d script to optimise db's at boot
Mod: zipalign
Description: zipalign binary + init.d script to run at boot (fixed to make it work!)
>>> available mods END <<<
Add ons and commands explained in detail:
1.) Fix permissions script is running after all the commands to ensure permissions are correct. You can also install the fix_permissions script as standalone command. (see command list)
2.) To install a rom or other cwm zip file put it into the "put_files_here" folder and run "install" or "rom-install" depending on what you want to do. You can also use this to restore system and data partition backups made by kn0x0ut or onandroid (those have to be in tar or tar.gz format).
3.) The busybox which gets installed is directly from busybox.net and has more commands than the "normal" busybox floating around from stericson.
Additionally if you use the "busybox" command some symlinks will get redirected from toolbox to busybox and give enhanced functions.
(for exampe: mv, cp, rmdir, rm, ...)
4.) "sqlite3" and "zipalign" will also install an init.d script so that they are running on system boot to optimize the dbs and/or zipalign the apks.
--- more to come ---
Current Version: v2.30
### Downloads ###
Please do link to this thread if you want to use the kn0x0ut toolbox for other projects.
(do not distribute kn0x0ut download links but instead link to this thread, not only for credits, but so people can report bugs etc in one place)
READ THE INSTRUCTIONS AND TRY TO REMOUNT YOUR SYSTEM WRITABLE BEFORE YOU TRY TO INSTALL A ROM! AND ONLY DO THAT OVER ADB SHELL!!!
>>> YOU HAVE TO RUN KN0X0UT AND ALL ITS COMMANDS AS ROOT USER IN TERMINAL OR OVER ADB SHELL. TO MAKE THE SHELL ROOT YOU HAVE TO TYPE "SU" AND THEN ENTER BEFORE USING ANY OF THE OTHER COMMANDS! <<<
kn0x0ut_2.31.zip - 14.84 MB
Do not run rom-install if any of the other commands fails, and please try them first. (at least busybox and supersu installation)
reserved
reserved
So if I already have Knox at 0x1 am I screwed?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
harosxcomp170 said:
So if I already have Knox at 0x1 am I screwed?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
well then this thing has no use to you, other than the addons and installing stuff on a running system instead of using custom recovery.
But it wont fix the knox warranty no. It just KEEPS it from getting tripped by allowing installs without custom recovery.
Now say if I odined back to completely stock with no root. Will that bring my Knox back to 0x0? Or has the damage already been done?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
harosxcomp170 said:
Now say if I odined back to completely stock with no root. Will that bring my Knox back to 0x0? Or has the damage already been done?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
sorry to say, but gtfo with these questions inside this thread! knox 0x1 stays knox 0x1 - so far nothing gonna bring it back - ssheeesh this you should really know man. one lil google search gives you 100 threads about just that! (completely offtopic to this tool also... sorry but is this xda or android central?!)
Yea sorry about that I didn't know if there was a break through or something I bought my phone off swappa with knox already voided.
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
harosxcomp170 said:
Yea sorry about that I didn't know if there was a break through or something I bought my phone off swappa with knox already voided.
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
well tbh, I wouldn't worry so much about it, I'm strongly considering to trip my flag to have custom kernel and recovery. This toolbox here can't fully replace it. But maybe we find a way to make our own signed kernels and/or recovieries or some other way around this knox warranty void bs.
My phone is still new and for such an expensive piece I rather don't risk anything before it's clear there are no bugs out or smth people dont yet know about (I mean with the hardware, not with my toolbox or smth). Plus its fun to try out whats possible.. (i learned so much about android and the shell by doin all this... good exercise hehe)
So until then I'll keep my warranty intact - and beside overclocking and some kernel tweaks and maybe easy nandroid backups/restore we can do quite alot.
---
@ the others with their flags still intact: Why so shy? Any success stories so far? This would get more attention if someone would confirm it working other than me hehe =). You all pushed me to make a script now use it! (try X-note for the start or smth .. thats what I'm using and it worked fine)
Cf root will trip the KnoX.
But samsung accepts one time warranty even if u tripped it.
This is my 3rd note, in 3 executive years. Ive never needed warranty. The golden rule with Samsung phones is if it works (hardware), it will stay to work for years. Just like German Mercedes from the '80s and '90 s.
Greetsz
Sent from my SM-N9005 using Tapatalk
but it's impossible to use your program without root? it's right. my phone it's already in rom MJ7, so, no soluce now to root without tripping the knox to 0x1..
Will i need to run scrtips once?
or before install more rom.
Will this wipe my phone? Dont wanna loose my data
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
no it wont wipe data partition.
If you just use the "install" command it wont wipe anything, just copy over and overwrite the files that exist.
If you use the "new_rom" command it will wipe the system apps and the framework before installing.
If you come from odexed and want to install deodexed version you must use the "new_rom" command or else you will have odex files and some incompatible system apps left.
---
I'm also working on a way to backup and restore system as well as data.
What I really would like to know is what happens if you create an odin image from your system partition and flash that back with odin or mobileodin. It would just "restore" the system to the state where you created the image, but the question is if that would trip knox or not.
To be honest I doubt it would, since we only install a system image back that was already "ok" for knox - you already got the custom system partition flag when one uses RDLV or somehow else attains root access because the system is not unmodified, so this wouldnt change anything.
The only problem with my thinking would be if odin / mobileodin implements a special check thats only triggered when you flash through it and which will then trigger the knox flag if it finds a custom image.
If you find any stories of people who just flashed a (custom) system image through odin or mobileodin please point me there. So this question can finally be answered fully.
If we could just flash system images with odin while leaving out kernel and recovery and keeping knox, this would make custom recovery obsolete kind of. The only thing we still couldnt do then would be to use custom kernel features. So please help me to find out!
Yeah
So will new rom erase
game saves
Sms
Installed apps
Settings?
Okay if i find such thread ill post or pm it to you
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
It shouldnt, although you might end up with other problems.. not 100% sure to be honest. (I only installed on freshly wiped device so far, or wiped afterwards etc, just to make sure)
Best thing to do is backup everything with titanium and then give it a try - but make sure you backup stuff to your external SD or copy it over to the pc, because the internal sd will get wiped if you have to factory reset. (just do a backup of everything with titanium and then copy the contents of your internal SD card (everything - to include game saves etc) to your pc.
If end up having to factory reset because of bugs from the old data you can just restore the apps with titanium and have your internal sd contents backed up.
---
If you give it a try (if you have the titanium backup and the internal sd contents you can always restore the old state at least) please report if you had to wipe data or if everything runs fine?
When I tested things around I did this already and the data stayed - but i did not test all the apps to really make sure.. so theres a small chance for problems - but I actually doubt it.
Update 14-Jul/18: Busybox v1.29.0 released (Complete changelog: here)
Hello XDA,
All the flashable zips include two builds.
SELinux Enabled and Normal
This post will give you a pretty good idea about the difference.
There are 401 applets included in the normal and 413 applets included in the selinux build.
Here's a list for the same.
NOTE: Installing busybox does not modify your device's selinux status.
Architectures supported: arm, arm64, x86, x86_64, mipsel, mips64el and mipseb.
The attached zips install busybox in one of /magisk/bbxyds, [/data/adb]/su/xbin, /system/xbin, [/system]/vendor/bin after cleaning older busybox binaries and their symlinks from the device (if any).
Universal busybox installer flashable zip detects the architecture and installs busybox accordingly.
Code for mounting the su.img and running in embedded mode is borrowed from the SuperSU project.
SELinux status is automatically detected by the installers.
Behaviour of all the installers as well as the cleaner can be manipulated using a bbx.conf file which should be placed in one of /sdcard, /data or /cache. For more details refer to the second post.
TWRP recovery or Flashfire is recommended for flashing the attached installers, however the code is pretty generic and should work on other recoveries too.
Projects using my BusyBox builds are:
Open Gapps
Apps2SD
Project Skynet
StØck ROM Sense 5 by @denkem
Stock Debloated roms for nexus 5, 6, 5x and 6p by @tupac4u
Inlightning Org
Universal SafetyNet Fix by @Deic
If you would like to include my builds in your project, a link to this thread in the project thread would be expected.
Also, if you can, pm me about it so I can add the name to this list.
Credits:
@7175 for his thread
@bovirus @Chinaboy5216 @skulldreamz for testing and reporting
XDA for...do I need to say it
Disclaimer: Neither me nor anyone else at XDA is responsible for what happens to your device. Please use the tools/utilites attached at your own discretion.
Having said that, I'll try my best to help you with any bugs or exceptions you might face.
Download: Click here
Mirror: Sourceforge
Busybox-CLEANER.zip and all the installers clean BusyBox in /su/xbin /data/adb/su/xbin /system/xbin /system/vendor/bin /vendor/bin /data/adb/su/bin /system/bin /su/bin /magisk/phh/bin /su/xbin_bind /data/adb/su/xbin_bind and /magisk/bbxyds
The installers will automatically detect 32/64 bit arch and install the appropriate binary
NOTE: If FlashFire gets stuck on a black screen or errors out when flashing, please flash from recovery instead. (There seems to be a /system mounting issue on some devices in FlashFire)
File list:
Busybox-<VERSION>-YDS-UNIVERSAL.zip
Flashable zip compatible with all architectures.
Busybox-<VERSION>-YDS-<ARCHITECTURE>.zip
Architecture specific flashable zip files.
Busybox-<VERSION>-YDS-<ARCHITECTURE>.tgz
Consists of pre-compiled busybox binaries.
Not flashable
Busybox-installer-<ARCHITECTURE>.bin
Executable files for installing busybox without rebooting in recovery mode. See 2nd post for more details.
Not flashable
Source code (zip, tar.gz)
Source code files automatically generated via Github releases.
Not flashable
For older versions refer to my androidfilehost, drive, mediafire or sourceforge folders.
Toolchains used for building these binaries can be found here (host arch -> x86_64).
For official busybox source and changelog refer here.
Do report how these work out for you, as most of the testing has been done on emulators.
You can request any applet in this thread. If it does not affect the size of the whole binary or there are enough users backing it, I'll add it in the next release.
When reporting please attach the BusyBox-YDS-installer.log, it should be in either /sdcard, /data or /cache.
Source:
https://github.com/yashdsaraf/busybox
https://sourceforge.net/p/busybox-yds/code
Op
bbx.conf:
Allowed options in bbx.conf are,
installdir=<path>
Change the directory for installing busybox to <path>. If <path> is not a valid directory, then the installer will fall back to the default installation directory.
Note: Any older busybox installation in the supplied directory will be cleaned.
Warning: Please use this option only if you are absolutely sure about what you are doing.
e.g installdir=/data/local/xbin
selinux=[0|1]
Controls the selinux support in busybox.
E.g To disable SELinux support
Code:
selinux=0
To enable SELinux support
Code:
selinux=1
noclean
If supplied, the installers will skip cleaning any previous busybox installations.Sample:
To install busybox in /data/local/xbin without cleaning previous busybox installations with SELinux support enabled, following would be a valid bbx.conf file
Code:
installdir=/data/local/xbin
noclean
selinux=1
Note: Busybox cleaner only reads the installdir option and cleans busybox in that directory
Self extracting executables:
All the .bin files in the download link in the above post are self extracting executables. They can install busybox directly from a terminal without rebooting in recovery.
Usage:
Install any terminal app.
Get root privileges,
Code:
su
E.g if you have the installer for ARM downloaded in sdcard, run this
in the terminal,
Code:
sh /sdcard/Busybox-installer-arm.bin
And watch the magic happen.
Options:
-h | --help
Show help message. -i | --interactive
Run script in interactive mode.-nc | --noclean
Do not clean previous busybox installation(s) (IF ANY).-oc | --onlyclean
Clean previous busybox installation(s) (IF ANY) and exit. If supplied, all other options are ignored except installdir.--selinux=[es|o]
Enable or disable selinux support in busybox.--installdir=<path>
Install busybox in <path>.Tip: To clean busybox in a custom directory, run the installer in onlyclean mode and set installdir to the custom directory which needs to be cleaned.
e.g. to clean busybox in /data/local/xbin run the installer as
Code:
sh <script_name> -oc --installdir=/data/local/xbin
@YashdSaraf
Thanks for new thread
"[TOOL][BIN]busybox flashable for all architecture via recovery"
I will remove "Latest" and add info that is flashable via recovery.
I will change the thread title in
Nice work .
Keep it up !!!
Sent from my E2303 using XDA Free mobile app
bovirus said:
..Thanks for new thread....
Click to expand...
Click to collapse
is the issue mentioned here addressed? @YashdSaraf, hope you read my pm.
@YashdSaraf had a quick question. I have been using your busybox zips since you've staying building and i first want to say thank you. My question is when i use the busybox unistaller zip or busybox cleaner with your zip it says that it removes 0 symlinks and when i use stericson busybox zip it says that I'm removing 3xx plus symlinks. I was just wondering wondering why his and osmosis show that binaries were symlinked and yours showed that 0 were? I want to lastly say though that your zip worked and busybox was installed and worked correctly. I like some of the extra binaries yours offers do just a curious question thanks.
Sent from my Nexus 6P using Tapatalk
m0han said:
is the issue mentioned here addressed? @YashdSaraf, hope you read my pm.
Click to expand...
Click to collapse
I did, I'm sorry I was too busy switching to a new OS. Anyways, I've got a couple of ideas over what might've gone wrong. I'll pm you the updated installers as soon as I'm done for testing. :good:
skulldreamz said:
@YashdSaraf had a quick question. I have been using your busybox zips since you've staying building and i first want to say thank you. My question is when i use the busybox unistaller zip or busybox cleaner with your zip it says that it removes 0 symlinks and when i use stericson busybox zip it says that I'm removing 3xx plus symlinks. I was just wondering wondering why his and osmosis show that binaries were symlinked and yours showed that 0 were? I want to lastly say though that your zip worked and busybox was installed and worked correctly. I like some of the extra binaries yours offers do just a curious question thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I did not update the uninstaller after systemless root was introduced so it must be looking only in the /system partition for busybox. I'll upload the updated uninstaller today.
Thanks for your support.
YashdSaraf said:
.....I'll pm you the updated installers as soon as I'm done for testing.....
I did not update the uninstaller after systemless root was introduced....
. I'll upload the updated uninstaller today.......
Click to expand...
Click to collapse
got your pm. will test the updated installer and revert by pm.
is this 'the updated uninstaller'? can this be used in 'any setup'?
m0han said:
got your pm. will test the updated installer and revert by pm.
is this 'the updated uninstaller'? can this be used in 'any setup'?
Click to expand...
Click to collapse
Yes the one attached in the OP is the latest one. It will clean busybox in /system/bin, /system/xbin, /su/bin, /su/xbin.
So yeah it can be used in 'any setup'.:good:
@YashdSaraf
Are there any news about busybox for ARM and 64boit Android SO (like 5.1.)?
YashdSaraf said:
.....I'll pm you the updated installer......
Click to expand...
Click to collapse
...will test the updated installer and revert .....
your zip worked well, i think. thanks.
86_64 for zenfone 2 Z00A?
@YashdSaraf
Thanks for sharing mate. really appreciated. :good:
PM sent
Cheers,
UITA
@YashdSaraf
thanks for your busybox.
I had some problems to install it (I tried arm/arm64/all zip file withS elinux).
Every time the installation end with error "Wrong architecture".
My build propri content about cpu is
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
To install I had to use previous zip file (1.24.1) where you not have archictecture check and replace 1.24.1. busybox with busybox extracted by 1.24.2 zip.
Where can i get the error log of your script? It show just only /data...
Please check your script.
Thanks.
@YashdSaraf Could you update busybox to 1.24.2?
@exodius48
All busybox files in first post are version 1.24.2.
@YashdSaraf
Please add a note in first post about the vesrion of busybox.
bovirus said:
@exodius48
All busybox files in first post are version 1.24.2.
Click to expand...
Click to collapse
Sorry for asked it. I couldn't find busybox version on 1st post, also on the tittle.
@exodius48
In the first post there are various Download links with all busybox for all platforms.
OK... the BusyBox app on the play store had an update to 1.24.2.
When I install the update from 1.24.1 to 1.24.2, it states that it installed successfully, it doesn't reflect it.
It still shows that 1.24.1 is installed.
I tried wiping the dalvik cache before and after as well as reinstalling the app and it still reflects 1.24.1.
Also, it displays that 1.24.2 will be installed in the system xbin but, doesn't.
Thank you.
bovirus said:
@YashdSaraf
thanks for your busybox.
I had some problems to install it (I tried arm/arm64/all zip file withS elinux).
Every time the installation end with error "Wrong architecture".
My build propri content about cpu is
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
To install I had to use previous zip file (1.24.1) where you not have archictecture check and replace 1.24.1. busybox with busybox extracted by 1.24.2 zip.
Where can i get the error log of your script? It show just only /data...
Please check your script.
Thanks.
Click to expand...
Click to collapse
Hey,
I think the reason for failure was that the script could not detect the /data partition.
Please try these zips instead.
arm arm64
There should be a BusyBox-YDS-installer.log in either /sdcard, /data or /cache, whichever your device supports.
Do attach it when reporting back.:good:
Ibuprophen said:
OK... the BusyBox app on the play store had an update to 1.24.2.
When I install the update from 1.24.1 to 1.24.2, it states that it installed successfully, it doesn't reflect it.
It still shows that 1.24.1 is installed.
I tried wiping the dalvik cache before and after as well as reinstalling the app and it still reflects 1.24.1.
Also, it displays that 1.24.2 will be installed in the system xbin but, doesn't.
Thank you.
Click to expand...
Click to collapse
I'm not sure what are you talking about. I'm not related whatsoever to any play store busybox installer apps. Try one of the installers from the op to install 1.24.2 busybox.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know that there is many tools apps etc to disable or hide SU.
I decide to make this just because those did't work on my device back in 2016 and or CyanogenMod/LineageOS ROM that I use, so I assume this happens to other in CyanogenMod/LineageOS users too, I start this thread and made this app that can help to pass a safety net test on any rooted device (hide SU only when using Lineage add on SU) as it is no longer just a SU hider app is little more.
This is only to CyanogenMod/LineageOS SU binary aka CM-SU, the CM-SU only works with CyanogenMod/LineageOS ROM's and ROM that use they source code as base
That can be Download from Lineageos download page click here to see
No it doesn't work with SUPERSU or any other SU that is not base on CM-SU
No it doesn't support Xposed Hide, if you use Xposed you can't pass safety net with CM-SU.
No it doesn't support AB devices (devices with two system partition) that can't be mounted as rw dynamically in android.
What is iSu?
A simple app to help the user to pass safety net test on CyanogenMod/LineageOS or any CyanogenMod/LineageOS base ROM's.
I personally test this on Marshmallow and Nougat CM base ROM's it works 100%, it also Supports Lollipop but Kit Kat and older OS's are not supported.
How To use it?
read Installation instructions, download Folder with instructions on the bottom of the post
Download and Install the app as a normal app, if you wanna the full app support, use a ROM with the supported SU version (CM-SU), download Folder with instructions on the bottom of the post
if on Marshmallow or Lollipop flash the zip (iSu_kernel_Reboot_Support), download Folder with instructions on the bottom of the post
Learn how to use the app, below instructions
How To pass safety net?
Su deactivated (demanding)
SELinux enforced (demanding)
Android debugging deactivated (not demanding for all devices)
Props known props or special props can't have a red warning (demanding)
Below are some samples of fails or pass:
PASS
*Android debugging only affects some devices, disable if you don't need it.
*In props if there is props with a red warning that may be the reason of the fail if SU and SELinux is set as the above.
If you have SU active you will always fail
FAIL everything
*Fail because SU is Activated
If you have SU deactivate you will not always pass
FAIL everything 2
*Fail because SELinux is in Permissive
If you have SU and SELinux on a correct position you may not always PASS, because some props cause fail of ctsProfile
FAIL ctsProfile
*The above fail because ro.boot.verifiedbootstate
*Some props may or may not cause full FAILS or a FAIL of ctsProfile
Detailed app function description?
The app is divided in 5 tabs (Checks, Controls, Monitor, Props and settings), plus widgets and tiles, bellow a detailed description:
Checks
Basic information about the application, the main start tab if it show a red warning on the SU state options because yours current SU is not supported and the app will work with limited functionality.
SU State, current user SU version and reboot support status
Update, Check for iSu updates
Safety Net test, Let the user try the safety net status, in case of fail it will tell what fail and current SU, SELinux and ADB state as those if on wrong position will cause the fail
Log, Generate a full logs of information about the device and how the app is running, in case of a problem share the log.zip on the thread and explain the problem
Controls
The main control tab, be aware there is extras actions for this controllers in settings tab
SU, Changes and show SU state. This function only works with CM-SU
SELinux, Changes and show SELinux state, plus allow user to fake enforce Selinux for devices that have problems when running with SELinux enforced
Android debugging, Changes and show Android debugging state
Tasker, Info about how to control the app using Tasker
Monitor
This tab only works with CM-SU
A Service to monitor when foreground app starts then, activate or deactivate SU and SELinux or ADB (base on settings options).
App monitor, Status and access to accessibility service.
Don't Care List, Select the apps that will not have effect to App monitor, when a foreground app start.
Deactivate SU, Select the apps that will deactivate SU when started
Automatic Re-Activate SU, If this switch is on, will automatic active SU when leave the app that deactivated SU
Activated SU, Select the apps that will activate SU when started
Automatic Re-Deactivate SU, If this switch is on, will automatic deactivate SU when leave the app that activated SU
Props
A tab to change the value of any ro.prop or read only prop, using the resetprop applets from magisk to make a tool to modify on the go any ro.prop, there is also a list of known props that can cause safety net fail they safe or unsafe value
Read Only editor, List of ro props and the ro props changed by the user
Special Props, Known props that has a complicated value that can't be define as OK or NOK
Known props list, just explanation about safe, unsafe or unknow values
Force set all Known props, Click to force all Known Props to the chosen value
Known props, the real list of known props and they current value click to change
Settings
Basic application setting, extra controls and notifications
Application, Allow to force language to English
SU, Extra SU options allow to deactivate it on boot This function only works with CM-SU
App monitor, Allow delays to app monitor This function only works with CM-SU
Props, Allow to apply props changes on boot
Notifications, Enable disable notifications or toast's of SU state This function only works with CM-SU
SELinux, Extra control of SELinux state base on SU is state changes This function only works with CM-SU
Android debugging, Extra control of Android debugging state base on SU is state changes This function only works with CM-SU
Widgets and tiles
The app has widget and tiles that can be used to control the app Controls
Widgets They only work with CM-SU for SU changes
Mono Widget, Allow to change and read SU state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
Dual Widget, Allow to change and read SU or SELinux state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
Tiles Only visible on Nougat
SU tile, Allow to change and read SU state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
iSu tile, Click to open the app
Installation instructions:
Download Folder: Click Here
There is three files, description:
iSu_X_x.apk Install the apk as a normal app.
iSu_kernel_Reboot_Support_V_X_x_and_up.zip Flashable zip, flash only if you are running Marshmallow or Lollipop
Explanation of the above, iSu only need flashable reboot support for Marshmallow or older OS.
The kernel reboot support , this files prevents from losing SU access after a reboot with SU deactivated.
Old reboot support, in case the current fail
Old reboot support download Folder: Click Here[/B]
iSu_kernel_Reboot_Support_V_X_x_and_up_Enforcing.zip Flashable zip, use only one zip, if running Marshmallow or older
iSu_kernel_Reboot_Support_V_X_x_and_up_Permissive.zip Flashable zip, use only one zip, if running Marshmallow or older
Explanation of the above, iSu only need flashable reboot support for Marshmallow or older OS.
The kernel reboot support use only one(enforcing or permissive), this files prevents from losing SU access after a reboot with SU deactivated.
Use the one base on yours current Selinux status to check on your device look in settings > About a phone > SELinux Status if is enforcing or permissive, some CM ROM Run with selinux in Permissive so check yours.
Be aware!!
Updating CM/Los nightly or any ROM update of any CM/Los base ROM will remove the changes made by the zip, so is need to re-flash those .zip after any ROM update, may be need to do it also with some custom kernel from developer that use a boot.img to share the kernel(check yours kernel zip content to know).
If you forget to flash the .zip in a update and have lost ROOT don't worry just go back to recovery and flash it after the reboot all will be good.
The below are obsolete after V3.6 of the app, see old_version folder in main download folder for those files just reference no longer supported
iSu_kernel_cmdline_Patch_V_X_x_and_up.zip
The kernel_cmdline is only need to some devices that after deactivating SU with the app still can't pass the safety check, Google is using kernel and bootloader arguments to determined that the user modify the stock SW(AKA is using custom ROM) and prevent from passing as "safe", this add extra safe arguments to cmline and help to achieve the pass current it only support some device (Nexus and Motorola, maybe other post on the thread device/vendor if the zip help you)
iSu_kernel_defaultprop_Patch_V_X_x_and_up.zip
This is only for those that have apps that use rootbeer SU detection...
explain in this post (Click here).
After flashing defaultprop_Patch zip the user will no longer have access to the option in Settings > Developer options > Root access
But that is not a problem as the same zip will enable root by default so you can use without changing that option.
XDA:DevDB Information
iSu, App for all CyanogenMod/LineageOS devices (see above for details)
Developer donation link:
To donate via paypal click here
No other donation option is available.
Contributors
All Contributors can be see in github click here
fgl27, I use osm0sis Anykernel2 for the kernel zip
App Source Code: https://github.com/fgl27/isu
Extra App credits: iSu readme credits
Version Information
Status: Stable
Current Stable Version: Check latest version in Download folder
Changelog
Created 2016-Oct-03
Last Updated Check latest version
Changelog
Last app version Click to Download
Awesome work! Glad I accidentally stumbled on to this. Magisk stopped working to hide root but this is still good. Woot!:good:
edit: In your isu.sh, shouldn't the end of the script be:
Code:
mount -o ro,remount /system
# instead of
umount /system;
edit 2: For anyone who wants to build their device/kernel with support baked in, so they don't have to patch, I distilled the changes down from your git and created this patch:
https://github.com/blastagator/cm_d...mmit/79118c58fee32d10aa75464ee95751c7e6b8fdc5
This should be a good basis for others to manually patch in support. Working well on my custom cm13 builds.
blastagator said:
Awesome work! Glad I accidentally stumbled on to this. Magisk stopped working to hide root but this is still good. Woot!:good:
edit: In your isu.sh, shouldn't the end of the script be:
Code:
mount -o ro,remount /system
# instead of
umount /system;
edit 2: For anyone who wants to build their device/kernel with support baked in, so they don't have to patch, I distilled the changes down from your git and created this patch:
https://github.com/blastagator/cm_d...mmit/79118c58fee32d10aa75464ee95751c7e6b8fdc5
This should be a good basis for others to manually patch in support. Working well on my custom cm13 builds.
Click to expand...
Click to collapse
Thanks. For me was similar, magisk did not support my device so user complain to me about support as I did not manage to make magisk to work on my device I manage to make this that seems to be 100% for the most none rooted app.
regards the RW/RO
Theoretically yes but things was a little odd when I first start test for this... for simple reason if we don't mount system as RW we can "hide" or "un-hide" SU because is need to move it and system boot in RO, and if leave it mounted as RW safety net check will not be successful even if SU is hide, but after some safety net update on the google side mount it as RO at the end was not working in the .sh and the unmout was, maybe was some other related problem but it work so I did not change...
So I keep the unmount did not test any more after, and in the java code every time the switch is use it start with RW and ends with RO and that does the trick...
I have update the reboot support and the app for Nougat, Selinux is a little more restricted on N and I did not had the time to test a universal .zip to support N as the changes I did in the ROM I build are a little more time demanding to make it right, or not I really only have my build to test on my devices as N is just starting there is no other ROM, I really need another ROM that doesn't have any of my changes to test and really make it fully work with a simple .zip
But every things is also fully working on N CM did not change the SU binary, safety net, pokemon and payment app are all good, at least for know...
:good:
I update the project for N but I only manage to fully test on my ROM so if any one try and have problem read #3 post and report on the thread.
Hey guys, just tried out this in my Redmi Note 2 Prime with Bule's (cleaned) MoKee ROM CM12.1, and worked great, until now, because says, when I'm going to "hide" su, that the "su state change fail" Don't know for what it was, but if you can help me solving this, I would be grateful
Bhb thank you, using on my daughter's xt1254 phone now which runs cm 13.
---------- Post added at 03:16 AM ---------- Previous post was at 03:12 AM ----------
Shadow646 said:
Hey guys, just tried out this in my Redmi Note 2 Prime with Bule's (cleaned) MoKee ROM CM12.1, and worked great, until now, because says, when I'm going to "hide" su, that the "su state change fail" Don't know for what it was, but if you can help me solving this, I would be grateful
Click to expand...
Click to collapse
This is the reason for the kernel hack.
Without it you can lose root.
Dirty flash your ROM and if the kernel hack won't work
Then just be sure to set everything back to normal before any reboots.
I "THINK" then you would be okay.
mrkhigh said:
Bhb thank you, using on my daughter's xt1254 phone now which runs cm 13.
---------- Post added at 03:16 AM ---------- Previous post was at 03:12 AM ----------
This is the reason for the kernel hack.
Without it you can lose root.
Dirty flash your ROM and if the kernel hack won't work
Then just be sure to set everything back to normal before any reboots.
I "THINK" then you would be okay.
Click to expand...
Click to collapse
Yeah, I did that, but dunno if was because of that it failed, or not... I'm fine for now, reverting it whenever I close the game, I put su back Maybe it was because I was trying to cheat on PoGO, and didn't work with Fly GPS, and uninstalling the app in a bad way provoked that I will do a nandroid and try again
Edit
Shadow646 said:
Yeah, I did that, but dunno if was because of that it failed, or not... I'm fine for now, reverting it whenever I close the game, I put su back Maybe it was because I was trying to cheat on PoGO, and didn't work with Fly GPS, and uninstalling the app in a bad way provoked that I will do a nandroid and try again
Click to expand...
Click to collapse
Are you using the kernel support, have you flash it in TWRP?
The app work in CM under 13 is ok, but the kernel support I have not tested in older them CM13, so I'm curious to know if it works, the only way to really test is to deactivate SU and then reboot if you have SU active after or if the app can activate SU after then is all good if you don't have and or can't activate in the app there is a problem...
the basic function of the kernel support is to have no problem after a reboot when you had disable SU, just like @mrkhigh point it out
So if you reboot with that off let me know the behavior if you can use and activate SU will be need a dirty flash of the ROM you are using...
When I have some time I will do some proper test in cm12.1 and only cm12.1 because my devices can only run that there is no older OS for me...
:good:
I update the app and kernel support to 1.5
Changelog and Download link first page post 2 and 3
In Downloads I add two kernel support one with selinux after boot in Permissive and other with Enforcing just check the zip name and check your device in settings > About a phone SELinux Status is using enforcing or permissive, this is need as some CM ROM Run with selinux in Permissive.
Any problem let me know.
bhb27 said:
Are you using the kernel support, have you flash it in TWRP?
The app work in CM under 13 is ok, but the kernel support I have not tested in older them CM13, so I'm curious to know if it works, the only way to really test is to deactivate SU and then reboot if you have SU active after or if the app can activate SU after then is all good if you don't have and or can't activate in the app there is a problem...
the basic function of the kernel support is to have no problem after a reboot when you had disable SU, just like @mrkhigh point it out
So if you reboot with that off let me know the behavior if you can use and activate SU will be need a dirty flash of the ROM you are using...
When I have some time I will do some proper test in cm12.1 and only cm12.1 because my devices can only run that there is no older OS for me...
:good:
Click to expand...
Click to collapse
Well, now I reinstalled all just because I messed all up, again.
Turned off the phone with root of and no kernel support, tried to flash kernel support, and that would be ok, if I didn't "flash SuperSu" stuff when rebooting :silly:. That made the switch work, but didn't pass validation when using PoGO.
Then, had to reflash ROM, delete chinese stuff, reinstall all of my apps, and iSu, of course, while noticing that there was an update; installed the app and new permissive kernel, and from now, so far so good
Hope that I will keep it clean and working. Thanks for the suggestions btw
@bhb27 Installed and working on sprint htc m8 cm13. The kernel mod is installed but untested.
Great work! I can confirm it worked in my moto g 2014 running cyanogenmod 14.1 official. Pokémon go worked!
Thanks dev!
At last something that works! Running CM14.1 rom on my OnePlus 3 and it works!
Pokémon Go go go...
Thx dev!
HC4Life said:
At last something that works! Running CM14.1 rom on my OnePlus 3 and it works!
Pokémon Go go go...
Thx dev!
Click to expand...
Click to collapse
Now go find that ditto.
Would there be anyway to automatically trigger this for certain apps? This is the first root hiding method i've found that actually tricks Barclays Mobile Banking. Great work
LJAM96 said:
Would there be anyway to automatically trigger this for certain apps? This is the first root hiding method i've found that actually tricks Barclays Mobile Banking. Great work
Click to expand...
Click to collapse
:good:
No there isn't yet, is not all that hard to make but is timing I had no time for the last week to start the implementation, but is in my plans, probably still do this year.
BTW is always nice to be remember that the app can be used for other then to catch monsters :laugh:
You might want to consider removing selinux enforce from the kernel service script. If the ROM doesn't have proper SE policy, it could gum things up. I think the switch in the app is probably sufficient in the event user needs to toggle Enforcing to run an app. I don't believe enforcing on boot toggles anything, but I could be wrong since my ROM boots enforcing. Safety Net actually keeps working for me if I toggle to permissive.
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge (G925xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G925F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Reserved
There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<