Related
NanoDroid
NanoDroid is a installer for various OpenSource related things, most noticably microG and F-Droid. It supports direct /system installation, both devices with or without A/B partition scheme, aswell as Magisk Mode (module) installation. It also includes several tools (eg. GNU Bash, shell utilities, more), scripts, fonts, sounds and additional features (system debloating, init scripts, automatic logcat creation), aswell as a companion F-Droid Repository.
Furthermore it allows the user to do fine-graded installations using configuration files, which allow to choose what to install, or if several alternatives are available, which of them, see "Alter Installation" in the full documentation (link at the end of this post).
In order for full microG experience NanoDroid contains a modified Play Store which allows (in-)app-purchases with microG, which would normally not be possible. It also tries to remove all previously installed GApps on it's own. For ROMs without builtin signature spoofing support NanoDroid includes an on-device Patcher which tries to patch your ROM from TWRP.
Versions until 15.1 were called NanoMod, starting with 16.0 they're called NanoDroid.
NanoDroid does now have a companion F-Droid Repository for easy updates of Play Store (patched with (in-)app-purchase support) and MPV builds Repository Info-Page
Current Release
Stable: 23.1.1.20210117 "BusyCompat"
Beta: --- (---)
Nanolx: latest stable and beta releases
Snapshot: read the documentation in the git repository on how to create a snapshot build
Supported Android Versions
NanoDroid officially supports the following Android versions:
4.4 / SDK 19 (KitKat)
System Mode only (Magisk does not support KitKat)
5.0 / SDK 21 (Lollipop)
5.1 / SDK 22 (Lollipop)
6.0 / SDK 23 (Marshmallow)
7.0 / SDK 24 (Nougat)
7.1 / SDK 25 (Nougat)
8.0 / SDK 26 (Oreo)
8.1 / SDK 27 (Oreo)
9.0 / SDK 28 (Pie)
Patchers works, if you've previously manually deodexed services.jar
Deodex Instructions
10.0 / SDK 29
Patchers works, if you've previously manually deodexed services.jar
Deodex Instructions
11.0 / SDK 30 (R)
Patcher does not work from TWRP
Patcher works from Magisk if your ROM's services.jar already contains classes.dex
Deodex Instructions
earlier versions will never officially be supported (you may still report bugs, though).
Future versions will be officially supported, eventually.
Summary
NanoDroid can be installed as a Magisk Module or directly to /system, though a bit functionality is only available with Magisk. It must be installed from TWRP!
NanoDroid includes
microG and it's companions
on-device framework-patcher for microG support (signature spoofing)
F-Droid and it's privileged extension
modified Play Store to allow (in-)app-purchases with Magisk
alternatively Aurora Store can be installed instead
custom init scripts
pseudo-debloat feature
disables applications systemless-ly
pre-configured default settings
several Open Source applications
include replacements for the pseudo-debloated applications
full list of included applications
Packages
Magisk Modules
Module packages, flashing through TWRP recommended, flashing through Magisk Manager possible starting with version 22.6.91 (22.7-beta2).
NanoDroid: includes
everything mentioned in the Summary
NanoDroid-microG: includes
microG and it's companions
GNU Bash
pseudo-debloat feature
app stores
NanoDroid-fdroid: includes
F-Droid and it's privileged extension
NanoDroid-BromiteWebView: includes
Bromite WebView
NanoDroid-OsmAnd: includes
OpenStreetMap for Android (OsmAnd+)
Extras
Extra packages, flashing through TWRP recommended, flashing through Magisk Manager possible starting with version 22.6.91 (22.7-beta2).
NanoDroid-pacher: includes
on-device framework-patcher (signature spoofing support)
NanoDroid-systest: includes
System Test script which generates a log to aid issue reporting
NanoDroid-uninstaller: includes
uninstalls all NanoMod/NanoDroid Magisk Modules
uninstalls NanoMod/NanoDroid installed in System Mode
uninstalls NanoMod/NanoDroid-Patcher addon.d environment
The GitLab repository contains the full documentation with infos about
more detailed info what's included
detailed installation instructions
setup instructions for microG
list of known Issues (and fixes/workarounds)
more
>> Full Documentation
ChangeLog
https://gitlab.com/Nanolx/NanoDroid/blob/master/ChangeLog.md
List of known issues (and fixes)
https://gitlab.com/Nanolx/NanoDroid#issues
Can we pass safetynet with xposed. with microg?
purval6300 said:
Can we pass safetynet with xposed. with microg?
Click to expand...
Click to collapse
No difference between GApps and microG.
In the github repository you'll find the following changes for upcoming 5.1 (no ETA)
updated Magisk to beta.13.170405 (which fixes the issues I had with 12.0 on Moto X Play and Galaxy S6)
improved nanomod-overlay script
the script does now have better output for -l/--list parameter (which lists all pseudo-debloated system apps)
the script does now have -s/--show parameter which shows all non-pseudo-debloated system apps with both apkname and label (label = the name that shows up in launcher)
there's no 'column' command on android, so the output is not pretty aligned, but well
Screenshots attached.
Suggestion
Add this for microG set up
Disable Battery Optimization, if you use Android 6 (Marshmallow) or above. Ensure that it is disabled for microG Services Core in System Settings > Battery > Menu > Battery optimization. Note that this is the case for the original Play Services, as it is required to keep a stable background connection.
atendedor_de_boludos said:
Suggestion
Add this for microG set up
Disable Battery Optimization, if you use Android 6 (Marshmallow) or above. Ensure that it is disabled for microG Services Core in System Settings > Battery > Menu > Battery optimization. Note that this is the case for the original Play Services, as it is required to keep a stable background connection.
Click to expand...
Click to collapse
I mentioned to ensure everything is set in 'Self Check', but I consider will re-word that paragraph to be more clear.
Hi. I got "updater process ended with signal 4" when tried to flash this.
Using galaxy s3, with RR 5.8.2.
djedjy said:
Hi. I got "updater process ended with signal 4" when tried to flash this.
Using galaxy s3, with RR 5.8.2.
Click to expand...
Click to collapse
After flashing in TWRP connect your phone to pc and use adb to grab a log from recovery
Code:
adb pull /tmp/recovery.log
Then post recovery.log (rename to recovery.txt) file here.
Will this work on my Galaxy S7 using stock ROM? I'm interested in installing microG to satify apps dependant on Google Play Services, but I couldn't get it because it needs signature spoofing, and the mods it recommended needed a deodexed ROM, which mine is not.
CyanogenLover said:
Will this work on my Galaxy S7 using stock ROM? I'm interested in installing microG to satify apps dependant on Google Play Services, but I couldn't get it because it needs signature spoofing, and the mods it recommended needed a deodexed ROM, which mine is not.
Click to expand...
Click to collapse
If your ROM is not deodexed you can't patch services.jar, so microG won't work. Anything else in the package would work, though.
Setialpha said:
If your ROM is not deodexed you can't patch services.jar, so microG won't work.
Click to expand...
Click to collapse
Is there a way to deodex the stock ROM without bricking my S7? It sounds complicated, and I'm sure it is, but there must be a way! :fingers-crossed:
Setialpha said:
After flashing in TWRP connect your phone to pc and use adb to grab a log from recovery
Code:
adb pull /tmp/recovery.log
Then post recovery.log (rename to recovery.txt) file here.
Click to expand...
Click to collapse
Here:
Code:
I:operation_start: 'Flashing'
Installing zip file '/sdcard/NanoMod-5.0.20170405.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
<>> <<>
<>> <<>< NanoMod 5.0.20170405 >
< NanoMod 5.0.20170405 > <<> <>>
<<> <>>Updater process ended with signal: 4
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/sdcard/NanoMod-5.0.20170405.zip'
Updating partition details...
I:Data backup size is 71MB, free: 4441MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
Truncating string cache entries.
I:Set page: 'filemanageroptions'
I:Set page: 'choosedestinationfolder'
I:Set page: 'filemanagerconfirm'
I:Set page: 'filemanageraction'
I:operation_start: 'Command'
I:Running command: 'cp "/tmp/recovery.log" "/sdcard"'
djedjy said:
...
Click to expand...
Click to collapse
You either have MD5/signature check for zip files active in TWRP, then disable it, or your TWRP is buggy,. Because it fails early, ar that stage the updater-script sets the progrssbar to 10% and mounts partitions.
Do you have the latest TWRP installed for your device?
FYI on AFH you can now find a microG only Magisk Module, too. framework-patcher.sh in github repo was updated to support both modules. You can also use 'mod.sh microg' to create the microG only zip from git repo.
Link: https://www.androidfilehost.com/?a=show&w=files&flid=150729
The microG only module does support
Code:
nanomod.reinstall
nanomod.play
configuration parameters, like the full package.
version 5.1.20170408 released
Version 5.1.20170408 released, with the following changes since 5.0.20170405:
Code:
5.1.20170408:
- Internal Changes
* only copy DroidGuard.apk to /sdcard if
'nanomod.microg' is '1' in 'nanomod-setup'
configuration file
* add new option 'nanomod.zelda' to 'nanomod-setup'
configuration file, allows to control whether to
install or not install Zelda ringtones and sounds
* 'nanomod.play=0' now actually works and does not
install any app store
- Variants
* full package: microG, F-Droid & apps, pseudo-debloat
feature, Zelda ringtones & sounds, GNU Bash, GNU Nano,
aapt utility
* microG package: microG only
* framework-patcher.sh updated to support both modules
- Removed files / features
* Effect_Tick Zelda sound
- I admit, that one was too annoying
* Magisk installation
* unsu Script
- Read: NanoMod is now only the Module, no longer
includes Magisk itself
- nanomod-overlay Script Changes
* parameter '-l', respectively '--list' now has
properly formatted output
* parameter '-r', respectively '--remove' now
only removed exact matches from config file
* parameter '-a', respectively '--add' now
properly formats config file
* new parameter '-s', respectively '--show' which
shows all non pseudo-debloated system applications
* new paramter '-d', respectively '--delete' which
will remove all overrides and thus re-enable all
applications, unlike '-r' / '--remove' this will
not change the config file, so you can re-debloat
using '-u' / '--update' again
- Updates
* Play Store (7.7.09.O)
* VLC (2.1.4~beta)
* GNU Nano (2.7.5)
* Substratum (631)
- Added applications
* F-Droid Privileged Extension (0.2.2)
- allows installation of apps using F-Droid
without enabling 'Unknown Sources' in the
security settings of your device
I also changed a few things in the README/first post here (for example paragraph "Installation" with download links is now almost at top, instead of bottom). Magisk is no longer installed, so this is now really a Magisk Module on it's own.
This work is exactly what the community needs to help move novices like me into an open-source-ONLY ecosystem. Thank you!!!
Setialpha said:
FYI on AFH you can now find a microG only Magisk Module, too. framework-patcher.sh in github repo was updated to support both modules. You can also use 'mod.sh microg' to create the microG only zip from git repo.
Link: https://www.androidfilehost.com/?a=show&w=files&flid=150729
The microG only module does support
Code:
nanomod.reinstall
nanomod.play
configuration parameters, like the full package.
Click to expand...
Click to collapse
I installed this version, but I cannot get Phonesky (play store) to have the correct signature. System is spoofing signature correctly, but somehow play store doesn't. Every tick in self check section is there, except the "Play Store (Phonesky) has correct signature" tick. The play store works fine signing in and downloading. However apps like gmail do not work. Maybe it needs to be put in priv-app?
Running Crdroid 7.1.1 (supports spoofing signature) oneplus one, latest nanomod package 0408, magisk v12
f41lbl0g said:
FYI on AFH you can now find a microG only Magisk Module, too. framework-patcher.sh in github repo was updated to support both modules. You can also use 'mod.sh microg' to create the microG only zip from git repo.
Link: https://www.androidfilehost.com/?a=show&w=files&flid=150729
The microG only module does support
I installed this version, but I cannot get Phonesky (play store) to have the correct signature. System is spoofing signature correctly, but somehow play store doesn't. Every tick in self check section is there, except the "Play Store (Phonesky) has correct signature" tick. The play store works fine signing in and downloading. However apps like gmail do not work. Maybe it needs to be put in priv-app?
Running Crdroid 7.1.1 (supports spoofing signature) oneplus one, latest nanomod package 0408, magisk v12
Click to expand...
Click to collapse
Phonesky ie play store works normally as a user app. I am using it that way (I am on normal gapps) and I have no problems.
- MultiFunctionsPlus Is The Successor Of MultiFunctions
- The Main Difference: The Pre-Activated Functions = Flashing MultiFunctionsPlus + Activator = Flashing MultiFunctions Only Or Deactivating The Pre-Activated Functions = Flashing MultiFunctionsPlus Only = Flashing MultiFunctions + Deactivator
Click to expand...
Click to collapse
MultiFunctionsPlusPage 1 Of 2Introduction:
A Module To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running, Changing DoubleTap2Wake(DT2W) Status, Fixing PlayStore Device Certification Status - Passing SafetyNet, Enabling The Low Ram Configurations, Disabling The Other Magisk Modules, Disabling The Magisk General Scripts & More].
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList) In Below
- P.S. All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Below
- P.S. All Functions Can Be Used With Any-Rooting-Tool Except The Ones For Magisk Users Only As Described In Below
Current Version: MultiFunctionsPlus v1.0.3.4.2.4B7 - Activator v1.0.0.17A4.0.0 - QuickFix4Busybox v0.0.0.0.0.3
Recommendations:
- For Magisk Users Only, Disabling MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager & Rebooting The Device Are Required To Load The Modules
- For Activating Any Function Using Any Root File Explorer Such MiXplorer To Access The Part Of Data Thru Root, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive And Then Reboot The Device
- P.S. In-Case Of Moving/Deleting The File Of Disable In Error, Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- Activator Is A Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator) So Actually There Is No Needing To Flash It To Use Any Function Such SELinuxModeInverter
- After Flashing The Module Of Activator & Rebooting The Device, It Will Do Its Functionality & Remove Itself
- P.S. For Any Magisk Version Below v14.0(1400), Use Any Method To Flash The Module As Described In Below Except Magisk Manager
- P.S. For Some Versions Of Magisk, Use QuickFix4Busybox As A Resolver For The Issue Of Internal Magisk Busybox Which Prevents Some Of Commands From Executing
Created: Nov.30.2019
Updated: Feb.22.2020
Download Link: Click Here (To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The Description)
** Magisk Installer: It Supports Magisk Only
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To v20.1(20100)
- For The Module Which Is Ended Its Name With v19000P (Or MMTEx1.x), It Supports Magisk v19.0(19000) To The Latest Version
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
- For The Module Which Is Ended Its Name With Unity1.5.x, It Supports Magisk v15.3(1530) To The Latest Version
- For The Module Which Is Ended Its Name With Unity1.5.4Ax, It Supports Magisk v8(800) To The Latest Version
- For The Module Which Is Ended Its Name With Unity4.x, It Supports Magisk v18.0(18000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity5.x, It Supports Magisk v19.0(19000) To The Latest Version
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
The Description: (1)
1- DalvikCache Cleaner (Advanced Dalvik/ART Cache Cleaner)
- Clearing The Dalvik Cache
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Maybe It Takes About 5 Min. To Finish The Process
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of DalvikCacheCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DalvikCacheCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
2- PlayStoreWithServicesData Cleaner (Advanced PS-GMS Data Cleaner)
- Clearing The Data Of Google Play Store & Google Play Services
- One Of The Methods To Resolve/Fix The Battery Draining & Re-Check PlayStore Device Certification Status
- After Doing Its Functionality, Check PlayStore Device Certification Status (Google PlayStore --> Settings --> Play Protect/Device Certification) Which Should Be Hidden For A While During Getting Its Status From Google
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of PlayStoreWithServicesDataCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/PlayStoreWithServicesDataCleaner/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
3- MagiskHideList Cleaner (Including MagiskHide Enabler & MagiskHideList Backup) [For Magisk Users Only]
- Clearing MagiskHideList [All Added Apps/Activities/Processes In MagiskHideList]
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To MagiskHide, Use The Function To Clear All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality, Taking A Backup Of HideList & Disabling Itself
- For Activating The Functionality Of MagiskHideListCleaner, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Inactive And Then Reboot The Device
- Additional Feature (Deactivating The Main Function + Activating The Sub-Function Of BackUp [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Inactive And Then Reboot The Device] = Taking A Backup Of HideList)
- Additional Feature (Deactivating The Main Function + Putting A Copy Of The File Of HideList.txt Into The Folder Of Retrieving [Copy The File Of HideList.txt From /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/HideList.txt To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/BackUp/Retrieving And Then Reboot The Device] = Retrieving/Restoring The Last Saved MagiskHideList)
- Additional Feature (Activating The Sub-Function Of HideEnabler [Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskHideListCleaner/Hide/Inactive And Then Reboot The Device] = Enabling MagiskHide Once At Every Booting)
Click to expand...
Click to collapse
4- SELinuxMode Inverter (Advanced SELinux Mode Changer/Manager)
- Inverting The Default Android SELinuxMode During Startup ([From Permissive To Enforcing] Or [From Enforcing To Permissive])
- The Function Changes The SELinuxMode For The Entirety Of The Device's Uptime Until Next Reboot
- The Default Android SELinuxMode Can Be Either Enforcing Mode Or Permissive Mode Which Depends On The Installed/Flashed Rom/Kernel
- SELinux Enabled Kernel/SELinux Development Mode Is A Main Point To Use The Function (The Installed/Flashed Rom/Kernel Must Have The Ability To Switch Between Enforcing Mode & Permissive Mode)
- Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SELinuxModeInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinuxMode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinuxMode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter/Wait/Active And Then Reboot The Device
=============================
The General Steps- SELinux Enabled Kernel/SELinux Development Mode Is Required Which Means The Installed/Flashed Rom/Kernel Has The Ability To Switch Between Enforcing Mode & Permissive Mode
- To Check The Above Mentioned Ability, Install Terminal Emulator From PlayStore --> Open It -->
-----> For Getting The Current Android SELinuxMode, Write su --> Click On Enter --> Write getenforce (Most Devices) Or sestatus (Some Devices) --> Click On Enter
-----> For Setting The Current Android SELinuxMode, Write su --> Click On Enter --> Write setenforce 0 (For Permissive Mode) Or setenforce 1 (For Enforcing Mode) --> Click On Enter
-----> Check Again The Current Android SELinuxMode
-----> If The Mentioned Steps Worked/Succeeded, Activate The Function Of SELinuxModeInverter
-----> Enforcing Mode Is Preferable For Security (Specially Banking Apps) & Permissive Mode Is Preferable For Mods (Specially Audio Mods)
-----> If The Mentioned Steps Didn't Work/Succeed, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Enforcing Mode & Permissive Mode So Flash Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode
- P.S. Maybe The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Can Use Only The Wait Mode (Not The Fast Mode)
Click to expand...
Click to collapse
5- SafeMode Enabler
- Booting The Android Into SafeMode
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Use The Function To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- The Function Disables All Installed Apps (User Apps) & Also The Root Access By Enabling SafeMode & After Booting, Remove The Data/Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Data/Uninstall) Then Reboot
- SafeMode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of SafeModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SafeModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
6- MagiskCoreOnlyMode Enabler [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- The Function Disables All Magisk Modules By Enabling MagiskCoreOnlyMode & After Booting, You Can Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot
- CoreOnlyMode Gives The Device The Ability To Get Into The Android Directly With User Interface Which Means The User Can Use The Device With All Features/Functionalities Except Magisk Modules Even Before Removing The Module(s) Which Caused The Bootloop/Issue
- Enabling CoreOnlyMode Keeps MagiskSU, MagiskHide & Systemless Hosts Activated, But No Modules Are Loaded/Enabled
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskCoreOnlyModeEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskCoreOnlyModeEnabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
7- Swap Controller (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- The Function Is Divided Into 2 Sub-Functions [SwapEnabler & SwapDisabler] For Improving Responsiveness/Performance
- SwapEnabler Re-Calculates Swap Space & Sets The New Size But SwapDisabler Sets Swap (Total) Size To Be 0 [It Can Be Checked Using DiskInfo From PlayStore]
- The Default Swappiness Value Is 35 For SwapEnabler & 0 For SwapDisabler
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of SwapEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Enabler/Inactive And Then Reboot The Device
- For Activating The Functionality Of SwapDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwapController/Disabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
8- Swappiness Changer (RAM Management)
- Swap Is A Part Of Android RAM Management Which Depends On 2 Important Factors Which Are Swap Space & Swappiness Value
- Swap Is A Virtual Memory Which Allows Physical Memory RAM To Be Extended Using A Portion Of Internal Storage Where Android Moves Inactive Processes/Apps Into Virtual Memory To Make Space For New/Active Ones
- There Are 3 Levels Of Swappiness Value [Low For 10, Mid For 30 & High For 60] For Improving Responsiveness/Performance [It Can Be Checked Using DiskInfo From PlayStore]
- The Function Disables Also KSM/UKSM For Reducing The Battery Drain & Lowering The CPU Usage
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of Low Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Low/Inactive And Then Reboot The Device
- For Activating The Functionality Of Mid Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/Mid/Inactive And Then Reboot The Device
- For Activating The Functionality Of High Swappiness, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/SwappinessChanger/High/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
9- MagiskDaemonHide Keeper (MagiskDaemon-MagiskHide Running Keeper) [For Magisk Users Only]
- The Function Is Divided Into 2 Sub-Functions [HideKeeper & DaemonKeeper] For Keeping Both Of MagiskDaemon & MagiskHide Running (Which Is Recommended To Be Used If Only Needed)
- HideKeeper Aims To Resolve The Issue Of Intermittent Work Of MagiskHide By Re-Enabling MagiskHide Every A Certain Time
- DaemonKeeper Aims To Resolve The Issue Of Losing Root Access Randomly (Or Magisk Is Not Installed) By Re-Starting MagiskDaemon Every A Certain Time
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of HideKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Enabling MagiskHide Every 36 Min. & The Fast Mode Can Be Used Re-Enabling MagiskHide Every 18 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Hide/Wait/Active And Then Reboot The Device
- For Activating The Functionality Of DaemonKeeper, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Inactive And Then Reboot The Device
-----> Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Re-Starting MagiskDaemon Every 10 Min. & The Fast Mode Can Be Used Re-Starting MagiskDaemon Every 5 Min.]
-----> For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDaemonHideKeeper/Daemon/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
10- DT2WStatus Inverter (DoubleTap2Wake Enabler/Disabler)
- Inverting The Default DT2W Status During Startup ([From Disabled To Enabled] Or [From Enabled To Disabled])
- The Function Changes The DT2W Status For The Entirety Of The Device's Uptime Until Next Reboot
- The Default DT2W Status Can Be Either Enabled Or Disabled Which Depends On The Installed/Flashed Rom/Kernel
- The Installed/Flashed Rom/Kernel Must Support The Feature Of DT2W (DoubleTap2Wake)
- Activating The Function = Inverting The Default DT2W Status
- For Activating The Functionality Of DT2WStatusInverter, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/DT2WStatusInverter/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
11- MagiskDeviceSpoofingTool Enabler (Device Emulator For Device Certification & SafetyNet) [For Magisk Users Only]
- Fixing PlayStore Device Certification Status & Passing SafetyNet
- The Function Changes Some Properties Of Build.Prop For The Entirety Of The Device's Uptime Until Next Reboot
- The Function Changes The Device Fingerprint To Another Certified One (Currently Pixel 2 XL)
- MagiskHide Must Be Working Properly Which Is A Main Point To Pass SafetyNet
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of MagiskDeviceSpoofingToolEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskDeviceSpoofingToolEnabler/Wait/Active And Then Reboot The Device
- P.S. The Device's Fingerprint Can Be Checked Using Device Info HW From PlayStore - SafetyNet Can Be Checked Using Either Magisk Manager Itself Or SafetyNet Helper Sample From PlayStore - Root Detection Can Be Checked Using RootBeer Sample From PlayStore
- P.S. Maybe Activating Both Functions Of PlayStoreWithServicesDataCleaner & DalvikCacheCleaner Are Required
- P.S. The Most Famous Reasons Of Root Detection Are Magisk Itself, Installed Rom/Kernel, Loaded Prop, Installed App, File/Folder In The Internal/External Storage & External Connection Thru Internet
Click to expand...
Click to collapse
12- LowRamConfig Enabler (RAM Management)
- Enabling The Low Ram Configurations For Low Ram Device
- The Function Changes The Low Ram Configurations For The Entirety Of The Device's Uptime Until Next Reboot
- Activating The Function = Doing Its Functionality
- For Activating The Functionality Of LowRamConfigEnabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Inactive And Then Reboot The Device
- Some Issues Which Are Related To Rooting-Tool/Rom/Kernel Itself Can Be Resolved Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Blackscreen & The Fast Mode Can Be Used For Resolving The Issue Of Non-Persistent After Rebooting]
- For Activating The Fast Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/LowRamConfigEnabler/Wait/Active And Then Reboot The Device
Click to expand...
Click to collapse
13- MagiskModules Disabler [For Magisk Users Only]
- Disabling The Other Magisk Modules
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, Use The Function To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskModulesDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskModulesDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
14- MagiskGeneralScripts Disabler [For Magisk Users Only]
- Disabling All Magisk General Scripts Of /data/adb/service.d & /data/adb/post-fs-data.d
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module Or Placing A Script, Use The Function To Remove That Script Manually
- Activating The Function = Doing Its Functionality & Disabling Itself
- For Activating The Functionality Of MagiskGeneralScriptsDisabler, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/MagiskGeneralScriptsDisabler/Inactive And Then Reboot The Device
Click to expand...
Click to collapse
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Active And Then Reboot The Device
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Re-Flash The Module
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
MultiFunctionsPlusPage 2 Of 2
Changelog:
v1.0.3.4.2.4B7: Improving The Code & Updating The Function Of [MagiskDeviceSpoofingTool Enabler] To Emulate "Pixel2XL"
v1.0.3.4.2.4B6: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v8(800) To The Latest Version
v1.0.3.4.2.4B4: Fixing Minors, Improving The Code & Supporting All Magisk Versions From Magisk v13.1(1310) To The Latest Version
v1.0.3.4.2.4B0/2: Improving The Code & Updating To Magisk v20.x
v1.0.3.4.2.4/4A1: Fixing Minors & Improving The Code
v1.0.3.4.2.3L: Improving The Code
v1.0.3.4.2.3F: Improving The Code, Adding The Function Of [MagiskModules Disabler] For Disabling The Other Magisk Modules & The Function Of [MagiskGeneralScripts Disabler] For Disabling The Magisk General Scripts
v1.0.3.4.2.3A/B: Improving The Code, Adding The Function Of [MagiskDeviceSpoofingTool Enabler] For Passing The SafetyNet & The Function Of [LowRamConfig Enabler] For Enabling The Low Ram Configurations
v1.0.3.4.2.2: Initial Release
Click to expand...
Click to collapse
The Description: (2)
*** Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations:
- Re-Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Move The Folder Of MultiFunctionsPlus From The Folder Of 4U [/data/DreamerMods/4U/MFP] To The Folder Of DreamerMods (/data/DreamerMods) Then Reboot
Click to expand...
Click to collapse
*** Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules, Scripts & HideList): Activating Some Functions Of MultiFunctionsPlus For Once To Resolve Some Issues (P.S. MultiFunctionsPlus Is Required To Be Flashed Before Using Activator)
- Flash The Module Of MultiFunctionsPlus (Don't Reboot) & Flash The Module Of Activator (Reboot Now) For Activating Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler, MagiskCoreOnlyMode Enabler, MagiskModules Disabler & MagiskGeneralScripts Disabler] For Once To Resolve Some Issues
- Booting The Android Into SafeMode For Giving The Ability To Remove Any App/Its Data Manually Which Maybe Caused The Bootloop/Issue (Rebooting The Device Manually Is Required To Get Back To The NormalMode)
- Clearing DalvikCache For Removing All Remnants Of The Uninstalled Apps & Resolving/Fixing Some Issues With The Installed Apps
- Clearing All Apps/Activities/Processes From MagiskHideList Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling The Other Magisk Modules Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Disabling All Magisk General Scripts Which Maybe Caused The Bootloop/Issue [For Magisk Users Only]
- Opening Magisk In CoreOnlyMode To Deactivate All Modules For Giving The Ability To Remove Any Module Manually Which Maybe Caused The Bootloop/Issue (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules) [For Magisk Users Only]
- Flashing/Re-Flashing The Module Of Activator Will Activate The Above Mentioned Functions (Even-If Magisk Is In Core Only Mode For Magisk Users)
Click to expand...
Click to collapse
*** Execution Mode: The Execution Mode Of Script/Module
- There Are 2 Modes [Execution In Normal Mode & Execution In Background Mode]
- Execution In Normal Mode: Executing The Script/Module Based On The Priorities Of Rooting-Tool/Rom/Kernel Itself Is Maybe A Proper Mode For Some Cases
- Execution In Background Mode (The Default One): Resolving The Issue Of Blocking The Other Scripts/Modules From Starting Early Due To The Execution Time Of Code Is Long & Also Related To Rooting-Tool/Rom/Kernel Itself (Such Losing The Functionality Of Xposed After Installing The Module Or Activating Any Function)
- For Activating Execution In Normal Mode, Copy The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
- For Activating Mode Of Execution In Background Mode, Delete The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/Status/Background/Active And Then Reboot The Device
Click to expand...
Click to collapse
*** FAQ/Notes:
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring Apps, Modules, Scripts Or HideList, Check Activator (+Bootloop/Bootscreen/Blackscreen Resolver For Apps, Modules & HideList) In Above
- After Flashing The Module Of Activator, MagiskHideList Will Be Cleared And For Retrieving/Restoring The Last MagiskHideList, Check The Function Of MagiskHideList Cleaner In Above
- All Functions Are Deactivated/Disabled By Default And The Needing To Activate Each Wanted Function Is Described In Above
- In Case Of Deleting The Folder Of Any Unwanted Function Such SELinuxModeInverter (/data/DreamerMods/MultiFunctionsPlus/SELinuxModeInverter) & Rebooting The Device, The Code Will Not Check The Unwanted Function Which Is Equivalent To The Permanent Deactivation/Removal Of The Unwanted Function So The Same Step Can Be Done With Any Unwanted Function (P.S. For Retrieving/Restoring The Unwanted Function, Deleting The Folder Of Status & Rebooting The Device Are Required)
- P.S. Deleting The Folder Of Status (/data/DreamerMods/MultiFunctionsPlus/Status) & Rebooting The Device Will Create The File Of Disable Again
- For Activating Any Function, Copying The File Of Disable From /data/DreamerMods/MultiFunctionsPlus/disable To /data/DreamerMods/MultiFunctionsPlus/<TheFunction>/Inactive (P.S. Negating The Negation Is A Form Of Affirmation) & Rebooting The Device Are Required
- Disable MagiskCoreOnlyMode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate Any Function (Disabling MagiskCoreOnlyMode & Rebooting The Device Are Required To Load The Modules)
- For Re-Flashing The Module Of MultiFunctionsPlus With Keeping The Same Configurations, Check The Details In Above
Click to expand...
Click to collapse
*** In-Case Of Failure: After Doing Successfully The Above Mentioned Steps
- During The Installation Process, Take The Screenshot After Flashing The Module & Send It
- Send These Logs (/data/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlus.log, /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusData.log & /data/DreamerMods/MultiFunctionsPlus/Log/MultiFunctionsPlusOld.log)
- Complete Info About The Device, The Used Rom, The Used Kernel & The Used Rooting-Tool
- Send The Folder Of DreamerMods (/data/DreamerMods)
- Send The Screenshots Of (Magisk Manager --> Main Screen, Magisk Manager --> Modules, Magisk Manager --> SuperUser & Magisk Manager --> Log --> SuperUser) [For Magisk Users Only]
- Send Magisk Log (Magisk Manager --> Log --> Magisk) [For Magisk Users Only]
- Send The Screenshot Of SuperUser Of The Used Rooting-Tool [For Non-Magisk Users]
- Send Full Logcat (Using Logcat Extreme From PlayStore)
Click to expand...
Click to collapse
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #0
Reserved For News/Updates #1
Reserved For News/Updates #2
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Could I Ask You To Send The Screenshots Of The Following?
-Settings --> Apps --> Instagram --> Storage
-Settings --> Apps --> WhatsApp --> Storage
-Settings --> Apps --> Messenger --> Storage
-Settings --> Apps --> SoundCloud --> Storage
u81 said:
Waiting for upload, don't see them yet.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Check This Post https://forum.xda-developers.com/ap...al-media-cache-advanced-t3799155/post76705484.
Don't have sound cloud
{
"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"
}
YouTube attached as well
Sent from my SM-N910F using Tapatalk
YouTube screenshot
Sent from my SM-N910F using Tapatalk
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
u81 said:
I'm only updated to Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify a few hours ago so the current storage usage is possibly much smaller than normal. (Data not wiped)
It should be up to normal size by tomorrow, I'd say.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Kindly Send Also A Screenshot Of Your Internal Storage (Unhide Option Should Be Selected)
Is this what you're looking for?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
u81 said:
Is this what you're looking for?View attachment 4517147
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Click to expand...
Click to collapse
No, From Your File Browser.
Is this what you're looking for?
If not, please share your screenshot and I'll find how to get that screenshot from my phone
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
Deleted
Will these do?
Sent using Tapatalk
Samsung Note4 - SM-910F - Alexander's DevBase5.8 + RamKernel RC7 + Magisk v15.3 + Greenify
Motorola G5S+ - Stock
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
abacate123 said:
I was thinking about one thing related to your modules. They're useful, but it'll be kinda messy sometime, since you're creating a lot of different modules, separately.
Since all of them have similar purposes (clear caches from something), how about you merge all of them into a single module, with an interactive terminal interface? I guess it'd be a great update, and not only easier to you to maintain and organize all of those modules, but easier to others to find them and use. Just a quick thought.
Click to expand...
Click to collapse
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Dreamer(3MF) said:
Currently There Are 8 Modules [WiFi Connection State On Status Bar - App Shortcut & Widget In Notification Area - SELinux Mode Inverter (Advanced SELinux Mode Changer) - Microsoft Intune Company Portal Hider - Tez Hider - Clear Dalvik Cache (Advanced Dalvik/ART Cache Cleaner) - Clear Google PlayStore With Services Data (Advanced PS-GMS Data Cleaner) - Clear Social Media Cache (Advanced Social Media Apps Cache Cleaner)] So What Do You Think?
Click to expand...
Click to collapse
Nice, but I was talking specifically about these cache related modules, not the others, I forgot to mention that. Merging them into a single module seems to be a nice idea. But well, just a thought as I said.
!!! Update lineage-16.0-20190910-UNOFFICIAL-clover.zip
https://androidfilehost.com/?fid=1899786940962581845
---------------------------------------
Download ROM https://androidfilehost.com/?fid=11410963190603907427
Supported-
DT2W
DT2C ( on Status bar)
exFAT
USB Preferences options (File transfe, usb tethering, MIDI,PTP,No data transfer)
Xiaomi performance setting option
!!!! Important
Unlocked Bootloader
Backup persist partition
(There are some project that changes your WIFI MAC Address. if it happened you will lost it forever.)
It shows wifi but after entering pwd it shows only saved. Can't connect at all.
Download TWRP--- https://mega.nz/#!qcA2BQIJ!xiBnnC0B4Z7fqpARbIY2ARdDY4hJLZgsriJsWaCCzNQ
-Boot TWRP
-connect your PC with USB
-your computer -Open CMD
cmd>adb shell
cmd>cd /dev/block/platform/soc/c0c4000.sdhci/by-name/
cmd>ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name/
cmd>dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/persist of=/sdcard/persist.img
(keep your persist.img in the safe place)
--------------------------
How to restore it if you have a problem.
(load your persist.img into sdcard.)
cmd>dd if=/sdcard/persist.img of=/dev/block/mmcblk0p48
------------------------------------------------------------
Step for Normal user
Flash Lastest Firmware (option)
https://github.com/XiaomiFirmwareUp...jKlFtxZa6wKy4bTGrLy5ptJJvfZy0d14c5fQlHypsZyLQ
Flash ROM
Flash GApps Nano 9.0
Boot System
Flash Magisk (Root Manager)-Option
-------------------------------------------------------------
****Step-For microG user (Test with NanoDroid 20.6)
Flash ROM
Flash Magisk (Root Manager)
Boot System for setting up Android.
Boot TWRP
Note download nanodroid here https://downloads.nanolx.org/NanoDroid/Stable/
-Flash NanoDroid-patcher
-Flash NanoDroid-microG
Boot System for setting up microG setting program.
-Self-Check --click menu for Adding System spoffs signature
-Google device registration (Enable)
-Google Cloud Messaging (Enable)
-Google SafetyNet (Enable)
-UnifiedNlp Setting
---tab Configur location backends menu then tic Deja vu location service
---tab Configure address lookup backens menu then tic Nominatim
Install fdroid.apk (lastest version. https://f-droid.org/en/) --No use NanoDroid-fdroid
-open f-droid program--->set up repo (Add 3 new repos below)
https://www.nanolx.org/fdroid/repo
https://fdroid.bromite.org/fdroid/repo
https://microg.org/fdroid/repo
Install satstate from f-droid
-Open device GPS by Use location widget from Status bar.
-Open satstate program and run GPS menu
Install MozillaNlpBackend from f-droid
Run microG Self-Check again but this time click UnifiedNlp setting---->Configure location backends-----Enable Mozilla Location Service
self-check Unifield status will pass all (6 options)
After a bit of a struggle I managed to get this installed and working last night
A few things I noticed:
1) It may have been previously unlocked by the ebay seller I got it from. The official unlocker I got from http://en.miui.com/unlock/ (https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ has other details) had issues, finally got it, at one point in time, to say unlocked even though all 3 steps didn't have any checkboxes next to them... Strange, but I finally looked at the fastboot_unlock binary that came with the unlocker exe, and that indicated it was unlocked.
2) I found 3 different TWRP to try and install, with 2 of them (I _think_ the one linked here, and the one linked at the EU community thread above) kept giving me "too large to transfer". I finally got the one linked above by the following process:
start powered off
hold power + vol down to get to Fastboot
fastboot devices
fastboot -s <DEVICE ID> flash recovery recovery.img
At this point, the screen went black except for at the upper right it said "press any button to power off", and fastboot exe is saying "waiting for <DEVICE ID>"
press a button, device powers off, leave it connected to the computer
hold power + vol down to get to Fastboot, fastboot exe should see the device and now do it's thing to send/flash the recovery.img
after fastboot finishes, do fastboot boot recovery.img
should now boot to TWRP, should be able to tap a button/screen to get into it
3) I also found I needed to perform a device wipe/reset from within TWRP before copying the LOS and OpenGAPPs zip files over. First time I tried it without wiping it had some weird install/configuration left and caused major issues upon booting LOS. Seemed to think it wasn't a fresh install, and had most of the apps keep crashing and restarting.
Please tell me Is the problem of changed mac address occuring with gsi roms or it is also there with normal flashable zip roms
Can it be repaired by flashing fastboot rom with mi flash tool?
hey,
Can someone tell me what kind of processor mi pad 4 plus is using?
ARM, ARM64, or x86
You heard about search engines? --> https://www.gsmarena.com/xiaomi_mi_pad_4_plus-9295.php
Hi Tom.
On one of your screenshots the lock screen says “charging rapidly”. I thought the pad 4 plus doesn’t support this function. Is it now possible with this version of LineageOS?
r0b said:
Hi Tom.
On one of your screenshots the lock screen says “charging rapidly”. I thought the pad 4 plus doesn’t support this function. Is it now possible with this version of LineageOS?
Click to expand...
Click to collapse
Try LOS 17 Android 10
@tom.android:
I tried LOS 17, but it was not running well on my Pad 4 Plus.
So I switched to this one here and LOS 16 so far runs well.
Though I have a problem with auto brightness which is not working properly. Once activated it doesnt have any effect and from time to time it just lowers brightness to the lowest point.
From your LOS 17 post I grabbed the auto brightness fix and flashed it, but it didnt work for LOS 16. Is there another fix you know about?
Also from time to time the tablet wakes up without me using it and not going to sleep again. This results into the device being display on all night long. Really annoying
r0b said:
Hi Tom.
On one of your screenshots the lock screen says “charging rapidly”. I thought the pad 4 plus doesn’t support this function. Is it now possible with this version of LineageOS?
Click to expand...
Click to collapse
Looks like different device to me. ???
I will update the thread soon thanks @phhusson
Till then follow this video at the end
Note: This pure AOSP vanilla phh treble rom only works on
1)arm 32 ab,
2)arm 32 64bit binder ab
3)arm 64 ab
I have shown tutorial for arm32 64bit binder ab device i.e Galaxy tab A 10.1
Desclaimer: Do at your own risk.
Download only this file for Galaxy Tab 10.1 A:
https://github.com/phhusson/treble_experimentations/releases/download/v400.a/system-squeak-arm32_binder64-ab-vndklite-vanilla.img.xz
Check your gsi treble version using this app first:
Treble Info - Apps on Google Play
Helps you check Project Treble, A/B and Architecture for GSI installation
play.google.com
Bitgapps:
For Galaxy tab A 10.1
https://www.pling.com/p/1462973/https%3A%2F%2Fdownloads.bitgapps.org%2FGApps%2Farm%2FS%2FBiTGApps-arm-12.0.0-R41_signed.zip
To solve device certification error:
1) Device ID apk method:
Download :
Device ID - Apps on Google Play
Obtain Device/Android ID ,Google Services Framework ID, IMEI,IMSI,IP,MAC Address
play.google.com
Google device certification website :
Sign in - Google Accounts
2) Magisk method:
Adb commands:
adb devices
adb shell phh-su 0 /system/bin/phh-securize.sh
Now boot to twrp and flash magisk Debug zip:
magisk_12
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Magisk debug apk:
https://github.com/topjohnwu/Magisk/releases/download/v22.0/Magisk-v22.0.apk
Magiskhide prop configuration Module :
https://forum.xda-developers.com/attachments/magiskhidepropsconf-v6-1-1-zip.5440861/
Bugs:
1) MTP not working but we can transfer files in TWRP if your device supports TWRP
2) Device certification error: solve it by following the method shown in the video.
3) Audio in video recording:
use open camera to solve this
https://www.google.com/amp/s/m.apkpure.com/open-camera/net.sourceforge.opencamera/amp
4) Graphical glitches:
Reduce windows animation scale in developers option but it can't be completely solved.
5)Volte not works: but you can try ims fix available in phhh treble setting. Except that 4g,3g network are working good.
Will it work on sm t290
the gapps link doesnt work.
Evolution X 7.9.2 for the OnePlus 8, 8 Pro, 8T & 9R [instantnoodle] [instantnoodlep][kebab][lemonades]
{
"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"
}
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab (Founder/Lead Developer)
@peaktogoo (Project Manager/Co-Founder)
@AnierinB (Project Specialist/Co-Founder)
Reach us on Twitter! @EvolutionXROM
Check out our website!
Spoiler: Feature List
Code:
Themes
- Theming Settings (Style, Color Source, Accent Color, Accent Background, Background Color, Luminance, Chroma, Tint Background)
- Custom Themes (Black, Clear, Vivid, Paint In The Snow, Espresso)
- Dark Theme Schedules
- Lock screen Clock Fonts (16 Fonts)
- Headline/Body Fonts (53 Fonts)
- SB Icon Packs (10 Styles)
- SB Signal Icon Packs (14 Styles)
- SB WiFi Icon Packs (10 Styles)
- System Icon Shape Packs (16 Styles)
- 3 Button Navbar Styles (10 Styles)
Status bar
- Status Bar Lyrics
- Clock Styles (Right, Center, Left)
- Clock & Date Configs (Auto Hide, Hide Duration, Show Duration, Seconds, AM/PM, Font Size, Date Position/Case/Format)
- SB Logo Pack (20 Styles, Right/Left)
- Network Traffic Indicators
- Battery Icon Styles (19 Styles)
- Battery Percent (Hidden, Inside Icon, Next To Icon)
- Battery Bar (Thickness, Alignment, Blend Colors, Reverse Direction, Colors, Animation)
- System SB UI Tuner
- Data Disabled Icon (On/Off)
- Old Style Mobile Data
- 4G Instead Of LTE
- Roaming Indicator
- WiFi Type Icon
- Colored Icons
- Notification Count
- Bluetooth Battery Status
- Mic/Camera Privacy Indicator
- Location Privacy Indicator
- Media Projection Privacy Indicator
Notifications
- ReTicker
- App Colored Background For Reticker
- Heads Up (Time Out, Importance Threshold, Less Boring, Stoplist/BlockList)
- Force Expand Notifications
- Notification Sound If Active
- Kill App Button
- Blink Flashlight For Incoming Call (When Ringing, When Silent, When Entierly Silent, Always)
- Blink Flashlight For Notifications
- In-Call-Vibrations (Connect, Waiting, Disconnect)
Quick Settings
- Clock
- Clock Font Size
- Date
- Battery Style (15 Styles)
- Battery Percent Location (Hidden, Inside Icon, Next To Icon)
- Battery Estimates
- Secure QS Tiles Requires Unlocking
- Quick QS Pulldown (Disabled, Right, Left, Always)
- Brightness Slider (Never, Expanded, Always)
- Brightness Slider Position (Top, Bottom)
- Auto Brightness Icon
- Hide Labels
- Label Text Size
- Smart Pulldown
- Vertical Layout
- Columns In Portrait (2-5)
- Columns In Landscape (2-6)
- QS Tile Animation Style (3 Styles)
- QS Tile Animation Druations (3 Speeds)
- QS Tile Animation Interpolator (8 Styles)
- Vibration On Touch
- Vibration On Touch Duration
- QS Footer Warnings
- Show Data Usage
- User Account Icon
- Edit Icon
- Power Menu Shortcut
- Running Services Shortcut
- Settings Shortcut
- Clear All Button (10 Styles, 5 Backgrounds)
Power Menu
- System Settings (Hold PWR Assistant + Hold Duration)
- Disable Power Menu On LS
- Power
- Restart
- Advanced Reboot Options
- Screenshot
- On-The-Go Mode
- Settings
- Lock Down
- Emergency
- Device Controls
- Users
- Logout
- Bug Report
Gestures
- System Settings
- Quick Tap
- Volume Button Playback Control
- Swipe To Screenshot
- Brightness Control
- PWR Button Torch
- Double Tap To Sleep Status Bar
- Double Tap To Sleep Lock screen
- AOSP Gestures
- Pill Length
- Pill Radius
- Hide IME Button Space
- Back Gesture Animation
Lock screen
- Edge Light
- Always On Fingerprint
- UDFPS Icon Picker (55 Styles)
- UDFPS Animation Picker (38 Styles)
- Lock screen Charging Info
- Hide Status Bar
- Hide QS During Secure Lock screen
- Media Cover Art (5 Filters)
- Ripple Effect
- Fingerprint Authentication Vibration
- Fingerprint Error Vibration
Buttons
- Navigation Bar
- Compact Layout
- Invert Layout
- Show Vol Panel On Left
- Per App Vol Control
- On-Screen NavBar
- Reorient Volume
- Volume Rocker Wake
- Keyboard Cursor Control
- Alert Slider Notifications
- Alert Slider Pulse
- Block Alert Slider In Pocket Mode
- Click To Partial Screenshot
Animations
- Screen Off Animation (3 Styles)
- Power Menu Animations (11 Styles)
- Android P Animation Style
Miscellaneous
- AOD Display Schedule
- Google Services
- Parallel Space
- Game Space
- Smart Pixels
- App Lock
- Launch Music App On Headset Connection
- Unlimited Photos Storage
- Unlock Higher FPS In Games
- Netflix Spoof
- Pulse Music Visualizer (Navbar, LS, Ambient)
- Volume Panel Timeout
- Jitter Test
- Ignore Secure Window Flags
- Show CPU Info
- Toast App Icon
- Sensor Block Per Package
- Wakelock Blocker
- Alarm Blocker
- Default USB Configuration
- Radio Info
Evolution X Launcher
- Icon Packs
- Notification Dots
- Icon Size
- Icon Font Size
- Max Lines For App Label
- Lock Layout
- Add App Icons To Home
- Dark Status Bar
- Double Tap To Sleep
- Wallpaper Scrolling
- Wallpaper Zooming
- At A Glance
- Swipe To Access Google Feed
- Hide/Show Status Bar
- Top Shadow
- Icon Labels On Desktop
- Hotseat Background
- Google Search bar
- Themed Icons
- Corner Radius
- Themed Icons In App Drawer
- App Drawer Search bar
- Icon Labels In App Drawer
- App Drawer Row Height
- App Drawer Background Opacity
- Recents Background Opacity
- Recents Scroll Vibration
- Recents Screenshot
- Recents Google Lens
- Recents Clear All
- Suggestions In All Apps List
- Suggestions On Home
- Blocked Suggestions
- Parallel Space
- Taskbar
- Rotation
- Hidden & Protected Apps
Spoiler: Device specific feature List
Code:
My signature Universal OPlusExtras application:
- Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer/Notification & Ringer/Refresh rate/ExtraDim/NightLight/ColorSpace)
- Ambient display gestures (raise2wake)
- Kcal
- Per-app refresh rate
- DC-Dimming toggle
- Auto HBM toggle (with lux adjustment preference)
- Power efficient Workqueue toggle
- MSM touchboost toggle
- fsync toggle
- Adrenoboost preference (off, light, medium, aggressive
- FPS overlay (9 Positions, 11 Colors & accent, 9 Sizes
- Powershare toggle
- Game mode toggle (240hz touch sampling rate)
- USB-OTG toggle
- USB2.0 Fastcharge toggle
- System Vibration Strength preference
• Google restore isn't functioning at this time.
You tell me
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT flash instantnoodlep (8 Pro) on instantnoodle (8) or vice versa, else you will semi brick your device! The only way to recover from this is by purchasing an EDL DEEP FLASH cable and using it in-conjunction with msmtool.
Please note that we ship OOS13 F.10 abl.img on 8, 8 Pro, 8T & 9R to bypass the BL unlocked warning!
Please note that we ship a Custom logo.img on 8, 8 Pro, 8T & 9R to better match the ROM!
First Time Install (8 & 8 Pro)
1. Be on any version of OOS12 or OOS13 (F.63 firmware is included in these builds)
2. Download vbmeta, recovery, and rom for your device from here
3. Reboot to bootloader
4. fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload rom.zip (replace "rom" with actual filename)
7. Format data, reboot to system & #KeepEvolving
First Time Install (8T & 9R)
1. Be on the latest OOS13 (F.63 for 8T & F.22 for 9R)
2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
3. Reboot to bootloader
4.fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to system & #KeepEvolving
Update (8, 8 Pro, 8T & 9R)
1. Reboot to recovery
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
4. Reboot to system & #KeepEvolving
OTA
1. Check for update. If available, select "Download and install" (approx 10-15 min)
2. Reboot & #KeepEvolvingFirmware Update (8, 8 Pro, 8T & 9R)https://forum.xda-developers.com/t/...lution-x-7-5-01-13-2023.4480927/post-87295281
Android version: 13.0_r49
Security patch level: May 2023
Build author: Anierin Bliss
Kernel Source: https://github.com/Evolution-X-Devices/kernel_oneplus_sm8250
Clang version: 14.0.6
ROM Developer: joeyhuab
Source code: https://github.com/Evolution-X
Credits: @jabashque @LuK1337 @mikeioannina @ZVNexus from LineageOS
Spoiler: OnePlus 8 (Instantnoodle) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/instantnoodle/evolution_instantnoodle-ota-tq2b.230505.005.a1-06020228-unsigned.zip/download
recovery:
https://sourceforge.net/projects/ev...ntnoodle/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/instantnoodle/vbmeta/vbmeta.img/download
Spoiler: OnePlus 8 Pro (Instantnoodlep) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/instantnoodlep/evolution_instantnoodlep-ota-tq2b.230505.005.a1-06020056-unsigned.zip/download
recovery:
https://sourceforge.net/projects/ev...tnoodlep/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/instantnoodlep/vbmeta/vbmeta.img/download
Spoiler: OnePlus 8T (kebab) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/kebab/evolution_kebab-ota-tq2b.230505.005.a1-06020305-unsigned.zip/download
recovery:
https://sourceforge.net/projects/evolution-x/files/kebab/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/kebab/vbmeta/vbmeta.img/download
copy_partitions:
https://sourceforge.net/projects/evolution-x/files/kebab/copy_partitions/copy_partitions.zip/download
Spoiler: OnePlus 9R (lemonades) latest downloads
rom:
https://sourceforge.net/projects/evolution-x/files/lemonades/evolution_lemonades-ota-tq2b.230505.005.a1-06020354-unsigned.zip/download
recovery:
https://sourceforge.net/projects/evolution-x/files/lemonades/recovery_erofs/recovery.img/download
vbmeta:
https://sourceforge.net/projects/evolution-x/files/lemonades/vbmeta/vbmeta.img/download
copy_partitions:
https://sourceforge.net/projects/evolution-x/files/lemonades/copy_partitions/copy_partitions.zip/download
Commonly asked questions & answers:
Q: Why am I getting "error cannot read" while attempting to sideload the ROM
Spoiler: Answer
Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.
Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.
For example:
./adb sideload ./rom.zip
This basically tells the shell "Hey, I want to execute this local binary rather than the one in PATH".
Q: I'm a windows user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?
Spoiler: Answer
Use the official Google USB driver
Q: I'm a linux user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?
Spoiler: Answer
Set up udev rules
Q: Why is MTP and/or Android Auto not working?
Spoiler: Answer
Set the default USB configuration in Settings > The Evolver > Miscellaneous > USB Configuration
Don't see your question? Well, feel free to post a comment in this thread, we will reply as soon as we can. We'd appreciate if users used XDA FIRST and the telegram group as a LAST RESORT.
To be continued (I'm sure).
Firmware update:
FLASHING THE WRONG DDR TYPE WILL SEMI BRICK YOUR DEVICE. THE ONLY WAY TO RECOVER FROM THIS IS BY PURCHASING AN EDL DEEP FLASH CABLE AND USING IT IN-CONJUNCTION WITH MSMTOOL!!
Spoiler: Method 1
1. Check your DDR type using the following command:
adb shell getprop ro.boot.ddr_type
0 = ddr4
1 = ddr5
if getprop returns an empty value, use the following commands instead (requires root):
adb shell
su
cat /proc/devinfo/ddr_type
DDR4 = DDR4
DDR5 = DDR5
1. Download and flash the firmware zip that matches your device and DDR type:
8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)
2. Reboot to recovery and then sideload the ROM.
Spoiler: Method 2
8 (instantnoodle)
8 Pro (instantnoodlep)
8T (kebab)
9R (lemonades)
Custom Kernels:
Custom kernels may be flashed at YOUR OWN RISK. However, we will not provide extended support regarding such and it is up to YOU, the end user to make your reports in the appropriate thread for X kernel, not in this thread.
Obtaining root:
Let it be known that we will not assist anyone with bug reports until they have disabled all modules and restored to the default, unpatched kernel that is shipped with the ROM!
Root can be obtained by either one of the following methods.
Spoiler: Method 1 (flashing magisk.apk/zip)
1. Download the Magisk.apk on your pc (you can change the file extension to .zip if you wish, though it is not required).
2. Reboot to recovery
3. Navigate to Apply update -> Apply from ADB
4. adb sideload magisk.apk (replace "magisk" with actual filename)
Spoiler: Method 2 (patching boot.img)
1. Download the full rom.zip from post #2 of this thread
2. Download payload-dumper-go that corresponds to the architecture of your pc
3. Run payload-dumper-go against the rom.zip
4. Grab boot.img from the extracted folder and transfer it to your device
5. Patch the boot.img with the magisk application and transfer the patched image to your pc
6. Reboot to bootloader
7. fastboot flash boot boot.img (replace "boot" with actual filename)
Retaining root across OTA updates:
When an OTA update is available, let it download and install. Before rebooting simply open Magisk Manager and click on the first "install" button and select "install to inactive slot". Once it's done, reboot and enjoy.
Reporting bugs and submitting logs:
In most cases logs should be provided when reporting bugs. This can be done by enabling USB debugging in developer options of the device, connecting it to your PC and running one of the following cmds depending on the type of bug/issue while reproducing it:
General system log
adb logcat > logcat.txt
Kernel log
adb shell su -c dmesg > dmesg.log
Please provide a detailed description of the bug/issue as well as link/upload the log you had taken.
There are exceptions to this as some issues are unable to be caught in logs. In this case, it is expected that users provide clear and accurate steps to reproduce the issue.
Getting involved in the development:
We've set everything up in such a way where all you need to do is install AOSP build dependencies, initialize a repo client, init the tiramisu branch of our manifest, sync the code and lunch your device (e.g lunch evolution_instantnoodlep-userdebug); Roomservice will automatically sync all device specific dependencies for you to compile without error. There is no need to manually clone anything due to this and applies to OnePlus 6, 6T, 7, 7 Pro, 7T, 7T Pro, 8, 8 Pro, 8T, 9R, 9 & 9 Pro (enchilada, fajita, guacamoleb, guacamole, hotdogb, hotdog, instantnoodle, instantnoodlep, kebab, lemonades, lemonade & lemonadep).
Device and ROM source changes can be submitted on github to the appropriate repositories by making pull requests via comparing forks. Please follow the google patch format for commits and triple check your changes by compile testing and verifying they're correct. Please retain proper authorship if you are not the author!
AB sir Pro.
Noice ! Can't wait to test
W W W W Whaaaaat!!!! Already! So fast, you guys are legends!
So can I dirty flash from 6.7? or have to clean install?
I'm sure you'll get round to adding the features, but does this have the same evolver features as 6.7?
Best dev ever
d3viou5 said:
W W W W Whaaaaat!!!! Already! So fast, you guys are legends!
So can I dirty flash from 6.7? or have to clean install?
I'm sure you'll get round to adding the features, but does this have the same evolver features as 6.7?
Click to expand...
Click to collapse
You can dirty, but it's in alpha stage.. so you shud be ready for bugs.
thanks dev. does magisk work?
david1907 said:
thanks dev. does magisk work?
Click to expand...
Click to collapse
Yup
OPlusExtras are back
Great job Anierinb! Man do you work quick! Can't wait to update to this and get all the cool android 13 stuff
So I did a dirty flash from 6.7 to 7 and all went well......
Is there a folder somewhere for the latest builds? I still have the version without the OnePlusExtras.
I guess without the Evolver there's no OTA.
Great job BTW. There are bugs as expected, but love how we have access to this so early!
d3viou5 said:
So I did a dirty flash from 6.7 to 7 and all went well......
Is there a folder somewhere for the latest builds? I still have the version without the OnePlusExtras.
I guess without the Evolver there's no OTA.
Great job BTW. There are bugs as expected, but love how we have access to this so early!
Click to expand...
Click to collapse
I don't think the new build is uploaded yet, but in any case you can check his SF folder
I have a c33 fw installed and on a custom a12 based rom.. Can I dirty flash the rom on top of it?
Updates with OPlusExtras, fixed BT, NFC and safetynet are up on SF
just a query, does anyone use this ROM without ROOT ?
AnierinB said:
Updates with OPlusExtras, fixed BT, NFC and safetynet are up on SF
Click to expand...
Click to collapse
Time to flash
I know this is alpha, so fully expecting this, but pretty much every installed app crashes.
Any reason for this?
I did dirty flash, my lazyness could certainly be a contributing factor.
Battery life is tuly aweful.
But hey, it's A13. V4A, Root, Safetynet, GCAM Mods All good......
d3viou5 said:
I know this is alpha, so fully expecting this, but pretty much every installed app crashes.
Any reason for this?
I did dirty flash, my lazyness could certainly be a contributing factor.
Battery life is tuly aweful.
But hey, it's A13. V4A, Root, Safetynet, GCAM Mods All good......
Click to expand...
Click to collapse
I just installed the latest version and came here just to post this. Initially Youtube and Chrome were crashing but after the App data wipe for youtube, it's working.
But chrome and KIWI browser are not at all working. haven't tested all apps though.
Looks like all Chrome depending apps are crashing. like (OLX, etc)
Biggest concern is : Screen Casting is auto connecting to my TV though i dont initiate it. I disconnect and after a few seconds it re connects