Related
Important notes for Developers / ROM 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 a lot of 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
Hello
I have decided to create a pure base, which can be a pattern for ROM Chefs (not only for beginners) ROM is initially safe de-bloated (read below what does it exactly mean), but all features are present and works!
ROM can be installed by normal users as well. If you like a little de-bloated ROMs, clean, but with all working features - there is no better alternative I think
ROM contains my extended CSC package, which I called G900FDAXX (this is a combination OXE, OJV + some additional). Final list of available CSC is as follows:
CAC, CAU, ECT, ILO, KSA, LEB, LYS, SEK, SER, SKZ, THR, TMC, WTL, XEO, XSG
NEW !!! I present you new, unique option: "Keep current CSC", so you can install my DevBase keeping your original CSC. My DevBase contains all possible CSCs from G900FD variant so there is no need to worry about it
How does it work? This option detects your current CSC and automatically applies it during install.
NOTE: Do not use so called "Superwipes" and/or additional /system formats, otherwise "Keep current CSC" option will not work properly. Please read THIS for explanation.
How can I check my current CSC?
Install Phone INFO app from Play Store and check your CSC. If you are using stock ROM and everything is ok with your CSC - all CSC fields in Phone Info app should display the same CSC, as below (otherwise, you probably forgot about wipe data when you were installing ROM with another CSC).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can I change my current CSC?
Q: Recently I tested several ROMs, in result of it my CSC has changed. I would like to install your DevBase, but first I want to restore my country's original CSC. What should I do?
No special/additional steps are needed. Just install my DevBase with edited options.prop file placed on internal sdcard or extSdCard -> type CSC=[your_csc] instead of CSC=KCSC. Remember to perform "Wipe data" in the recovery before install. Note that sometimes additional reboot is required after completing pre-configuration steps to display your CSC correctly in Phone Info app).
ALEXNDR.G900FDXXS1CQD1:
1. Base:
- Odexed (original stock files) + stock kernel
- Multi CSC (list of natively supported CSC as above) (*)
- Removed SecurityLogAgent (annoying on rooted phones)
- Rooted systemlessly (Magisk v13 or SuperSU 2.82) (*)
- All original features are present and works
- No visual changes (100% stock look)
- Safe De-Bloated (more info below)
What does it mean and why is it called "safe"?
- ONLY apps available in stores are removed from DevBase, so you can easy (re)install any of these app if you like
- ONLY pre-installed system apps are 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 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 apps list:
ChatON
Chrome
Drive
Dropbox
Flipboard
Google+ / Photos
Group Camcorder
Group Play
Hangouts
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
Smart Remote
2. Modded systemlessly - contains SYSTEMLESS DevBase
- All mods known from previous DevBase versions (up to v3.x) 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). Init.d support has been removed as it is deprecated (use post-fs-data.d or su.d instead). For more information, guides, tips & tricks - see SYSTEMLESS DevBase.
(*) - 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 - copy this file, then edit it using
# e.g. Notepad++ (do not use Windows Notepad!), then place your 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.
#
# I agree to use any part of my work to create more advanced custom ROM,
# but it would be great if you add me to the credits
# Enable root access with the selected method. Allowed values:
# magisk - install Magisk & MagiskSU as root solution (default)
# supersu - install SuperSU as root solution, without Magisk
# noroot - do not root device (NOTE: you will get unmodified ROM!)
root=magisk
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or copy your current CSC contents).
# You can force the use of natively supported CSC by typing (use UPPERCASE!): CAC, CAU, ECT, ILO, KSA, LEB,
# LYS, SEK, SER, SKZ, THR, TMC, WTL, XEO, XSG
CSC=KCSC
NEW !!! Starting from DevBase v3.0 there is a new customization method - you can change frequently switched root options just by renaming installer's ZIP file name (instead of editing options.prop file). Currently supported "strings" in the file name: "magisk", "supersu", "noroot":
Case 1 (default) - install the ROM with Magisk & MagiskSU as root solution
(just flash ZIP file "as it is")
Case 2 - install the ROM with SuperSU as root solution, without Magisk
(place "supersu" string anywhere in the ZIP file name, e.g. "G900FDxxx_DevBase_v4.x_supersu.zip")
Case 3 - do not root device (NOTE: you will get unmodified ROM!)
(place "noroot" string anywhere in the ZIP file name, e.g. "G900FDxxx_DevBase_v4.x_noroot.zip")
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! I highly recommend you to update bootloader/modem also to the newest versions available in post #3, to avoid potential bugs/issues.
Wipe data is NOT required if you are coming from stock ROM or a previous version of my DevBase (if you leave "Keep current CSC" option untouched in /options.prop or if you choose same CSC as you are currently using). In other cases - wipe data is highly recommended!
I do not recommend using any additional superwipes or formats before install my DevBase (my installer cleans your system well enough!).
Credits:
@Chainfire for systemless SuperSU and a lot of inspiration
@topjohnwu for Magisk, Xposed, another inspiration & some binaries used separately
@wanam for Xposed framework used in older DevBase versions
@amarullz for Aroma Installer used in older DevBase versions
@svadev & @_riddle for deodexed tools/binaries used in older DevBase versions
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
DOWNLOADS
Download ROM:
>> G900FDXXS1CQD1_DevBase_v4.3.zip << (Android 6.0.1, updated Jul-04-2017, more info in post #300)
>> Recent ROM versions for SM-G900FD <<
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
v4.3 (starting from G900FDXXS1CQD1 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 (see changelog HERE)
v4.2 (not released for G900FD):
- Added possibility to add systemlessly NEW apps to /data/devbase/system/(priv-)app (up to 5 apps in "app" & 5 apps in "priv-app"). The only condition is that you need to rename its directories to CustomApp[1...5] (e.g. CustomApp1, CustomApp2, etc..). These apps will remain even if you flash a new DevBase as corresponding dummy directories will exist in future DevBase updates
- In case of DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc
- SYSTEMLESS DevBase updated to v1.6 v1.8 (see changelog HERE)
v4.1 (not released for G900FD):
- 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 G900FD):
- 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 (starting from G900FDXXS1CPH1 DevBase):
- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)
v3.7 (starting from G900FDXXU1CPF4 DevBase):
- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)
v3.6 (starting from G900FDXXU1CPE1 DevBase):
- 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 (starting from G900FDXXU1CPE1 DevBase):
- 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 G900FD):
- 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 (starting from G900FDXXU1CPE1 DevBase):
- 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 G900FD):
- Potential fix for reported problems with root (rare cases)
v3.3 (starting from G900FDXXS1BPD3 DevBase):
- 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 G900FD):
- 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 G900FD):
- 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 G900FD):
- 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 (starting from G900FDXXS1BPC3 DevBase):
- 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 G900FD):
- 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 G900FD):
- 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 G900FD):
- 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 G900FD):
- 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 ~1.6GB to about ~1.3GB. 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 G900FD):
- 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, up to G900FDXXU1BOJ1 DevBase):
- 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)
DOWNLOADS
Useful PC Odin flashable files:
>> Recent bootloader versions for SM-G900FD <<
>> Recent modem versions for SM-G900FD <<
>> Recent kernel versions for SM-G900FD <<
(suitable kernel is already included in my ROM)
Note:
To update bootloader and/or modem you have to power off the phone, wait min 10 seconds and then go directly to Download Mode using Vol_down+Home+Power key combination. Load bootloader using BL button and/or modem using CP button in PC Odin. Push "Start".
DOWNLOADS
Optional MODs
I put some of my favorite MOD's - especially for normal users who want to use my rom - as it is. 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 TWRP / CWM / FlashFire flashable ZIPs:
1. Modified Camera app:
- Full functionality of the Camera app in low battery
2. Modified Phone app:
- Disabled increasing ringtone
3. Modified Messages app:
- Disabled SMS to MMS auto-converting
- Increased SMS/MMS recipient limit (10 -> 1000)
- Increased SMS/MMS hour limit (100 -> 1000)
- Disabled SMS / MMS log history in call logs
- 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 G900FD (Marshmallow) <<
>> MODs for G900FD (Lollipop) <<
In case of MODs installed to /system - you can restore original apk using backup stored in /data/backup/alexndr
Nice work
Have you found much difference between the G900F and G900FD firmwares?
For example, would it be easy enough to patch a F firmware to work on FD?
Only FD S5???
djb77 said:
Nice work
Have you found much difference between the G900F and G900FD firmwares?
For example, would it be easy enough to patch a F firmware to work on FD?
Click to expand...
Click to collapse
No, it's not easy as FD kernel and many FD apps have some special features included to support dual sim (e.g. Messages app from G900F works with G900FD but doesn't recognize many dual SIM operations).
core720 said:
Only FD S5???
Click to expand...
Click to collapse
I have no experience with MD variant. I bought G900FD variant 3 days ago
Maybe it is enough to replace the kernel and the modem to work properly in Brazil...
_alexndr said:
No, it's not easy as FD kernel and many FD apps have some special features included to support dual sim (e.g. Messages app from G900F works with G900FD but doesn't recognize many dual SIM operations).
Click to expand...
Click to collapse
Cool, thanks for that info. If it was possible I would integrate FD support into TGP, but it doesn't sound as easy as the other variants.
alexndr Thank you for your work
deodexed clearance
_alexndr said:
Download ROM:
>> G900FDXXU1BOF1_DevBase_alexndr.zip << (Android 5.0, updated Jun-27-2015)
>> Recent ROM versions for SM-G900FD <<
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.
Download Deodexed ROM:
Note:
Deodexed ROM might be potentially less stable due to performing additional actions using tools that are still under early development (thanks to @_riddle & @svadev). If you do not know why do you really need deodexed ROM then it means you do not really need it! Please do not report bugs without the information that you are using deodexed version.
>> Recent Deodexed ROM versions for SM-G900FD <<
Click to expand...
Click to collapse
Finally some new action abt this awesome phone, so 1st of all let me say thank you!!!!
Second, I just want to clear something about the deodexed version of this rom. You said might be unstable due....
Unstable ight come from the fact that you have used those scripts to deodex it? Or due the fact that some apps might not work on deodexed roms? im a bit confused abt that afirmation.
Anyway Im downloading both versions for testing and I will try to use them for couple of days before posting up again for info.
chasemyass said:
Finally some new action abt this awesome phone, so 1st of all let me say thank you!!!!
Second, I just want to clear something about the deodexed version of this rom. You said might be unstable due....
Unstable ight come from the fact that you have used those scripts to deodex it? Or due the fact that some apps might not work on deodexed roms? im a bit confused abt that afirmation.
Anyway Im downloading both versions for testing and I will try to use them for couple of days before posting up again for info.
Click to expand...
Click to collapse
Testing started...
I was on android 4.4.2 as you can see from my BB from screenshot and used FlashFire to flash the odexed version and all my installed apps remained, but (there is always a but isnt it? ) phone was working in slow motion and the google didnt wanted to upgrade play services since i was coming from an older version (didnt received any error) so my next logical reaction was tdo a factory reset from recovery.
After that everythings works awesome so far. I will keep you guys updated if anything needs to get noticed here.
Congratz again and ty for this rom
Sent from my SM-G900FD
chasemyass said:
Finally some new action abt this awesome phone, so 1st of all let me say thank you!!!!
Second, I just want to clear something about the deodexed version of this rom. You said might be unstable due....
Unstable ight come from the fact that you have used those scripts to deodex it? [...]
Click to expand...
Click to collapse
Yes, exactly As I have mentioned already - these tools are under early development. Potentially problems may occur but not necessarily
BTW - I'm on deodexed for 3 days (just for testing) - no problems so far
chasemyass said:
Testing started...
I was on android 4.4.2 as you can see from my BB from screenshot and used FlashFire to flash the odexed version and all my installed apps remained, but (there is always a but isnt it? ) phone was working in slow motion and the google didnt wanted to upgrade play services since i was coming from an older version (didnt received any error) so my next logical reaction was tdo a factory reset from recovery.
After that everythings works awesome so far. I will keep you guys updated if anything needs to get noticed here.
Congratz again and ty for this rom
Sent from my SM-G900FD
Click to expand...
Click to collapse
I highly recommend you to update BL / CP also (note that BL / CP contains also a part of radio firmware -> NON-HLOS.bin / modem.bin).
It is not good combination: Lollipop ROM + KitKat baseband (NON-HLOS+modem)
_alexndr said:
Yes, exactly As I have mentioned already - these tools are under early development. Potentially problems may occur but not necessarily
BTW - I'm on deodexed for 3 days (just for testing) - no problems so far
I highly recommend you to update BL / CP also (note that BL / CP contains also a part of radio firmware -> NON-HLOS.bin / modem.bin).
It is not good combination: Lollipop ROM + KitKat baseband (NON-HLOS+modem)
Click to expand...
Click to collapse
Hmm I will try, but if I will do that, will I loose root? And what will be so problematic regarding kk bb with lp rom cooked over? No need to explain, just pass a link so I can see by myself. Thx
Sent from my SM-G900FD
chasemyass said:
Hmm I will try, but if I will do that, will I loose root? And what will be so problematic regarding kk bb with lp rom cooked over? No need to explain, just pass a link so I can see by myself. Thx
Sent from my SM-G900FD
Click to expand...
Click to collapse
No, you will not lose root
There were a lot of problems reported in G900F in case of using the newest firmware + an older modem/baseband (e.g. lost of wifi passwords every reboot).
I'm not sure if there are same problems in G900FD, but devices are very similar so could be...
_alexndr said:
No, you will not lose root
There were a lot of problems reported in G900F in case of using the newest firmware + an older modem/baseband (e.g. lost of wifi passwords every reboot).
I'm not sure if there are same problems in G900FD, but devices are very similar so could be...
Click to expand...
Click to collapse
I will test and report here then. As I will test a bit more with this setup... Thank you mate!
EDIT: Bug confirmed. Wifi psswd lost after reboot when using KK baseband, duh!
Sent from my SM-G900FD
thanks for this rom
I found one bug on deodex version
when I set alarm and turn it off the alarm icon still appear on statusbar
chasemyass said:
I will test and report here then. As I will test a bit more with this setup... Thank you mate!
EDIT: Bug confirmed. Wifi psswd lost after reboot when using KK baseband, duh!
Click to expand...
Click to collapse
So please update bootloader + modem to the newest version (BOF1 + BOE2) and should be ok
iNTER5LOve said:
thanks for this rom
I found one bug on deodex version
when I set alarm and turn it off the alarm icon still appear on statusbar
Click to expand...
Click to collapse
Strange, no problem here on deodexed. Try to backup your apps & data and then perform wipe data / factory reset from recovery
(note that deodexed version needs about 10 minutes for first boot after performing wipe data)
_alexndr said:
So please update bootloader + modem to the newest version (BOF1 + BOE2) and should be ok
Strange, no problem here on deodexed. Try to backup your apps & data and then perform wipe data / factory reset from recovery
(note that deodexed version needs about 10 minutes for first boot after performing wipe data)
Click to expand...
Click to collapse
my fault
its wanam xposed issue not your rom :good:
Hello!
My phone says in About menu 900FD, but on the download screen: 900MD. Is it normal? I have bought it as 900FD.
Now I'm on a deodexed stock ROM (installed with FlashFire to save KNOX0x0). Do I need clean install the DevBase ROM, or simply dirty flash is enough?
G.
Georgie9117 said:
Hello!
[1] My phone says in About menu G900FD, but on the download mode: G900MD. Is it normal? I have bought it as G900FD.
[2] Now I'm on a deodexed stock ROM (installed with FlashFire to save KNOX0x0). Do I need clean install the DevBase ROM, or simply dirty flash is enough?
Click to expand...
Click to collapse
[1] Don't worry, same here. I was also confused due to this info in DM, but did some test that confirmed it is definitely G900FD. See attachments G900MD doesn't support e.g. LTE800 (band 20) while G900FD support it. No comments are required
[2] Dirty flash SHOULD be enought.. I could guarantee that wipe data will not be necessary only in case of flashing over pure stock installed via PC Odin or FlashFire
Detach3
Introduction
This Magisk module is for detaching apps from the Google Play Store.
It removes your defined packages from the 'Manage apps and device" section and disables them from auto-updates.
Installation
Flash module in Magisk Manager only.
Not necessary to reboot after flashing this module.
This module is designed to flash as many times as you like.
It is configured with a *configuration file. You can create one before flashing this module to define your package(s) or the default one will be used instead, which detaches YouTube by default.
Add your package name(s) you would like to detach to the configuration file, with each package name on a new line.
You can add more package names to your configuration file or the default one at any time, then simply just flash module again to apply it. Again, no need to reboot or any other user interaction needed.
Read the log that Magisk Manager displays when flashing the module, it displays the detached package(s) for confirmation.
*Configuration file: /storage/emulated/0/Android/detach.cfg
Reattach
https://forum.xda-developers.com/t/module-detach3-detach-market-links.3447494/post-84951411
Scheduler
https://forum.xda-developers.com/t/module-detach3-detach-market-links.3447494/post-84981039
Uninstallation
Uninstall with Magisk and reboot.
Troubleshooting
Follow uninstallation method. After reboot open playstore, navigate to the 'Manage apps and device' section so it can populate and then re-flash the module.
Still have an issue? Post your problem in detail and upload your Magisk installer log, found in your Download directory after saving it ( Shown here ).
Changelog
Spoiler: Click to expand
v3.00
- Initial release
v3.01
- Disabled Fallback broadcast
v3.02
- Disable auto-update for detached apps
- Disable playstore running in background
- Added uninstall script to revert changes
v3.03
- Updated sqlite3 binary
- Added support for x86 and x64
v3.04
- Added package check for configuration file
- Minor alterations
v3.05
- Recompiled sqlite3 binaries
- Improved device platform check
- Added database check
- Added the default detach.cfg file
- Minor alterations
v3.06
- Improved installer checks
- Fixed inflating uninstall script error
- Tidied installer script
- Added reattach feature*
* Comment out package name(s) in detach.cfg to reattach.
v3.07
- Fixed minor install.sh error on Android 11
- Improved some installer logic
- Added scheduler feature*
*Termux and Termux:API apks need to be installed beforehand for scheduler
v3.08
- Fixed playstore update log error on some devices
- Fixed script not applying package names with the same string of characters
- Fixed minor installer check for checking packages
- Fixed termux-api binary check
- Disabled package checks on some devices
- Added option to open playstore with scheduler notification
- Added option to open configuration file with scheduler notification
- Added option to flash module with scheduler notification
v3.10 - Note: Disable scheduler and uninstall previous version before installing this version.
- Removed package check (Some users have had issues, reboots etc.)
- Removed scheduler (Not needed for now)
- Removed unnecessary coding
- Added new method to prevent detached apps repopulating
- Added disabling of Play store trackers
- Other minor alterations in installer script
- Cleaned up installer script for new method
v3.11
- Added ignore GET_USAGE_STATS in AppOps
v3.12
- Updated sqlite binaries
- Removed disabling of fallback receiver
- Added disabling of alarm manager background service
v3.13
- Updated sqlite binaries
- Added ignore RUN_ANY_IN_BACKGROUND in AppOps
- Added ignore RUN_IN_BACKGROUND in AppOps
- Disabled App Discovery Service
Frequenly Asked Questions
Spoiler: Click to expand
Q. Can I use the old detach.txt?
A. No, I decided to ditch it. It now uses a new method explained in the installation section.
Q. Where is the boot script installed?
A. No boot script is needed for detaching, everything is done while flashing the module.
Q. Does this break safetynet?
A. No, it doesn't conflict with safetynet at all.
Q. Why shouldn't I re-enable Play Protect?
A. It will interfere with the module's purpose.
Q. Will having Play Protect disabled, open me up to vulnerabilities?
A. No, the playstore scans their market apk's after developers upload them.
Q. I usually install after-market apks (modified ones) and I think play protects me from this?
A. You should scan your unknown apk with Total Virus.
Q. How do you find a package name?
A. Magisk Manager lists your apps with the package name underneath each one, in the Magisk Hide list.
Q. What Magisk version is needed?
A. The module template is designed for Magisk v20.4+
Q. Do I need to uninstall previous version before updating?
A. No, unless stated. Just flash updated version.
Q. Do auto-updates still work for all my other apps that aren't detached?
A. Yes, auto-update and other notifications etc still work.
Download
See attached below -- detach-3.xx.zip
Previous versions
Detach Market Links for Theme Ready Apps *
Introduction
This Mod is for detaching apps from the Google Play Store that are included in the Theme Ready Apps zip and/or aroma installer from Team Black Out for CMTE and Substratum theme engines.
*Now also includes majority of all themed apps by Team Black Out by using an optional txt file.
The purpose is that updates will not show in your update list and also in update notifications from the Google Play Store.
This allows you to auto-update or the ability to use the update all button without the worry of updating Theme Ready Apps which will break your themes for those apps updated.
The Google apps that are detached if you're not using the optional txt file are Gmail, Google App, Google Plus, Hangouts, YouTube and Gboard (Google Keyboard).
Installation
Flash Mod in recovery, no need to wipe anything but if using SuperSU systemless mode or Magisk, flash this mod afterwards.
No need to flash again in-between ROM updates if using SuperSU systemless mode or Magisk or if your ROM supports addon.d scripts.
To detach more themed apps, place the detach.txt file either on root of your sdcard or internal storage and remove the comment from the apps you wish to detach and then flash Detach.zip
You can also use the optional detach.txt file to just selectively detach Theme Ready Apps.
If you don't use the supplied detach.txt file, only Theme Ready Apps will be detached.
To add your own custom packages (apps), read here > https://forum.xda-developers.com/showpost.php?p=72194332&postcount=147
Uninstallation
Rename detach.txt on sdcard to detach.remove, flash Detach.zip again and reboot.
This will remove all files related to installation, including the txt and custom file and restores all market links.
Note
If not using SuperSU or Magisk, you need to have init.d support.
The configured script doesn't execute until after 60 seconds when boot has completed, this also includes the remove script too.
This Mod has been tested by myself on Android 6 and 7.
You still have the ability to update your Theme Ready Apps via Google Play Store but you'll need to use the search function instead.
Changelog
v1.0
- Initial release
v1.1
- Changed detach method
v1.2
- Disabled service for database
v1.3
- Bug fixes
v1.4
- Added static sqlite binary
v2.0
- Added themed apps to detach with configuration txt file (optional)
v2.1
- Cleaned up installation script
- Added mod removal option
v2.2
- Magisk compatible (systemless installation)
- SuperSU systemless mode compatible (systemless installation)
- Fixed init.d detection
- Fixed market links reappearing
- Updated detach.txt (added Wallpapers, Pixel Launcher, Capture (GoPro))
v2.3
- Updated script and detach.txt (added Gboard, Clock, Camera, Google Connectivity Services, Google VR Services, Google Play Services)
v2.4
- Updated script and detach.txt (added Google Carrier Services and the ability to add custom packages)
v2.5
- Fixed market links reappearing
v2.6
- Main script updated for removal process
- Disabled code for a playstore service that no longer needs to be disabled
- Removed Contacts, Phone and Photos from default install
Thanks @hinxnz, I'll try the newest one.
Report 1.3: My theme ready gapps were detached except Google Calendar. I installed Black Google Calendar from TBO. Is there something I can do for this?
sunanulh said:
Thanks @hinxnz, I'll try the newest one.
Report 1.3: My theme ready gapps were detached except Google Calendar. I installed Black Google Calendar from TBO. Is there something I can do for this?
Click to expand...
Click to collapse
I was thinking about adding more themed apps to detach but would have to either use a config file on sdcard for example or probably better to make an aroma version but I would need all the package names first.
hinxnz said:
I was thinking about adding more themed apps to detach but would have to either use a config file on sdcard for example or probably better to make an aroma version but I would need all the package names first.
Click to expand...
Click to collapse
I think a "fulfilled" config file is simpler. So the users have just to add/remove '#' symbol.
For the name of the apps, maybe you can ask to TBO.
Cheers
hinxnz said:
I updated mod, see if it works for you now & I made a thread for it too > http://forum.xda-developers.com/and...detach-market-links-theme-ready-apps-t3447494
Click to expand...
Click to collapse
It's still not working on Stock rooted N. Thanks for trying.
Glad I saw your post that you put this thread up!
I downloaded 1.3 and flashed it and rebooted and waited for two minutes, but YouTube is still showing an update.
cmo220 said:
It's still not working on Stock rooted N. Thanks for trying.
Click to expand...
Click to collapse
Could you call script manually with Terminal Emulator and post output
RED ZMAN said:
Glad I saw your post that you put this thread up!
I downloaded 1.3 and flashed it and rebooted and waited for two minutes, but YouTube is still showing an update.
Click to expand...
Click to collapse
But the first version still works for you?
YouTube hasn't been updated for awhile AFAIK, what version is showing an update?
Are the other theme ready apps showing in your 'My apps & games' list?
Do you have any apps in your 'Wishlist', found in side menu?
hinxnz said:
Could you call script manually with Terminal Emulator and post output
But the first version still works for you?
YouTube hasn't been updated for awhile AFAIK, what version is showing an update?
Are the other theme ready apps showing in your 'My apps & games' list?
Do you have any apps in your 'Wishlist', found in side menu?
Click to expand...
Click to collapse
I couldn't get a /su.d folder so I put it in /system/su.d, which was already there and working. Here is the output.
angler:/ $ su
angler:/ # /su.d/99-detach.sh
sush: /su.d/99-detach.sh: not found
127|angler:/ # /system/su.d/99-detach.sh
angler:/ # Component {com.android.vending/com.google.android.finsky.services.DailyHygiene$DailyHygieneService} new state: disabled
CANNOT LINK EXECUTABLE "sqlite3": cannot locate symbol "u_setDataDirectory_55" referenced by "/system/xbin/sqlite3"...
Aborted
CANNOT LINK EXECUTABLE "sqlite3": cannot locate symbol "u_setDataDirectory_55" referenced by "/system/xbin/sqlite3"...
Aborted
And a bunch more of the same error.
The first version? I've deleted the previous versions .zips.
I've installed 1.0, 1.2, and 1.3.
Youtube has been showing this way for about a week, even after reboots.
11.32.53 is what's showing on Google Play, I've got 11.29.55 installed from TBO Theme Ready Apps v 21.
com.google.android.youtube
Showing up in the My apps & games list as installed...
Gmail
Google App
Google+
Google Photos
Hangouts
Wishlist, yes, I've got several.
RED ZMAN said:
The first version? I've deleted the previous versions .zips.
I've installed 1.0, 1.2, and 1.3.
Youtube has been showing this way for about a week, even after reboots.
11.32.53 is what's showing on Google Play, I've got 11.29.55 installed from TBO Theme Ready Apps v 21.
com.google.android.youtube
Showing up in the My apps & games list as installed...
Gmail
Google App
Google+
Google Photos
Hangouts
Wishlist, yes, I've got several.
Click to expand...
Click to collapse
Could you call script in Terminal Emulator and post output too.
For example:
Code:
su
/system/su.d/99-detach.sh
I don't think I've used terminal emulator except for twice since the G1, so I'm not sure if I did this right.
[email protected]:/ $
[email protected]:/ $ su
system/su.d/99-detach.sh <
sush: /system/su.d/99-detach.sh: not found127|[email protected]:/ #
hinxnz said:
Could you call script in Terminal Emulator and post output too.
For example:
Code:
su
/system/su.d/99-detach.sh
Click to expand...
Click to collapse
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Surge1223 said:
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Click to expand...
Click to collapse
Thank you Surge! :highfive:
Surge1223 said:
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Click to expand...
Click to collapse
Cheers, thanks and yeah that's definitely the reason
Super idea, this would of been good a few months ago when google pushed their framework update and it broke some apps that i kept from updating,,, @Shaftamle google keyboard is the main on one, thank you
3GotoM ym morf tneS
Version 1.4 works for me now on 7.0. Thanks everyone!
Installed version 2.0 earlier today and seems to be working perfectly. Nothing showing needing updated.
Thanks!
How to add Black Google Calendar and Black Keep in the list?
sunanulh said:
How to add Black Google Calendar and Black Keep in the list?
Click to expand...
Click to collapse
Just remove the comments from those two as well as the other theme apps you flash.
Here's an example, theme ready apps, calendar and keep will be detached.
Code:
Contacts
Gmail
Google App
Google Plus
Hangouts
Phone
Photos
YouTube
#Inbox
#Duo
#Dropbox
#PushBullet
Calendar
Keep
#Telegram
#Swiftkey
#Translate
I have tried installing your script... And no matter how I go about... I cannot get the script to populate the su.d directory like it should...
And... Since I don't understand your flashable... I can't pull what I want out of it...
Could you explain how to install said script without recovery?
Thanks
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge (G925xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G925F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Reserved
There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<
I just updated to android 10 on my oneplus 6 via local storage. Then fastboot installed twrp, flashed stock boot img, flashed twrp installer zip, rebooted to twrp & then installed magisk 20.1 including riru v15 & edxposed by justin (sandhook) for android Q.
The problem I am facing is that I am not able to install apks as whenever I manually try to install an apk, it says 'Sorry, no application available'
Please help out!
Apologies for bumping the thread but can someone help me out with the package installer details?
The path it is stored in the /system/ directory and share the apk? If I somehow could replace it as a system application and make it run?
Hello there, I'm facing the same problem with Android 10 and LineageOS 17.1.
I can install apk's via F-Droid and Aurora Store, I would assume Play Store works too, but I currently don't have it.
When I download an apk with a browser and I click on the notification in the notification drawer, it works and installs the app.
But when I try to open the finished download via the downloader manager, it does not work. The error is the same as posted by the OP (Sorry, no application available)
I also can not open apk's from non-default file explorers (Root Explorer, ES File Explorer) which gives the same error, but opening from built-in Files (com.android.documentsui) works.
The Package Manager is correctly located in
Code:
/system/priv-app/PackageInstaller/PackageInstaller.apk
I've tried the suggestions from a very old thread here on XDA:
- Delete Cache and Data for Package Manager
- Reset all app preferences
- Reboot to TWRP and clean Dalvik/Cache
- Disable all apps that can draw over other apps
But that didn't fix it unfortunately. Any ideas would be welcome.
Redmi Note 8 Pro, unlocked bootloader, recommended vendor
Android 10, LineageOS 17.1-20200330-UNOFFICIAL-hyper-begonia
Kernel 4.14.158+
NoGapps, microG
Magisk Modules:
- Bromite
- Magisk Manager for Recovery Mode (mm)
- NanoDroid (microG sub-module)
- Riru - Core
- Riru - EdXposed
- Smali Patcher
- Systemless Hosts
Xposed Modules:
- AFWall+
- EdXposeed Manager
- XposedGMSCoreUnifiedNlp
- Amplify (disabled)
- FakeMyGPS (disabled)
- GravityBox (disabled)
- XPrivacyLua (disabled)
Features:
- Fully rewritten su binary!!!
- In-app su binary Updater!!!
- SuperPower access prompt (no countdown timer!)
- SuperPower access logging (date and time only!)
- SuperPower access notifications (Faster, with guaranteed security!)
- Deep process detection (all apps and processes!)
- Works with non-standard shell locations
- Always runs in ghost mode
- Supports SuperSU/Magisk
SuperPower Premium's current extra features include:
- Full Command Logging (input/output/error)
- Per app notification/logging settings
- Pin protection for Superuser prompt
- App list and preferences backup/restore
Download:
SuperPower on Google Play Store:
https://play.google.com/store/apps/details?id=wkroot.superpower
SuperPower Premium on Google Play Store:
https://play.google.com/store/apps/details?id=wkroot.manager.premium
If you have rooted your device through SuperSU or Magisk, the fastest/easiest/recommended way to installing SuperPower's su binary is to download and install the attached SuperPower-v30.5.apk, which has the "su binary Updater" feature.
If Magisk is your root, you can use both SuperPower and Magisk at the same time, if you use the SuperPower-v30.5.apk to install the SuperPower's su binary!!!
Note: the TWRP zip is attached at the bottom of this post!
Donation via PayPal:
https://www.paypal.com/cgi-bin/webs...ss=BQJLWCA5L8WMG¤cy_code=BRL&source=url
Developer's journey
Since 2016, I have been working on ChainsDD's Superuser's su binary, fixing several bugs and security issues, to make them work on my devices. The result of that work is a fully rewritten/full-featured su binary and root access manager app: SuperPower - Root Access Manager!
SuperPower is highly compatible with SuperSU. Also, it uses the SuperSU's tools to ensure its working on SELinux-enabled devices.
Special thanks:
@zinxv, @ChainsDD and @Koush, for have built Superuser/su binary;
@Chainfire for have built SuperSU.
Wanderson Kalil, author of SuperPower.
Changelogs
v5.7 - 2023-03-03
- Fixed --mount-master inherinting SuperPower instead of init mount namespace
- Fixed Termux stuck on prompt
- Added Support for SuperSU/Magisk
v5.6 - 2022-11-09
- Added support for Android 11/12
v5.5 - 2020-11-09
- Removed unused receiver causing crashes at app's opening
- Fixed bug of "Settings" screen not opening in Multiuser mode
v5.4 - 2020-11-06
- Fixed a performance regression on the "apps" screen
- Fixed a bug introduced in v5.3
v5.3 - 2020-10-30
- Improved support for Android 11
- Fixed SuperPower's Prompt/Notifications not being shown on Android 10 due to code incompatibilities
v5.2 - 2020-09-25
- Fixed app not opening on some devices
v5.1 - 2020-09-16
- Fixed a crash on the "Info" screen
v5.0 - 2020-08-14
- Removed the su binary Updater feature (Google Play Store requirement!)
- Improved "Root" setting
v4.8 - 2020-07-18
- Made some improvements into the Settings/Preferences screen
- The su binary Updater is now only available to the device's owner
- The su binary is now deleted immediately after SuperPower has been uninstalled
- Fixed a crash after an app has been installed
v4.7 - 2020-07-12
- Fixed an in-app crash introduced in v4.6
v4.6 - 2020-07-10
- If SuperPower app is not installed, the SuperPower's su binary is automatically removed from the device as part of app uninstall!!!
V4.4 - 04/07/2020
- Updated su binary version to match SuperPower version
v4.3 - 2020-07-03
- added new permission to support Android 11
- added option to switch the Settings screen
- added suppport for Scoped Storage: removed backup/restore of apps/preferences feature and related permissions
v4.2 - 2020-06-26
- Added Uninstall/Unroot button to the su binary Updater feature so you can remove SuperPower's su binary from your device (Google Play Store Requirement!)
v4.0 - 2020-06-13
- Finally republished on Google Play Store again!!!
v4.0 - 2020-05-15
- Fixed Language Switcher not working on Oreo (8.0+) devices
- Added Language Switcher feature
- Improved translations
- Fixed a bug in the Settings screen on some devices
v3.7 - 2020-05-04
- SuperPower: updated Privacy and Secutity Policy
- su: all apps and processes that call the su binary are now forced to run in their own mount namespace (on failure, fallback to private mount namespace!)
- su: removed --id/--mount-master/--mount-namespace (Google Play Policy compliance!)
- SuperPower: removed option to disable mount namespace (Google Play Policy compliance!)
2020-04-27 - v3.6
- Fixed a crash in the "Information" tab
2020-04-16 - v3.4
- Initial public release
reserved!
After 14 days of release, Yesterday - 2020-04-29 - I received an email from Google Play stating that SuperPower v3.6 has been removed from Play Store due to a policy violation! Keep reading to understand the situation!
In v3.6, all the apps and processes that call the SuperPower's su binary run in private mount namespace by default, with an option/parameter to run in the master mount namespace (--mount-master), and another one to run in different mount namespaces (--mount-namespace).
However, allowing apps and processes that call the su binary to execute in mount namespaces other than their own mount namespace should be considered a security vulnerability, not a feature, as it disables an important Android security feature. Therefore, the --mount-master/--mount-namespace options are now out of the SuperPower's su binary's command-line.
From v3.7 onwards, all the apps and processes that invoke SuperPower's su binary - including SuperPower - will execute in their own mount namespace (on failure, the su binary fallback to running in private mount namespace).
Root app developers should be aware that this is the default behavior on Android 4.2.2, where su binary runs in non-daemon mode.
Thus, all of these changes make SuperPower the most secure Root Access Manager app available into the world.
Wanderson Kalil, author of SuperPower - Root Access Manager.
RESERVED!
reserved
Thanks for the work!
Will you share the app here? Still not available at play store.
Running in ghost mode is similar to Magisk hide?
And how is the installation procedure for people with/without Magisk installed.
Regards,
Enviado de meu HD1903 usando o Tapatalk
lucfig said:
Thanks for the work!
Will you share the app here? Still not available at play store.
Running in ghost mode is similar to Magisk hide?
And how is the installation procedure for people with/without Magisk installed.
Regards,
Enviado de meu HD1903 usando o Tapatalk
Click to expand...
Click to collapse
The entire Magisk's system is kept on your device, only the Magisk's su binary is replaced (this is only when you updates the su binary through the SuperPower's su binary Updater!).
Enviado de meu SM-J120H usando o Tapatalk
Greetings & thanks for sharing your work. A few questions...
I am on Android 10 currently rooted with Magisk. I have downloaded the app from Play as well as updater apk (there are 2, what's the difference?)
I open updater & there's no option to update binaries. Any suggestions on what to try & which updater apk is correct for OP8 rooted with Magisk?
I understood that SU binaries would be updated from the app, does the tarp zip need to be flashed?
It would be great to have a Magisk Module for this.
Thanks in advance
are you still updating this? does it play well with a11 or 12?
SuperPower v5.6:
The 2 main reason for this version of SuperPower are:
1: I lost SuperPower's keystore (file needed to publish apps on Play Store)!
2: Android 11 have code execution restrictions that prevents SuperPower's prompt/notifications/logging from working!
3: Added su binary Updater feature to SuperPower.apk, you can now replace MAGISKSU BY SuperPower's su binary!
Important note: Android 12 fully break SuperPower su's binary from working:
Setting LD_LIBRARY_PATH from su binary is no longer possible/allowed by Android 12, meaning it's not possible to do a login shell (call /system/bin/sh) from SuperPower's su binary. There is no fix for that, and we can't bypass that system protection/restriction.
Update: the above restriction is already fixed: since we cannot call setenv("LD_LIBRARY_PATH", "/system/lib", 1) from su binary on Android 12, the solution is to inherit the environment of the caller process for a new process image and call execve().
Update 2: we need to set /system/lib64 first instead of /system/lib so the linker link the binaries through the correct libc.so.
Note 2: DON'T DELETE THIS POST: I'm the author of SuperPower - Root Access Manager!!!