{
"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"
}
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION ENDING IN 27.1 or 27.5 AND TWRP 2.7+ OR CWM 6.5.0.0+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 15 mins to stabilise! The first boot will take 15 minutes!
SCREENSHOTS
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 and F2FS Data partitions
Based off omni-5.1.1-20150508-zombi_tf300t-KANG source by lj50036/hardslog
Full Aroma Installer for main rom including choice of 4 kernels and ROM2SD/DATA2SD/F2FS support
Remixed _thatv11 kernel with OMNI ramdisk - repacked by sbdags
Grimlock kernel with OMNI ramdisk and _that init - by hardslog
DPI Size: 160 (TF300 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-POP, Android-L, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, Keyboard Manager
Tweaks: File system and performance optimised, Init.d support, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
Bug List
[*]No Floating windows yet
Change Log
20150728 ZOMBi-POP RC1 changes
- RELEASE CANDIDATE 1!
- Fixed the problem with ROM2SD and DATA2SD not working correctly on beta 4
- Added SuperUser and Secure Kernel as options to the installer (Turn these off for work wifi or watching sky go, etc)
- Added dock battery icon as an option to the installer under tweaks
- Fixed partitions not getting unmounted correctly for tuning during installation
- Fixed WiFi across the unified bases for TF700/TF300/TF201
- OmniSwitch now working - thanks hardslog
- Tidied up some installer messages
- Google play services updated to unified version for all devices
- Updated Google Maps to version 9.12.0
- Updated Google TTS to version 3.5.6
- Updated Google Calendar to version 5.2.2-98195638
- Updated YouTube to version 10.28.59
- Updated Apex Launcher to version 3.1.0
20150723 ZOMBi-POP Beta 4 changes
- Unified Aroma installer for TF700/TF300/TF201
- Rebased from omni-5.1.1-20150718-zombi_tf300t-KANG maintained by lj50036, hardslog, sbdags
- Merged source from omni-5.1.1-20150718-zombi_tf700t/tf201t-KANG maintained by lj50036, hardslog
- Updated all kernels and modules to the unified versions - thanks lj50036
- Added inverted kernel for TF201 users
- Aroma re-written to allow multi device selection and detection
- Additional tweaks added from TF701 Zombi-pop
- Amended SuperSU installer script to give correct permissions and install locations
- Reverted to latest Banks Gapps - means another wipe - sorry!
- Updated Google Calendar, Google Mail, Google Hangouts, YouTube, Google Search & Google Maps to latest versions
- Updated ESFile Explorer and Nova Launcher to latest versions
- Added flashable zip to enable dock battery - NOTE - this means you can't change the battery icon
20150119 ZOMBi-POP Beta 3 changes
- Rebased from omni-5.1.1-20150508-zombi_tf300t-KANG maintained by lj50036, hardslog
- Repacked Grimlock kernel for 5.1.1 (Grimlock lite is still using 5.0)
- Retweaked some File System and Virtual Memory parameters - focus on smoothness and battery
- Added Aroma code to remember previous selections as well as offer various installs
- sbdags best auto install, omni default auto install, previous options and previous auto install
- Viper4Android sound enhancer updated to lollipop version + updated the audio_effect.conf file
- Updated Google Play Store to version 5.5.8
- Updated Google Play Services to version 7.3.29
- Updated Google Search to version 4.5.13.19
- Updated Google Maps to version 9.8.1
- Updated Google Hangouts to version 3.2.91698097
- Updated Google Play Music to version 5.9.1854R
- Updated Google Calendar to version 5.2-91668080
- Updated ESFileExplorer to version 3.2.5.1
- Fixed swipe gestures on google keyboard
- Fix for Battery Drain on Google Play Services
- Removed Titanium Backup from the zip file
20150422 ZOMBi-POP 5.1 Beta 2 changes
- Rebased from omni-5.1.1-20150422-zombi_tf300t-KANG maintained by lj50036, hardslog
- New base is from OMNI 5.1.1 merged by lj50036
- Browser History is back again! Thanks lj50036 or Hardslog
- You can now choose to install, no GAPPS or minimal GAPPS (just playstore and syncs)
- Updated Google Maps to version 9.7.1
- Updated Google Search to version 4.4.11.16
- Updated Google Mail to verison 5.1.90765967
- Updated Google Calendar to version 5.2-90091543
- Updated Google Hangouts to version 3.1.89134953
- Updated Google Text-to-Speech to version 3.4.6.1819666
- Updated YouTube to version 10.14.56
- Updated ESFileExplorer to version 3.2.5
- Updated Android Terminal to version 1.0.70
- Updated Banks Gapps:
- Google Play Services 7.3.28 (1863718-438)
- Google Play Store 5.4.12
- fixed OC on Some TF201's running Grimlock-lite
20150330 ZOMBi-POP 5.1 Beta 1 changes
- Rebased from omni-5.1-20150330-zombi_tf300t-KANG maintained by lj50036 & harslog
- Adaptive brigtness fixed and values changed
- Browser speed tweaks incorporated into source
- OmniSwitch updates
- Settings changes to alarms and notification interruptions
- Updated Google Music to version 5.8.1836R
- Removed Titanium Launcher - as it needs to be installed form the store now
- Testing Aroma 3.00 scripts from Amarullz
- Repacked omni / _that kernel with preinit init binary
- Updated YouTube, Hangouts, Google Search, Calendar, Maps to latest 5.1 versions
- Updated Google Play Store and Services to 5.1 versions
- Updated Apex Launcher to version 3.0.3
- Recompiled Browser.apk with speed tweaks
- Moved tibu to system to try and fix install issues
- Shrunk all gapps by removing duplicate lib files from binaries
- Cleaned up gapps inconsistencies (sbdags)
20150218 ZOMBi-POP Beta 4 changes
- Rebased from omni-5.0.2-2015-02-19-zombi_tf300t-KANG source maintained by lj50036
- Show Optimizing app dialog on first boot
- Prevent copyNativeLib of package scanning to reduce booting time
- Keyguard: don't refresh ui when screen off which causes high power when screen off
- Prevent App Not Responding when broadcast receiver is killed
- lowmemorykiller: Fix high min-free values
- Removed my minfree init.d script to test new default values
- Changed the interactive governor tweaks to help battery life and heat
- min_sample_time from 40000 to 10000
- go_maxspeed_load from 90 to 98
- max_normal_freq from 1500000 to 1300000
- midrange_freq from 760000 to 1150000
- Updated SuperSU to version 2.46
- Updated Apex Launcher to 3.0.2
- Updated Google Maps to version 9.4.0
- Updated YouTube to version 10.05.6
20150212 ZOMBi-POP Beta 3 changes
- Rebased from omni-5.0.2-2015-02-11-zombi_tf300t-KANG source maintained by lj50036
- Updated Grimlock Kernels for exfat and ntfs support (hopefully!)
- New Kernel - Grimlock LITE - OC reduced to 1700mhz and voltage reduced for better battery/heat
- Rebuilt _that/omni kernel with oom patches and repacked ramdisk
- Reverted some vm and kernel tweaks which seems to have got performance back on track
- Reverted read_ahead_kb to 4096 as no benefit to 2048
- Fixed Tibu not installing correctly and updated to version 7.0.0.2
- Removed Chrome and Dolphin / Flash
- Rebuilt all GAPPS from latest PA GAPPS modular package Feb 2015
- Resized Nexus-Lollipop bootanimation
- Added the Unknown Pleasures bootanimation
- Aroma theme updated - thanks Shonkin for the bg picture
- Fixed Overclocking not working on data2sd with _that's kernel. You now get 4x1800 cores on data2sd
- CPU will use all 4 cores at 90% max load instead of 85% on basic cpu tweaks
- Fixed missing sdcardi on grimlock kernel
- Fixed init.d on Grimlock 5 kernel by repacking init.zombi.rc
- Fixed zipalign script so it runs properly once after a dirty or clean install
- Set the lowmemorykiller to less aggressive 2048,4096,8192,16384,24576,32768 via init.d script
- Rewrote Aroma installer which gets us a step closer to it remembering previous installs (but not yet!)
- Split out the extra tweaks into two parts for further debugging - Basic and Extended
- Spilt out Disable Software Rendering and Force GPU rendering for further testing
- Reordered init.d scripts to make more sense
- Updated Titanium Backup to version 7.0.0 and cleaned up installation script
- Force GPU Rendering is not getting applied correctly - do it manually for now
20150127 ZOMBi-POP Beta 2 changes
- Rebased from omni-5.0.2-20150127-zombi_tf300t-KANG source maintained by lj50036/hardslog
- Fixed Auto-rotation - thanks hardslog/lj50036!
- NEW Material AOSP Broswer - very nice!
- Omni Switch but no windows mode yet
- Fixed missing sdcardi folder for data2sd and rom2sd users
- Fixed the Apex and Nova Launchers getting missed up on install
- CLEANTweaks init.d re-balanced to be less aggressive - hopefully stops so many reboots
- Recompiled latest framework-res.apk with zombi-pop default_wallpaper.jpg
- Updated Google Chrome to version 40.0.2214.89
- Updated Google Maps to version 9.3.0
- Updated YouTube to version 10.02.3
- Updated Android Terminal Emulator to version 1.0.64
20150121 ZOMBi-POP Beta 1 changes
- Fixed Auto-rotation
- Added Linaro build of Grimlock Kernel (needs more testing)
- AOSP Browser: Materialize (green)
- First Release for TF300/TF201
20150119 ZOMBi-POP Pre-Release 3 changes
- New name - new logo! ZOMBi-POP
- Rethemed Aroma to new ZOMBi-POP theme
- Added 2 optional beta tweaks for testing (screen and kernel)
- Fixed _thatv11 kernel option
- Added Grimlock v5.0 (not tested)
20150118 Lollipop Pre-Release 2 changes
- Updated to latest OMNI Lollipop source omni-5.0.2-20150117-zombi_tf700t-KANG maintained by lj50036
- Fixed issue with AOSP Browser getting installed when not selected
- Fixed issue with Live Wallpapers getting installed when not selected
- Fixed issue with Launcher3 getting installed when not selected
- Fixed issue with Terminal not getting installed when selected
- Fixed issue with DSPManager still getting installed when Viper4fx is installed
- Removed stock calendar as google app one is far superior
- Fixed init.d scripts not running due to wrong permissions and wrong ramdisk init.rc call
20150117 Lollipop Pre-Release 1 changes
- Updated system and data apps to use new lollipop structures
- Updated all apps to latest versions
- Removed xposed as not compaitble with lollipop
- Tweaked the force gpu options
20150111 Lollipop Alpha 1 changes
- Updated to latest OMNI Lollipop source maintained by lj50036
- New PA GApps Lollipop version 2015
- Initial Beta test build to see what works and what doesn't
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk/ZOMBi-X ROMS)
@lj50036 - Source Guy (From CROMBi-kk/ZOMBI-X ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
@ikkeT- The Fin
Credits
Google
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : fatboyinlycra, berndblb, drewski_1, duckredbeard, keshavmot2, corb06, jmaybush, JoJoDaClown, kansasboy001, TrofeoSC
To Do
Fix loads of stuff!
XDA:DevDB Information
ZOMBi-POP, ROM for the Asus Transformer TF300T
Contributors
hardslog, lj50036, sbdags, _that
Source Code: https://github.com/zombi-x
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
ROM Firmware Required: JB Ending with 27.1 or 27.5 bootloader
Based On: OMNI AOSP
Version Information
Status: Stable
Current Stable Version: 20150728 RC1
Stable Release Date: 2015-07-28
Current Beta Version: 20150723 Beta 4
Beta Release Date: 2015-07-23
Created 2015-01-24
Last Updated 2015-07-27
Reserved
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF300 by following these instructions.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.7+ Note this ROM will NOT install with older versions of recovery!
TWRP OFFICIAL DOWNLOADS
Download the recovery file from above, put it into the same folder where you have adb and fastboot files. Please rename it to twrp.blob or cwm.img and follow the instructions below:
CWM:
Connect your transformer to your PC, reboot to the bootloader to enable fastboot by either holding down [power] and [volume down] or opening a command prompt in your adb.exe folder in windows:
Code:
adb reboot bootloader
To flash the recovery:
Code:
fastboot -i 0x0B05 flash recovery cwm.img
or
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
A blue bar will go accross the screen on the tab and the command prompt will indicate it was successful in about 10 seconds
Then reboot the tablet either back to the bootloader or to android to complete
Code:
fastboot -i 0x0B05 reboot-bootloader
fastboot -i 0x0B05 reboot
You can now access the recovery by pushing [volume up] on the RCK icon in the bootloader screen
Click to expand...
Click to collapse
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-POP ROM DOWNLOAD
Note: The first boot after install will take 15 mins whilst everything is built. Some people might think it is looping but it is not. The ROM also takes about 15 mins to stabilise after the first boot
ZOMBi-POP RC1 LP 5.1.1 Full Mirror 1
ZOMBi-POP RC1 LP 5.1.1 Full Mirror 2
MD5 sum: e3980e1bffa539e676ac1269268abcd1
Flash this patch please as there is a file missing that gives better performance
RC1 Performance Patch
Remember if you are on rom2sd you beed to flash rom2sd1.zip first and if on data2sd use data2sd1.zip first.
FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have ZOMBI-POP, ZOMBi-X, CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of ZOMBi-POP to flash it to ROM2SD and the installer will do the rest.
- Install ZOMBi-POP and choose ROM2SD or DATA2SD install
The ROM2SD1.zip below is only needed if you need to switch your recovery to between normal and rom2sd mode. For Example you want to backup or restore a rom2sd installation. Flash once to go rom2sd and flash again to go back to normal. A reboot always puts you back to normal. Thanks to _that!
ROM2SD1.zip Download Mirror 1
ROM2SD1.zip Download Mirror 2
MD5 Sum: 7b699136d59ea3d5538570ccaf422acf
The DATA2SD1.zip below is only needed if you need to switch your recovery to between normal and data2sd mode. For Example you want to backup or restore a data2sd installation. Flash once to go data2sd and flash again to go back to normal. A reboot always puts you back to normal.
DATA2SD1.zip Download Mirror 1
DATA2SD1.zip Download Mirror 2
MD5 Sum: 9d5e9e2fd32593f981624499b37924b2
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the ZOMBi-POP zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
Using GParted to setup a micro SD for ROM2SD or DATA2SD!
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
Note for DATA2SD just do one partition in stead of 2
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android (not needed for data2sd)
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall ZOMBi-POP but this time choose the ROM2SD / DATA2SD option
Reserved
All,
The ROM is still in BETA and by flashing it you are helping the BETA Testing process
It may still have some bugs, spontaneously reboot, drain the battery faster or heat up a bit. The aim is to make it better and fix them.
If you find a bug and want to report it here please post a logcat (after it occurred) with a description of what you were doing at the time and the rough timing in the logcat to look at (these things get huge!).
You can also post a dmesg which is the kernel boot logs and can indicate issues with data corruption or hardware.
If you get a reboot then please post a last_kmsg from the /proc folder.
How to get a logcat
How to get useful logs
Thank you!!
Join us on IRC for a chat or if you have questions:
Freenode
zombi-x
There is no Q&A section for this rom as it is still in dev so you are ok to post your questions here!
One for me
MIRROR 1 & 2 are up for your flashing needs ..... :good:
Thx Josh & Team ZOMBI
Cannae reserve a post but this one will do
@lj50036
I know all the kinks haven't been worked out yet, but is dock battery icon in this version?
toolhas4degrees said:
@lj50036
I know all the kinks haven't been worked out yet, but is dock battery icon in this version?
Click to expand...
Click to collapse
No not yet, most of the dock keys are working, but no battery support as of yet....
Thx Josh
Could it be possible to enjoy this project with the transformer prime???
Thx un any case, great effort, great success team!
jacmat said:
Could it be possible to enjoy this project with the transformer prime???
Thx un any case, great effort, great success team!
Click to expand...
Click to collapse
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Thx Josh
lj50036 said:
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Click to expand...
Click to collapse
so good to hear that, thanks so much for your work Josh!
Good to know! It would be great if it could work on the ME301T also! Is the hardware that different?
Hi, this rom work on TF300TG ???
Thanks
lj50036 said:
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Thx Josh
Click to expand...
Click to collapse
Thanks! Flashed with grimlock 5.0 and it runs well, but I had issues with chrome browser lockups...
lj50036 said:
I am testing it now and have had good results....
Just need a bit more testing and then I will make a thread for the 201 ...... :good:
Thx Josh
Click to expand...
Click to collapse
Thank you very much, Josh, you and your team bring to prime's owners a reason to smile
jlamaeli said:
so good to hear that, thanks so much for your work Josh!
Click to expand...
Click to collapse
You will see a thread when its ready... :good:
EV0LU710N said:
Good to know! It would be great if it could work on the ME301T also! Is the hardware that different?
Click to expand...
Click to collapse
There maybe a compatible pack but we will have to wait and see... :good:
medievalspawn said:
Hi, this rom work on TF300TG ???
Thanks
Click to expand...
Click to collapse
It should but you will lose 3G....
luismiguel1977 said:
Thanks! Flashed with grimlock 5.0 and it runs well, but I had issues with chrome browser lockups...
Click to expand...
Click to collapse
Logcat after the browser crashes .....
jacmat said:
Thank you very much, Josh, you and your team bring to prime's owners a reason to smile
Click to expand...
Click to collapse
Will have to wait and see.... :good:
Thx Josh
lj50036 said:
There maybe a compatible pack but we will have to wait and see... :good:
Click to expand...
Click to collapse
That would be fantastic, surely would make a bunch of people very happy, myself included!
By the way, if you need a beta tester or some help with the development, I would be very happy to help out! I have a tablet ready to test drive!
lj50036 said:
There maybe a compatible pack but we will have to wait and see... :good:
Click to expand...
Click to collapse
Thank you man, would be great! :good:
excellent, downloading now, can you recomend a good gapps package for the rom
thanks
matt_simpson said:
excellent, downloading now, can you recomend a good gapps package for the rom
thanks
Click to expand...
Click to collapse
It's built in as choices.
Important notes for Developers / Chefs !!!
This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it does not mean that I do not need to thank anyone - there are people who helped / inspired me anyhow (see "Credits").
I will risk the statement that at this moment my "DevBase" is the most tuned and nuanced custom ROM available at XDA Forum
I agree to use any part of my work to create other custom ROMs, but it would be great if you add me to the credits
EDIT: Note related to creating "$ZIPFILE" which contains a file larger than ~4GB (e.g. system.img): the order of adding content to "$ZIPFILE" is very important! META-INF need to be added as the first dir in the archive! Example (my DevBase case):
Code:
zip -r -9 G960FXXU1xxxx_DevBase.zip META-INF options.prop ALEXNDR
It seems that misunderstanding of the above problem is the main reason why many devs give up and do not use my base as a pattern.
Hello
I have decided to create a pure base with my unified installer (should work with many other Samsung devices), which can be a pattern for ROM Chefs (not only for beginners) ROM is initially safe de-bloated (read below what does it exactly mean), but all features are present and works!
ROM can be installed by normal users as well. If you like a little de-bloated ROMs, clean, but with all working features - there is no better alternative I think
ROM for G960F/FD contains slightly modified OXM multi CSC package, list of available CSCs is as follow:
ACR, AFG, AFR, ATO, AUT, BGL, BNG, BRI, BTC, BTU, CAC, CAM, CEL, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS, MAT, MID, MM1, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAK, PCL, PHE, PHN, PNG, PTR, ROM, SEB, SEE, SEK, SIN, SKZ, SLK, SMA, SMP, STH, TEB, TEL, THL, THR, TMC, TNZ, TPH, TUN, TUR, VAU, VFJ, VNZ, WTL, XEF, XEH, XEO, XEU, XEZ, XFA, XFE, XME, XNX, XNZ, XSA, XSG, XSP, XTC, XXV
NEW !!! I present you new, unique option: "Keep current CSC", so you can install my DevBase keeping your original CSC even if it is not listed above! Note that in such case this option has some limitations - more informations you can find in related older threads, e.g. HERE
ALEXNDR.G960FXXU1ARC5:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC OXM (list of natively supported CSC as above) (*)
- Removed / skipped SecurityLogAgent.apk (annoying on rooted phones)
- Removed / skipped Rlc.apk (to avoid "OEM unlock issue")
- Rooted systemlessly (Magisk v16.1 or SuperSU 2.82 SR5) (*)
- All original features are present and works (except Samsung KNOX related apps)
- No visual changes (100% stock look)
2. CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (may not work for all CSCs)
- Added "LTE Only" network mode (NOTE: voice calls may not work in this mode)
- 4G/3G network support in any CSC (master/slave SIM, applies to dual SIM variants)
- Call Recording (added "Record" button)
- Enabled "Recent App Protection" feature
3. Virtual / physical Safe De-Bloat (more info below) (*)
What does it mean and why is it called "safe"?
- ONLY apps available in stores are removed / skipped in DevBase, so you can easy (re)install any of these app if you like
- ONLY pre-installed system apps are removed / skipped, DevBase installer will never touch any updated app nor app installed manually from a store
- By default virtual Safe De-Bloat is applied with exact same effect as physical (completely skips apps at boot). You can force to delete apps physically but it is recommended only if you really need more space in /system
Thus, the following conclusions can be drawn:
1. If you install my DevBase directly over stock ROM without performing "Wipe data" - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager", like any other app. Removed manually app will not appear again until you use my DevBase while updating.
2. If you perform "Wipe data" while installing my DevBase - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update.
Removed / skipped apps list:
Excel
Facebook
LinkedIn
OneDrive
PowerPoint
Word
(*) - these options can be controlled by editing options.prop file (you can find such file in ZIP's root directory). Just place modified options.prop file (use e.g. Notepad++ to edit) in the root directory of internal emulated scdard (/data/media/0) or extSdCard (recommended if you plan to format internal emulated sdcard) and then start the installation. More info below:
#
# DevBase by ALEXNDR (_alexndr @ XDA)
#
# Configuration file to allow customize the installation.
#
# File inside the ZIP installer is just for reference - please DO NOT modify it!
# If you want to change some options listed below - edit the copy of this file, then place
# modified options.prop file in the root directory of internal emulated scdard (/data/media/0)
# or in the root directory of extSdCard (recommended if you plan to format internal emulated
# sdcard) and then start the installation.
#
# TIP: You do not need to repeat this step every next update I will release. As long as your
# customized options.prop file is present in the (ext)SdCard - future DevBase installers will
# "read in your mind" that you want to install with such options again.
#
# NOTE: All below variables and values are case sensitive!
# Enable root access with the selected method. Allowed values:
# magisk - install Magisk & MagiskSU as root solution
# supersu - install SuperSU as root solution & suhide (default)
# noroot - do not root device
root=magisk
# Possibility to remove bloatware physically from /system. Virtual debloat is
# normally applied instead of physical with exact same effect, so please use this
# option only if you really need more free space in /system. Allowed values:
# false - use virtual debloat to remove useless apps (default)
# true - remove bloatware physically from /system
phydebloat=false
# Possibility to skip flashing BL/CP (Exynos devices). It will also skip
# auto-reboot when the installation has finished (it is normally required
# for flashing BL/CP operation to pass successfully). Allowed values:
# false - flash the newest BL/CP matched to the ROM (default)
# true - do NOT update BL/CP and skip installer's auto-reboot
skipblcp=false
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or copy your current CSC contents).
# You can force the use of natively supported CSC by typing (use UPPERCASE!): ACR, AFG, AFR, ATO, AUT, BGL,
# BNG, BRI, BTC, BTU, CAC, CAM, CEL, CPW, DBT, DKR, ECT, EGY, EUR, GLB, ILO, INS, ITV, KSA, LAO, LUX, LYS,
# MAT, MID, MM1, MWD, MYM, NEE, NPL, NZC, OPS, ORX, PAK, PCL, PHE, PHN, PNG, PTR, ROM, SEB, SEE, SEK, SIN,
# SKZ, SLK, SMA, SMP, STH, TEB, TEL, THL, THR, TMC, TNZ, TPH, TUN, TUR, VAU, VFJ, VNZ, WTL, XEF, XEH, XEO,
# XEU, XEZ, XFA, XFE, XME, XNX, XNZ, XSA, XSG, XSP, XTC, XXV
CSC=KCSC
# Custom CSC Features. Allowed value in each line ("Example_line" does nothing):
<Example_line1>value</Example_line1>
<Example_line2>value</Example_line2>
# Custom debloat list. Allowed value in each line: exact app name with .apk extension.
# (NOTE: without app's path/directory, without spaces after extension, no wildcards!)
Example_system_app1.apk
Example_system_app2.apk
NEW !!! Starting from DevBase v3.0 there is a new customization method - you can change frequently switched root options or encrypt your device just by renaming installer's ZIP file name (instead of editing options.prop file). Currently supported "strings" in the file name: "magisk", "supersu", "noroot", "encrypt", "rescue", "skipblcp", "phydebloat", "CSC_xxxx.zip":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
EDIT: Magisk does not work in G960F (yet), SuperSU is temporarily default root solution..
Case 2 - install the ROM with SuperSU as root solution, without Magisk
(place "supersu" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_supersu.zip")
Case 3 - do not root device
(place "noroot" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_noroot.zip")
Regardless of the above root options, starting from DevBase v4.4+, you can also use "encrypt" option (place "encrypt" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_encrypt.zip"). All your data will be encrypted "on-the-fly" at next boot after ROM update/reinstall. Wipe data is NOT necessary to use this option. You will NOT lose your data & apps but it is extremely important - do not interrupt encryption process during this "special" boot! Booting can take much longer and you may think it is a bootloop, but it isn't! If you have a large amount of used data - it is recommended to connect your phone to the charger during boot (and open a beer to avoid heart attack while waiting). You do not need to use "encrypt" option again in case of another DevBase update(s) - please read carefully notes below. EDIT: Encryption is not supported in G960F (yet)..
In DevBase ROM v4.5+ there is a "rescue" option, which may be especially helpful in case of encrypted device if you experienced bootloop caused by e.g. systemless mod/module/xposed stored on /data (without access to /data from TWRP). In case of bootloop just place "rescue" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_rescue.zip" and then (re)install the ROM - should help in case of (probably) all possible bootloop reasons. In addition to the normal (re)installation of the ROM (thus restoring the original /system, kernel, modem, etc.) this option will also force "Core Only Mode" in Magisk and will move all SYSTEMLESS DevBase modifications to /data/devbase/system/.backup, before performing bind mounts, so original files will be used.
In DevBase ROM v4.6+ there is a possibility to force CSC by renaming ZIP file name - this is the only case-sensitive variable which have to be put at the beginning of ZIP file name and must be folloed by "_" (due to the fact that there is a high risk that ZIP file name may contain CSC code accidentally). Example (to force CSC DBT): "DBT_G960Fxxx_DevBase_v5.x.zip"
In DevBase ROM v5.0+ there is a "skipblcp" option which allows you to skip BL/CP update (it also disables auto-reboot when the installer finished work as it is just not necessary then). Just place "skipblcp" string anywhere in the ZIP file name, e.g. "G960Fxxx_DevBase_v5.x_skipblcp.zip" and then install the ROM.
In DevBase ROM v5.0+ there is also a "phydebloat" option which allows you to remove apps physically instead of virtually while de-bloating. Virtual de-bloat is a reversible method - you can easy restore any app by editing enforceskippingpackages.txt file. It has exact same effect as removing apps physically (it completely skips apps at boot), so forcing to delete apps physically is recommended only if you really need more space in /system.
Notes related to encrypted devices:
How to confirm that your data are encrypted:
1. Go to TWRP and check if it is possible to mount /data. If NOT - all is ok "Failed to mount '/data' (invalid argument)" will be the a frequent message that you need to like in the future
How to update DevBase ROM to a newer version:
1. Copy a newer DevBase ROM to extSdCard or OTG storage (you do NOT need to use "encrypt" option in ZIP file name again, if your device is encrypted already - it just remain encypted)
2. Go to TWRP -> "Install" and flash ZIP file from extSdCard or OTG
3. That's all
The risk of data loss in case of encrypted devices, depending on the ROM scenario:
1. DevBase only: VERY LOW RISK (*)
2. Coming from other custom ROM with encrypted data - MEDIUM RISK (recommended backup)
3. Installing other custom ROM over DevBase - MEDIUM RISK (recommended backup, anyway)
4. Installing pure stock (using Odin) over DevBase (or over any other custom ROM) - VERY HIGH RISK (not recommended!)
(*) There is still a risk to get into a bootloop if you install stuffs like: Xposed framework, incompatible Magisk or Xposed module, incompatible systemless MOD in /data/devbase/system, etc. In case of bootloop just try to use "rescue" option described above
Installation:
TWRP recovery (KNOX 0x1): open file using "Install (Zip)" option and confirm operation. If you want to perform "clean install' - perform "wipe data/factory reset" BEFORE flashing Zip!
Wipe data is NOT required if you are coming from stock ROM (already rooted) or a previous version of my DevBase (if you leave "Keep current CSC" option untouched in /options.prop or if you choose same CSC as you are currently using). In other cases - wipe data is highly recommended!
I do not recommend using any additional superwipes or formats before install my DevBase (my installer cleans your system well enough!).
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk and another inspiration
@Tkkg1994 for pre-patched stock kernel for G96xF
@Duncan1982 & @bennebartsch for initial tests
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download ROM
>> G960FXXU1ARC5_DevBase_v5.3.zip << (Android 8.0, updated Mar-19-2018)
>> SM-G960F/FD repository <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files could (soft) brick your phone! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
v5.3 (starting from G960FXXU1ARC5 DevBase):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
- Possibility to change CSC in case of S9/S9+ has been temporarily disabled for safety reasons (needs more research)
v5.2 (starting from G960FXXU1ARC5 DevBase):
- Added support for devices with /odm as CSC location
- Added support for flashing $ODM, $VENDOR, $KEYSTORAGE, $DQMDBG images
- Added support for custom debloat list and custom CscFeature list in options.prop
- options.prop file format has been changed to CR/LF (Windows) - more noob-proof solution, user can edit a copy of options.prop file even in Windows Notepad (the installer still supports ANY text format of options.prop file - Win/Unix/MAC)
v5.1 (not released for G960F):
- Created new "no_verity" function in the installer, compatible with Samsung's Oreo, based on @Chainfire's patch tool (no-verity-opt-encrypt has been removed).
v5.0 (not released for G960F):
- SYSTEMLESS DevBase has been removed due to the fact, that in case of modern devices/firmwares we need to perform many changes physically in /system anyway, so it loses the sense of use here. If you liked it - you can still install it separately from HERE (it does not need to be re-installed after ROM update as it is installed in /data)
- Added "skipblcp" option to let users skip BL/CP update (additionally it disables auto-reboot when the installer finished work as it is just not necessary then)
- Added "phydebloat" option to let users choose beetween virtual and physical debloat (to get more space in /system)
- Other (minor) optimizations & improvements
v4.6 (not released for G960F):
- Initial support for devices with /system/omc as CSC location
- SYSTEMLESS DevBase updated to v2.0 (see changelog HERE)
- Added possibility to force CSC by renamig ZIP filename. Due to the fact that trere are many different CSC and it is possible that $ZIPNAME may contain a CSC accidentally - to force CSC you need to put CSC in $ZIPNAME at the beginning and CSC must be followed by "_". Example $ZIPNAME (to force CSC DBT): "DBT_G960FXXU3xxxx_DevBase.zip"
- Added auto efs-backup during install. Installer will create first backup (efs_backup.img.gz) and recent backup (efs_recent.img.gz). The installer will prefer external storage as default backup location (/external_sd or /usb-otg) due to encryption support. MD5 sum and restore command will be stored in efs_backup.txt or efs_recent.txt file
- Other (minor) optimizations & improvements, e.g. added more error messages in case of something went wrong during install
v4.5 (not released for G960F):
- Added new "rescue" option (readable only as string in ZIP file name due to the fact, that we will need this option rarely). It can be a potentially very helpful option in case of bootloop @ encrypted device, caused by a systemless mod/module/xposed stored on /data (without access to /data from TWRP) - more info in post #1
- SYSTEMLESS DevBase updated to v1.14 (see changelog HERE)
v4.4 (not released for G960F):
- Added new "encrypt" option (readable only as string in ZIP file name due to the fact, that we need to do it only once). Now you can easy encrypt all data in your device, just during the ROM upgrade (without data loss).
- SYSTEMLESS DevBase updated to v1.13 (see changelog HERE)
v4.3 (not released for G960F):
- "root.supersu" & "root.magisk" variables in the options.prop file have been replaced by one "root" variable (dropped possibility to install both - SuperSU & Magisk - due to the fact that Magisk v13+ does not support SuperSU as root solution)
- SYSTEMLESS DevBase updated to v1.9 v1.12 (see changelog HERE)
v4.2 (not released for G960F):
- Added possibility to add systemlessly NEW apps to /data/devbase/system/(priv-)app (up to 5 apps in "app" & 5 apps in "priv-app"). The only condition is that you need to rename its directories to CustomApp[1...5] (e.g. CustomApp1, CustomApp2, etc..). These apps will remain even if you flash a new DevBase as corresponding dummy directories will exist in future DevBase updates
- In case of DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- SYSTEMLESS DevBase updated to v1.6 v1.8 (see changelog HERE)
v4.1 (not released for G960F):
- Added full Magisk support - MagiskSU is now default root solution (ROM should pass SafetyNet with Magisk Hide enabled in settings)
- Since systemless Xposed does not need to be re-installed every new DevBase I will release (in case of using the same root solution) - it makes no sense to keep it anymore as installation option
- SYSTEMLESS DevBase updated to v1.5 (see changelog HERE)
v4.0 (not released for G960F):
- A huge step in the systemless direction! DevBase installer now installs pure odexed stock ROM (just slightly debloated), then systemless SuperSU, then systemless DevBase, then (optionally) systemless Xposed
- All Knox related applications are available again (except SecurityLogAgent, to prevent annoying security alerts)
- Fake KNOX 0x0 status (check it in PhoneINFO app) - most of Knox related apps should work again, like in case of untouched KNOX flag
- All mods known from previous DevBase versions (up to v3.x) now are applied systemlessly - all modified files (including modded apps) are placed in /data/devbase/system instead of physical /system partition. Mods section (#4) has been updated to install mods to /data/devbase/system/(priv-)app if systemless DevBase has been detected (otherwise will be installed as usual, to /system)
- Deodex on-the-fly feature has been removed. If you really need deodexed ROM - you can install someone else's deodexed ROM, then systemless DevBase as an overlay
- Init.d support has been removed as it is deprecated (use su.d instead)
v3.8 (not released for G960F):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (not released for G960F):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (not released for G960F):
- Major improvement/bugfix in deodex_from function (added "-g" switch to zip command - finally no issues in case of deodexed Android 6.0.1)
v3.5 (not released for G960F):
- Improved root_from function (Android 5.1+) - added "setprop selinux.reload_policy 1" removal from init.rc (thanks to @Chainfire)
- Fixed bug in new alghoritm for checking whether stock recovery should be installed or not (introduced in v3.4)
- Added new functionality - installer will store a copy of patched stock kernel in /data for those who flashed custom kernel but for some reasons want to revert to the stock kernel (Android 5.1+)
v3.4 (not released for G960F):
- Completely changed alghoritm for checking whether stock recovery should be installed or not (it applies to FlashFire users). Now it depends on previously used recovery (instead of checking KNOX flag which was not 100% reliable across devices/recoveries)
v3.32 (not released for G960F):
- Updated set_csc, kcsc_backup, kcsc_restore functions to support more devices
- Updated partition detection algorithm to support more devices
- Fixed path to options.prop file placed in external sdcard in case of updating Marshmallow while using FlashFire
- Minor intaller's optimizations/bugfixes
v3.31 (not released for G960F):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for G960F):
- Improved method of reading options from ZIP file name (previous was directory/path sensitive also)
- Added support to mod_csc function for other than UNIX text format (it's a little ridiculous, but in case of some CSCs - original /system/csc/other.xml file has Windows or MAC text format!)
- Initial support for options.prop file in CRLF text format (DOS/Windows)
v3.21 (not released for G960F):
- Fixed installer's issue if there is a [space] present in ZIP filename or a directory containing DevBase (see #1728)
v3.2 (not released for G960F):
- Another improvements in add_initd function (details - see v1.3)
- Improvements in set_perm, set_perm_rec and root_from functions (recovery-independent structure)
- Improvements in deodex_from function related to Android MM
- New get_con function in the main sh script (useful for devs)
- BusyBox updated to 1.22.1 (bionic) [no, this is NOT a mistake!]
- Minor intaller's optimizations/bugfixes
v3.1 (not released for G960F):
- Significantly improved "add_initd" function in the update-binary shell script. Added support for (probably) all available Samsung's platforms (e.g. Exynos) and all available firmwares (based on Android 4.4+)
- In case of installation with Xposed framework installer checks if Xposed Installer app is present in /data/app and installs it automatically if necessary
- Minor intaller's optimizations/improvements
v3.0 (not released for G960F):
- Entire installer has been re-written from the scratch! All "magic" moved to update-binary which is a shell script. It opens up new possibilities never possible before!
- Introduced new customization method - you can change most frequently switched options just by renaming installer's ZIP file name. Currently supported "strings" in the file name:
"noroot" (means "do not root"), "deodex", "xposed", "initd" (no other comments are required, I hope..)
- Starting from v3.0 init.d support is disabled by default
v2.3 (not released for G960F):
- Added option to install suitable Xposed framework in one step while installing DevBase (for maximum comfort). There is a new xframework.sh script - device independent structure and full Android 5.1+/6.0+ support. Backup method is compatible with well known Xposed uninstallers (tested with @wanam's)
v2.2 (not released for G960F):
- Significantly improved root_supersu.sh script - device independent structure and full Android 5.1+/6.0+ suport including on the fly kernel/ramdisk/sepolicy patching if necessary. SU binaries are still copied to /system as it is the best choice in case of custom ROMs
- Changed order of performed operations in the updater-script due to new root_supersu.sh script advantages
- Installer wipes partitions designated for RAW content (e.g. kernel / recovery image) before writing to them
- Minor additions in dex_injector.sh script related to Android 6.0+
v2.11 (not released for G960F):
- Fixed some minor installer's issues ("set_perm" function in set_csc.sh did not work correctly while using wildcards in the path (it was exclusively FlashFire issue! no problem with TWRP / CWM). Fortunately - only /system/etc/csc_*.txt were really "affected" - it didn't cause real issues as these files are empty)
v2.1 (not released for G960F):
- As some people felt a bit disapointed / worried about DevBase v2.0 ROM file size - finally I have decided to debloat stock system.img (in same way as in v1.x => "Safe De-Bloat") and remove option to install all available bloatware. ROM file size has been reduced from about ~2GB to about ~1.6GB. Note for Devs / Chefs: Do not use Windows tools - you need Linux with "selinux" package installed (to handle SELinux contexts) to mount (rw) system.img safely. If you want to add / change any system content this way - remember about proper chown/chmod/chcon
- Added device check during install as flashing directly to EMMC block is potentially more risky for "other" devices. Installer will abort installation if device is not N910F (trlte(xx)). If you want to try this ROM on other N4 devices - you need to remove this check manually from updater-script (it is more conscious procedure)
v2.0 (not released for G960F):
- Completely new concept of ROM development that makes it easy to build most tuned and nuanced custom ROMs. No more arduous manual analysis or (often) invalid permissions / SELinux contexts taken from a kitchen. The main idea is to flash original, stock /system image as EMMC block (in same way as PC Odin does) instead of extracting ZIP's contents to mounted partition, then setting permissions, then creating symlinks, etc. However, it requires more knowledge related to sh scripts as ALL necessary changes need to be done on the fly, while installing (e.g. by injecting modified classes.dex and/or modified images/xmls to /res/../* into an apk). There are no limits, all depends on your creativity!
- One common ZIP installer for Odexed and Deodexed ROM - you can control it by new "deodexed.rom" entry in options.prop (there is new dex_injector.sh script which can deodex on the fly the whole ROM using previously processed classes.dex files)
- ROM is still Safe De-Bloated by default but removing bloatware during install is not mandatory - you can control it by new "safe.debloat" entry in options.prop (there is new protection included to avoid overfilling /system in case of large size of additional MODs and/or large multi CSC package)
- Major improvements in csc_detect.sh script - it is able to detect previous CSC even in cases of flashing over e.g. CM based ROM and/or previously formatted system partition. However, if detected CSC is NOT included in my multi CSC package, in both mentioned cases it is still not possible to keep detected CSC (as there is no CSC related content to backup / restore)
- Improvements in all sh scripts - additional "metadata" entries in updater-script (related to processed contents) are not required
- Improvements in root_supersu.sh script - it is suitable for 32 and 64 bit OS
- Added full zip support from the command line
v1.x (initial version, further improvements, not released for G960F):
- Built without using a kitchen. All set_metadata* / symlink entries are result of arduous manual analysis. For more info about the method - see hidden content for Devs / Chefs in THIS thread.
- New customization method without using Aroma (options.prop)
- Many useful scripts for easy installation: CSC applying/autodetection, backup/restore of security files, backup/restore of existing CSC package, XML modding on the fly, root, init.d support
- Many small changes and improvements "in the meantime" which I simply do not remember...
- Safe De-Bloated (see post #1 for details)
Reserved #4
First again ;D. Welcome!
@_alexndr
Is Knox fully removed and all Samsung Security disabled in build.prop?
iamnotkurtcobain said:
@_alexndr
Is Knox fully removed and all Samsung Security disabled in build.prop?
Click to expand...
Click to collapse
If we are talking about really important Knox content, whose presence is annoying or harmful to the rooted phone - then YES
If we are talking about all apps with *knox* in file name, whose presence just does nothing - then NO
You can of course have your own opinion on this subject - that's why there is a possibility to add your own debloat list to options.prop file (then just place modified options.prop file in the root directory of /sdcard or /external_sd - these settings will be used by the installer as long as it exist)
build.prop changes:
Code:
ro.security.vaultkeeper.feature=0
wlan.wfd.hdcp=disable
ro.config.tima=0
_alexndr said:
If we are talking about really important Knox content, whose presence is annoying or harmful to the rooted phone - then YES
If we are talking about all apps with *knox* in file name, whose presence just does nothing - then NO
You can of course have your own opinion on this subject - that's why there is a possibility to add your own debloat list to options.prop file (then just place modified options.prop file in the root directory of /sdcard or /external_sd - these settings will be used by the installer as long as it exist)
build.prop changes:
Click to expand...
Click to collapse
The vaultkeeper line isn't in build.prop. I checked.
Security Log Agent is also still there. Isn't that bad?
iamnotkurtcobain said:
The vaultkeeper line isn't in build.prop. I checked.
Security Log Agent is also still there. Isn't that bad?
Click to expand...
Click to collapse
You probably checked it wrong
First: You need to check necessary changes in already installed ROM, NOT by extracting system.img
In my ROM concept there are pure stock images in ALEXNDR/images - my installer performs all necessary changes on the fly while installing including changes in build.prop
Secondly: Even if you will see an app in /system which SHOULD be removed - this is not necessarily bad [emoji14] because there are 2 scenarios of removing unnecessary apps in my ROM:
- virtual (default) - unnecessary apps are added to enforceskippingpackages.txt file - that means that these apps will be completely skipped/ignored at boot (even if physically exists)
- physical (may be forced by editing options.prop or by renamig ZIP file) - unnecessary apps will be romoved physically
Please read carefully post #1 (it has been updated)
I have the Rom installed that's why I asked
Security Log Agent is there, RLC too. Removed both.
iamnotkurtcobain said:
I have the Rom installed that's why I asked
Security Log Agent is there, RLC too. Removed both.
Click to expand...
Click to collapse
But it completely does not matter as long as these apps exists in /odm/omc/{your_csc}/etc/enforceskippingpackages.txt
If its presence in /system bother you - you can force "phydebloat" in the future by placing your custom options.prop file in the phone
EDIT: @iamnotkurtcobain, I must admit that you were right about ro.security.vaultkeeper.feature line in build.prop (I just edited post #7) There is NO ro.security.vaultkeeper.feature=1 line in original build.prop, so the installer just was not able to change it to ro.security.vaultkeeper.feature=0
In exact same way works this patch:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
If you flash it - you will see that ro.security.vaultkeeper.feature=0 line also will NOT be added. I will try to discern if it is necessary even if ro.security.vaultkeeper.feature line does not exist at all. Thanks for being vigilant :good:
EDIT2: ro.security.vaultkeeper.feature=1 line exists in original /vendor/build.prop and (starting from v5.3) its value will be changed to "0" during install
_alexndr said:
But it completely does not matter as long as these apps exists in /odm/omc/{your_csc}/etc/enforceskippingpackages.txt
If its presence in /system bother you - you can force "phydebloat" in the future by placing your custom options.prop file in the phone
EDITiamnotkurtcobain, I must admit that you were right about ro.security.vaultkeeper.feature line in build.prop (I just edited post #7) There is NO ro.security.vaultkeeper.feature=1 line in original build.prop, so the installer just was not able to change it to ro.security.vaultkeeper.feature=0
In exact same way works this patch:
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
If you flash it - you will see that ro.security.vaultkeeper.feature=0 line also will NOT be added. I will try to discern if it is necessary even if ro.security.vaultkeeper.feature line does not exist at all. Thanks for being vigilant :good:
Click to expand...
Click to collapse
Lol np mate
Another question. Did you encounter any superSU issues?
I use TWRP and superSU the last few days and it worked perfectly (stock Rom, debloated myself). No superSU hangs, crashes.
Today I flashed your Rom (really great btw) because I wanted to install fresh and half an hour ago I had a root problem. Apps that use root started to hang and crash.
Really strange.
Hope magisk is working soon.
I flashed your @_alexndr ROM and everything works perfectly and I'm looking forward to even more mods. :good:
Maybe something which protects the battery more.
:laugh:
if someone has problems: with the SuperSU just flash over it in TWRP again.
Works fine with the current version.
Is secure folder still working with this rom?
mix1987 said:
Is secure folder still working with this rom?
Click to expand...
Click to collapse
As far as I know - these apps will never work with KNOX 0x1 (at least in case of S8 or newer device):
- Samsung Pay
- Samsung Pass
- Secure Folder
Fake KNOX 0x0 status also will not help
Thread has been updated
v5.3:
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
- Possibility to change CSC in case of S9/S9+ has been temporarily disabled for safety reasons (needs more research)
@_alexndr
Looking forward to version 5.4
Due to the fact, that I support both devices (S9/S9+) and S9/S9+ cross device section jus has been created - please move all discussion here:
https://forum.xda-developers.com/galaxy-s9-plus/development/rom-u1arc5-devbase-v5-2-t3764822
(I just sent request to move above thread to S9/S9+ cross-device development)
_alexndr said:
Download ROM
>> G960FXXU1ARC5_DevBase_v5.3.zip << (Android 8.0, updated Mar-19-2018)
>> SM-G960F/FD repository <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files could (soft) brick your phone! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Click to expand...
Click to collapse
Thread closed at OP request:good: