Database Info

External sdcard rw permission enabler plus extras [Module] - Android General

External sdcard rw permission enabler plus extras
{
"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"
}
The latest magisk modules v4.4 & ( v5.0 located page #7 ) is for Android 6 to 11 . Providing External Sdcard write access permissions, It can add quick access links in root directory to your external sdcard. Works on single or multiple partition sdcard filesystem's.
Adds ntfs support to most devices from Android 6 to 10 , an including exfat support from Android 6 to 8. Supports usbotg for Android 6 up on compatible devices.
All sdcard & otg mounting an symlinks methods are technically unique an first of their kind here. No one else cared enough to put in the time needed to add this back to android after removed from Marshmallow an above . So it takes great effort to find universal techniques for most/all devices.
So devices configurations will vary.
READ BELOW LOOK FOR LATEST UPDATES.
Some Info
Dual linkage from the system storage and media_rw directories.
Links are made to root dir & mnt dir.
Link 1 in root - external_sd
Link 2 in mnt - sdcard1
Both links utilize external read & write permission for access by apps requested.
Example
Titanium backup can use both these points for storage access for backups to sdcards.
NOT FOR USE WITH ADOPTABLE STORAGE SDCARD SETUP
INSTALL
Flash zip in recovery an reboot.
Magisk module users v4.1 an above flash in magisk.
If using v4.2 up uninstall module before updating versions or if re-flashing module again when option for ntfs & exfat support are chosen.
If using v4.4 , uninstall an install is supported in both magisk manager and recovery.
Note
init.d support or magisk is needed
First zip uses init.d support.
Second zip v4 an higher uses magisk support.
Some apps may need you to grant them access to external storage, others may ask to direct them to the path which can easily be found rite in root folder and also mnt folder - ( this is found in root folder. )
Locations example
Path in root directory are :
/external_sd
/mnt/sdcard1
/usbotg
/mnt/usbotg
Some devices may only support one location for their external sdcard in /storage because their is no /mnt/media_rw folder. Module will detect the correct available location to create dual symlinks.
Volume Deamon info:
What is vold (Volume Daemon) that most Android OS support , why this module uses a custom type when selected (vold posix) option on install ;
http://strayinsights.blogspot.com/2018/05/android-external-storage-support-volume.html?m=1
####### UPDATED #######
LATEST UPDATE , V4.4 - FOR MAGISK USER
# AUTO INSTALL #
-External Sdcard access
-Permissive on install
-Sepolicy patches on install
Some changes below;
:Note for custom vold only (vold posix option when using boot patch):
Best success for using custom vold will be achieved in recovery mode install .
For devices that supports vold an sdcard binaries only, this is auto checked when vold posix is selected .
# Change log: v4.4
.added support for recovery install an uninstall of module.
.added custom vold safety protection auto uninstall on failure to fully boot.
added full driver support from Android 6 to 10 , for both the 32 & 64 bit variety.
.added additional upgrades to sdcard an usbotg mount & symlinks methods .
.added additional configurations for write access to devices on Android 11 OS.
.added options to choose internel or external app install location for supporting devices.
.added usbotg symlinks an direct folder support in root dir.
.added some other big systematic changes to setup.
.added full uninstall module an boot image patch by re flashing module if installed.
Click to expand...
Click to collapse
LATEST UPDATE , V4.3 - FOR MAGISK USER
# AUTO INSTALL #
-Permissive on install
-Sepolicy patches on install
NOTE:
Use Boot Patch if module didn't work for you with SD link option.
Warning make or have a backup of your ROM to flash if you use custom vold option.
What does vold do? It's the core mount management for most Android devices that mounts internal , external & usb/otg storage devices. Custom vold adds the custom binaries that most non custom rom lacks for mounting ntfs sdcards an otg storage devices. Do to the nature of how it works for full reasons unknown when changing vold binary its a 10℅ chance the device may decide not to full boot an need to be dirty flash to restore start up. So still try with caution .
# Many upgrades some added changes are below #
# Change log: v4.3
.added newer sdcard an usbotg mount & symlinks methods .
.added additional configurations for write access to devices that dont have even basic setups.
.added back options to choose busybox on install only if wanted.
.added some other systematic changes.
.
Click to expand...
Click to collapse
How does this module work ? Some more info can be found here
https://forum.xda-developers.com/showpost.php?p=83054737&postcount=76
UPDATE , V4.2 - FOR MAGISK USER
# AUTO INSTALL #
-Permissive on install
-Sepolicy patches on install
-Modded busybox on install
-Apps install location set to external storage
NOTE:
Use Boot Patch an also try it with the custom vold options if module didn't work for you with SD link option. V4.2 only
# Many upgrades some added changes are below #
# Change log: v4.2
.added new latest magisk install template with selection.
.added advance techniques for sdcard symlinks - Optional
.added custom boot.img patch if symlinks failed to create in root - Optional
.added custom vold binary for some devices on Android 6-9 - Optional
.added ntfs & exfat full support for Mediatek devices, also qcom support in Android 8-9 64bit only - Optional
.added mounting & symlinks support for multiple partitions on sdcards, all links & folders made in root. Exfat, Vfat, Ntfs, Ext4 & ( F2fs if kernel supported )
.added usbotg ntfs & exfat mount support on boot.
.added install & uninstall options in magisk manager when flashing zip to undo any changes.
.
Click to expand...
Click to collapse
How does this module work ? Some more info can be found here
https://forum.xda-developers.com/showpost.php?p=83054737&postcount=76
UPDATE , V4.1 - FOR MAGISK USER
INSTALL
Within Magisk Manager App ONLY {Not Recovery}
In the Modules Tab using the yellow plus sign button at bottom of modules tab , locate where you download an saved this zip (downloads folder most likely).
NOTE
When installing Follow the on srceen instructions , volume key check should be selected quickly on startup test or installer will exit. (Will just have to restart installer if so)
Info
-System remounted RW
-Provides full Permissive mode -Optional
-Provides Invert back Selinux Enforcing mode -Optional
-Sepolicy internal & external sdcard Platform.xml patch for rw permissions to system files & directories on some devices
-Provides app backup access write permissions an quicker access to external_sd mounted in root dir.
-Example.. titanium backup can use external sdcard link in root folder or /mnt/sdcard1 to store backup files..
-Custom Magisk installer
-Custom modded busybox -Optional
-Custom Ext.sdcard dual mounts -Optional
-Can be used alone with only write sdcard access installed systemless
-Systemless altering (patching) of files .
Custom install selection v4.1 options
-Choose android version on install to select custom sepolicy injection on boot.
-Choose Permissive on install
-Choose Selinux Enforcing on install
-Choose None to leave selinux as is on install
-Choose Modded app2sd busybox on install
-Choose Symlink Dual ExternalSD on install
-ExternalSD write access by default on install , can run it standalone if no other options are selected.
-Any Options install will be listed in magisk within module tab.
Uninstall or disable ExternalSD module within Magisk module tab or custom recovery.
# After first beta version 4 lagacy install for Magisk.
# Change log: v4.1
- New Template install.
.added new latest magisk install template with selection.
.added sepolicy patch - Android version - Optional install.
.added permissive mode - Optional install.
.added busybox modded app2sd version -Optional install.
.added sdmount for symlinks - Optional install.
.added external Sd write access enabler' Standalone mode - if no options selected on install.
.script - adjustments in post-fs-data.sh for file backups, file sed an patching.
.script - adjustments in sdmount.sh for better mounting & optimized bootcomplete start execution for creating symlinks & automatic file deletion on magisk module removal.
Click to expand...
Click to collapse
Update v4.1
# first magisk module build date;
11/04/2020
Uninstall - For older Magisk v4 & init.d support installs
Flash first top zip again once to remove mod with init.d support
Flash bottom v4 magisk uninstall for magisk .
Disclaimer
You choose to install anything on your devices the decision is always your , xda is not responsible for your actions on your device & either am i, if you have doubt about something ask questions about it first.
Latest Updated (04/10/2020)
Including Latest Magisk support, version v4.4
Thanks to :
@Techguy777 for helping with testing device compatibility.
Hopefully you find this useful.
Please Give Your Feed Back!
It takes devs time to create mods for You but it take nothing for You to hit LIKE BUTTON!! ?
Report errors to developers we cant know if to continue updates or to correct anything we don't read minds
NEED HELP PERSONALLY:
Telegram - https://t.me/Ziona242
Let me know which device it doesn't work for

Magisk supported?
Sent from my TECNO CX Air using Tapatalk
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
I don't want to tamper my system if it's not systemless
Sent from my TECNO CX Air using Tapatalk

Mickey03 said:
Magisk supported?
Sent from my TECNO CX Air using Tapatalk
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
I don't want to tamper my system if it's not systemless
Sent from my TECNO CX Air using Tapatalk
Click to expand...
Click to collapse
Will make one for magisk tomorrow, this version uses initd support but how its setup you can install an uninstall easily without a trace .

Ok, I will wait. Just infom me here!
Sent from my TECNO CX Air using Tapatalk

Mickey03 said:
Ok, I will wait. Just infom me here!
Click to expand...
Click to collapse
No problem
Updated
 @Mickey03

Ziona said:
No problem
Updated
@Mickey03
Click to expand...
Click to collapse
Which one is the Magisk version? The last one or the middle?
Sent from my TECNO CX Air using Tapatalk

@Ziona The Magisk version can't be installed. I think u are using old template. Can u use the official latest template or Unity 5.0 or the newer Magisk Manager Extended template by @Zackptg5 please?
I tried to install on latest Magisk canary and installation ended with error
Sent from my TECNO CX Air using Tapatalk

Mickey03 said:
@Ziona The Magisk version can't be installed. I think u are using old template. Can u use the official latest template or Unity 5.0 or the newer Magisk Manager Extended template by @Zackptg5 please?
I tried to install on latest Magisk canary and installation ended with error
Sent from my TECNO CX Air using Tapatalk
Click to expand...
Click to collapse
I'll try an update that one for you but it works on lastest stable magisk v20.4
What Android version you on?
Updated @Mickey03

dianamavrilk said:
Magisk version for android pie not work for mie its beta version
Click to expand...
Click to collapse
Did you try the standard version with init.d support to test if it works on your device on pie. If not you can flash it once again an it will uninstall easily. Then send your devices info.

dianamavrilk said:
nit.d support version it no no work also for mre . good job bat its beta version not stable
for moment nothing works for android 9 pie. may phone HTC U12+ android 9 magisk stable 20.4 end magisk 20.1 castom site edxposed
p.s insayd zip istall lSDCard
name=Ext_Sd RW & Symlink Enabler
version=v4 (beta)
versionCode=40
author=Ziona @xda developers
description=Enables external SDCard write access for your Apps on Marshmellow, Nougat, Oreo, and maybe Pie !
maybe Pie ! not work
Click to expand...
Click to collapse
Ok will look into this

Ziona said:
I'll try an update that one for you but it works on lastest stable magisk v20.4
What Android version you on?
Click to expand...
Click to collapse
I am not using latest Magisk 20.4, I am using the latest canary.
I am running on Android 7.0
Sent from my TECNO CX Air using Tapatalk

dianamavrilk said:
running on Android 7.0 end 8.0 work very well .you don't have special permission to access))
root permissions ent LACKY PATCHER suffisent probleme permissions since android 9 pie
Click to expand...
Click to collapse
Could you write this more clearly i didn't understand it all fully.

Hey try the update.
 @Mickey03

@Ziona Your module completely disturb Xposed. Xposed becomes disabled internally after your module installation and ur module also doesn't work. I didn't get any symlink for my sdcard at the root and /mnt first. Sorry
Btw do u have Telegram account? If u have, We can chat there and move ur module to the next level.
Sent from my TECNO CX Air using Tapatalk

Mickey03 said:
@Ziona Your module completely disturb Xposed. Xposed becomes disabled internally after your module installation and ur module also doesn't work. I didn't get any symlink for my sdcard at the root and /mnt first. Sorry
Btw do u have Telegram account? If u have, We can chat there and move ur module to the next level.
Sent from my TECNO CX Air using Tapatalk
Click to expand...
Click to collapse
Module works well for all my devices
Do you know if a module in xposed is unstable and disabling both my module an xposed.
In magisk module tab did you see External Sdcard write access w/ symlinks. - SDlink, next to android version or busybox by v4.1 depending which options you choose?
Whats your telegram

dianamavrilk said:
running on Android 7.0 end 8.0 work very well .you don't have special permission probleme since pie 9.0
i don't understand why you don't access i have full access to remove apk to sd card
Click to expand...
Click to collapse
That's what am thinking if something is creating a problem for him with xposed With the first methods. Xposed is buggy on some systems.
But i will be posting a magisk update in a few minutes, because that was the wrong one uploaded its for Samsung. Sorry ? @Mickey03

Ok, Thanks! What about Telegram?
Sent from my TECNO CX Air using Tapatalk
---------- Post added at 07:04 PM ---------- Previous post was at 07:04 PM ----------
@Ziona Also add [Magisk] in the zip name
Sent from my TECNO CX Air using Tapatalk

Mickey03 said:
Ok, Thanks! What about Telegram?
Sent from my TECNO CX Air using Tapatalk
---------- Post added at 07:04 PM ---------- Previous post was at 07:04 PM ----------
@Ziona Also add [Magisk] in the zip name
Sent from my TECNO CX Air using Tapatalk
Click to expand...
Click to collapse
Its up!
To make it fit just added - Mv4.1 to the end.
TG Number # ?

Ziona said:
Its up!
To make it fit just added - Mv4.1 to the end.
TG Number # ?[/QUOTE @MIkesew1320 on Telegram. You can send me a PM or give me ur username, I can send u a PM.
Sent from my TECNO CX Air using Tapatalk
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Ziona said:
Its up!
To make it fit just added - Mv4.1 to the end.
TG Number # ?
Click to expand...
Click to collapse
I hope it doesn't conflict with Xposed and working fine. Let me try it..... Tnx!
Sent from my TECNO CX Air using Tapatalk
Click to expand...
Click to collapse

Confirmed! Working like a charm!
Btw, Can u add another symlink for usb otg at /root please?
Sent from my TECNO CX Air using Tapatalk

Related

{
"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"
}
PROJECT DIRECT INJECT
Exit_Only said:
Welcome to the world of direct injection, Its been unavailable for your android smartphone...UNTIL NOW. This tweak package takes your android device to a whole new level of awesomeness by direct injecting high octane scripts into your turbocharged engine.
This is a collection of scripts from multiple developers repacked into one package. Big thanks to all the developers involved.
Click to expand...
Click to collapse
This mode is incompatible with some devices\firmwares or create various system problems! Make a nandroid backup before installing.
General Q & A Section:
Q.) How can I tell if this is actually working or not?
A.) Open Terminal Emulator and type this command...
Code:
su
directinject
Q.) How can I see if rambooster work properly?
A.) Open Terminal Emulator and type this command.
Code:
su
rambooster
Q.) How cand I see if entropy working properly?
A.) Open Terminal Emulator and type this command...
Code:
su
entro
Q.) How can activate RNGD and entro binaries?
A.) Open Terminal Emulator and type this command...
Code:
su
entropy
Q.) How do I turn on entropy?
A.) Open Terminal Emulator and type this command...
Code:
su
entropy_on
Q.) How can I stop entropy?
A.) Open Terminal Emulator and type this command...
Code:
su
entropy_off
Q.) How do I uninstall it?
A.) Download the uninstall, you put on your card and then flash the file.
Code:
su
uninstall
reboot
Q.) Can I use DirectInject and Crossbreeder?
A.) Yes, you can.In the first time disable entropy (on DirectInject) then install Crossbreeder.
Q.) How do I install NOS Control?
A.) NOS Control installs like any .apk
Q.) How can I get CPU Tuner on my device?
A.) Open Terminal Emulator and type this command...
Code:
su
cputuner
GENERAL WARNING: Do NOT I repeat DO NOT use ANY other tweaks with this package. There are only two approved scripts that are compatible with this, Seeder Entropy and Cross breeder. If you choose to do so after reading this you do so AT YOUR OWN RISK. If you ask bout other tweaks in my thread YOU WILL BE IGNORED.
WHAT IS NEEDED TO INSTALL Project Direct Inject:
1.) Root access (su binary required)
2.) Busybox v1.20.4+ w/ run-part support (busybox required)
3.) Need to be on 2.3.3+ gingerbread or higher
4.) Terminal Emulator app app installed
5.) Enough space in your /system partition (10 mb available minimum)
If you do not meet these requirements then DO NOT USE IT!!!
WHAT IS NEEDED FOR CPU TUNER:
1.) Need a fully unsecured boot.img (Look inside "default.prop", if it says "ro.secure=0" then your kernel meets this requirement, if it says "ro.secure=1" then cputuner WILL NOT work!!!)
2.) Your need a kernel that supports max overclock freq of 1.3ghz and a min freq of 384mhz.
3.) Need a kernel that has these 3 governors (Conservative, Ondemand, and Performance)
4.) On HTC Sense ROMs you need to disable per flock (Setcpu will do this for you)
If you don't meet ALL these requirements then do NOT attempt to use CPU tuner!!!
Installation
1.) Make sure you meet the requirements above
2.) Download the latest version of Project Direct Inject
3.) Boot into recovery (TWRP or CWM doesn't matter)
4.) Make a nandroid backup
5.) Flash inside cwm recovery
6.) Reboot
7.) Press thanks button me and Exit_Only
APK Direct Inject Control
What i need to install this app:
Terminal Emulator
Project Direct Inject
Direct Inject is an application that gathers in one place all orders of Project Direct Inject
Ryuinferno said:
Behold.....
THE NOS Controller!!! Since many of you find it troublesome to key in commands every time, I wrote up a damn simple app to save those finger punches!!! Well, I am currently limited by my knowledge of Java, this is the best I can do for now (Requests? Be prepared, I won't attend to any as I can't add more features yet...more learning to do...sorry... )
But, take note that you will need to install the latest version of 4cyl Turbo v0.5.7_r2 w/ 250 shot NOS first and have Terminal Emulator installed before using this app! Do not be silly and think that this app is gonna do everything for you!
The app is very simple and straightforward, so no instructions will be given here...enjoy!
Click to expand...
Click to collapse
Download Direct Inject Control: Click Here
About the Tweaks:
8 init.d scripts total (11 init.d scripts if you opt for NOS Entropy, zRAM, and Int2Ext)
Zipalign /data & /system apps on each boot ( With detailed Logging of Activities)
Calibrates Battery automatically (make sure your battery is at 100% before flashing)
NOS Entropy with Light, Moderate, and Aggressive Governors (Optional during install, Moderate is default governor)
Ext4 Tweaks
Zero UI Lag
Maxed out speed & Performance
Disables most logging activities
GPS enhancements (USA/CANADA/MEXICO/ALASKA Only)
Sqlite3 for Jellybean (Complied from CM10.1 Source)
4.2.2 Binaries (Better app processing, Complied from CM10.1 Source)
Disables logcats
Get your Privacy back (No internet redirects)
Lots of kernel tweaks (Disabled most kernel sleeps and Adjusted Linux values)
Extended Reboot Commands
VM heap tweaks
Net speed tweaks
Ext4 Perfect Remount
Outstanding battery life
Sqlite3 Reindexed and Vacuumed (If you see errors in db files please ignore, this is normal operation)
RAM booster and Media Server Killer binary (Very Aggressive RAM Recovery tool)
4Cyl Turbo Binary (Exit_Only Exclusive)
Stable relase:
Download v.3.2.6: Click here
Code:
Fixed the three remaining bugs in v3.2.5_t9 and removed the touchscreen tweak as it was causing screen issues on some devices!!!
Download v3.2.4: Click Here
Code:
v3.2.4 - Fixed ALL bootloops on ALL devices
Added seperate flashable zips for Sqlite3 Binaries in SECOND POST BELOW OP
Removed Max Freq mod in CPU Tuner
Removed needed interactive Gov and now using Ondemand Gov
Updater script now backups and restores CronMOD int2ext scripts by default
Updater script now backups and restores CM init.d scripts for Selinux and Userinit
Fixed ALL remaining bugs
Added new entropy scripts for on & off Functions
Updater no longer removes Crossbreeder during install process
Added Sqlite3 Database Optimizer Script (YOU NEED TO FLASH THE REQUIRED SQLITE BINARY IN THE SECOND POST BELOW THE OP)
Fixed Deepsleep script to work correctly without errors
Much more im sure I am forgetting!!!
Download v3.2.2: Click here
Code:
v3.2.2 - Fixed All Boot Looping issues on ALL DEVICEs
Fixed Bootlooping on HTC Sense Devices
Removed Zipalign on boot script and binary
Added BRAND NEW Cpu Tuner script and binary
Pick between three different profiles (Battery, Performance, or Balanced)
Fixed Battery drain on single core devices
Adjusted Minfree values to be more aggressive
Fixed Assert Error from test releases
Read Ahead set to 3072kb
Updated Logging engine
Plenty more I am forgetting!!!
Download v3.2.1: Click here
Code:
Lots of upgrades to cputuner with new CPU core log engine
Added brand new move dalvik script
Much more coming later!!!
Download v.3.0.0: Click here
Code:
v3.0.0: Started over with complete rebuild
Must lighter and much faster
Installs correct busybox to /xbin
Only 2 binaries now 'directinject' & 'rambooster'
Updated rambooster + added init.d script to run ram booster every 45 minutes
Auto runs zipalign every 2 days or 48 hours
Patched rngd binary for better entropy generation without killing battery life
Adjusted Linux values
Brand new interval script
Brand new iptable rebuild script
Much much more!!!
Download v.1.0.2: Click here
Code:
v1.0.2: Fixed image issue
Added newest code to entire project
Added new functions to sqlite scripts
Added new warnings during install
Download v.1.0.0: Click Here
Code:
v.1.0.0. A new world, a new script
[B]FIRST RELEASE OF PROJECT DIRECT INJECT[/B]
Download v0.7.0: Click here
Code:
v0.7.0: Added new and improved DNS caching (Similar to crossbreeder)
New init.d script that automatically activities DNS caching
Added new DNS tweaks for build.prop
My new custom 'dnshelp' binary that will help you use dnsmasq binary
Modified rambooster (Two custom options 'Moderate' & 'Aggressive')
Fixed Adj minfree script to work right
Much much more I am forgetting
Download v0.6.0: Click here
Code:
vo.6.0. Adjusted sysctl values
Made sysctl tweaks optional
Updated 4cylturbo binary to include optional install pieces
Updated install.sh with new code and new backups
Added bash and nano binaries along with bash, nano, & terminfo folders for /etc (Two diff versions)
Added sqlite3 and script (Two diff versions)
Fixed bash and nano not working correctly
Updated uninstall.sh to restore more stock items and delete more stuff
Adjusted hedge values
Added in optimized RAM tweaks (much better ram management vs v0.5.7-r2)
Fixed multiple script errors and adjusted values
Full zip size is much bigger (7.03mb)
Other stuff I'm sure I am forgetting. THIS IS A MAJOR UPDATE.
Download v0.5.7r2: Click here
Code:
v0.5.7r2 Adjust sysctl.conf correctly this time
Removed disable vsync
Removed cron (These newer versions of busybox don't support "ENABLE_CRON" so script is useless)
Fixed logging on scripts
Adjusted vm values slightly
Download v0.5.7r1: Click Here
Code:
v0.5.7r1 - Added extended reboot scripts
Fixed root issues
Fixed greenify issues
Updated install script
Added uninstall script (This will remove nos 100% from your device)
Updated directions inside zip file
Removed some sysctl commits
New performance boosters added
Download v0.5.6: Click her
Code:
v0.5.6: - Reverted back some scripts
Removed Fix Permissions script
Fixed up install.sh script (Thanks Poo)
Fixed root issues on Samsung Galaxy S Advance
Download v0.5.5: Click here
Code:
This version should solve problems with freezes and root loss.
Download v0.5.4_r1: Click here
Code:
v0.5.4_r1: - Fixed random reboots some people were having (myself included)
Made more stuff optional during install
Fixed root access issue some users experience (I never had this issue so I need feedback)
Updated ad blocker
Updated logging engine
Much smoother and zero lag
Download v0.5.4: Click here
Code:
v0.5.4: - THIS IS ONLY EXECUTIBLE VIA TERMINAL EMULATOR OR SCRIPT MANAGER.
THIS IS NOT NOT NOT RECOVERY FLASHABLE
Added init.d script to add init.d support if your ROM/Kernel does not support it already (Optional during Terminal install)
RAMBooster Binary is now much more Aggressive at clearing RAM
Updated 4Cylturbo binary with code changes
Fixed ALL Logs and Script Errors
NOS Entropy Governor is moderate by default instead of light
Removed All Code Errors from Sysctl Config
Added 'S' to beginning of all scripts to support Samsung Galaxy S 1 Owners (You guys are so old skool :P )
Added int2ext script (Thanks to Cronicory for original)(WARNING: YOU MAY HAVE TO FORMAT YOUR SD CARD TO USE THIS SCRIPT. YOU CAN OPT OUT OF THIS DURING INSTALL)
Logcat disabling script is now 100% Optional during install (YOU CAN NOW KEEP LOGCATS ACTIVE)
Added Bash and Nano Shell Binaries (COMES IN HANDY FOR BASH SHELL SCRIPTS LIKE CRON)
Download v0.5.2: Click here
Code:
v0.5.2: - THIS IS NOW A FLASHABLE ZIP AGAIN
Fixed /data logs for scripts
Fixed most script errors
Adjusted a few things here and there
More to come later
Download v.0.5.1: Clcik here
Code:
v0.5.1: - Fixed logging errors
Fixed ALL install.sh errors
Added Team Kernelizers build.prop injector script (Thanks RErick & Decialman)
Build.prop injector is now a option in install.sh
Added auto reboot to install.sh (SOME DEVICES WILL NOT ALLOW THIS TO WORK, SOME WILL HAVE TO REBOOT MANUALLY)
Fixed all init.d script errors
Updated 4cyl turbo engine logger
Added new directions to README_users.txt
Will add more as I remember it
KNOWN ISSUES & BUGS:
1.) WiFi tethering DOES NOT work when using this tweak package!!! There is no solution to this problem and I am not trying to find a solution, sorry for the inconvenience!!!
CURRENT WORKARUND: Flash the newest crossbreeder!!! This will fix your borked tethering!!!
Uninstal
Code:
su
uninstall
reboot
Standard Disclaimer: Flash at your own risk. Myself nor XDA is responsible for any damage this thing may cause you.
For this wonderful work we must thank Exit_Only
Original thread: Click here

enricogrim said:
Hi,
I have an old version of NOS, before installing a newer version it's better I uninstall the old one or install the new one directly?
thank you very much
Click to expand...
Click to collapse
You can just install the new one (through recovery or terminal depending on the release version) since the installer replaces it's own old/invalid files
Sent from my GT-I9070 using xda premium

enricogrim said:
Hi,
I have an old version of NOS, before installing a newer version it's better I uninstall the old one or install the new one directly?
thank you very much
Click to expand...
Click to collapse
Exactly what he said. 4cyl turbo has implemented a script that deletes all files init.d that you have and replaces them. For a new installation, whether it is installed by CWM or Terminal is not required before uninstallation, just install the new version.

Did what u said...follwed every step..said yes to every promt...still after rebooting when i type su 4cylturbo or rambooster..it says doesnot exist..where did i go wrong...
PS I'M A USER!!
Sent from my GT-I9070 using xda app-developers app

kanidevil666 said:
Did what u said...follwed every step..said yes to every promt...still after rebooting when i type su 4cylturbo or rambooster..it says doesnot exist..where did i go wrong...
PS I'M A USER!!
View attachment 1959685
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
this mean don't install this mod correct
just try again and put the folder install on SDCARD or SDCARD0

kanidevil666 said:
Did what u said...follwed every step..said yes to every promt...still after rebooting when i type su 4cylturbo or rambooster..it says doesnot exist..where did i go wrong...
PS I'M A USER!!
View attachment 1959685
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Try v0.5.2 instead since it's flashable and see if it works.
Flash it in TWRP/CWM and I suggest you mount system first before flashing the zip. Also, as always don't forget your nandroid backup If it did work, then you can proceed to install the latest version through terminal if you want to.

Damn mounting/unmounting always confuses me...By mounting the system do u mean mount or unmount..
Coz i think in cwm it shows like this
"A Blue Tick and it shows unmount storage...and a blank box when its shows mount storage"
So just tell which 1 should i go with, tick or untick
And after flashing it, will the terminal command "4cylturbo" respond??
Sent from my GT-I9070 using xda app-developers app

kanidevil666 said:
Did what u said...follwed every step..said yes to every promt...still after rebooting when i type su 4cylturbo or rambooster..it says doesnot exist..where did i go wrong...
PS I'M A USER!!
View attachment 1959685
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
For v0.5.4 follow these instructions
Code:
1.) DOWNLOAD NEWEST VERSION, IF YOU WANT TO USE NOS ENTROPY THEN PLEASE REMOVE SEEDER OR CROSSBREEDER FIRST, YOU CAN FIND THE NEEDED UNINSTALL SCRIPTS IN SEEDERS OR CROSSBREEDERS THREAD. USE XDA SEARCH TO FIND IT.
2.) DOWNLOAD TERMINAL EMULATOR APP FROM GOOGLE PLAY STORE... (IF YOU ALREADY HAVE IT THEN SKIP THIS STEP)
3.) EXTRACT "install" FOLDER FROM /sdcard FOLDER INSIDE ZIP AND PUT IT ON YOUR ACTUAL "/sdcard"...
4.) EXIT OUT OF WHAT EVER FILE EXPLORER YOU ARE USING...
5.) OPEN THE TERMINAL EMULATOR APPLICATION...
6.) TYPE THIS COMMAND IN TERMINAL EMULATOR...
[B]
su
sh /sdcard/install/install.sh
^
There is a space here!!![/B]
FOLLOW THE PROMPTS AND CHOOSE WHAT YOU WANT INSTALLED!!!
7.) REBOOT YOUR DEVICE FOR ALL MODS TO TAKE AFFECT... (Rebooting is a REQUIREMENT, Failure to reboot WILL cause random app force closings)
8.) ENJOY THE SPEED AND PERFORMANCE :D

