First, let's give credit where credit is due. @ZeNiXxX and @SKULSHADY are the developers of this ROM. Additional credit goes to @phhusson and @Dil3mm4 as well as:
LineageOS Team (https://www.lineageos.org)
AICP (https://www.aicp-rom.com)
MSM-Xtended Team (https://forum.xda-developers.com/one...0-pre-t3693585)
Crdroid (https://crdroid.net)
Omnirom (https://omnirom.org)
And all the other Developers, Testers, Donators and Users.
The source code which can be reviewed and continued too can be located here https://github.com/Havoc-OS and https://github.com/Havoc-Devices You can request features https://goo.gl/forms/b8rY79XtUZnd5ji42 Announcement are made here https://t.me/Havoc_OS and additional support can be requested here https://t.me/havocofficial. Finally, the official Havoc-OS page can be located here https://sourceforge.net/projects/havoc-os/files The original official thread is actually located here and was originally posted by @EnesSastim and an updated thread can be found here originally posted by @mountaser halak I, myself, @MotoX4 did full testing in verifying the support of MotoX4 having tested on several XT1900-1 (both Andriod One, Amazon Moto Retail, and * Project FI).
However, the purpose of this thread is only to bring awareness that MotoX4 users (such as yourself) do have another ROM to choose from and to include full instructions on how to install this on your MotoX4 device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Not working:
Tethering
- You tell me
FEATURES:
Code:
[SIZE="4"][B][U][SIZE="5"]General:[/SIZE][/U][/B]
System-wide Rounded UI
Full OMS support
System-wide burn-in protection
Spectrum support
Compiled using SDCLANG
Razer Phone lock/unlock sounds
OTA support
Signature spoofing
Micro-G support
[SIZE="5"][B][U]Included Apps:[/U][/B][/SIZE]
AdAway
Google Calculator
Google Markup
Lean Launcher
[SIZE="5"][B][U]Settings:[/U][/B][/SIZE]
[B][U]Battery:[/U][/B]
Battery performance profiles
Sensor block per-package
Wakelock blocker
Alarm blocker
Optimal charge level alert
[B][U]Display:[/U][/B]
Live display (Day/Night/Outside)
Colour profiles (sRGB, DCI-P3)
Font manager
Ambient display
Always on display
Expanded desktop
[B][U][SIZE="5"]Havoc Settings:[/SIZE][/U][/B]
[B][U]Status Bar:[/U][/B]
Quick pulldown
Smart pulldown
Tap to sleep
Brightness control
Battery icon styles
Bluetooth battery status
Battery bar
Battery saver color
Clock & date options
Statusbar logo
No sim network hide
Disable no sim icon
Volte icon
Network icon customization
Net activity
Custom carrier label
System icons
[B][U]Panels:[/U][/B]
Power menu tweaks
Volume dialog tweaks
[B][U]Quick Settings:[/U][/B]
Brightness slider customization
QS panel footer customization
QS layout editor
Custom header images
[B][U]Notifications:[/U][/B]
Disable fc notifications
Force expanded notifications
Disable immersive mode messages
Kill app button in notification
Screen-on notifications
Toast icon
Toast animation
Toast icon color
Toast text color
Heads up toggle
Heads up timeout
Heads up blacklist
Heads up stoplist
Snooze timer
Statusbar ticker
Ticker animation
In-Call vibration options
Less annoying in-call notifications
[B][U]Recents:[/U][/B]
Stock recents customization
Clear all button customization
Memory bar
Recent styles
Hide apps from recents
Icon pack
Immersive recents
Recents layout (Stock/Grid/Android Go)
OmniSwitch
Slim recents
[B][U]Interface:[/U][/B]
Berry styles (Light/Dark/Black/Auto)
Blur personalization
Dashboard suggestions
Dashboard conditions
Screen stabilization
[B][U]Lockscreen:[/U][/B]
Charging info
Hide statusbar
Lockscreen elements visibility
Notification count
Lockscreen colors
Clock and date options
Lockscreen alpha
Double tap to sleep
Wake and unlock
Ambient display music ticker
Ambient display bottom view (Weather/Battery/None)
Music cover art
Music visualizer
Disable power menu
Disable qs panel
Fingerprint vibration
FP unlock on boot
Face auto unlock
Custom bottom shortcuts
[B][U]Navigation:[/U][/B]
Navigation mode(Stock/Smartbar/Fling)
Dynamic navbar color
Pulse
[B][U]Buttons:[/U][/B]
Swap back and recents
Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer)
Accidental touch
Power menu customization
Long press power button torch
Disable buttons
Button backlight customization
Hardware keys customization
Swap volume buttons with rotation
Volume keys for media volume
Playback control
[B][U]Gestures:[/U][/B]
Three finger screenshot
Pie control
App circle bar
Gesture anywhere
Screen-on gestures
Touchscreen gestures
[B][U]Animations:[/U][/B]
System Animations
Android P animations
Disable animations
QS tile animations
Listview animations
Custom Bootanimation
Screen off animation
[B][U]System:[/U][/B]
SELinux mode Toggle
Smart Pixels
Suspend actions
System app remover
Allow untrusted overlays toggle (for Substratum Support)
CPU info overlay
[B][U]IME Settings:[/U][/B]
Selector notification
Auto keyboard rotation
Disable fullscreen keyboard
[B][U]Weather:[/U][/B]
Weather service settings
Statusbar weather
Lockscreen weather
[B][U]Miscellaneous:[/U][/B]
Screenshot editor
Wake on plug
Pocket detection
Camera shutter sound
Disable safe headset volume
Launch music App on headset Connection
Scrolling cache
Events[/SIZE]
How to install Havoc-OS on Moto X4
!! Please read before proceeding !!
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
!! You will be wiping everything because regardless if you are coming from stock or a different ROM as this ROM works best with a full wipe !!
Note: If upgrading this ROM a full wipe is not necessary. See upgrade instructions below.
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), select "advanced wipe" to wipe your device (select all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
If coming from stock:
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Continue:
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest Amr64 A/B ROM located here: https://sourceforge.net/projects/havoc-os/files/arm64-ab/ - NOTE: You want the ROM that comes without Gapps. You can install Gapps after (see instructions below).
Extract the zip (XZ file) onto your computer. -- I suggest the free and open source program 7zip https://www.7-zip.org/
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img /sdcard/
In TWRP select Install *
Select Install image
Locate your .IMG file and flash it to "SYSTEM"
* TWRP troubleshooting:
A small group of individuals has reported that TWRP will not correctly install IMG files directly. If you're one of those few people a manual install may work for you.
First wipe your phone again
Reboot back to bootloader. - Stay at bootloader
As an administrator on windows or as root on Linux run this command
Code:
fastboot -u flash system Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste the example posted here).
Credit to @*.jpg for this solution.
NOTE: Do NOT yet install Gapps. See instructions below.
After a successful install, REBOOT your phone.
Congratulations, you're done!
If adding Gapps: -- Read me
Your phone will work perfectly fine without Gapps. But if you do want to install Apps and use Google products and services; I recommend the minimal Gapps install known as Pico. You can learn about the many different Gapps flavors by visiting the Open Gapps Wiki found here https://github.com/opengapps/opengapps/wiki/Package-Comparison
Let your phone boot the ROM for the 1st time. - !! IMPORTANT !! You want to fully boot your phone and let the ROM load for the 1st time before installing Gapps.
After your phone as successfully booted up and loaded the ROM, reboot back into recovery
Download the latest Gapps - https://opengapps.org
Upload the zip to your phone
Install Gapps
Wipe cache/dalvik
Additionally, if you're one of those paranoid people who want to keep your distance away from Google (to each their own, but I love me some Google ) you do have the following alternatives.
https://apkpure.com/
https://en.uptodown.com/android
https://f-droid.org
Just remember that these are unofficial sources and you take the risk that can potentially come with them.
UPGRADING - How to upgrade this ROM.
Also known as a dirty upgrade, you do not need to wipe everything and start over. However, if this dirty upgrade fails a fresh install is recommended.
Download the latest ROM
Reboot into recovery
Install your new .img file
Wipe cache/dalvik
Reboot
If all has gone well you're done! If not, a full wipe and install are recommended.
* Project Fi
If you do not have Google Project Fi as your cellular provider, you can ignore this.
The Google Project Fi app will inform you that you cannot activate using this GSI/Rom. Assuming, you have already previously activated your phone before trying out new GSI/ROM's, you can technically, safely ignore this warning as you will still be able to send and receive calls, text, data, etc... and continue to use the Project Fi app to manage your account. However, if this is your first time activating or you simply wish to be sure you get the latest carrier and tower updates (recommended), this fix is for you.
First let's give credit where credit is due. @Sass86oh for originally coming up with this fix here and a personal thanks to @johnjingle for pointing this out to me here.
Google Project Fi Fix
You will need to make a minor and yet important edit to your system before installing the Project Fi app. If you have already installed the Project Fi app before making this edit, you should close the app, clear both the app's cache and clear the app's storage, then proceed to uninstall the Project Fi app.
Using your preferred root text editor navigate to /system/
Locate the file build.prop
Carefully make the following changing, listed below, to the file build.prop
!! Important !! Double check you have correctly made the correct changes.
Save your changes
REBOOT your phone
Go to: Setting > System > About
Verify that your device model is a Moto x4
Install Project Fi
Open Project FI and proceed with the activation
Congratulations, you're done!
!! IMPORTANT !! These values are CASE SENSITIVE which means if you type "Payton" rather than "payton" it will NOT work !! Be sure you double-check what you type before saving !!
Locate and edit to match. -- Do NOT rush (Do NOT be in a hurry). This is something you want to carefully take your time with.
Code:
ro.product.model=Moto x4
ro.product.brand=Motorola
ro.product.name=payton
ro.product.device=payton
ro.product.manufacturer=Motorola
ro.build.product=payton
ro.opa.eligible_device=true
Headphone jack fix found here. credit: @abrfilho
????
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
abrfilho said:
Battery is great in this rom, here I just can't change color profile and use the wide lens, is there a way to fix that?
Click to expand...
Click to collapse
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
SchmilK said:
On other roms installing moto camera is supposed to work with 2nd camera. I haven't tried it, just read it.
Click to expand...
Click to collapse
Yeah, when I was using phh's Pie AOSP I was able to use the wide lens, even on modded GCam, but here I'm not able. ?
I already installed Moto Camera here.
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
*.jpg said:
For some reason, the .img file wouldn't install from TWRP, but flashing it from bootloader finally worked after several attempts. I ended up using the copy partitions installer and it finally worked. I was coming from Lineage 15.1 so I don't know whether this can help anyone else. I look forward to giving Havoc a try!
Click to expand...
Click to collapse
How can you do that? I think I can't just fastboot flash havoc.....img right?
I installed via TWRP, but I am stuck at the android loading screen. I will try to re-flash I guess.
khanhlinh said:
How can you do that? I think I can't just fastboot flash havoc.....img right?
Click to expand...
Click to collapse
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
Code:
fastboot -u flash system [*your GSI here*].img
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
I rebooted to TWRP and installed the OpenGapps 9.0 micro version which went smoothly.
This command worked for me. I'm setting up TiBu and the remainder of my apps now.
---------- Post added at 12:35 PM ---------- Previous post was at 12:15 PM ----------
Havoc-OS-v2.0-20181016-GSI-ARM64-AB-Official.img doesn't appear to be rooted. I don't want to foul anything up by installing an alternate root by mistake. Is there somewhere in the ROM to activate it or is it okay to flash Magisk? (Or SuperSU or whichever)
Click to expand...
Click to collapse
You can flash Magisk without a problem.
khanhlinh said:
I followed the instructions closely but still can't boot up. Always return to bootloader after I flash the image. Latest twrp, I did notice that the slot don't change.
Click to expand...
Click to collapse
I am having the same issue, except I get to the android text sometimes. I have tried installing the rom with gapps and w/out.
Not sure what I am doing wrong I came from Lineage trebelized and I did wipe everything even internal storage. Should be simple.
*.jpg said:
It's the only method I could use to flash that wouldn't result in rebooting to TWRP. I couldn't get the version with Gapps to get past the "Checking Info. . ." screen, but the non-Gapps version booted up very quickly.
Click to expand...
Click to collapse
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
I only managed to enter system with GApps version by disabling all networks (removing SIM and not connecting to wifi), but everytime prompted some login, I could configure without a problem using the normal version with GApps flashed.
absaget0 said:
I managed to successfully flash the ROM with TWRP but i'm getting the same infinite "Checking info..." screen, tried both ""Copy your data from the cloud" and "Set up as new" options but both end up in the same "Checking info..." loop.
Click to expand...
Click to collapse
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Nice work bro... Please keep it live and update it time to time
johnjingle said:
Same issue for me, I finally got both to boot, but I am now stuck at checking info too.
Click to expand...
Click to collapse
can you skip if you turn the phone off and on again?
xdacinq said:
can you skip if you turn the phone off and on again?
Click to expand...
Click to collapse
unfortunately no. at the same position i got the loop. But the Version without gapps worked.
Well, I'm puzzled why some of you are having so many issues. I had 3 MotoX4's to play with and all of them worked without issue. Granted, all 3 are XT1900-1 devices and I wouldn't imagine a big different between XT1900-1 through 7. Did this with the original Amazon Moto Retail (the one which says Moto and not Andriod One), plus the Andriod One I got from Motorola and finally the Project Fi phone too (also an Andriod One edition), but none of them had the issues some of you are reporting. -- Which is why I felt confident sharing this in this forum.
I will add that I always used the ROM without Gapps included (and later installed Gapps after adding the ROM). Gapps tends to update often and I wanted to start fresh with the latest edition, so I installed the Rom without Gapps, confirmed that all was working, and then rebooted back into recovery and installed Gapps (as instructed in post 1).
For the few of you reporting issues... Perhaps start from scratch (as if coming from stock) and see if that resolves things.
I included this in the instructions and someone who sent me a PM made it clear where they were making mistakes. -- DO NOT install Gapps right away. Load the ROM 1st (let your phone boot up the ROM as if you're done and then reboot and install Gapps). I made this clear in my instructions and I think some folks are ignoring that little bit (those of you getting the "checking info" message).
Related
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
4: Custom Roms
What are custom roms? Simply put they are modified versions of Android containing advanced tweaks, stability, and performance. Custom Roms are device specific for the most part. In other words, a Rom for the Moto G6 Plus will not work on a Moto G6 or G6 Play. There are a few exceptions to this rule, but they do not apply to the Moto G6 family so I won’t get into detail about it here. As of Android 8.0(Codename Oreo), Google has redesigned the framework of Android with a system called Project Treble. I will get in to that more later on in the Generic System Image(GSI) section of this guide, but to quickly summarize, it means Custom Roms that do not have to be built to be device specific. For a more detailed analysis of custom roms you can read the information in the spoiler tags below.
Spoiler
Android is a free open source software(FoSS)! This means anyone, anywhere in the world can help contribute to Android. This allows developers to add, remove, or modify the source code, and even publish there modified source code for others to use. The most popular example of this is called LineageOS(formerly CyanogenMod(CM)). At one point it was reported over 50 Million people ran CM! Why did 50+ million people decide to ditch the standard Android software provided by the phone’s manufacturer? There are a number of reasons such as :
Bloatware: Stock firmware is commonly infested with applications installed by your carrier to generate more revenue. Rom’s do not have this problem.
Updates: Android updates typically require approval by the carriers as they want certain functions disabled (tethering for example), to make you pay extra for this feature. Since carriers have they final say when updates are pushed out to devices, and wanted bloatware installed, etc, users were lucky to receive security updates. Users were even luckier to see a version update (Oreo to Pie for example). Rom’s do not rely on a carrier to be updated.
Stability: Since users were lucky to receive updates, you were forced to live with bugs for a long periods of time. Maybe even the entire life of the device. Since Custom Roms receive regular updates, this means bugs were fixed in a timely manner.
Performance: Custom roms are usually more optimized for the hardware they run on then stock roms. They may overclock your phone’s processor(CPU) to make it function faster then it was originally designed.
There are other various reasons but you get the idea.
For a list of features added to LineageOS (read this). Other roms may or may not include these features and more!
So how do you install a custom rom? Currently Moto G6 Plus users have access to LineageOS 15.1 (Based on Android 8.1). LineageOS 16(Android 9 Pie based) is in the development stage. There is no time line on a release just yet so not ask for an ETA! Let’s get started!
Downloads:
++Download these files to your PC.
*ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (HERE). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
* TWRP - (Download) - This is a modified Recovery Software allowing you to flash files that will allow you to fipe your device and install custom roms and other various things. Thanks to XDA Member @erfanoabdi who has ported it to our device.
++Download these files to your phone’s sdcard(Do not place them on the internal storage)
*Magisk - (Download) - Download the Stable version here. While not required, I do suggest you download the Latest Uninstaller and Latest Magisk Manager as well.
*copy-partitions-AB.zip - (Download) – Our phone is what’s known as an A/B device. This translates into slot_a and slot_b. The means we have a system_a partition and a system_b partition for example. By default some of these _b partitions are empty. This will populate these empty partitions with a copy of the data on the respective _a partition to help prevent you from bricking your device!
*LineageOS 15.1 [Unofficial] – You have 2 options:
lineage-15.1-20180811-UNOFFICIAL-evert.zip – This version was built on August 08 2018 by @erfanoabdi and @rahulsnair who are the real developers for the Moto G6 Plus.
lineage-15.1-20181003-UNOFFICIAL-evert.zip – This version was built on October 03 2018 by me Xplorer4x4. This version uses the same device specific binaries and source code @erfanoabdi and @rahulsnair used, but uses updated LineageOS source code. This is a bug fix release and does not include additional features.
Gapps – These are Google Apps like YouTube, PlayStore, Gmail, and more. -Again you have two options:
-OpenGapps – (Download) – Personally I prefer OpenGapps as you can customize which apps you want to install. The only downfall is that when you flash an update to LOS, you will have to flash Gapps again. In the Platform Column choose ARM64, in the Android Column choose 8.1, and then you can choose any Variant. I personally use the Nano Package and manually install the Gapps I want form the Play Store.
-MindTheGapps – (Download) – What you get is what you get. You don’t get to choose which gapps are installed, but if you flash an LOS update in the future, you won’t have to flash them again.
Please keep reading for detailed instructions on how to install LineageOS 15.1.
WARNING: This will wipe out all apps and data stored on your phone! It will not wipe your SD Card. Any apps purchased/installed from the Play Store can be restored using WiFi or LTE when you are done installing a ROM.
Known Bugs: Everything works except making calls with Bluetooth devices.
Instructions:
*On the device:
4A: Open the settings app and navigate it in this order: System -> About.
4B: On the About screen scroll down to Build Number and tap on it 5 times. You will see a notification at the bottom of the screen that says “Developer Options Enabled.”
4C: Tap the back button, and open Developer Options.
4D: Find “Android Debugging” and enable it.
*On your PC:
+Windows:
4E: Using Windows Explorer, navigate to the location of twrp-3.2.3-42-evert.img. Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies. You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see.
copy-partitions-AB.zip
+Linux:
4E: Using your favorite terminal interface, navigate to the location of twrp-3.2.3-42-evert.img.
+Linux + MAC + Windows:
4F: Simply type(or copy and paste) the following command:
Code:
fastboot boot twrp-3.2.3-42-evert.img
*On your device(it should be booted in to TWRP at this point):
Create a TWRP Backup: Tap Backup -> Select Storage -> Micro SD Card - > OK. You will see a section that says "Select Partitions to Backup." Make sure to select all of these boxes. At the bottom of the screen Swipe the Blue Button where it says “Swipe to Backup.” When this is done, tap the Home button.
4G: Now tap on "Select Storage," select Micro SD Card, and tap OK.
4H: Navigate to the location of the copy-partitions-AB.zip and tap on the zip.
4I: Swipe the blue arrows button next to “Swipe to confirm Flash.”
4J: Tap the home button.
4K: Tap Wipe → Format Data(Do not tap Advanced Wipe, or Swipe for Factory Reset).
4L: Type yes
4M: Tap the blue check-mark in the bottom right corner.
4N: Tap Home button.
4O: Tap Install->Select Storage→Micro SD Card→OK
4P: Tap lineage-15.1-20180811-UNOFFICIAL-evert.zip or lineage-15.1-20181003-UNOFFICIAL-evert.zip
4Q: Swipe to install.
4R: When flashing is done, tape the home button.
4S: Tap Wipe→Format Data→Type yes→Tap Blue Check Mark at bottom right corner.
4T: Tape Home button when done.
4U: Tap Reboot → System
Congratulations, you have installed Lineage OS but we are not done yet! Let the device boot until you see the LineageOS Welcome screen. Note that the first time booting up a custom rom will take longer then a typical reboot. It should take no more than 5 minuets to complete!
Once on the LineageOS Welcome Screen, you can complete the setup or reboot back to your bootloader. Once the device powers off, hold the Power Button and Volume Down button until the bootloader displays on the phone screen.
4V: Boot TWRP again:
Code:
fastboot boot twrp-3.2.3-42-evert.img
4X: Tap install and navigate to the directory where you placed your gapps.zip and Magisk.zip.
4Y: Tap the Gapps.zip and choose add More zips.
4Z: Tap the Magisk.zip and Swipe to install.
We need to Wipe->Format Data one last time or else your Gapps will give you multiple errors when you boot LOS again. Once you have Formated Data, you can now reboot to system and enjoy LOS!
Small error?
Thanks for the effort that's gone into this post.
Just a quick editing note: the link to download Magisk (https://androidfilehost.com/?fid=5862345805528069013) seems to point to twrp-.2.1-37-evert.img rather than Magisk.
Detailed excellent guide. Almost everything covered.
Btw what advantage this twrp 42 holds over the one from twrp site?
JaggedPill said:
Detailed excellent guide. Almost everything covered.
Btw what advantage this twrp 42 holds over the one from twrp site?
Click to expand...
Click to collapse
Use the version from twrp website. I haven't had a chance to update the guide. Encryption is supposed to work on official twrp but I think myself and other testers verified encryption is not working right now.
Sent from my Phh-Treble vanilla using Tapatalk
What are the steps to compile for this device? Can you provide that information please? I have compiled for others, but this one is new to me and I think you use some configuration or additional files.
@Xplorer4x4 can you provide me your local_manifest file?
Does anyone know if we have any microg rom options for the Moto G6 plus?
Followed your instructions, after step 4U the device stays completely dark, no bootloader, no volume down + power key helps, nothing.
tmr2020 said:
Followed your instructions, after step 4U the device stays completely dark, no bootloader, no volume down + power key helps, nothing.
Click to expand...
Click to collapse
Try one of the following options:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
The second one is the official Rescue Tool from Lenovo. Read the user's guide first. I don't know why your phone is dead, but this might help you.
WoKoschekk said:
Try one of the following options:
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
The second one is the official Rescue Tool from Lenovo. Read the user's guide first. I don't know why your phone is dead, but this might help you.
Click to expand...
Click to collapse
Thanks, I discovered the first thread after stopping banging my head against the wall. It actually worked. I can now use fastboot and adb etc. again. AFAIK, it is not possible to flash twrp recovery, it has to be booted on demand with adb/fastboot? I tried flashing lineage recovery instead, maybe I should not have done that, idk. Anyways it still booted to fastboot after that. I also seem to be confused by the a/b scheme.
Anyways I started all over with the copy-partitions-a-b (as I had a completely broken system, I cant imagine syncing the gargabe between a and b would help much?) and flashing lineage 17.1 again. It now boots to lineage. I rebooted to fastboot/twrp again to sideload opengapps (are they a/b compatible yet?!).
And how do I get a working recovery system again? I can't flash twrp? Can I flash lineage-recovery? Or something else?
And what does "active a" in twrp actually mean? That it will flash to "b"? Or that it will flash to "a"?
---------- Post added at 07:50 PM ---------- Previous post was at 07:34 PM ----------
I has just booted once to LineageOS, after trying to install Gapps, it's stuck in a bootloop. Going to twrp and selecting either A or B and then clicking on reboot, warns "no os installed"!
What am I doing wrong?
What am I doing wrong?
Click to expand...
Click to collapse
Get informations about A/B partitions (seamless updates) and how it works.
You must flash the GApps before our first boot into system.
bom Diagood morning i am stuck in the boot animation of Lineage 18.1 it does not install at all but other custom good piexel base PE style installs normal what can i do wrong ??
Rafinha863 said:
bom Diagood morning i am stuck in the boot animation of Lineage 18.1 it does not install at all but other custom good piexel base PE style installs normal what can i do wrong ??
Click to expand...
Click to collapse
Did you follow the install instructions on the official LineageOS web page?
WoKoschekk said:
Você seguiu as instruções de instalação na página oficial do LineageOS?
Click to expand...
Click to collapse
sim eu seguiyes I followed everything risks the process by adb sideload and completed but when starting the ROM it does not boot is only in the boot animations of Lineage
Rafinha863 said:
sim eu seguiyes I followed everything risks the process by adb sideload and completed but when starting the ROM it does not boot is only in the boot animations of Lineage
Click to expand...
Click to collapse
if it's an endless bootanimation then try to force reboot the device by holding the power button for 10-15 seconds.
WoKoschekk said:
se para uma animação de inicialização sem fim, tente forçar a reinicialização do dispositivo de bloqueio o botão liga / desliga por 10-15 segundos.
Click to expand...
Click to collapse
I already did this procedure and it didn't work either
Rafinha863 said:
I already did this procedure and it didn't work either
Click to expand...
Click to collapse
Latest stock ROM installed? Did you format (not only wipe!) /data?
WoKoschekk said:
Mais recente ROM de estoque instalada? Você formatou (não apenas limpe!) / Data?
Click to expand...
Click to collapse
yes I did data format every installation process correct but it is in bootanimation
WoKoschekk said:
Mais recente ROM de estoque instalada? Você formatou (não apenas limpe!) / Data?
Click to expand...
Click to collapse
Não te entendiI did not understand you are telling me to just format the date and not clean the system I noticed that in the function mount on the ceiling the actions of system vendor persist are all unchecked is this correct?
Rafinha863 said:
Não te entendiI did not understand you are telling me to just format the date and not clean the system I noticed that in the function mount on the ceiling the actions of system vendor persist are all unchecked is this correct?
Click to expand...
Click to collapse
Your internal storage is devided into several partitions e.g. /system, /vendor, /boot and /(user)data. The option format data is the same as the option factory reset. Both of them delete all your apps, settings and so on.
Your OS and all related Moto stuff is stored on /system (OS) and /vendor (Moto). By default they are unmounted, but could be mounted as r/w. If you delete them, you won't boot because no OS is installed.
This TWRP supports encryption (no need to wipe data) , OTA update (TWRP persist), & also it can root within itself.
The root is achieved with Magisk 17.1, no need to flash any encryption disabler or anything, it simply works!!
I present you: [LR. Team] TWRP
Credits to original devs & authors, not me.
Download link by LR. Team: https://yun.baidu.com/s/1jj0NE1pqeF1ejiNAsm1qUw
Download password: jjfd
Mirror by me: https://www64.zippyshare.com/v/HQdMlIDX/file.html
FEATURES said:
* Delete redundant languages, keep English, add Chinese language, default Chinese.
* Modify the default configuration, for example, the default time zone is East Eight Zone, default screen brightness, default vibration, default 24 hours, default return button on the right, default Chinese and so on.
* Modify the default configuration file path to reduce the possibility of conflicts with other people's compiled versions.
* Adjust and optimize the Chinese text and description, and re-edit all the items one by one, which is more accurate, understandable and humanized. Also added display mtp enable off display, file operation result display, operation page title display, permission description when modifying permissions, etc. UI text display.
* Modify the unlocking interface and adjust the height of the sliding unlocking bar, which can effectively prevent misoperation (the original unlocking bar and the operating unlocking bar are of the same height. When the unlocking is completed, the sliding may be repeated, and the corresponding action is directly operated).
* Open more partition backup and restore, such as modern baseband partition, bootloader, persist, cust and other partitions, easy to backup the underlying files before flashing, can restore the underlying files after flashing.
* Add .bin and .mbn format image files, so you don't need a zip brush package, you can write the underlying file. The original version only supports the flashing of .img format image files. (Be sure to pay attention to the selected partition!!!!)
* Solve the problem of interface jam when using the simulation operation (the simulation operation is mainly for testing the theme, and no actual operation).
* Add the manual installation root function in Advanced Options > root system. Add a display root system option on this basis for manual operation.
* Added the ability to unenforce encryption, in advanced options > Unforce Encryption. You can remove the official system to force encryption and cancel the check.
* Change the built-in root mode and add magisk as the default root mode.
* Fixed button and button operations for some interfaces.
* The adb/usb debug mode is enabled by default, which is convenient for operating the phone through the computer command line in rec mode.
* MTP is enabled by default. In the rec state, you can also connect your phone to your computer to facilitate file copying.
* Modify the logo interface, modify the header of the main interface page, and add the display phone model and team name, author name.
* Fix some logical relationships and modify some interface displays.
* Added clear root function
* Added clear power-on password function
* Added clear battery information function
* Added signature boot function
* Added restore official rec function
Click to expand...
Click to collapse
CHANGELOG said:
2018.10.02
1. Support pt, to be tested.
2. Add the remove dm checksum and cancel the forced encryption function.
3. Built-in root and clear root changed to Magisk v17.1
4. Repair automatic decryption data
Click to expand...
Click to collapse
FLASHING PROCEDURE said:
1. Working brain
2. Common sense
3. Common knowledge of flashing via fastboot
4. UNLOCK THE MI 5S PLUS
5. Use cmd line: fastboot flash recovery [name of the file]
6. First reboot to recovery: fastboot boot [name of the file]
IF TOUCHSCREEN IS NON-RESPONSIVE ON FIRST RECOVERY BOOT, FORCE REBOOT IT USING [VOL UP + POWER].
After flashing, if you encounter Chinese UI, press Language then select English.
Root menu is in the [Advanced] .
Click to expand...
Click to collapse
Enjoy!!
Crescendo Xenomorph said:
This TWRP supports encryption (no need to wipe data) , OTA update (TWRP persist), & also it can root within itself.
The root is achieved with Magisk 17.1, no need to flash any encryption disabler or anything, it simply works!!
I present you: [LR. Team] TWRP
Credits to original devs & authors, not me.
Download link by LR. Team: https://yun.baidu.com/s/1jj0NE1pqeF1ejiNAsm1qUw
Download password: jjfd
Mirror by me: https://www64.zippyshare.com/v/HQdMlIDX/file.html
Enjoy!!
Click to expand...
Click to collapse
this twrp support flashing to android pie pixel ex, cyberian os etc?
mustofal said:
this twrp support flashing to android pie pixel ex, cyberian os etc?
Click to expand...
Click to collapse
yes...
Thanks, works great, apart from
- Touchscreen works only after second start using power + volume up (as described by you already above)
- but ROOT does not seem to work under ... however it performs the Magisk v17.1. Installer without error.
- I noticed, that after startup, a 'decrypt data' passwort is requested, which I just cancelled away -> what is this used for and could it affect the non-rooting issue? - Do I need to format data first?
Figured out that it was all about formatting the data partition.
add turkish language ?
Work like a charme on my mi 5s plus. Thank you so much. Root work well too. I flashed with fastboot but It doesn't work. Than i tried to boot instead flash and It work well. Thanks again
_Ayhan_ said:
add turkish language ?
Click to expand...
Click to collapse
you can make a request to original devs... I'm only sharing....
Crescendo, pleeease give us more detailed instructions. Some of us are 'casual users' and have forgotten things. My last flashing was almost 2y ago
Crescendo Xenomorph said:
yes...
Click to expand...
Click to collapse
Regret i using this TWRP flash "RR-O-v6.0.0-20180222-natrium-Unofficial" i get "error 7" in TWRP but i flash "Viper-natrium-20171018-Coral-v3.1.1-Final-N" ROM it no problem... Any idea ?
How to install Xiaomi.eu ROM for Redmi Note 9S / 9 Pro India
We will release fastboot ROM versions until TWRP for curtana is released
TWRP for curtana is released.. so all next version will be for TWRP, not fastboot..
Steps to install our ROM for FIRST TIME from China ROM (All your data and files on internal storage will be deleted!)
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file HERE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 10min)
Steps to install UPDATE of our ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
- After reboot its done (first boot may take up to 5min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Xiaomi.eu ROM features
Based on China Stable / Weekly builds (except POCOF1, HMNote6Pro, HMNote8T, HMNote9ProMax, HMNote9Pro_HMNote9S)
Enabled search gesture (swipe up) on the desktop
3way reboot menu (in dev settings)
Dark Mode (Night Mode) for all devices (In the dev settings except 9.x/10.x)
Removed ads in MIUI system apps
Face Unlock for all devices
Vertical clock widget on lockscreen
Steps counter in Assistant screen
More shortcuts on left lockscreen
Wake up gestures
AI preloading option in MIUI Lab
Fullscreen gestures
Option to auto-expand first notification
Notifications priority settings
More edit options in Gallery app
Enabled MiDrive in File Explorer
Added landscape mode for SMS app
Sunrise/Sunset in the weather app
Google apps support integrated
Removed 5GHz region restrictions
Confirm dials from call logs
Morning report on alarm at morning
More apps supported for AOD notifications
More styles for AOD screen
Raise to wake gesture
AOD notification received animation
Default volume control stream toggle
Tap fingerprint sensor to wake toggle
More Camera features
Double tap to lock screen
Battery AI scenes
Allowed disabling specific system apps
Importing theme .mtz from zhuti.xiaomi.com via ThemeManager
No useless Chinese bloatware apps
More free RAM due to less background processes
Unified flat style app icons for both system and 3rd party apps
Advanced menu with color icons
No any Chinese character under the full system
Mi Video, Mi Music, Mi Browser: No any useless Chinese content
No possibility to re-lock bootloader accidentally with flash any xiaomi.eu release
Added real 27 languages translation made by Official MIUI Fansites and MIUI Fans
Added EU T9 dialer support
Added charging sound switch
Added Screen-OFF animation
Optimized GPS settings for EU
Optimized Battery consumption
Optimized RAM consumption
Added 3D Touch to MI5S 3GB RAM version
Added GSMalphabet into SMS app options
Added more icons grid layout 4x5, 4x6, 4x7, 5x5, 5x6, 5x7 (depends on device)
SafetyNet passed (Google Pay)
Play Store Certified
Deodexed
Added automated tasks in Security app
Added game speed booster
Added erase module (magic elimination) to Gallery photo edit options
Fixed low volume sound via headphone
Charging screen
And more, and more made by our 9 years MIUI mods experience.
Enjoy..
Bro,
I tried this method.
Command window force close in between.
Now my device is booting in fastboot screen.
Please help me
What to do
rohit1990 said:
Bro,
I tried this method.
Command window force close in between.
Now my device is booting in fastboot screen.
Please help me
What to do
Click to expand...
Click to collapse
You connect devices to computer in fastboot mode
-open Mi flash tool and flash official FW
I think it better to wait for twrp to release first and then all are become more easy to flash rom
@ingbrzy
What is the difference between this rom and indian rom which comes with the phone?
Please explain, i want to know.
Randsome said:
@ingbrzy
What is the difference between this rom and indian rom which comes with the phone?
Please explain, i want to know.
Click to expand...
Click to collapse
https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
ingbrzy said:
https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Click to expand...
Click to collapse
I got the phone with the global stable, can I use the method in OP?
sure..
Not Working
Please be carefull.
Version V11.0.1.0 causes an infinite reboot loop to Redmi Note 9s devices.
Version V11.0.3.0 or higher works fine.
What I idid:
- Installed all required drivers.
- Unlocked bootloader after waiting 168 hours.
- Downloaded ROM
- unzip ROM
- Ejecute windows_fastboot_first_install_with_data_format.bat
- It finish with 3 errors. The script try to install these files, but they are missing from the ROM:
- firmware-update/recovery.img
- firmware-update/logo.img
- firmware-update/multi_image.mbn
- After the script finish, the device reboots automatically.
After a time, the initial setup screen to connect to a wifi shows up... then after a few seconds it reboots.
It doesnt matter how many times you try, it alwais reboots.
It doesnt matter how many times I reflash. It just dont work.
I'm not the only one with this problem. There is more people reporting the same problem:
xiaomi.eu/community/threads/miui-11-0-stable-release.52628/page-98
Edit: Version V11.0.3.0 or higher works fine.
can you try install it on linux OS?
seems make_f2fs binary has an issue on windows install process.. so can not format userdata partition properly..
you can try to install this fastboot india global rom below
https://mifirm.net/model/curtana.ttt
After flashing the indian global ROM, the device works again.
It's recogniced as Redmi Note 9 Pro instead of 9S, but it works.
yeah you use fastboot rom right?
Remember do not select clean all and lock (which will re-lock your bootloader)
That's exactly what I did
Thank you.
DjXavy said:
After flashing the indian global ROM, the device works again.
It's recogniced as Redmi Note 9 Pro instead of 9S, but it works.
Click to expand...
Click to collapse
You can flash the global ROM (not india) via https://mirom.ezbox.idv.tw/en/phone/curtana/
This is the direct link to download the flashable rom: https://bigota.d.miui.com/V11.0.3.0...M_20200318.0000.00_10.0_global_991071324c.tgz
Released V11.0.3.0.QJWMIXM..
- Fixed bootloop after install..
Will we be able to pass from stable eu to developer eu (when it's released) without losing data?
Sent from my Redmi Note 9S using Tapatalk
There are no more dev global roms released.. Stables only..
Cant flash the rom. Only write boot and stop after this. Dont do anything more. Any idea?
Try to flash it under linux if you can. Execute linux_fastboot_first_install_with_data_format.sh with root privileges.
It should work, at least it worked for me.
GravityBox - all-in-one tweak box - Xposed module for devices running Android 11
Version 11.0.5 [R]
Version for JellyBean is available in this thread: https://forum.xda-developers.com/showthread.php?t=2316070
Version for KitKat is available in this thread: https://forum.xda-developers.com/showthread.php?t=2554049
Version for Lollipop is available in this thread: https://forum.xda-developers.com/showthread.php?t=3037566
Version for Marshmallow is available in this thread: https://forum.xda-developers.com/showthread.php?t=3251148
Version for Nougat is available in this thread: https://forum.xda-developers.com/showthread.php?t=3653953
Version for Oreo is available in this thread: https://forum.xda-developers.com/showthread.php?t=3739929
Version for Pie is available in this thread: http://forum.xda-developers.com/showthread.php?t=3908768
Version for Q is available in this thread: http://forum.xda-developers.com/showthread.php?t=3974497
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Introduction
The app utilizes Riru-EdXposed Magisk module which uses original Xposed Framework API created by rovo89.
!!!!!! WARNING !!!!!!
This module utilizes EdXposed Framework which is still in early development stage and may contain bugs or might not be fully compatible with the system of your Android device. I take no responsibility for any issues arising from using GravityBox with EdXposed and strongly recommend creating a full backup of your device before activating the module.
Requirements
- Magisk v21 or later
- Riru v23 or later (Magisk module)
- EdXposed Manager (Application)
- Avoid using Resource hooking support if possible (Can be disabled in EdXposed Manager settings)
Installation
This procedure assumes you have working Magisk installation.
1) Install Riru module in Magisk Manager
2) Install and run EdXposed Manager app and download Riru-EdXposed module v5.1.3.x or later (currently Alpha/Canary)
3) Install downloaded Riru-EdXposed module in Magisk Manager
5) Reboot and open EdXposed Manager app to check if EdXposed works and is active
6) Install GravityBox and enable it in EdXposed Manager
7) Reboot and profit
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Feature highlight
--- Lockscreen tweaks
--- QuickSettings tile management with additional tiles
--- Statusbar tweaks
--- Navigation bar tweaks
--- Pie controls
--- Power tweaks
--- Display tweaks
--- Phone tweaks
--- Media tweaks
--- Hardware/navigation key actions
--- GravityBox Actions - interface for 3rd party apps
--- Notification control (per-app notification LED/sounds/vibrations)
--- Fingerprint launcher
--- Advanced tuning of Framework and System UI parameters
... and many more
Compatibility
GB's main concept is to make most of the preference changes to be done on the fly without need to reboot a device to achieve custom-ROM like experience.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM.
It is very similar to a situation when you installed ROM built from source for Nexus to some Xperia device - it won't work.
GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source, and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win. They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 11 (AOSP)
- officially supports devices/systems it was developed and tested on
- Samsung, HTC, MIUI, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS MODULE WAS NOT EXPLICITLY DESIGNED FOR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
GravityBox [R] has been designed for and tested on
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Reporting bugs
If possible, please use Github issue reporting interface for reporting bugs.
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach logs that can be exported from EdXposed Manager app.
Real-time logging can be performed by using ADB: adb logcat -s EdXposed-Bridge
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that it will work flawlessly on yours.
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Preferred way is to use GitHub interface to fork your own copy of GravityBox, make changes and then send pull request against original repository.
Anoter way is to simply download this file: https://github.com/GravityBox/GravityBox/raw/r/GravityBox/src/main/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/r
If you're a dev and have some ideas for additional features, feel free to fork it, work on it and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/r/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are more than welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there are three premium features:
- Backup/restore of GB settings.
- Ultimate notification control
- Advanced Tuning
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- RikkaW for creating and maintainng Riru Magisk module
- solohsu & MlgmXyysd for creating and maintaining EdExposed Magisk module
- @frank93 for donating Pixel 3a for development
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @simmac for app icon
- @romracer for Motorola specific code contributions
- @firefds for Samsung specific code contributions
- CyanogenMod project
- ParanoidAndroid project
- Slim, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- ArthurHub for Image cropping library
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, Fatih Firinci, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/r/CHANGELOG.txt
Changelog 11.0.5 - 08/08/2021
- Lockscreen: added option to blur media artwork on lockscreen (thanks to robbins)
- Navbar: allow cursor control keys in gestural navbar
- Dialer: adjusted for compatibility with the latest Google Dialer
- Properly identify OnePlus 8T as device running OxygenOS ROM (thanks to F-i-f)
--- should improve compatibility significantly
Developed and tested on:
- Pixel 3a running Google OS
- OnePlus 7Pro running Oxygen OS 11
Current issues
- Display: Expanded Desktop - immersive modes not working
- Key actions: Home double-tap not working
- Lockscreen: Changed custom carrier text won't appear immediately
- Custom Battery indicator: stock battery may appear for a while after the reboot
- ... + potentially others mainly device/system variation specific
Removed features
- GPS and SlimKat tiles - location modes (battery saving/high accuracy/device) no longer exist in Android 11
- Audio Recording tile - background recording of audio not possible in Android 11
Download
https://github.com/GravityBox/GravityBox/releases/tag/v11.0.5_r
Settings
It is possible to restore settings that were backed up in GravityBox [Q]
Simply transfer "GravityBox" folder from internal storage of one device to internal storage of another device.
Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
- Keyboard app (e.g. Gboard) in order to be able to use "Volume key cursor control" feature
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.
Credits
@frank93 for donating Pixel 3a for developemnt
Commit history
Commit history for transition from 11.0.4 to 11.0.5
@C3C076
Mate, you did it. Congratulations.
Can't wait to try it out.
Really appreciate your efforts in bringing this to us 11ers.
Cheers
2021 is looking good! Thank you so much. Working flawlessly on my pixel 3a
@C3C076
THIS is the first gift I've received of the new year. Thank you, sir!!!
Now, that's pretty awesome!
And the January update from Google should drop soon as well.
Thanks a lot @C3C076!
Got my Github notification this morning about the [R] pre-release! Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems. Everything working perfectly fine! All I had to do was first disable GravityBox [R] in EdXposed Manager, and disabled Kirisakura AK3 (kernel) module helper in Magisk Manager. Upgraded to Android 11 with no issues at all, and everything system and root-wise seems to work perfectly fine. My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
Though I'm gonna play it safe and OTA each month, instead of factory image (sans "-w" flag) jumping. Gonna work my way up to the current firmware, then test out GravityBox [R] - thanks so much @C3C076! The fact that so many people like me have held off on upgrading to the latest Android version just based on your work should speak volumes! I'll report back once I'm able to actually play around with GB[R] some. The baby's starting to wake... :O
edit: my son rolled over, coo'ed, and faceplanted back to sleep <3
- Also should note, I was on Kirisakura 5.2.6 kernel before. Now on 6.6.0, all is well!
- Also wanted to note, SafetyNet was passing (with my current configuration) on 09-2020 build with no further modifications necessary. I just finished updating up to 12-2020, and SafetyNet is still passing . Activating GravityBox module now, and will further report back!
edit 2: Seems verrrry stable so far! The only thing I found that didn't work properly (or rather, worked 80% correctly) was for an option that I don't even normally use, and accidentally toggled, haha. Under QuickSettings management -> Tiles per header, each option works fine, but when selecting 8, it still only shows 7.
Other than that, at least as far as the options that I personally use, everything seems fine! I didn't get a chance to test out every function affected by my set of GB options in such a short time, of course, but I will certainly report if there are any issues. And of course I won't list every single option I ticked off, but attached is my backup file / preferences of my current config for anyone who may be curious. Again, keep in mind that compared to the vast functions GB offers in totality, I only use what I use so of course I can't account for the entirety of GB. But from what I've tested so far, it seems damn stable and this has made my transition to Android 11 pretty much seamless!
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
i5lee8bit said:
Just now updated my Pixel 4 XL from 08-2020 (Android 10) to 09-2020 (Android 11) using my keep root / seamless update method with no problems.
[...]
My current running list of Magisk / Xposed modules: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84193393
(I'm hoping @Ghisy finds this helpful, hehe)
[...]
Activating GravityBox module now, and will further report back!
Click to expand...
Click to collapse
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Ghisy said:
Ha, thanks!
I'd be interested in your seamless update process if you don't mind sharing! Although I might go the image (sans -w) route instead.
Not sure I'll update until the week-end, I don't have much time on weekdays.
Click to expand...
Click to collapse
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
i5lee8bit said:
see my edit above =)
But I also wanted to separately post a big finding of great news (at least for me)! - The volume key cursor control option now seems to persist through reboots, without needing to toggle the option again after reboots! Not sure, tbh, if this was fixed on [Q] already due to / as a side effect of the big Riru / EdXposed updates, but at least I can confirm that it definitely works on [R] now as intended. Woohoo!
Also @C3C076, donated an extra $10 USD via PP (20485146561217901). You're already very generous for enabling Family Library, and this should cover for installing the unlocker on my backup/secondary Android devices as well as my wife's phone. I also figured it would be better to donate via PP than disabling Family Library and purchasing again from Play Store, assuming higher fees from Google.
Click to expand...
Click to collapse
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
i5lee8bit said:
see my edit above =)
Click to expand...
Click to collapse
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
If I can share my experience. I applied standard system update procedure from settings being on Pie (had it on your pixel to bring update for GB for Pie). This went without uninstalling magisk etc. I simple went incrementally from Pie through Q up to R and then several security update. Only after I was in the latest update I grabbed boot.img from corresponding system image, patched it using magisk and then flashed using fastboot. All apps and settings were preserved from Pie.
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
frank93 said:
thanks. sounds about "right", your last step is basically what i’ve been doing as well previously (the "system update" never worked for me though, but i didn’t care too much). there must be something fishy going on with my device then. i’ll try again soon.
(in the end i wouldn’t even mind being without root for a few bootups inbetween, so .. i’ll flash the stock boot image and try booting android 11 then. if it works, i can try getting back root just as well afterwards i guess.)
Click to expand...
Click to collapse
Yeah, note that I never flashed full rom image. I went using standard system update from settings. In the end it was only patched boot.img I flashed.
okay, apparently not even a "real" firmware update (using the original stock boot image) works for me. loops back to bootloader 2-3 seconds after the google-logo. so i guess there’s something else wrong with my device/system.
i’ve "updated" back to the latest/last android 10 for now (there the firmware upgrade/downgrade works!?), and i’ll scratch my head another time i think. thanks for your input though!
i5lee8bit said:
and @Ghisy, I'll send you some more details when I get a chance, certainly well before the weekend. Though if it's any consolation, in total the actual updating process only took me about an hour, if not less! Probably took me more time to actually download the files and prep, lol. XD
Click to expand...
Click to collapse
Thanks, I appreciate it! You took one for the team and shared interesting info too! *(air) high five*
C3C076 said:
Thanks. Your support is very much appreciated. Too kind. Interesting find about volume key cursor control. As you can see in the 2nd post I listed it there as currently not working . Looks like I'll have to take a look again. Do you use whitelist (App list mode enabled in EdXposed settings) ?
Click to expand...
Click to collapse
I use App List mode, but not White List mode, as I use the Pass SafetyNet option (so basically on Blacklist mode). Because I also have GPay working and all (I've linked to that thread before, it's the one I linked with my list of active modules). Hahaha, I didn't even realize you put in the 2nd post about it not working - weird! Definitely working for me though, using these current configurations.
frank93 said:
would you mind sharing your upgrade procedure from android 10 to 11 though? i’m not sure why, but my "usual" procedure (using the complete firmware, patching the boot.img, flashing everything including that boot-image afterwards) fails with all of the android 11 images. :/
(feel free to directmessage if you think it’s off topic here of course.)
Click to expand...
Click to collapse
Since I'm sure others may find it useful, I'll post it here. Also, @C3C076 may find it useful to follow this concept, assuming things are similar for Pixel 3a (I've been a long time HTC user, up til U12+ and only then switched to Pixel phones, 4 for wife and 4 XL for me to be exact).
My firmware update procedure is basically predicated on restoring the stock boot and dtbo (dtbo in case custom kernel flashed) images for your current build, which restores the stock firmware (and therefore recovery) and "unroots" / stock-ifies the phone without removing any of your Magisk or EdXposed configs, which allows you to simply boot into recovery and apply (sideload) OTA zip from stock recovery. Before booting back into system after OTA flash, reboot back into bootloader and flash the new build's Magisk-patched boot image, and when you boot up into system, voila, seamless, intuitive, and relatively safe update to new firmware version. Worst case scenario, if you bootloop you just flash the stock boot image (or even better, a modified Magisk Core Only boot image) and fix whatever is causing the problem.
Here is a link to my guide for September 2020 build, which was the first Android 11 build. There's a bunch of additional notes due to the major update at the time, though some of the info is a bit outdated. I assumed everyone at the time was on a very specific versions of firmware, Magisk, EdXposed, and even modules, etc. But if you read, especially the 2nd post, you can certainly understand how it all works and how we could apply the process from any firmware version. Here's the thread: https://forum.xda-developers.com/t/...0-009-coral-magisk-stock-boot-images.4160787/
- I recommend giving the procedure a read, as you should be able to understand the intuition behind the process I use.
As we're already (assuming) on latest Magisk, Magisk Manager, EdXposed, Riru, etc. etc, we don't need to worry as much about compatibility of our installed modules before OTA'ing. So basically, I condensed down what needs to be disabled, in my case, to the old GravityBox module (obviously), and the old Kirisakura (my kernel on Q) kernel helper Magisk module. You would also want to disable any modules, Magisk and EdXposed, that may not be compatible with [R] yet.
So here was my update procedure, from here on, coming from August 2020 build already on Magisk 21.2 and up to date EdXposed / Riru / etc. modules - SPECIFICALLY FOR PIXEL 4 XL "CORAL"
(OPEN THE "SPOILER" TO VIEW!):
Spoiler: Pixel 4 XL (and by extension and intuition, hopefully other Pixel series) keep-root / updating guide-procedures
NOTE: The files I provide are specifically only for Pixel 4 XL!! You will need to obtain the correct files for your own device to follow this procedure, but the same idea should be able to be applied!
First, I downloaded the boot and dtbo file(s) for Aug. 2020 thru Dec. 2020 builds. Here's a link to my AFH uploads for these files: P4XL Boot / DTBO files
Then, I patched each month's boot image with Magisk 21.2, and put them to the side.
There's only stock dtbo.img for 08-2020 because dtbo will remain stock throughout the updating procedure, fyi.
Actually, hell, for Pixel 4 XL "Coral" users, to make your life extremely easy, I've uploaded all the files you'll need to follow this here!! - LINK HERE
And OTA files from Google servers: LINK#2 HERE
Disabled GravityBox [Q] module in EdXposed Manager / Uninstall GravityBox [Q]
(Don't bother installing GravityBox [R] yet)
Disabled Kirisakura AK3 Kernel Helper module in Magisk Manager
(you'll also want to disable any modules that potentially may not work with [R])
-- Reboot once to finalize disabling the modules --
(Don't boot back into system until this section is done, to ensure all root, settings, mods, etc. are retained - this is basically the 2nd post of the September guide I linked earlier)
- Reboot into Bootloader mode -
fastboot flash boot 08-boot.img
fastboot flash dtbo 08-dtbo.img
(these steps revert recovery to stock)
- Reboot into Recovery mode-
(when No Command / Android icon shows up, hold power button and tap volume up to get to recovery menu)
Choose option: Apply update from ADB
adb sideload (09-2020 OTA zip).zip
after OTA zip flash completes, REBOOT BACK TO BOOTLOADER
fastboot flash boot 09-patched.img
- NOW REBOOT INTO SYSTEM! -
When your phone boots back into Android (11), you will be rooted, with all mods and settings retained. And if you passed SafetyNet before with the right combination of mods and settings, it should still pass now. While you can, I wouldn't yet bother installing GravityBox [R] quite yet. Let's first continue to incrementally upgrade until we're at 12-2020 (or 01-2021 depending on when you're reading this). Basically, just make sure the Android System Update notification (sorry, I don't remember exactly the notification label, but you'll know when you see it) indicates the update completed before proceding.
Now we just repeat my OTA update procedure again, except no need to flash stock dtbo images, as we're not doing anything (like flashing custom kernel) in this short amount of time that modifies the dtbo partition.
Reboot into bootloader mode
fastboot flash boot 09-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (10-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 10-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 10-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (11-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 11-patched.img
Boot to system
Allow time for the system update notification to indicate update was completed.
Reboot into bootloader mode
fastboot flash boot 11-boot.img
Reboot into recovery mode
Apply update from ADB
adb sideload (12-2020 OTA zip).zip
Reboot to bootloader
fastboot flash boot 12-patched.img
Boot to system
EDIT: Google released January 2021 firmware update, literally minutes after (or maybe while??) I was posting this! Here is my January 2021 easy update guide for Pixel 4 XL: https://forum.xda-developers.com/t/...5-003-coral-magisk-stock-boot-images.4213263/
Allow time for the system update notification to indicate update was completed.
Install GravityBox [R], activate module, reboot one more time, have fun!!
Also install custom kernel or whatever else you might need to do as well.
To be honest, I kinda rushed this post, so I'll re-read it later and make sure I didn't make any little mistakes. But hopefully if you read my guides threads and stuff (like, actually read it), the entire concept should be very clear and intuitive to you! Assuming other Pixel phones (at least AB Pixel devices) have similar partitioning schemes, this should be very useful knowledge to have, as it makes updating to new firmware versions incredibly easy and low risk. Good luck, I hope this huge post helps some people / makes a better day for someone! =)
EDIT: @frank93, seeing your linked post, I see you have a Pixel 4a. Unfortunately you obviously can't use the exact files I provided / linked, but you should still be able to follow the same procedure. Just grab the OTA's, plus the full factory images, pull the necessary boot and dtbo files from the factory images, and Magisk patch the boot images for each month, and name / organize all the files and put them aside on your computer. You should still be able to follow my procedure, but with your files. I hope it works for you with no problems if you decide to try it!
Has anyone tried one plus 8t?
...aaaand Pixel January 2021 update just dropped
Awesome! 2021 is looking good! Donation sent! Keep up the awesome work bro! Working flawlessly on my Pixel 3xl
Version for Marshmallow is available here: https://forum.xda-developers.com/t/...zation-for-old-touchwiz-mm-framework.3372401/
Version for Nougat is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-n-framework.3692391/
Version for Oreo is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-o-framework.3749479/
Version for Pie is available here: https://forum.xda-developers.com/t/...-14-customize-samsung-oneui-24-05-20.3908114/
Version for Q is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-2-0-30-12-20.4044757/
Version for R is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-3-x-14-03-21.4212051/
Firefds Kit [ S ]
Xposed module for Samsung S devices.
Known working devices:
Galaxy S20
Galaxy S20
Galaxy S10
Features
The module has the following features:
Fake system status to Official
Custom advanced power menu options:
Power off
Restart
Emergency mode
Recovery (with custom text)
Download
Data mode switch
Screenshot
Switch User (when multi user is enabled)
SystemUI restart
Flashlight
Screen Recorder (requires Samsung screen recorder app installed)
Disable restart confirmation
Enable performing power menu reboot / power off actions only after unlocking secure lock screen (stock behavior)
Disable display of power menu when secure lockscreen is locked
Change default behavior of reboot to reboot to recovery
Replace Reboot to Recovery icon with system default restart icon
Enable call recording and call recording settings
Replace add call button instead of call recording and adding record by menu option
Clock Size option
Enable Call ID and spam protection option
Enable Screen Record tile and Settings options
Enable screen record while in call
Enable additional advanced hotspot settings option
Hide VoLTE icon in status bar
Hide persistent USB connection notification
Hide persistent charging notification
Enable block phrases in messages app settings
Enable native blur on notification panel pull down
Enable multi user toggle
Set max user value selector
Show seconds in status bar clock toggle
Show AM/PM for seconds on clock toggle
Show clock date on right of clock toggle
Add date to status bar clock options
Enable fingerprint unlock on reboot toggle
Enable biometrics unlock on reboot toggle
Add network speed menu to show network speed in the status bar
Data icon symbol selection (4G, LTE, 4G+, 4.5G)
Show Data usage view in quick panel
Double tap for sleep
Hide NFC icon
Disable Bluetooth toggle popup
Disable sync toggle popup
Disable high level brightness popup
Hide carrier label
Carrier label size selection
Disable loud volume warning
Disable volume control sound
Disable low battery sound
Screen timeout settings
NFC behavior settings
Auto MTP
Disable camera temperature check
Enable camera shutter sound menu
Disable call number formatting
Disable SMS to MMS threshold
Force MMS connect
Bypass exchange security (currently not working)
Disable signature check
Disable secure flag
Attention
This version was tested by the community and not by me, as I don't have an Android 12 Samsung device.
THERE COULD BE BUGS/CRASHES/BOOTLOOPS, but it's pretty stable.
Please upload any xposed logs when you encounter any issue. I can't help you without the logs!
Installation
To install this module you need the following apps and modules installed on your device:
Magisk v24.0 and above - https://github.com/topjohnwu/Magisk/releases
Option 1 - Zygisk
LSPosed Magisk Zygisk Release module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Option 2 - Riru
LSPosed Magisk module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Riru Magisk module v25.0.0 and above - https://github.com/RikkaApps/Riru/releases
Download
Directly from LSPosed Manager or from Github : https://github.com/Xposed-Modules-Repo/sb.firefds.s.firefdskit/releases
Source Code
https://github.com/Firefds/FirefdsKit/tree/S
Known Issues
A lot has changed since Android 11. Since I don't have an Android 12 device all tests have been done with various testers. THERE MAY BE UNKNOWN ISSUES!!
Some features are removed on purpose. Since GravityBox has been working on Samsung Oreo devices without much issues, I only implemented features that need special Samsung coding.
Reporting Issues
When reporting an issue, please include Xposed logs and screenshots if any. Reporting should be done through Github - https://github.com/Firefds/FirefdsKit/issues
External Libraries
The project uses the following libraries:
https://github.com/rovo89/XposedBridge
https://github.com/rovo89/XposedMods/tree/master/XposedLibrary
Samsung framework libraries which are used for compile only
EdXposed Whitelisting
Users who want to use EdXposed's whitelist feature should whitelist the following apps:
Android System - android
Call - com.samsung.android.incallui
Call Settings - com.samsung.android.app.telephonyui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.s.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
Credits
This module wouldn't have been here without the following people:
RikkaW - Creator of Riru Magisk module, which provides a way to inject codes into zygote process
@rovo89 - Creator of the original Xposed framework APIs
solohsu and MlgmXyysd - Creators of the EdXposed Magisk module and Installer that made all of this possible
@C3C076 - Creator of GravityBox Xposed modules, which I learnt a lot from
@wanam - Creator of the original XTouchWiz module, which this module is based on.
@topjohnwu - Creator of Magisk
@AbrahamGC - For the Extended Power Menu - Pie - Odex framework Smali guide
Big thank you to @m8980 and @ianmacd for testing countless versions and sending xposed logs
Telegram
Announcements and pre release versions - https://t.me/firefdskit
This is a moded version of Wanam's XTouchWiz:
https://github.com/wanam/XTouchWiz
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
okij said:
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
Click to expand...
Click to collapse
Thanks! This looks great! I'll add it to the next version
firefds said:
Thanks! This looks great! I'll add it to the next version
Click to expand...
Click to collapse
Thanks! I'm glad you like it and look forward to the next version.
IIRC Firefds Kit 11 uses the same icons (I have been using it until I switched to Android 12 two months ago), so you might use the new icons there too.
Thanks.
All my devices now bootloop with NoClassDefFoundError: com.android.systemui.BasicRune
Any chance we could add those whitelists to LSposed "Recommended"? Exactly the most important call recording check is missing.
Btw if LSposed 1.7.2 is installed, Riru can be uninstalled? -> looks like Sui uses Riru, so no switching.
In the end, I could leave Firefds enabled if I don't change anything, luckily call recording is on by default.
Thanks for the update for Android 12. Everything working good on my A52s 5g. Hope that one day you can add the ability to adjust the height of the navigation bar. That was available in the gravitybox app but there is no upgrade for 12 yet and not sure there will be which is why I've asked here... appreciate your efforts though.
Is there an easy way to fix bootloop in case something went wrong?
donkeyman1234 said:
Is there an easy way to fix bootloop in case something went wrong?
Click to expand...
Click to collapse
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me delete it worked and I didn't have to disable lsposed modules or the magisk
Kuba1996 said:
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me it worked and I didn't have to disable lsposed modules or the magisk
Click to expand...
Click to collapse
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
donkeyman1234 said:
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
Click to expand...
Click to collapse
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root without custom recovery?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
You can look at last post here and try do something like that. Mabye try in recovery choose "update from adb" and try erase with adb command (your directory: riru-core). Or try use this but I dont think it will work
[Tool][Aroma] Magisk Manager Recovery Tool V2.5
Warning: It's not a Magisk module! Description This is a Magisk module management tool that can be used in Recovery mode. It's based on Aroma Installer. You can manage almost everything in Magisk with this tool. You can manage installed modules...
forum.xda-developers.com
Kuba1996 said:
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root witchout custom recovery?
Click to expand...
Click to collapse
I used magisk patched AP file to root. There is no twrp for s22u.
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Also You can flash in odin patched ap and rest of file but with HOME_CSC not CSC
Check this:
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Had the same issue with my s22u. I reflashed through odin. Gonna try and flash this module again with magisk bootloop protector. fingers crossed.
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Hello,
Thank you for A12 update.
So nice to have your magic on this version.
I would also love to see the ability to adjust navbar, and the possibility to move cursor with buttons in navbar like in GravityBox.
For me, Force MMS to connect isn't working on BeyondRom 4.1.
Is it working for others ?
I am using LSPosed zygist latest version and safety net 2.2.1
nishantgupta107 said:
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Click to expand...
Click to collapse
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
doggydog2 said:
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
Click to expand...
Click to collapse
Yes, some os settings did get reset. Not sure why. But now I'll wait for a stable release (I have reflashed it now 5-6 times)
Arobase40 said:
You can install Magisk Bootloop Protector module...
It will disable Magisk modules when bootloop occurs.
Click to expand...
Click to collapse
Thanks. I did install, but it did not work, the phone kept rebooting, reflash was my last resort.
Bootloop
S10 plus UI 4.1 A12
LSPosed-v1.8.0-6482-zygisk