Related
Please note that I held no responsibility if you damage your phone, brick it or anything! This was made based on my own experience.
Hi, just thought I share my experience in changing CSC code. Initially I purchased my S5 with XSE (Indonesian) CSC code. Not having the patient for lollipop, I flashed Kazakhastan ROM and my CSC code changed to SKZ. After several months, samsung decided to release lollipop for XSE region and I flashed to it but was stuck with XXV (Vietnam). Not sure what happened but it seems that it takes the first code in the multi-CSC rom. Anyway this had me frustrated for a couple of months. So without further ado, here is the steps:
1. Download requirements:
-Download the BOC3 indian ROM: G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5 (must be this ROM - this rom allows change CSC code without root)
-Download your country ROM (for my example is G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5)
-Download and install Cygwin - or any app which can modify .tar files, but lets use Cygwin for this case
-Download and install Odin 3.09 or higher (to flash ROMs)
2. Flash the indian ROM (G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5) to your device
3. While waiting for the ROM to flash, open your country rom, remove .md5 at the end so the name will be from G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5 to G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar
4. Open the G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar with winzip or winrar, extract cache.img and hidder.img and place in home folder of Cygwin
5. Open cygwin and type the following:
tar -H ustar -cf csc.tar cache.img hidden.img
6. Test the indian rom, open dialer and type *#272*your-imei-number# - a selection of CSC should appear meaning that the ROM can change CSC without root
7. Flash in Odin, put the csc.tar in CSC and flash - this will not trip knox - I have tried this myself
8. Boot your phone, open dialer and type *#272*your-imei-number# - from here more codes should appear including the ones included in the csc.tar file
9. Select your country code (in this case I selected XSE) and it will automatically reboot
10. Shut down and check your CSC in bootloader (hold power + up + home) it should be correct now
11. Flash your country rom, clear cache and everything and voila!
Please also note that this guide should work on other devices as long as the device has a rom with *#272*your-imei-number# enabled without root
Hope this helps!
adit said:
Please note that I held no responsibility if you damage your phone, brick it or anything! This was made based on my own experience.
Hi, just thought I share my experience in changing CSC code. Initially I purchased my S5 with XSE (Indonesian) CSC code. Not having the patient for lollipop, I flashed Kazakhastan ROM and my CSC code changed to SKZ. After several months, samsung decided to release lollipop for XSE region and I flashed to it but was stuck with XXV (Vietnam). Not sure what happened but it seems that it takes the first code in the multi-CSC rom. Anyway this had me frustrated for a couple of months. So without further ado, here is the steps:
1. Download requirements:
-Download the BOC3 indian ROM: G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5 (must be this ROM - this rom allows change CSC code without root)
-Download your country ROM (for my example is G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5)
-Download and install Cygwin - or any app which can modify .tar files, but lets use Cygwin for this case
-Download and install Odin 3.09 or higher (to flash ROMs)
2. Flash the indian ROM (G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar.md5) to your device
3. While waiting for the ROM to flash, open your country rom, remove .md5 at the end so the name will be from G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar.md5 to G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar
4. Open the G900HXXU1BOD3_G900HOLB1BOD1_G900HXXU1BOCA_HOME.tar with winzip or winrar, extract cache.img and hidder.img and place in home folder of Cygwin
5. Open cygwin and type the following:
tar -H ustar -cf csc.tar cache.img hidden.img
6. Test the indian rom, open dialer and type *#272*your-imei-number# - a selection of CSC should appear meaning that the ROM can change CSC without root
7. Flash in Odin, put the csc.tar in CSC and flash - this will not trip knox - I have tried this myself
8. Boot your phone, open dialer and type *#272*your-imei-number# - from here more codes should appear including the ones included in the csc.tar file
9. Select your country code (in this case I selected XSE) and it will automatically reboot
10. Shut down and check your CSC in bootloader (hold power + up + home) it should be correct now
11. Flash your country rom, clear cache and everything and voila!
Please also note that this guide should work on other devices as long as the device has a rom with *#272*your-imei-number# enabled without root
Hope this helps!
Click to expand...
Click to collapse
will try this gan, not increase knox right?
hope it works.
Terima kasih..
noez92 said:
will try this gan, not increase knox right?
hope it works.
Terima kasih..
Click to expand...
Click to collapse
Knox remains 0x0 gan dijamin aman
adit said:
Knox remains 0x0 gan dijamin aman
Click to expand...
Click to collapse
so frustating to see XXV, festive effect, tiengviet lang :laugh:
---------- Post added at 12:37 AM ---------- Previous post was at 12:34 AM ----------
can you help for process in CYGWIN? because it says no directory
nvm, already do it in another directory.
omg!
i can confirm this method works on my G900H.
Nice job gan.
Thanks banyak...
Need available csc code for sgh-t889 on v4.3
How do i get the available csc code coz someone told me its what cozing my network &b data problems
Which ROM are you on? Does *#272*imei work?
Am on stock rom 4.3 & that code doesnt work on it
AFAIK, the only rom with working CSC change is BOC3 indian ROM: G900HXXU1BOC3_G900HODD1BOC3_G900HXXU1BOAD_HOME.tar .md5
That ROM is for S5 & mine is a Note 2
Please see the title and the forum, this is an S5 forum, better luck looking at note 2 forum.
adit said:
Please see the title and the forum, this is an S5 forum, better luck looking at note 2 forum.
Click to expand...
Click to collapse
Where we get this rom? Can you please give the link??
Hello all the community,
You will find here all informations needed either to simply update your phone but also to mod it a bit using custom recovery, rom, kernel and some tips.
Global discussion might be continue in the dedicated user thread here.
BEFORE ALL
1/ Always make a save of your data. We don't know what might happening even in a simple official update.
2/ Flashing Custom kernel, Custom rom, Root will trip knox. So you're warned.
MARSHMALLOW (6.x.x) DEDICATED POST
Last Update 03/05/2021
Currently MM rom may have those issues: http://forum.xda-developers.com/galaxy-s5/general/horrible-marshmallow-update-s5-bugs-bugs-t3390766.
LATEST STOCK FIRMWARE (UPD 23/08/18)
- Latest available is : G903FXXS1BRH2
Version: Android 6.0.1
Changelist: 14252124
Build date : 23/08/2018
Region Code : VOD (Netherlands)
PDA: G903FXXU2BRH2
CSC: G903FXXU2BRH2
How to proceed in order to update your phone :
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Power off your phone.
5/ Make a charge > 70%
6/ Download Odin 3.12.3
7/ Extract it somewhere and launch it in administrator mode.
8/ Put your phone in download mode.
To do it, press & maintain 3 buttons (Menu, volume down & power). Then push "Volume up"
9/ Quit Kies. Connect your phone to your PC. Odin will detect it in ID :COM
10/ Download lastest firmware available
10/ Select "AP" and select the downloaded firmware in tar file (if it is a zip file, you need to decompress it)
11/ Verify that only "Auto reboot" & "F-reset" is ticked. Click on Start.
12/ Wait till the phone reboots and that's it.
ROOT
How to proceed in order to root your phone :
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Download Chainfire Autoroot File
5/ Power off your phone.
6/ Make a charge > 40%
7/ Download Odin 3.10.7
8/ Extract it somewhere and launch it in administrator mode.
9/ Put your phone in download mode.
To do it, press & maintain 3 buttons (Menu, volume down & power). Then push "Volume up"
10/ Quit Kies. Connect your phone to your PC. Odin will detect it in ID :COM
10/ Select "AP" and select Cf-autoroot tar file (if it is a zip file, you need to decompress it)
11/ Verify that only "Auto reboot" & "F-reset" is ticked. Click on Start.
12/ Wait till the phone reboots.
CUSTOM RECOVERY (UPD 14/03/21)
How to proceed in order to have a custom recovery in your phone :
- NO ROOT
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Download TWRP Recovery (Upd#14/03: Currently 3.5.1.9)
5/ Power off your phone.
6/ Make a charge > 40%
7/ Download Odin 3.12.3
8/ Extract it somewhere and launch it in administrator mode.
9/ Put your phone in download mode.
To do it, press & maintain 3 buttons (Menu, volume down & power). Then push "Volume up"
10/ Quit Kies. Connect your phone to your PC. Odin will detect it in ID :COM
10/ Select "AP" and select TWRP Recovery tar file
11/ Verify that only "Auto reboot" & "F-reset" is ticked. Click on Start.
12/ Wait till the phone reboots.
- ROOT
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Make a charge > 40%
5/ Download TWRP Recovery IMG and copy it to your sdcard
5/ Download Flashify
6/ Launch Flashify. Select "Recovery image" then "Choose a file" and select the TWRP Recovery img file in your sdcard
7/ Reboot your phone.
CUSTOM KERNEL AVAILABLE (UPD 27/03/17)
- @cosmin691 kernel is based on Last MM sources G903WVLU1BPF1
UPDATE 25/03 : cosmin691 kernel
Currently sources are not uploaded.
Features:
- Always permissive
cosmin691 is currently working on a merged kernel using both sources of SM-G903 (F & variant W) and updated features. Stay tuned.
- @WILMANS2M kernel is based on Last MM sources G903FXXU1BPC1 UPDATE 14/04 : Shedkerneo beta 4
Sources (github) here.
Features:
- Enforcing by default but can be turned into permissive
- All governors unlocked (except OnDemand)
- All IO schedulers unlocked
- RKP & TIMA disabled
- Deleted Samsung rooting restriction
- DM-Verity disabled
CUSTOM ROM AVAILABLE (UPD 03/05/21)
- @WILMANS2M Rom is based on Last MM Samfirmware G903FXXU1BRH2.
UPDATE 03/05/21 : Shedrock.1.9.0.5.BRH2
-Deodexed, debloated (some remain though),
-Viper (with profiles, kernel & a few DCC),
-Xposed
-Many tweaks script (Better call voice quality, Faster boot, DHA Tweaks, many tweaks & scripts io boost, ram boost, zipalign, sd...),
-Preprogrammed Cron.d (each day autoclean, file trimming, databases optimizing), No more autoreboot after having installed the rom (you stay in recovery).=> Choose "reboot system"
Changelog:
<*>New base BRH2</*>
<*>Magisk Root added</*>
<*>Updated Busybox</*>
<*>Gravity Box xposed module updated</*>
<*>AllMyTweaks xposed module updated</*>
<*>Amplify xposed module updated</*>
<*>>Serial Number Changer xposed module updated</*>
<*>SudoHide xposed module updated</*>
<*>>Xhanghouts xposed module updated</*>
<*>Custom old kernel Shedkerneo beta5 always available</*>
<*>Viper choice always in aroma (classic or last Magnum Opus)</*>
<*>Xposed choice always in aroma</*>
...
EDIT: Missing Themes store for touchwiz: https://mega.nz/#!FUpQQKzC!oQPsUYLAabDtWQnyAsNilnFZreIGJSidgO1OlNG8_3A
...
**** shedkerneo features: https://github.com/ShedrockN4/s5neoltemax/releases
**** Classic ARISE: Deuteronomy version & no dolby atmos
Magnum Opus: Latest available & Dolby Atmos, AMD Zirene 3D
By default, enforcing mode. If you want the permissive one, use SelinuxToggler to switch.
- @Zapryanovv Rom is based on MM Samfirmware G903FXXU1BPJ2.
UPDATE 06/02/17 : Zapryanovv ROM v6.1 - FINAL
ROM INFO:
- Based on G903FXXU1BPJ2. (MM - 6.0.1)
- Rooted / Deodexed / Zipaligned / Busybox / Deknoxed
- Cleaned and removed Google and other unnecessary apps for more space. (Size: 722 MiB)
- New "hosts" file for minimal ads in browser or everywhere.
- Without the anoying warning "Check battery cover".
- Build.Prop tweaks (Updated WITH THE BEST by me).
- Init.D Support [Also Init.D tweaks like: dalviktocache, dalvikvm, zipalignonboot and many more...]
- Su.D Support
- Sound mod
- Xposed
....
TIPS
1/ How to use Titanium Backup with ExternalSD (sources)
-Go to Preferences -> Backup Folder Location.
-Click on Storage provider at the top (it's not obvious that it's clickable).
-Click on DocumentProvider storage. That will take you to a File Manager interface. You may have to click on the 3-dot menu on the top-right to enable the (external) SD card to be shown, then click the menu lines in the top-left and select your SD card, and click the "Select" at the bottom right. (You don't have to select your Titanium Backup folder here, you're just using this to get access to your SD Card.)
-Now you should be back in Titanium Backup and you can browse like you used to to get to your preferred backup folder on your external SD Card
I warn you that using this Document Provider storage is much slower - at least it seems so for me. But, it seems that it's the only way to go for now.
WORKING !
2/ How to roll back to Lollipop
1/ Flash Lollipop rom using Odin BUT untick "reboot"
2/ Pull out battery
3/ Go into Download Mode
4/ Flash TWRP recovery and format /data, /cache & /dalvik & /Internal SD card
5/ Reboot
6/ Once installed, go to "Parameters" and make a "Factory Reset"
FOR LOLLIPOP, go Post 3 (last update: 28/03).[/COLOR][/B][/SIZE]
Available mods, tips & bloatware in Post 2
USEFUL TOOLS
1/ Debloater
2/ Xposed (xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211)
=> List of xposed modules working/not working on Marshmallow.
3/ XPOSEDInstaller+ | Xposed™ Without Recovery!
USEFUL LINKS
TOP: Unpack/modify/Repack kernel img under win
TOP: Howto have SELinux permissive at boot without custom kernel (but use init.d script)
1/ Disable annoying "Check battery cover"
2/ EFS/NV_DATA full Backup/Restore
3/ Pit File
4/ Optimize build properties
5/ XBatteryControl+ The first intelligent battery calibrator
6/ ExtSD Fix
7/ Official ViPER4Android Audio Effects
8/ Fast Push 1.4.8 (the Easiest way to Push & Pull files
9/ ANDROID MULTITOOL v3.5.8 (to Kitchen your rom)
10/ DroidShell - Windows Shell Integration for Android Development
11/ Repair Guide
CREDITS
@Chainfire for root, @twrp for recovery, @LastStandingDroid for ....well too much , @svadev for his marvellous deodexing tool, @wanam, @gatesjunior, @Albe95, @NotGrump903, @kaodd, @rafitcu for our first and great custom kernel , @LetMeShow, @adbpusher123, @alexndr, @zhuhang, @mrchezco1995, @androidexpert35[/MENTION, [MENTION=981278]worstenbrood, @guitardedhero[/MENTION, [MENTION=516740]arcatarc, @TheRoyalSeeker[/strike]
Reserved
LOLLIPOP (5.x.x) DEDICATED THREAD.
LATEST STOCK FIRMWARE (UPD 26/09)
- Latest available is : G903FSWC1API1
Version: Android 5.1.1
Changelist: 5560999
Build date : 26/09/2016
Region Code : SWC (Switzerland)
PDA: G903FXXU1API1
CSC: G903FXXU1API1
How to proceed in order to update your phone :
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Power off your phone.
5/ Make a charge > 70%
6/ Download Odin 3.10.7
7/ Extract it somewhere and launch it in administrator mode.
8/ Put your phone in download mode.
To do it, press & maintain 3 buttons (Menu, volume down & power). Then push "Volume up"
9/ Quit Kies. Connect your phone to your PC. Odin will detect it in ID :COM
10/ Download lastest firmware available
10/ Select "AP" and select the downloaded firmware in tar file (if it is a zip file, you need to decompress it)
11/ Verify that only "Auto reboot" & "F-reset" is ticked. Click on Start.
12/ Wait till the phone reboots and that's it.
ROOT
How to proceed in order to root your phone :
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Download Chainfire Autoroot File
5/ Power off your phone.
6/ Make a charge > 40%
7/ Download Odin 3.10.7
8/ Extract it somewhere and launch it in administrator mode.
9/ Put your phone in download mode.
To do it, press & maintain 3 buttons (Menu, volume down & power). Then push "Volume up"
10/ Quit Kies. Connect your phone to your PC. Odin will detect it in ID :COM
10/ Select "AP" and select Cf-autoroot tar file (if it is a zip file, you need to decompress it)
11/ Verify that only "Auto reboot" & "F-reset" is ticked. Click on Start.
12/ Wait till the phone reboots.
ROOT (From @adbpusher123)
https://www.dropbox.com/s/pz8x0wj4f6okjdg/CF-Auto-Root-s5neolte-s5neoltexx-smg903f.zip?dl=0
make sure you have ------>(OEM UNLOCKED)<------MOST IMPORTANT,unknown sources, USB debugging all enabled or you will go into a bootloop or soft-brick
flash this with ODIN everything should work fine
CUSTOM RECOVERY (UPD 06/04)
How to proceed in order to have a custom recovery in your phone :
- NO ROOT
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Download TWRP Recovery (Upd#06/04: Currently 3.0.2.0)
5/ Power off your phone.
6/ Make a charge > 40%
7/ Download Odin 3.10.7
8/ Extract it somewhere and launch it in administrator mode.
9/ Put your phone in download mode.
To do it, press & maintain 3 buttons (Menu, volume down & power). Then push "Volume up"
10/ Quit Kies. Connect your phone to your PC. Odin will detect it in ID :COM
10/ Select "AP" and select TWRP Recovery tar file
11/ Verify that only "Auto reboot" & "F-reset" is ticked. Click on Start.
12/ Wait till the phone reboots.
- ROOT
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Make a charge > 40%
5/ Download TWRP Recovery IMG and copy it to your sdcard
5/ Download Flashify
6/ Launch Flashify. Select "Recovery image" then "Choose a file" and select the TWRP Recovery img file in your sdcard
7/ Reboot your phone.
TWRP RECOVERY from @adbpusher123
as of right now that I know of the neo does not have a working CWM recovery soo TWRP will have to do
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
(when in the app look for this name Samsung Galaxy S5 Neo Exynos flash that one in the app and you should be good)
CUSTOM KERNEL AVAILABLE (UPD 13/05)
- Permissive Stock only
Stock kernel to be only permissive. Here thanks to @LastStandingDroid or here thanks to @wobbler611.
- Custom kernel by @rafitcu here.
Toolchains used: aarch64-linux-gnu-4.9
Add: All governors stock: -Performance, Userspace (i use this for stock), Ondemand, Conservative, Interactive (this have a few tweaks)
- BFQ-v7r6 and I/O scheduler, LMK (Low memory killer), calibrated power coefficient, GPU tweaks, Init.d Support (i think)
-More stable
-Minimum clock set at 300 Mhz
...
Use the Kernel auditor APP to configure kernel.
It will break SuperSU. Need to flash it to patch kernel.
A BIG thank to him
- CUSTOM RECOVERY
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Download Kernel. Copy it to sdcard
5/ Power off your phone.
6/ Make a charge > 40%
9/ Put your phone in recovery mode.
To do it, press & maintain 3 buttons (Menu, volume up & power).
10/ Then choose "Install" and select the zip file in your sdcard.
12/ Reboot the phone.
- NO CUSTOM RECOVERY (but needs root)
1/ Go to "Parameters/About". Tap 8 times on "Version number". Developer mode is activated.
2/ In "developer option", tick "Activate". Go down and activate "OEM Unlock" & "USB Debugging"
3/ Go to "Parameters/Security" & tick "Unknown Sources"
4/ Make a charge > 40%
5/ Download kernel. Extract it and copy "Boot.img" to your sdcard
5/ Download Flashify
6/ Launch Flashify. Select "Boot image" then "Choose a file" and select the kernel img file in your sdcard.
7/ Reboot your phone.
CUSTOM ROM AVAILABLE (UPD 06/09)
Currently 4 are available.
- @LastStandingDroid Rom.
You can find it here.
UPDATE 06/02 : Currently version 1.2 based on G903FXXU1APA6 (BTU)
This rom is deodexed, debloated, xposed (option), vipered (option) and enable init.d scripts.
BUT you need a permissive kernel (modified stock or customized) or you will experience bootloop. See above to find them.
- @WILMANS2M Rom is based on Last Samfirmware G903FXXU1APG2.
UPDATE 06/09 : Currently version 1.3.8.2 based on G903FXXU1APG2
MultiCSC (separate zip file, no aroma): Choose the one you want, decompress and add/replace files under /system in rom zip.
Rom default is XEF.
Deodexed, debloated, battery cover popup disabled, block message enabled, enable ADB debugging By Default, Better call voice quality, Faster boot, DHA Tweaks, many CSC mod as Call Recording enable, No conversion from sms to mms, Time stamp change to sending time & not receive time, Download Booster quicksetting available, SMS delivery & MMS read & delivery reports activated by default, Real init.d script included in the installation (Works even on stock kernel), Viper & Dolby Atmos available (beats included & more, many profiles...), many tweaks & scripts (io boost, ram boost, zipalign, sd...), nova only, Preprogrammed Cron tasks, Bravia engine, lib to correct DB optimisation error, 5way reboot menu, xposed. You can flash on stock non patched kernel.
Changelog:
- Working SecMMS mod (sent sms time & unlimited characters)
- Updated ARISE to 3.4
- Deleted Power Nap xposed module because of some reboot)
No update for SuperSU to 2.78 because it causes many problems.
About Cron:
=> You can see if cron is started completely by watching in /data/tweakslog/cron_service_test.log
=> You can see if cron is working by watching in tweakslog/cronjob.log (a test is made every 10 hours)
=> Cron tasks log are stored in /data/cronlog
=> Check good start of all scripts in /data/tweakslog
No xposed. Follow adbpusher123 instructions about this mod.
XPOSED from @adbpusher123
(make sure you have ran the policy fix from the viper4android)
this is for stock or close to stock roms only!!!!!!
1.Install Xposed Installer App
Xposed installer App
2.Make a backup not needed but always helpful
3.Copy the Xposed file and the uninstaller to your sdcard
xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip (XPOSED FRAMEWORK FILE)
EXPOSED UNISTALLER FILE
4. Flash "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip"<---- Xposed FrameWork File) through TWRP recovery this is the one for our SM-G903F and Canadian variants that are running 5.1.1
if anyone has ARM64 system on 5.1.1 or 6.0.0 orrrrrr this phone with 6.0.0 contact me and ill put thoses files up as well
- ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)
- ARM64 means the devices that are running arm64 operating system (Galaxy S6, Note5 and all their variants...)
- SDK22 means Android Lollipop 5.1.x
- SDK23 means Android Marshmallow 6.0.x
DEBLOATING & Disable annoying "Check battery cover" from @adbpusher123
for debloating just download this and flash with recovery and bam!!!!! done
for Disable annoying "Check battery cover
just go into rom toolbox or anyapp that you can see system app and freeze or disable this apk "Popupuireceiver.apk"
BE CAREFUL: DO NOT USE THIS SOFT WITH LastStandingDroid DEBLOATED ROM AS YOU WILL EXPERIENCE BOOTLOOP.
USEFUL TOOLS
- Viper4Android (currently 2.4.0.1)
- Xposed (currently v85.1 which need to be flashed). You will also need the Xposed App Installer.
MAKE YOUR OWN CUSTOM ROM
Some remarks from @LastStandingDroid
Remove the how to dirty flash xposed instructions, it's outdated and isn't recommended since twrp is available.
Also easier to use is osf mount & Linux ext2/3/4 read since you can mount the system.img as read/write after convert it. Disk internals only allows read access afaik.
Creating a modified system.img is rather going to give you a faster flash and boot time on first flash will be improved greatly
instead of using disk internals.
Also you should never dd a system while booted.
Click to expand...
Click to collapse
- Using a modified recovery
- Using a decompress system file
How to proceed :
1/ First is to download a firwmare image from sammobile for our phone.
2/ You will need to decompress the file.Then you have access to system.img but you currently cannot decompress it (well you can but file properties will be different). Download this and decompress it anywhere. But the "system.img" in this folder and launch sparsechunk2img.bat.
You will now have a systemfix.img. Download and install DiskInternals linux reader.
3/ Once done, create an "IMG" folder on your PC and a "system" folder in it. Open Linux Reader, select "open'" and choose your "systemfix.img". On the right select all files, make a right click and select "save" and choose to save in the created "system" folder before.
4/ Time to use the deodex tool from @svadev. Decompress and put it in a empty folder (ex: C:\NEODEX) and launch SVADeodexerForArt.exe. Choose the "system" folder created before and tick all 3 boxes and wait till deodexing's completed. Now you have in C:\NEODEX all deodexed files which are in app, framework and priv-app folder. You can now replace original folders with those from NEODEX folder.
5/ You will have now a deodexed rom
6/ Time to make the zip file....
....to be continue
- Using an image instead of just put all files in a zip.
How to proceed :
1/ As we need to dump from phone, it is better to begin with clean system. So install latest official firmware and make a factory reset (save all needed file before as sdcard will be formatted). (see howto above)
2/ Use Chainfire Autoroot to root the system (see howto above)
3/ Install TWRP Recovery (see howto above)
4/ Now you will have the latest firmware rooted and a custom recovery. Time to remove bloatware and applications not needed using "Debloater".
As our Galaxy S5 Neo is not able to enable "block mode" when using "Debloater", you can just select "remove". You can refer to the list of removable apps/bloatware at the end of the thread.
5/ You have now a debloated, rooted rom. But odexed. If you want to remain odexed, time to build img so go to "point 13". If not, see below.
6/ To have deodexed files, you first need to decompress the tar downloaded file. Then you have access to system.img but you currently cannot decompress it (well you can but file properties will be different). Download this and decompress it anywhere. But the "system.img" in this folder and launch sparsechunk2img.bat.
You will now have a systemfix.img. Download and install DiskInternals linux reader. Once done, create an "IMG" folder on your PC and a "system" folder in it. Open Linux Reader, select "open'" and choose your "systemfix.img". On the right select folder "app", "framework", "priv-app" and build.prop file. Select "save" and choose to save in a the created "system" folder before. You need to move the build.prop file from "system' folder to the "img" folder. (here is the structure : IMG/System/App, Framework & priv-app folder)
7/ Time to use the deodex tool from @svadev. Decompress and put it in a empty folder (ex: C:\NEODEX) and launch SVADeodexerForArt.exe. Choose the "system" folder created before and tick all 3 boxes and wait till deodexing's completed. Create a "system'" folder there and put the deodex "app,framework, priv-app" folder in it. (Structure : NEODEX/System/App, framework & priv-app)
9/ Power off you phone. Go into recovery mode (push and maintain volume up, menu & power button).
10/ Once TWRP Recovery activated, on PC, maintain "Right Shift" & make a "Right Click". Select "open command prompt".
11/ Type :
adb devices (to see if your phone is well connected)
adb remount
adb shell
cd system
rm -rf app
rm -rf framework
rm -rf priv-app
Exit
adb push c:/neodex/system /system/
12/ Wait till it is finished. Then type "reboot". Now you have a debloated, deodexed, rooted rom.
13/ Time to build your system.img. Again go into recovery mode (Push & maintain Volume up, menu & power button).
On your desktop, maintain "Right Shift" & make a "Right Click" then select "Open Command Prompt" and type :
adb shell
su
dd if=/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM of=/sdcard/system.img
14/ Once done, type "reboot". Then copy this system.img on your PC.
Download this script (thanks @LastStandingDroid).
Extract it on your PC and put the "system.img" in the decompress folder. Recompress it in a zip file and copy it on your sdcard.
Done. Happy flash !
- Method by LastStandingDroid
LastStandingDroid said:
@WILMANS2M
quick sum up how I did it
Tools Needed:
osf mount http://www.osforensics.com/tools/mount-disk-images.html (has option to read/write images)
linux disk internals: http://www.diskinternals.com/ (better option if you want to extract, should keep permissions/symlink
ext2fsd
download http://sourceforge.net/projects/ext2fsd/ for adding read/write ext2/3/4 support in Windows
Download desired firmware
extract system.Img
convert it with Simg2img.
open osfmount locate to the converted spare image (raw) and press open.
before clicking OK on the bottom (or pressing enter) make sure to untick read/only in order for you to edit the system.img
If you feel that the image size is too huge you can decrease the free space. I think osf mount can do it. but I resized it in Linux
read http://unix.stackexchange.com/questions/36123/how-to-resize-ext3-image-files
you might need to write -f before the size I did it and it worked.
now it's time to sleep 2 am
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Tips:
1/ How to revoke stupid lag issues in some apps (Thanks to @LastStandingDroid):
- open start manager > battery > detail and de select the items you want to stop being optimized.
(this is similar to doze mode on 6.0 if not implemented it early)
- Remember to disable DWFS or what it's called the Samsung bs performance booster for some minutes until we reduce performance
2/
Out of Order said:
Information:
There was a report of force closes after modifying SM-G903F ROM, earlier in the thread.
The force closes only happen if you delete "Google Web View", since the new play store overlay (and nearly every other app overlay) is based on that app (in app purchases, news etc.).
Don't touch Google Web View and everything will be fine.
Regards,
Click to expand...
Click to collapse
LIST OF BLOATWARE/APPS REMOVABLE
- Container, preloadedkiosk, preloadedsso folders
- In System/App
AllshareFileShare, AllshareFileShareClient, AllshareFileShareServer, AllshareMediaShare
AntHalService, ANTPlusPlugins, ANTPlusTest, ANTRadioService
BBCAgent
BeaconManager_20
Bridge
ChocoEUKor
Chrome
ChromeCustomizations
CoolEUKor
Drive
ELMAgent
GalaxyAppsWidget_Phone_EssentialsOnly
GearManagerStub
Gmail2
Hangouts
KnoxAttestationAgent
KnoxFolderContainer
KnoxSetupWizardClient
Maps
MobilePrintSvc_Samsung
MSSkype_stub
Music2
OneDrive_Samsung
OneNote
Photos
QuickConnect_20
RCPComponents
RoseEUKor
SCONE_Android_ProxyService_Lib
SPrintSpoolerLMR1
STalkback
SwitchKnoxI
SwitchKnoxII
Videos
Youtube
- In System/priv-app
Excel_SamsungStub
GalaxyApps_3xh
HealthService
Kies
KLMSAgent
PhotoStudio_WQHD_Zero
PowerPoint_SamsungStub
sCloudBackupAppZero
sCloudDataRelay
sCloudDataSyncZero
sCloudSyncMemo
SFinder_L
SHealth4_3
SNoteProvider
SPDClient
SPPPushClient_Prod
S-Voice_Android_phone
Word_SamsungStub
....
Nice thread, feels like home
Thanks. Takes times though....will not finish it today.
Great job! It was time to get it done! Thanks
Hey @WILMANS2M
You did it!
Great job!! It's gonna be very useful.
Thanks a lot!!
:thumbup::thumbup::thumbup::thumbup:
Sent from my SM-G903F using XDA Free mobile app
it's a pleasure to help and test
Thanks for the credits
But without all you guys and Chainfire and the guys from TWRP our phones would still be bloated and locked as hell. Thumbs up for all the nice work which has been done here [emoji106]
Send from my SM-G903F using Tapatalk
New Firmware Released: PDA: G903FXXU1APA3 CSC: G903FVFG1AOJ1
Yep thanks. Not at home atm so will update later.
Envoyé de mon GT-I9505
valuable work, thank you :good:
a small question concerning Xposed
Which version should I install for our phone model
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
thank you again
V79 arm sdk 22
Envoyé de mon GT-I9505
SUVDrop said:
New Firmware Released: PDA: G903FXXU1APA3 CSC: G903FVFG1AOJ1
Click to expand...
Click to collapse
you mean which can be found here http://forum.xda-developers.com/showthread.php?t=3295464
now it's 03.22 am ? I really need to learn to get to sleep earlier ?
also I believe the "DE bloater" is not really do much. only disables?
I updates script can be done to fix it. but I'm so tired right now
Sent from my SM-G903F using Tapatalk
No LSD. You must tick remove. Otherwise yes only disable. On the phone y9u will see the command using rm
Envoyé de mon GT-I9505
Thread updated with LastStandingDroid last rom, list of removable app/bloatware and some other little things.
androidissime said:
...concerning Xposed
Which version should I install for our phone model
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
thank you again
Click to expand...
Click to collapse
I would the one (now) mentioned under "Useful Tools":
xposed-v79.1-sdk22-arm-custom-build-by-wanam-20160120
thanks :good:
@WILMANS2M absolutely great s5 neo index thread. I couldn't have done it better myself. gosh I'm very impressed. I totally need to learn to create better info in my threads
also hence, you're bloat list contains files we don't have Samsung_music20 doesn't exist.
and the do it yourself thread can be updated
quick sum up how I did it
Tools Needed:
osf mount http://www.osforensics.com/tools/mount-disk-images.html (has option to read/write images)
linux disk internals: http://www.diskinternals.com/ (better option if you want to extract, should keep permissions/symlink
ext2fsd
download http://sourceforge.net/projects/ext2fsd/ for adding read/write ext2/3/4 support in Windows
Download desired firmware
extract system.Img
convert it with Simg2img.
open osfmount locate to the converted spare image (raw) and press open.
before clicking OK on the bottom (or pressing enter) make sure to untick read/only in order for you to edit the system.img
If you feel that the image size is too huge you can decrease the free space. I think osf mount can do it. but I resized it in Linux
read http://unix.stackexchange.com/questions/36123/how-to-resize-ext3-image-files
you might need to write -f before the size I did it and it worked.
now it's time to sleep 2 am
Sent from my SM-G903F using Tapatalk
Thank you very much LastStanfingDroid. Will add your method. Do not worry currently thread not finished
Envoyé de mon GT-I9505
Hi guys,
here is a very easy step to enable multi window mode in your MARSHMALLOW updated lava pixel v1
1. Root your device (see threads available on XDA)
2. Download a root explorer ( Es file manager recommended)
3. Grant root access to the explorer
4. Go to system folder of root directory
5. Open build.prop
6. Find the line build type and change the word 'user' to 'userdebug' and save and reboot your device
7. Go to developer option and enable multi window
THATS ALL ENJOY
Also please you like this
Give a THANKS ?
Hello
Do you remember my custom ROMs for older devices? Do you remember my "DevBase" and its idea? If not - please read hidden content below:
>> [ROM] DevBase for Note 3 (SM-N9005) <<
>> [ROM] DevBase for Note 4 (SM-N910F) <<
>> [ROM] DevBase for S5 (SM-G900F) <<
>> [ROM] DevBase for S5 Duos (SM-G900FD) <<
Since I created these custom ROMs - many things have changed. Main idea of my previous work was the ability to flash these ROMs over stock ROM without wipe data - to let users simply jump between official ROM and DevBase with most necessary modifications for advanced users. It was relatively simple to implement until Samsung introduced both: dm-verity's boot prevention + forced /data encryption (starting from S7/S7edge series). What does it mean? If you disable /data encryption - you are able to use TWRP like in older devices, you are able to flash custom ROMs available in this section, but you are not able simply switch to official stock ROM. Since I bought my S7 edge I realized, that the most reasonable way is to go in the "systemless direction".
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but do not want to decrypt your device (for privacy/security reasons)? (!)
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (see hidden content above)
SYSTEMLESS DevBase is developed and physically tested on S7 Edge (G935F). However, it should work on ALL UNLOCKED SAMSUNG DEVICES running Android 6.x/7.x/8.x. Exynos? Snapdragon? NO MATTER !!!
Prerequisites:
- Samsung device running stock or stock-based Android 6.x or newer (7.x/8.x)
- Rooted device - Magisk v12+ or SuperSU v2.76+ installed in SYSTEMLESS mode (!)
- Stock, untouched /system partition (not mandatory, but recommended for OTA)
(!) WARNING (related to installing TWRP and/or rooting Nougat - e.g. ZPLN, DPLT or newer): There are confirmed reports that installing TWRP and/or rooting encrypted phones running stock Nougat causes bootloop (even if you just flash TWRP, without rooting). You will need to restore both - stock recovery and stock kernel (if you e.g. tried to flash SuperSU or other ZIP which might modify the kernel) to make your device bootable. You need to remove stock encryption (by formatting /data after rooting). If you need data encryption - you can easy re-encrypt already rooted device (by setting "KEEPFORCEENCRYPT" flag to "true" before (re)flashing Magisk or SuperSU).
SYSTEMLESS DevBase v2.0:
1. Benefits / main features:
- Works with encypted /data partition (**) (!)
- Working official OTA updates! (see Tips & Tricks - post #4)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Added 4G/3G network support (master/slave SIM card - applies to Duos variants)
- Call Recording (added "Record" button, auto record calls - starting from Nougat)
- Enabled "Recent App Protection" feature
(**) may not work starting from Android 7.0 Nougat
Installation:
1. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System" (DO NOT wipe /cache after flashing in case of encrypted /data!)
2. FlashFire app (***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Tap "FLASH"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices (!). It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data (!). It does NOT require custom recovery to work!
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk, another inspiration & some binaries used separately
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> SYSTEMLESS_DevBase_v2.1.zip <<
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
v2.1:
- Fixed potential "Google Play services" FCs in case of S8 or newer device(s)
v2.0:
- Initial support for devices using /system/omc CSC location (e.g. S8 / S8+ / Note 8)
- Added support for /system/preload as app location
- Other improvements & optimizations in the installer
v1.15:
- Added support for BINDSBIN mode (required by latest suhide) in case of SuperSU as root solution
v1.14:
- Added possibility to bypass all systemless mods by creating /cache/.disable_devbase file. It is usefull option especially for encrypted devices (without access to /data from TWRP) in case of you experienced bootloop due to placing a problematic MOD in /data/devbase/system/.. If /cache/.disable_devbase file exists then all systemless mods in ../app ../framework & ../piv-app will be moved to /data/devbase/system/.backup
- Backup all mods (to /data/devbase/system/.backup) instead of delete in case of major Android update has been detected
v1.13:
- Fixed bug with combination Magisk v15+ & SYSTEMLESS DevBase if we are trying to install one by one directly after wipe/format data
v1.12:
- Improved compatibility with Magisk v15+
v1.11:
- Fixed issues and improved compatibility with Magisk v14.5+
v1.10:
- Fixed not working /sbin support after clean installation of Magisk v14+, then SYSTEMLESS DevBase
v1.9:
- Improved/tuned compatibility with Magisk v13+ (which has been re-built from the scratch)
- Updated Magisk's binaries (e.g. resetprop function is now an applet available in magisk binary)
- Systemless BusyBox will be installed even with Magisk (since it has been removed from Magisk v13+)
v1.8:
- Fixed unroot2ota script to work while busybox is NOT in the $PATH (typical Magisk's case)
v1.7:
- Added support for /sbin via /data/devbase/sbin (you can only add a NEW item, e.g. script/binary/executable file). It can be an interesting feature for advanced users which would like to add custom commands, because /sbin is in the $PATH
- resetprop & unroot2ota now are placed in /sbin, in result unroot2ota command will natively work even with Magisk (without SuperSU)
v1.6:
- Improved/fixed Systemless Safe De-Bloat - now it should work in any case (even if enforceskippingpackages.txt file does not exist in your stock FW)
- In case of SYSTEMLESS 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
- Added new features to Systemless CscFeature MOD: Allow 3G network mode in case of slave SIM card (Duos variant); Enabled "Recent App Protection" feature
v1.5:
- Added full support for MagiskSU as root solution. SuperSU is no longer the only available prerequisite
- Improved build.prop support in case of SuperSU as root solution, without magisk installed (seems like we can't rely on resetprop binary @ Android N)
- unroot2ota: removed SuperSU's sukernel dependency
v1.4:
- Improved/changed support for /data/devbase/system/build.prop file (uses @topjohnwu's resetprop binary)
- "ro.warranty_bit" & "ro.boot.warranty_bit" are set to "0" at boot -> fake KNOX 0x0 status (uses @topjohnwu's resetprop binary)
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added SYSTEMLESS BusyBox bionic (the most stable and respected release)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
v1.0:
- Initial version
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
UPDATE: Due to the fact that installing TWRP and/or rooting encrypted phones running stock Nougat is not possible without format /data - the above described advantages applies to stock ROMs based on Android up to 6.0
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot may be performed if /data/devbase/system/build.prop file has been added, modified or removed (SuperSU case). It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SamsungCamera6): Create "SamsungCamera6" directory in /data/devbase/system/priv-app and then put modified "SamsungCamera6.apk" file into it. Set rwxr-xr-x (755) permissions to "SamsungCamera6" directory, rw-r--r-- (644) permissions to "SamsungCamera6.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Optional MODs
I put some of my favorite MOD's. These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom rom, nor from someone else's thread (thanks to @majdinj & @tdunham for their excellent modding guides). All files are FlashFire / TWRP flashable ZIPs.
These MODs are compatible with SYSTEMLESS DevBase - installer will try to detect if your /system has been moddified (or not) already. If the installer will not detect any popular /system modifications like SuperSU / busybox / Xposed (installed to /system) then will try to install app systemlessly to /data/devbase/system/(priv-)app
1. Modified Camera app:
- Full functionality of the Camera app in low battery
2. Modified Messages app:
- Disabled SMS delivery notifications (*)
(*) If you long press a message you can still check if the message has been delivered or not, we do not need to see and hear notifications for every sms. It's annoying to me!
>> MODs for G935F (Marshmallow) << (**)
>> MODs for G935F (Nougat) << (**)
(**) Original apps come from stock ROM for G935F, but these MODs should work on all S7 flat & edge variants (Exynos based)
In case of MODs installed to /system - you can restore original apk using backup stored in /data/alexndr/backup
Incredible work, man! Thanks
I'm HAPPY to see you in this Forum with an S7edge !
@_alexndr
Congrats mate! Great job I will test it in a few days
# 1 question
What about framework folder support with modded files ?
# 2 question
Modded deodex apps putted in /data/devbase/system folders will work on odex system ?
For example:
/data/devbase/system/priv-app/SystemUI/SystemUI.apk
will be deodexed
but orginal one:
/system/priv-app/SystemUI/SystemUI.apk
will be odex (with arm folders)
# 3 question
For example if I put systemui.apk the modded will be run and original no ? Or they collaborate toggether ?
Edit:
If I correct understand examples they are colaborate
# 4 question
system/etc/permissions files not supported too ? For exapmle platform.xml
••••
This tool have a BIG potential to be the greatest !
Have a nice day
ambasadii said:
@_alexndr
Congrats mate! Great job I will test it in a few days
# 1 question
What about framework folder support with modded files ?
# 2 question
Modded deodex apps putted in /data/devbase/system folders will work on odex system ?
For example:
/data/devbase/system/priv-app/SystemUI/SystemUI.apk
will be deodexed
but orginal one:
/system/priv-app/SystemUI/SystemUI.apk
will be odex (with arm folders)
# 3 question
For example if I put systemui.apk the modded will be run and original no ? Or they collaborate toggether ?
Edit:
If I correct understand examples they are colaborate
# 4 question
system/etc/permissions files not supported too ? For exapmle platform.xml
����
This tool have a BIG potential to be the greatest !
Have a nice day
Click to expand...
Click to collapse
#2: Deodexed apps works great in odexed rom, but odexed apps will not work at all in case of deodexed framework!
SYSTEMLESS DevBase uses bind mounts so entire /system/priv-app/SystemUI directory (and its content) will be virtually replaced by /data/devbase/system/priv-app/SystemUI => it means you will not see oat/arm directory => entire app will act as deodexed in /system/...
See attached screenshots - first is with moded SamsungCamera5 present in /data/devbase/system/priv-app, second is after deleting /data/devbase/system/priv-app/SamsungCamera5 (and reboot)
Now it is good time to answer #1: With framework I intentionally dropped possibility to replace systemlessly files in .../framework (for security reasons @ to avoid unintentional bootloops). Imagine that you "systemlessly" replace ../framework/oat directory by empty one => then all jars corresponding to *.odex files in oat/arm(64) will immediately require classes*.dex files inside jars (otherwise will not work). Even if you replace entire framework by deodexed (with classes.dex inside jars) -> as I stated above (answer #2) -> almost all apps in /system/app & priv-app will stop working as almost all apps are originally ODEXED.
Imagine also that you leaded device into bootloop by replacing files in framework AND you have encrypted /data. There is no easy way out for normal users (which are not able to play with "fake" /cache/su.img to make workaround matched to the problem) they will not be able just remove files (causing the problem) from /data/devbase/system/framework using TWRP
In sum - thats why I have not introduced such possibility for normal users, but you as the DEV may extend this idea and try to systemlessly replace entire framework, app & priv-app by deodexed content (I have not tested it personally, IMO it does not worth the effort)
#3: The answer is now clear from the answer to question #2 - modded will run and original will NOT (original will "virtually disappear")
#4: It is easy to extend support for etc/permissions/* files by editing 0000000devbase, I will think about it
Now almost everything is clear
so for example if i put /data/devbase/system/framework/services.jar and delete from system/framework/oat/arm64/services.odex file should work ?
add support for etc/permissions/* files to fix ext-card permissions (platform.xml)
ambasadii said:
Now almost everything is clear
so for example if i put /data/devbase/system/framework/services.jar and delete from system/framework/oat/arm64/services.odex file should work ?
add support for etc/permissions/* files to fix ext-card permissions (platform.xml)
Click to expand...
Click to collapse
The only way to "virtually remove" files using this method is "fake" (e.g. empty) parent directory. Another way is to create "fake" file with same name (but size 0 bytes).
There is a chance that it will work for services.jar - but such "fun/play" is only for advanced DEVs, like you :good: you need to extend support for framework and subdirectories in 0000000devbase su.d script. Then you can try to systemlessly replace jar by deodexed&modded one in /data/devbase/system/framework... and odex file by "fake 0 sized" odex in /data/devbase/system/framework/oat/arm64/...
EDIT: @ambasadii, there is no need to "remove" (whatever it means) odex file as it will be ignored in case of jar or apk contains classes*.dex inside
Ok I will test it
Sent from my SM-G935F using XDA-Developers mobile app
_alexndr said:
you need to extend support for framework and subdirectories in 0000000devbase su.d script. Then you can try to systemlessly replace jar by deodexed&modded one in /data/devbase/system/framework...
Click to expand...
Click to collapse
correct ?
Code:
if [ -d "/data/devbase/system/framework" ] ; then
for i in `ls /data/devbase/system/framework` ; do
mount -o bind /data/devbase/system/framework/$i /system/framework/$i 2>/dev/null
done
fi
if [ -d "/data/devbase/system/etc/permissions" ] ; then
for i in `ls /data/devbase/system/etc/permissions` ; do
if [ -f "/data/devbase/system/etc/permissions/$i" ] ; then
mount -o bind /data/devbase/system/etc/permissions/$i /system/etc/permissions/$i 2>/dev/null
fi
done
fi
EDIT: @ambasadii, there is no need to "remove" (whatever it means) odex file as it will be ignored in case of jar or apk contains classes*.dex inside
Click to expand...
Click to collapse
good news, remove it means delete
ambasadii said:
correct ?
Code:
if [ -d "/data/devbase/system/framework" ] ; then
for i in `ls /data/devbase/system/framework` ; do
mount -o bind /data/devbase/system/framework/$i /system/framework/$i 2>/dev/null
done
fi
if [ -d "/data/devbase/system/etc/permissions" ] ; then
for i in `ls /data/devbase/system/etc/permissions` ; do
if [ -f "/data/devbase/system/etc/permissions/$i" ] ; then
mount -o bind /data/devbase/system/etc/permissions/$i /system/etc/permissions/$i 2>/dev/null
fi
done
fi
Click to expand...
Click to collapse
Basically correct but you need to add bind mounts only for files (just in case)
I will send you today new (pre-release v1.1) version with "slightly tuned code" and with support for framework
good news, remove it means delete
Click to expand...
Click to collapse
Nice joke :silly: "whatever it means" => FYI => it may also mean bind mounts with files (0 bytes size)
Welcome to the S7 bro
Hi alexndr
I love you from 9005 to now.
Plz add a option in cmera mod,that under i geting 60fps video,i can get pic.
Mean, camcorder 60fps and camera pictures together .
I cant write eng.plz exercise me.
Sent from my SM-G935F using Tapatalk
Awesome to see you here! Thanks @_Alexandr
Gesendet von meinem SM-G935F mit Tapatalk
Nice to see a familiar face in the S7 (E) section! Good luck with all your plans here.
Verstuurd vanaf mijn SM-G935F met Tapatalk
Nice to find you here Alexandr, been using your Roms on my old note 3 about 8 months ago and they were the most stable "custom Roms". But then you were providing a full unmodified ROM with root access, can you do something like this here for those of us that wish it? I personally don't have access to a PC so I can't flash newer firmwares with Odin, so I'm stuck using flashable ROMs.
It is possible to install magisk and work hide magisk for apps, for example bank apps?
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 G935FXXU2xxxx_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 - probably there is no better alternative
ROM contains my extended CSC package, which I called G935FAXX (this is a combination of OXX, OXA, OXE, OLB, OJV, OJK + some additional). Final list of available CSC is as follows:
ACR, AFG, AFR, ALE, ARO, ATO, AUT, BGL, BNG, BTC, BTU, BVO, CAC, CAM, CAU, CEL, CHK, CHO, CHP, CHQ, COO, CPW, CYO, DBT, DKR, DRC, ECT, EGY, EON, ETL, EUR, GLB, ILO, INS, INU, ITV, KOR, KSA, LUX, LYS, MAT, MAX, MID, MM1, MRT, MRU, MTZ, MWD, MYM, NEE, NPL, NZC, ORX, PAK, PCL, PCT, PCW, PHE, PHN, PTR, ROM, SEB, SEE, SEK, SER, SIN, SIO, SLI, SLK, SMA, SMG, SKZ, STH, THL, THR, TMC, TPA, TPH, TPL, TRG, TTR, TTT, TUN, TUR, TWO, UPO, UYO, VIM, WTL, XEF, XEH, XEO, XEU, XFA, XFE, XFM, XFU, XID, XME, XSA, XSG, XSP, XTC, XTE, XXV, ZTO
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.G935FXXU8EUE1:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC (list of natively supported CSC as above) (*)
- Removed KNOX related content (useless on rooted phones)
- Rooted systemlessly (Magisk v23.0) (*)
- All original features are present and works (except KNOX related apps)
- Added "App Lock" feature (Settings -> Advanced features)
- 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 "Call/Message block" option in Settings
- Added "Show network speed" toggle (Settings -> Display -> Status bar)
- 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 (via "Record" button or "Auto record calls" option)
- Enabled "Recent App Protection" feature
3. Xposed framework & Xposed Installer app [optional] (*)
4. 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. Allowed values:
# true - install Magisk as root solution (default)
# false - do not root device
root=true
# Install Xposed framework matched to the ROM (there is also a possibility to detect Xposed profile
# automatically, but auto-detection will not work if user will perform wipe /system). Allowed values:
# auto - detect Xposed profile automatically
# true - force Xposed framework installation
# false - do not install Xposed framework
xposed=auto
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or keep current CSC contents).
# You can force the use of natively supported CSC by typing (use UPPERCASE!): ACR, AFG, AFR, ALE, ARO, ATO,
# AUT, BGL, BNG, BTC, BTU, BVO, CAC, CAM, CAU, CEL, CHK, CHO, CHP, CHQ, COO, CPW, CYO, DBT, DKR, DRC, ECT,
# EGY, EON, ETL, EUR, GLB, ILO, INS, INU, ITV, KOR, KSA, LUX, LYS, MAT, MAX, MID, MM1, MRT, MRU, MTZ, MWD,
# MYM, NEE, NPL, NZC, ORX, PAK, PCL, PCW, PHE, PHN, PTR, ROM, SEB, SEE, SEK, SER, SIN, SIO, SKZ, SLI, SLK,
# SMA, SMG, STH, THL, THR, TMC, TPA, TPH, TPL, TRG, TTR, TTT, TUN, TUR, TWO, UPO, UYO, VIM, WTL, XEF, XEH,
# XEO, XEU, XFA, XFE, XFM, XFU, XME, XSA, XSG, XSP, XTC, XTE, XXV, ZTO
CSC=KCSC
# Custom CSC Features. Allowed value in each line: <Example_line>value</Example_line>
<CscFeature_Common_SupportWcdmaInSlave>true</CscFeature_Common_SupportWcdmaInSlave>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
<CscFeature_Setting_EnableMenuBlockCallMsg>true</CscFeature_Setting_EnableMenuBlockCallMsg>
<CscFeature_Setting_CustNetworkSelMenu4>LTEONLY</CscFeature_Setting_CustNetworkSelMenu4>
<CscFeature_Setting_SupportRealTimeNetworkSpeed>true</CscFeature_Setting_SupportRealTimeNetworkSpeed>
<CscFeature_SmartManager_ConfigSubFeatures>roguepopup|autoclean|autorestart|applock|trafficmanager</CscFeature_SmartManager_ConfigSubFeatures>
<CscFeature_SmartManager_DisableAntiMalware>true</CscFeature_SmartManager_DisableAntiMalware>
<CscFeature_SystemUI_SupportRecentAppProtection>true</CscFeature_SystemUI_SupportRecentAppProtection>
<CscFeature_Message_DisplaySmsTimeAs>server</CscFeature_Message_DisplaySmsTimeAs>
<CscFeature_Message_DisplayMmsTimeAs>server</CscFeature_Message_DisplayMmsTimeAs>
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
<CscFeature_RIL_ForceConnectMMS>true</CscFeature_RIL_ForceConnectMMS>
# Custom physical debloat list. Allowed value in each line: path to app's directory in /system.
# (NOTE: wildcards are allowed here)
/system/*app/SamsungPass*
/system/*app/SamsungPay*
/system/*app/SecureFolder*
/system/app/SecurityLogAgent
/system/priv-app/KnoxCore
# Custom virtual debloat list. Allowed value in each line: exact app name with .apk extension.
# (NOTE: without app's path/directory, wildcards are NOT allowed here!)
Excel_SamsungStub.apk
Facebook_stub.apk
FBAppManager_NS.apk
FBInstaller_NS.apk
FBInstagram_stub.apk
FBServices.apk
FotaAgent.apk
Hangouts.apk
MSSkype_stub.apk
Music2.apk
OneDrive_Samsung_v2.apk
OneNote.apk
Photos.apk
PowerPoint_SamsungStub.apk
Videos.apk
WhatsApp.apk
Word_SamsungStub.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: "noroot", "encrypt", "rescue", "xposed", "CSC_xxxx.zip":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
Case 2 - do not root device (NOTE: you will get unmodified ROM!)
(place "noroot" string anywhere in the ZIP file name, e.g. "G935Fxxx_DevBase_v6.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. "G935Fxxx_DevBase_v6.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.
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. "G935Fxxx_DevBase_v6.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_G935Fxxx_DevBase_v6.x.zip"
In DevBase ROM v5.6+ there is "xposed" option which allows you to force Xposed framework installation. It is NOT forced by default - you need to force it manually while installing ROM with Xposed first time, renaming ZIP's file name to e.g. "G935Fxxx_DevBase_v6.x_xposed.zip". Next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible.
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
Notes related to EFS backup:
During install, my ROM's installer always performs EFS backup to {storage}/.backup/efs (where {storage} may be /external_sd, /usb-otg, /sdcard - in the preferred order). It is recommended to copy EFS backup occasionally outside the phone and store in safe location (PC, OTG, etc). There are 2 backups - when you first time installed my ROM (efs_backup.tar.gz) and recent, created additionally, just in case (efs_recent.tar.gz). Most useful will be most probably the first one (efs_backup).
You probably will never need these files, but sometimes s**t happens and restoring EFS backup may be the only one way to rescue your device!
When do I need to restore EFS backup?
- lost/invalid IMEI number
- proper IMEI but unable to connect to the network
- connected to the network but unable to make a call and/or transfer data
- unrecoverable bootloop (even after clean DevBase install with default settings)
NOTE: In contrast to many other custom ROMs - my installer uses gzip compression (*.img.gz) to store EFS backup(s). Restore command for your device is stored in txt file in the same directory with EFS backup. If you forgot command - you can read txt file containing proper command @ PC (Notepad) or even directly form TWRP using Terminal's 'cat' command, e.g.:
Code:
cat /external_sd/.backup/efs/efs_backup.txt
NOTE:: Do not panic, read the txt file peacefully and type command exactly as it is in TWRP's Terminal, then tap blue [enter] button. After all - please reboot device. If the problem was EFS related - your device just has been rescued
Installation:
CWM / 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 format /system before install my DevBase (my installer cleans your system well enough!).
Credits:
@samsung for awesome device & stock firmware base
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk and another inspiration
@rovo89 for Xposed framework & Xposed Installer app
@Tkkg1994 for TWRP for Oreo (quota support)
@Zackptg5, @osm0sis & @jcadduono for no-verity*
Hit Thanks button if you like my work. If you really appreciate my work - feel free buy me a coffee/beer (or flowers/wine for my wife who is patiently enduring my hobbies) https://www.paypal.com/donate/?business=RFGVQYRC34RVQ¤cy_code=EUR
Due to the fact, that some countries banned PayPal - I have created also Patreon site: https://www.patreon.com/_alexndr
Download ROM
>> G935FXXU8EUE1_DevBase_v7.4.zip << (updated Jul-10-2021, more info HERE)
>> SM-G93xF/FD repository (recent ROMs & BL packages) << (MEGA)
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
v7.4 (starting from G935FXXU8EUE1 DevBase):
- Fixed unzip issue which caused unexpected installation termination - applies to TWRP 3.5.0_9-1 and newer
v7.3 (starting from G935FXXU7ETBD DevBase):
- Fixed bootloop issue in case of Android Q and "noroot" scenario - thanks to @Zackptg5 for the up to date dm-verity disabler
v7.2 (not released for G935F):
- Fixed bootloop issue in case of Android Q and encrypted devices (applies to dirty update)
v7.1 (starting from G935FXXS7ETA8 DevBase):
- Potential fix for "make_ext4fs: not found" error in newer TWRP versions and in result "Failed! Not enough space..." message appears while applying CSC during install (applies to N960x devices)
v7.0 (not released for G935F):
- Initial support for Android Q / system-as-root devices
v6.0 (starting from G935FXXU3ERL3 DevBase):
- Introduced logging entire installation process (to devbase_install.log file, placed in /data or /cache in case of encrypted devices). These logs may significantly increase the possibility of my help in case of problems with/after installation
- Major imrovements/bugfixes/optimizations related to Android Pie support (e.g. takes care about special SELinux contexts for /odm content, introduced in Pie)
- Removed SuperSU support. Changed allowed "root" variable value in options.prop to true/false (backward compatible with old options.prop file)
- Removed "skipblcp" option - baseband/modem will be always updated, bootloader need to be flashed separately (update is usually not mandatory)
v5.9 (starting from G935FXXU2ERG2 DevBase):
- Changed device detection method to bootloader's prefix (instead of ro.product.*)
- Improved support for applying custom mods automatically at each ROM's install/update, introduced in v5.6 (added support for etc, fonts, media & usr directories in {storage}/devbase/system)
- Added support for custom {storage}/devbase/post-installation.sh script
v5.8 (starting from G935FXXU2EREM DevBase):
- Improved unzip_flash function in the installer to detect properly more flashing errors (e.g. EXT4 partition mismatch)
- Changed /odm flashing method to file based due to potential /odm partition mismatch (applies to carrier branded treble devices)
- Minor optimizations/improvements in the installer (this time mainly to improve installation speed)
- Busybox has been removed from /system/xbin to run properly some banking apps
v5.7 (starting from G935FXXU2ERD5 DevBase):
- Improved/expanded built-in RMM lock prevention (thanks to @jesec for idea of overriding properties via factory.prop)
- OEM unlock status will always be displayed correctly in Developer options (to avoid confusion) with stock kernel included in the DevBase ROM
v5.6 (starting from G935FXXS2DRDC DevBase):
- Added "App Lock" feature (Settings -> Advanced features)
- Added Xposed framework as installation option (it is NOT forced by default - you need to force it manually while installing with Xposed first time, e.g. by "xposed" string in ZIP's file name, but next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible)
- Added support for applying custom mods automatically at each ROM's install/update by placing modded apps in {storage}/devbase/system/(priv-)app or placing modded framework files in {storage}/devbase/system/framework (where {storage} may be: /sdcard, /external_sd or /usb-otg)
v5.5 (starting from G935FXXS2DRCC DevBase):
- Added support for flashing optional, CSC related partitions ($OMR, $PRELOAD)
- Added possibility to update recovery (optional, performs update if exists $NAME/images/recovery.img)
- Partition(s) may be wiped only by writing new block's image
- Minor optimizations / improvements in the installer
v5.4 (starting from G935FXXS2DRC3 DevBase):
- Big step forward in DevBase ROM customization ability - almost all current ROM features (hidden up to v5.3) have been moved to options.prop (you will be able to easy add new or remove current feature)
- Return to dm-verity-opt-encrypt boot patcher if necessary (wherever it works well, there are still devices which need "no_verity" function introduced in v5.1)
- Initial support for forcing (changing) CSC in case of devices with /odm as CSC location
- Minor optimizations / improvements in the installer
v5.3 (not released for G93xx):
- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)
v5.2 (not released for G93xx):
- 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 (starting from G935FXXU2DRB7 DevBase):
- 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). In case of Oreo & Magisk as root solution - "no_verity" function will be used as additional support for patching fstab* (as long as Magisk does not do it correctly)
v5.0 (not released for G93xx):
- 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 (starting from G935FXXU2DRAG DevBase):
- 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_G93xFXXU1xxxx_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 (starting from G935FXXU1DQLF DevBase):
- 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 (starting from G935FXXU1DQL8 DevBase):
- 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 (starting from G935FXXS1DQF6 DevBase):
- "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 (starting from G935FXXU1DQD7 DevBase):
- 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 (starting from G935FXXU1DQD1 DevBase):
- 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 G93xx):
- 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 G93xx):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (not released for G93xx):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (not released for G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- Potential fix for reported problems with root (rare cases)
v3.3 (not released for G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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 G93xx):
- 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)
Optional MODs
[WORK IN PROGRESS, MODDING HAS LOW PRIORITY]
These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom ROM, nor from someone else's thread (thanks to @majdinj, @tdunham, @Grouxho & @yash92duster for their excellent modding guides). All ZIP files are TWRP flashable:
>> MODs for SM-G93xF/FD <<
TIP: Are you tired with re-installing your favorite MODs every time you update this ROM? Just take advantage of the new DevBase feature, intruduced in v5.6 (see "Changelog"). It is enough to put your favorite apks and/or jars in /sdcard/devbase/system/(priv-)app (or ../framework) and these MODs will be detected & applied automatically every time you update this ROM. You can also use your /external_sd to store your favorite MODs (it is mandatory if you are using encryption).
Example for "G93xF_DisableHighVolumeWarning.zip" (modded SystemUI.apk):
- unzip SystemUI.apk file from my flashable MOD
- create /sdcard/devbase/system/priv-app/SystemUI directory
- place modded SystemUI.apk in above directory
Next time you will update my ROM - my installer will use modded SystemUI.apk instead of stock app included in my ROM
NOTE: Use this feature consciously and carefully! It may happen that your MOD is not compatible with a newer Samsung's base (especially in case of major Android update)! I will warn you about it, but only in case of MY MODs, I am not able to predict what kind of mods you are using.
Welcome
Sent from my SM-G955F using Tapatalk
DQD1?
Very nice can't wait
Why no roms have Canadian CSC lol. Iv will give this a try?
Sent from my SM-G935F using XDA-Developers Legacy app
Hi @_alexndr and thanks for the new base, just a couple of questions, could be possible to add UUB CSC or TTT or TPA? this are to be used in Latinamerica
For the other side, is it possible to give indications how to disable safety volume, with this option I will very glad to test your ROM!!! I know I have to modify services.jar, but the question will be where!!
S-Health not working, Knox tripped message.
civato said:
S-Health not working, Knox tripped message.
Click to expand...
Click to collapse
You can add:
Code:
ro.config.tima=0
to /data/devbase/system/build.prop (then reboot)
The advantage of systemless build.prop support is that you need to add it only ONCE.
Your favorite entries stored in /data/devbase/system/build.prop will be used even after another DevBase update (this file will not be touched while the installer run next time)
I will consider to add this line by default by the installer if it does not exists already in /data/devbase/system/build.prop
thanx.
how to use on flat.G930F?
_alexndr said:
You can add:
Code:
ro.config.tima=0
to /data/devbase/system/build.prop (then reboot)
The advantage of systemless build.prop support is that you need to add it only ONCE.
Your favorite entries stored in /data/devbase/system/build.prop will be used even after another DevBase update (this file will not be touched while the installer run next time)
I will consider to add this line by default by the installer if it does not exists already in /data/devbase/system/build.prop
Click to expand...
Click to collapse
Some questions if I may?
1*Is there a way you can do it on installation of the rom. Like adding it in the option.prop or in the update binairy of the devbase.zip?
2*Using a kernel with dm verify disabled (like a custom kernel), what will be the disadvantages of that?
3*Is there a way of installing directly to data/devbase/system (like a modded app) with a zip installed with recovery?
I would also like to say this is a very smooth rom and a good solid way of installing a rom to your needs, Thanks for that!
Calvin.manneson said:
thanx.
how to use on flat.G930F?
Click to expand...
Click to collapse
edit:tried to rename zip and replace images inside the zip....how to fool installer?
@civato.. if you come out of your 'cave' occasionally...hope you tempted to share ...:victory:
edit:success!!
edited update_binary inside zip...flashed ok
:laugh:
Calvin.manneson said:
@civato.. if you come out of your 'cave' occasionally...hope you tempted to share ...:victory:
:laugh:
Click to expand...
Click to collapse
Sorry it is nice and quiet here in the man cave. No time to do a lot of android stuff. I just am reading up on my edge s7.
Can you put bootloader and modem in zip file so we can flash via recovery?
civato said:
Some questions if I may?
1*Is there a way you can do it on installation of the rom. Like adding it in the option.prop or in the update binairy of the devbase.zip?
2*Using a kernel with dm verify disabled (like a custom kernel), what will be the disadvantages of that?
3*Is there a way of installing directly to data/devbase/system (like a modded app) with a zip installed with recovery?
I would also like to say this is a very smooth rom and a good solid way of installing a rom to your needs, Thanks for that!
Click to expand...
Click to collapse
1*I will think about it in the next release
2*Should work with any kernel which can be successfully patched by Magisk or SuperSU (systemless). If you flash a custom kernel - you basically need to reinstall Magisk (or systemless SuperSU) to apply all necessary patches to your new kernel.
There is another way, for advanced users - if your just flashed custom kernel supports init.d (but it is mandatory that scripts need to be executed in post-fs-data) - you can manually put 0000000devbase script to /system/etc/init.d, but you need to remove check for init.supersu.rc / init.magisk.rc file(s) (as there is no official support for this) - in such case systemless mods should work even without systemless root
3*Of course you can do it directly or via ZIP. You can also see my method (slightly expanded for encrption support via /cache) - see MODs for Nougat in post #5 here:
https://forum.xda-developers.com/showthread.php?p=70036256&postcount=5
Calvin.manneson said:
thanx.
how to use on flat.G930F?
Click to expand...
Click to collapse
Calvin.manneson said:
[...]edit:success!!
edited update_binary inside zip...flashed ok
:laugh:
Click to expand...
Click to collapse
I have plan to release also ready to use version for G930F
Work in progress with DQD2 (in both versions - G930F(D)/G935F(D))
This release will contain "ro.config.tima=0" entry in /data/devbase/system/build.prop by default (but only in case of fresh installation, if you install it over previous DQD1 DevBase -> you need to add this line manually as the installer never touch existing file) - due to issue with S-Health reported by @civato
_alexndr said:
1*I will think about it in the next release
Click to expand...
Click to collapse
Also possible to add the
"wlan.wfd.hdcp=disable"
This for screenmirroring support.
I did the things above on my own in the devbase.zip and added the LUX csc as there is still no official support for it. I created one so I got autocorrection in mu csc region on the keyboard. ANd added it to the zip package and made the changes on the option.prop and SW_Configuration.xml so it installs just fine.
One problem I got when I create my own system.img (with the new DQD2) it boots just fine (full clean install) but it got stuck on the Network status checking right after you confirm the samsung legal stuff on the installation wizard.
It just keeps spinning there and doesn't go any further. Any tips?
Edit:
The private mode is it working I did not test it yet or do I need to add a modded "PersonalPageService"
civato said:
Also possible to add the
"wlan.wfd.hdcp=disable"
This for screenmirroring support.
I did the things above on my own in the devbase.zip and added the LUX csc as there is still no official support for it. I created one so I got autocorrection in mu csc region on the keyboard. ANd added it to the zip package and made the changes on the option.prop and SW_Configuration.xml so it installs just fine.
One problem I got when I create my own system.img (with the new DQD2) it boots just fine (full clean install) but it got stuck on the Network status checking right after you confirm the samsung legal stuff on the installation wizard.
It just keeps spinning there and doesn't go any further. Any tips?
Click to expand...
Click to collapse
Good idea to add also "wlan.wfd.hdcp=disable", I forgot about screen mirroring fix :good:
I will add LUX CSC if such CSC will be released oficially with Nougat (I had some bad experience with using old xmls in case of major Android update)
_alexndr said:
Good idea to add also "wlan.wfd.hdcp=disable", I forgot about screen mirroring fix :good:
I will add LUX CSC if such CSC will be released oficially with Nougat (I had some bad experience with using old xmls in case of major Android update)
Click to expand...
Click to collapse
Maybe you can add the official dutch (NL t9) in the T9DB folder so you get autocorrection for the NL typing people. (I extracted that on a official samsung Nougat rom and confirmed it working.
See attachments.