This script hangs phone and creates problem in phone UI
Sent from my GT-I9070 using xda app-developers app

ramansehra said:
This script hangs phone and creates problem in phone UI
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
What ROM and what version of 4cyl you use?

Very good, Great job
Enviado desde mi GT-I9070 usando Tapatalk 2

I'm currently using LightJB 1.2 with co core 6.0.
. 0.4.2 version of 4cylturbo works good with me, but this version hangs my phone to black screen while using.
Sent from my GT-I9070 using xda app-developers app

kanidevil666 said:
Did what u said...follwed every step..said yes to every promt...still after rebooting when i type su 4cylturbo or rambooster..it says doesnot exist..where did i go wrong...
PS I'M A USER!!
View attachment 1959685
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Have you updated your busybox?
Sent from my GT-I9070 using xda app-developers app

v5.2
not able to flash through recovery method

Bhaji eh recovery naal ni hona,
Tuhanu terminal emulator te jake command type karni paini aa
Sent from my GT-I9070 using xda app-developers app

sarabjit singh said:
not able to flash through recovery method
Click to expand...
Click to collapse
The file is named 'NOT FLASHABLE'.You have to install it via terminal emulator.
Sent from my GT-I9070 using xda premium

flash
ramansehra said:
Bhaji eh recovery naal ni hona,
Tuhanu terminal emulator te jake command type karni paini aa
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
v0.5.2: - THIS IS NOW A FLASHABLE ZIP AGAIN
read 1st page carefully
---------- Post added at 06:57 PM ---------- Previous post was at 06:53 PM ----------
rushilkr said:
The file is named 'NOT FLASHABLE'.You have to install it via terminal emulator.
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
v0.5.2: - THIS IS NOW A FLASHABLE ZIP AGAIN
IF USING FLASHABLE VERSION Find the flash able zip file on your sdcard then flash it.
7.) Boot out of recovery [ONLY FOR FLASHABLE VERSION]
read 1st page carefully

sarabjit singh said:
v0.5.2: - THIS IS NOW A FLASHABLE ZIP AGAIN
read 1st page carefully
---------- Post added at 06:57 PM ---------- Previous post was at 06:53 PM ----------
v0.5.2: - THIS IS NOW A FLASHABLE ZIP AGAIN
IF USING FLASHABLE VERSION Find the flash able zip file on your sdcard then flash it.
7.) Boot out of recovery [ONLY FOR FLASHABLE VERSION]
read 1st page carefully
Click to expand...
Click to collapse
Read the title of this thread.Its about v 0.5.4 .It is NOT flashable.
Sent from my GT-I9070 using xda premium

Datico said:
Very good, Great job
Enviado desde mi GT-I9070 usando Tapatalk 2
Click to expand...
Click to collapse
ramansehra said:
I'm currently using LightJB 1.2 with co core 6.0.
. 0.4.2 version of 4cylturbo works good with me, but this version hangs my phone to black screen while using.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem too. A new version came out, hopefully all issues resolved. Check OP!
sarabjit singh said:
not able to flash through recovery method
Click to expand...
Click to collapse
Only version v0.5.2 is with flash method.
Flash method:
Code:
1.) Make sure you meet the requirements above
2.) Download the version of NOS FLASH
3.) Boot into recovery (TWRP or CWM doesn't matter)
4.) Make a nandroid backup
5.) Find the flashable zip file on your sdcard then flash it.
6.) Boot out of recovery
To me it worked without problems.

0.5.2
Grady22 said:
I had the same problem too. A new version came out, hopefully all issues resolved. Check OP!
Only version v0.5.2 is with flash method.
Flash method:
Code:
1.) Make sure you meet the requirements above
2.) Download the version of NOS FLASH
3.) Boot into recovery (TWRP or CWM doesn't matter)
4.) Make a nandroid backup
5.) Find the flashable zip file on your sdcard then flash it.
6.) Boot out of recovery
To me it worked without problems.
Click to expand...
Click to collapse
i tried 0.5.2v dude but not succeed

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.

{
"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"
}
For LeEco Le 2​Supports all Roms​
NOTE:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this Kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
What is MultiRom?
MultiRom is one-of-a-kind multi-boot mod. It can boot any Android Rom as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiRom can boot from USB drive connected to the device via OTG cable. The main part of MultiRom is a boot manager, which appears every time your device starts and lets you choose ROM to boot. Roms are installed and managed via the modified TWRP recovery. You can use standard ZIP files to install secondary Android Roms, daily prebuilt image files to install Ubuntu Touch and MultiRom even has its own installer system, which can be used to ship other Linux-based systems.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
Boot from USB drive Attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
All MarshmallowRoms
All Nougat Roms
SUPPORTED DEVICES:
LeEco Le 2 X520
LeEco Le 2 X526
LeEco Le 2 X527
LeEco Le S3 X522
Please Test it in other Le 2 and S3 Similar Devices and Report it Below.
Bugs:
Fingerprint Sensor doesn't work 4/10 Times while Dual Booting
In EUI, 4K Recording doesn't work in Stock Camera App after Installing MultiRom
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:​This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.​
Updating/changing ROMs:
1. Primary Rom (Internal)
Flash Rom's zip File as Usual, Do factory reset if needed (it won't erase secondary Roms)
Go to MultiRom in recovery and do Inject curr. boot sector.
2. Secondary Android Roms
If you want to change the Rom, delete it and add new one. To update the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.​
GitHub Source Codes:
MultiRom Organization for LeEco Devices​Le 2 MultiRom Device Trees​MultiRom Manager App Source Codes​
Current Status:
Everything Works and Everything is Bugfree...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to Le 2
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, Super Stable, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For LeEco Le 2, Tool/Utility for the LeEco Le 2
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-leeco
Version Information
Status: Stable
Current Stable Version: v33
Stable Release Date: 2017-03-15
Created 2017-01-15
Last Updated 2017-03-23

Download Links:
MultiRom Manager App 2.4-rishabhrao

FAQ
1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Donations are Welcome!!!
YouTube Videos:​

This does not work on the S3 x522. and neither does the other multi-boot tool as it does not support le_s2_na

Guyz I'm on cm13 by sir Codeworkx.. And I'm receiving this error everytime.. .
Do i need to backup my current LOS then flash EUI then multirom and restore LOS backup as a secondary ROM...???

Prathamesh Kapure said:
Guyz I'm on cm13 by sir Codeworkx.. And I'm receiving this error everytime.. .
Do i need to backup my current LOS then flash EUI then multirom and restore LOS backup as a secondary ROM...???
Click to expand...
Click to collapse
Just go to buiod.prop and change device name to s2 enough
Hit thanks if it works

Great work bro
Sent from my Le X520 using XDA-Developers Legacy app

Kr1shna55 said:
Just go to buiod.prop and change device name to s2 enough
Hit thanks if it works
Click to expand...
Click to collapse
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached

Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Check by changing your dpi bro.. default would be 160.. change it to 400 or above

mdfarazb2 said:
Check by changing your dpi bro.. default would be 160.. change it to 400 or above
Click to expand...
Click to collapse
Okz bro thx I'll surely try....

Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Check above post
Sent from my HTC 10 using XDA Labs

jhakjhuk1853 said:
Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Check above post
Click to expand...
Click to collapse
Ty Jignesh bro I'll try that...

Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Same here!
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
jhakjhuk1853 said:
Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Check above post
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Device not showing dpi more than 200

I can't install the official 19s from TWRP it ends in error 7 saying it's for le_s2_ww but the device is s2
Eventough I changed the device name in build. Prop I can't install

Kr1shna55 said:
I can't install the official 19s from TWRP it ends in error 7 saying it's for le_s2_ww but the device is s2
Eventough I changed the device name in build. Prop I can't install
Click to expand...
Click to collapse
Change first line of stock firmware zip's updater script
Not ur build.prop
TWRP doesn't care about your build.prop
This problem happens bcz all newer twrps are made for custom roms lile lineage as lineage uses device name s2 and no le_s2_ww to maintain consistency...
So stock will have problems if updater script not modified properly
Sent from my LeEco Le 2 using XDA Labs

britdude said:
This does not work on the S3 x522. and neither does the other multi-boot tool as it does not support le_s2_na
Click to expand...
Click to collapse
Change ur build.prop device name to s2
And it ll alll work just fine
Also tell me s3's ro.product.device name in the stock rom
I ll add support for it right away
Sent from my LeEco Le 2 using XDA Labs

Prathamesh Kapure said:
Multirom TWRP installed fine but multirom zip ends with error code 7...And after installing MR TWRP everything got smaller in size and my touchpal keyboard messed up....ss attached
Click to expand...
Click to collapse
Don't install MultiRom manually
Use the app to install BOTH THE RECOVERY AND THE MULTIROM ZIP TOGETHER
Sent from my LeEco Le 2 using XDA Labs

jhakjhuk1853 said:
Installing multirom zip isn't needed
Just inject boot.img from recovery
Also dpi you can change from settings
Sent from my HTC 10 using XDA Labs
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
Check above post
Click to expand...
Click to collapse
You will never get the BOOT UI in that way
Always install both the MultiRom TWRP Recovery and the MultiRom ZIP TOGETHER
And injecting is sometimes not needed
Depends on the ROM
But actually not needed as we have no kexec implementation
Using App to install is both easier and recommended!
Sent from my LeEco Le 2 using XDA Labs

Rishabh Rao said:
Change ur build.prop device name to s2
And it ll alll work just fine
Also tell me s3's ro.product.device name in the stock rom
I ll add support for it right away
Click to expand...
Click to collapse
S3's ro.product.device is le_s2_na

Disable Force Encryption NEO​Do you all know what DFE is? no?
Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption:
- Confidence in data retention. Even if your device has TWRP/OFOX or other custom Recvoery, before accessing your data, you will need to enter the password from the lockscreen, otherwise it will be impossible to read the data.
What disadvantages follow from this?
- As an enthusiast who wants to flash different ROMs, you may have noticed that every time that you flash a new ROM, you have to format the "/data" section. Which can be a pain.
Why is it necessary to do this?
- The fact that every ROM is assembled/compiled on a different database and may have different approaches (encryption keys) for data encryption. In order for this to work you need to format the data partition so that when the new ROM boots it can encrypt the system with its own unique encryption keys, so that the integrity of the data partition is maintained and it is accessible to the user.
So what does the DFE do?
- Removes the keys that are used to encrypt the data section from the fstab file
Read more about fstab here source.android.com
What are the advantages of using DFE?
- You don't need to FORMAT the data in the following cases:
*If you change the android database (From 11 to 12 and vice versa)
*If you change vendor database, miui/aosp/OOS/LOS and so on
*** !!!! You will still need to make wipe data for the ROM to work correctly
-There are also disadvantages:
*Since the data is not encrypted in any way, then access to them is free. Anyone who gets access to your device will be able to access ALL the data
*You need to carefully monitor the sequence of actions when installing or changing the ROM, so that the DFE is active, otherwise you may lose data because the data will try to be encrypted again, you will get a bootloop, and all data will be lost
What is DFE-NEO?
*Many people know DFE from this thread XDA, it has stopped working for A/B devices with dynamic partitions, there is also a problem that in some ROMs the system has the RO(Read-Only) status of the system partition. Starting with A13 Google will promote EROFS(Enhanced Read-Only File System) which will not be possible to manipulate without first converting to EXT4, in order to change the status to RW(Read-Write). Because of this, it is not possible to modify fstab directly in 100% of cases. This is where DFE-NEO comes in.
*The NEO method works by utilizing Magiskinit and Overlay.d GitHub
How does it work without Magisk?
*In fact, in no way. If my script does not detect magisk in the boot_a/Boot_b section, magisk will be installed, after which the main bianrys files will be deleted, so there will be no root access but magiskinit itself will continue to work. In this regard, the system boot time will be longer by 40-50 seconds ( from the brand logo )
And so what can this script do:
-Hides Encryption - Forces the system to think that the data is encrypted.
-Reflash recovery after OTA - only for devices with recovery in boot_a/_b
-Flash current recovery - only for devices with recovery in boot_a/_b
-Flash DFE
-Flash magisk
Spoiler: Arguments.txt
{
"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"
}
If you want to change the parameters , then you need to change the file argumetns.txt inside the archive , or put the modified arguments.txt to the archive, or to rebuild the archive with the changed argumetns.txt
Code:
# legacy or neo
DFE method=neo
# both | in-current | un-current
Flash SLOT=both
# none|system|bootloader|recovery
Reboot after installing=none
# You can add your own language, to do this, just drop
a file into the language folder by analogy with the topic
that is already there
# indo|russian|english
Language=english
Code:
# ================================================== #
Force reading arguments.txt=false
# ================================================== #
Flash DFE= true
Disable AVB= true
Disable QUOTA= true
Hide not encrypted= true
# ================================================== #
Flash Magisk= false
# ================================================== #
Reflash Recovery for OTA= false
Reflash current Recovery for Recovery= false
# ================================================== #
Wipe DATA= false
Remove PIN= false
# ================================================== #
Skip warning= false
Modes of operation of these parameters
These parameters have two modes:
• true (yes, true),
• false(no, not true)
Exceptions for specific parameters
• DFE method(DFE method)= neo(new method)
Another argument for DFE method
legacy(old method)
• Flash slot= both (patching boot_a and boot_b sections, also applies to magisk firmware, twrp)
More arguments for Flash slot
• in-current (patching of the boot_x section, where x is the current slot, also applies to magisk firmware, twrp)
• un-current (patching the boot_x partition, where x is the opposite slot)
• Reboot after installing(Reboot after installation)= none (no, that is, there will be no reboot)
More arguments for Reboot after installing
• system(restart into the system, simple reboot)
• bootloader (reboot to fastboot mode)
• recovery (reboot into recovery mode)
• Language(installer language)=english(English)
More arguments for Language
• indo(Indonesian)
• russian (Russian language)
So we have sorted out the modes of operation of all parameters. Now, what does each of them mean.
The values of these parameters
Here the functions of the parameters are described in true mode, for exceptions depending on the mode of operation of the parameter
• DFE method - DFE patching method
• Flash slot - patching the boot partition
• Reboot after installing - reboot after installation
• DISABLE DINAMIC REFRESHRATE - disable dynamic screen formatting, ONLY FOR MIUI
• Language - the language of the installer
• Force reading arguments.txt - dfe-neo will immediately address the arguments in arguments.txt without the possibility of creating a temporary arguments.txt
• Flash DFE - DFE firmware
• Hide not encrypted - The ROM will think that encryption is enabled
• Skip warning - at the end, a guide will be shown on the correct use of dfe after firmware
• Reflash recovery for ota - reinstalling recovery after ota updates, according to the Flash slot parameter mode=
• Reflash current Recovery for Recovery - flash the current recovery, according to the Flash slot parameter mode=
• Wipe DATA - deleting the contents of the /data section without formatting the internal memory (where the Android, Downloads, Music, etc. folders are located) If you sew DFE for the first time, then we still do format data
• Remove PIN - remove password
• Disable AVB - system integrity check is disabled (or whatever you call it, you can set false if you flash magisk)
• Disable QUOTA - (to be honest, I didn't understand what it was, but you can leave it true)
• Flash Magisk - Installing Magisk, according to the Flash slot parameter mode=
And you can also set up your own temporary arguments.txt during installation:
In DFE-NEO, in addition to using arguments.txt in .zip archive, you can still set up your temporary one.
Launch the dfe-neo archive and select Configure Arguments now ( volume + >> volume - )
And we are offered to configure the parameters.
Volume + indicates change
Volume - indicates select
What should I choose DFE method= neo or legacy?
• Neo method - patches the boot partition, we leave neo if the system partitions are read-only, also suitable if the system partitions are editable
• Legacy method - patches fstab.qcom in the /vendor/etc/ section, this method cannot be used if the system partitions are read-only.
Also be careful and read what the script writes at the end of the installation
If you data is encrypted, then after flashing DFE you need to format data
If DFE was installed with Magisk you can upgrade or downgrade the Magisk version later without flashing DFE again
If you uninstall Magisk via uninstall or Magisk app Then the DFE will stop its work! In this case, you will need to flash the DFE again
If DFE was WITHOUT Magisk, it WILL work, but you can also install Magisk later. And also follow the warning 1 and 2
If you install TWRP or another custom recovery, then DFE by analogy with Magisk, will stop working
If you update/Install a new ROM, then DFE will need to be flashed again, by analogy with Magisk
You can install DFE as a magisk module. BUT THIS IS NOT A MODULE, BUT JUST AN INTERFACE FOR INSTALLATION
Demo vido: https://t.me/mfpupdate/22
And also you can flash as a regular zip archive via TWRP, while you do not have to reboot TWRP.
The work consists of the same mechanism as Magisk. If your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will be overwritten
After updating/changing ROM you need to reflash dfe again
You can flash dfe without rebooting twrp
No needed for system to be RW for DFE to work
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
Download link - SourceForge
TG group : @PocoF3DFE
Donate only TG link https://t.me/mfpupdate/47

Great job Alexey. Very useful mod

LeeGarChat said:
Hello everyone, I am writing a script to disable encryption on A/B devices. if you help me with testing on other devices, I will be glad, at the moment it works fine for Poco f3 ( Alioth/Aliothin ). I'm sure it will work just as well on other devices.
And so what can this script:
Hide no encrypted - Forces the system to think that the data is encrypted.
Reflash recovery after OTA - only for devices with recovery into boot_a/_b
Flash current recovery - only for devices with recovery into boot_a/_b
Flash DFE
Flash magisk
The work consists of the same mechanism as Magisk. If u recovery if your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will turn off
After update/change ROM u need reflash dfe
You can flashing dfe without reboot twrp
No needed RW system
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
TG group : @PocoF3DFE
Click to expand...
Click to collapse
Great job bro its perfectly work on my Redmi Note 11 Spes, thanks buddy

sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）

wsdyleon said:
sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）
Click to expand...
Click to collapse
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery

LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
thank u for your answer，but i donnt konw how to flash it.i flash"dfe+magisk+reflash"on my phone in twrp，but bootloop for me

LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
my english still sucks,after flashing the zip ，the ro system would still ro，just dfe。am i right?

LeeGarChat said:
Download link - SourceForge
Click to expand...
Click to collapse
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;​Permission adb Okay;​cmd command:​
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true

lopestom said:
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;​Permission adb Okay;​cmd command:​
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true
Click to expand...
Click to collapse
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?

LeeGarChat said:
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?
Click to expand...
Click to collapse
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.

lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Send me download link on you ROM. I'll check structure

LeeGarChat said:
Send me download link on you ROM. I'll check structure
Click to expand...
Click to collapse
UMIDIGI Power 5 4GB_N_V1.0_20220315 - SPFT release
UMIDIGI_POWER5_4GB_N_V1-0_20220315.rar

Great.

lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Test 0.9.0 version please

LeeGarChat said:
Test 0.9.0 version please
Click to expand...
Click to collapse
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.

lopestom said:
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.
Click to expand...
Click to collapse
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic

Awesome job LeeGarChat, much appreciated by all users I have quoted your post link in other threads too so all can see the magic .
My device is Shamshung Galeksi M21 2021 (SM-M215G) But when I flashed from TWRP it showed some red error : 577 something like that, then when I flashed from Majisk it showed error code 3 : DFE-NEO only for virtual_ab devices
Treble Check shows my device is treble compliant having AB partition and TWRP displays following partitions: System, Vendor, Product, Odm, Cache, Data, EFS, Metadata, Sec EFS, Micro SD Card, USB OTG.
In my Shaomi Readmi Note 10 (mohito) TWRP displays Slot A & Slot B under Advanced Tab and ROMs get directly flashed to Inactive Slot B, also everytime I try flash new custom ROM I have to first flash MyUi Factory ROM and also System partition doesnt show in TWRP Mount section.
My question is what is the difference between Shamshung Galeksi M21 Android 11 out-of-box & Shaomi Readmi Note 10 Mohito ? why TWRP shows System partition mount in Shamshung and not in shaomi though both are A/B devices?
Pls help.

LeeGarChat said:
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic
Click to expand...
Click to collapse
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again

lopestom said:
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again
Click to expand...
Click to collapse
can you tell us in PM how you fixed the problems you wrote about earlier

History of updates and news
June 16
Update DFE-NEO 0.10.0 beta
- Added Feature, choose wether you want to flash DFE legacy / neo ( for legacy need RW system and not working with erofs)
july 14
Update dfe-neo beta 0.11.0
- Add magisk 25.1
- Add volume key selector
- Add remove lockscreen-pin select for key selector
july 20
Update dfe-neo beta 0.12.0
- Add new arguments:
- Wipe data
- Reboot after
july 22
DFE-NEO-0.12.4-BETA update
- Add additional settings (optional) like wipe data, reboot after
- Add disable dynamic refrash rate display ( only miui and works with dfe-neo method )
july 23
DFE-NEO-0.13.0-BETA update
- Add new arguments into arguments.txt, now u can change it without volume key
- Add new options "remove avb" " remove quota" ( default removed )
- The code has been slightly rewritten
- Update somthing patches for safety net fix based on later version 2.3.1 https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1
july 24
DFE-NEO-0.13.3-BETA update
- Minor fix
- Cleaning ui print
- Added calculation of script running time
july 25
I show by my example how to install a ROM in conjunction with DFE-NEO, as well as additional zips
Download DFE-NEO LINK ( Alway later version )
Thread XDA LINK
Please subscribe to the updates and news channel LINK
Thanks
july 28
DFE-NEO-0.14.0-BETA update
- Add language select ( it is currently configured only in the file arguments.txt )
Languages:
• Russian
• English
• Indo
• you can add your own language
- Fix ro.dfe.neo.state
- Add force reading arguments.txt
july 30
DFE-NEO-0.14.1-BETA update
- Reworked my_print function to work correctly in other languages. previously, it worked fine only with English
- Updated the Russian language. fixed typos
july 30
DFE-NEO-0.15.0-BETA update
- Add support A-Only devices
Languages v003:
- There was a bug with a large number of characters ****