Related
Hey there, I'm proud to present the first dual boot project for the Galaxy J2 (all variants).
This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
So, first things first :
/*
* 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.
*/
Click to expand...
Click to collapse
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Code:
[B]Android
[/B]
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
[B]Windows (GUI)[/B]
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
Romname_dual.zip
would create a new
Rom_name_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/show....php?t=2491299
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads :
Click here to download!!
reserved
Update:don't work j2 prime
Not working on my J200y
erkin98 said:
Update:don't work j2 prime
Click to expand...
Click to collapse
Ya, it's actually for j2lte and j23g, i.e j200g/gu/h/f
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
OpenWatch OS:
Project OpenWatch is the initiative undertaken by BLOCKS, who came into the limelight for their modular smartwatch. The goal of this is to make an AOSP based fully open source OS (OpenWatch OS) so any smartwatch that can have AOSP builds or be ported to AOSP can have a fully functional Watch OS. We are already working to convert 3 prominent traditional roms to be compatible with smartwatches and their smaller screens.
We also want to give as many smartwatches as possible a central location to get TWRP and information on their devices so instead of having to look everywhere on the internet for information its all under one umbrella.
Tools Required:
Standard MTK drivers installer
https://goo.gl/PraJuZ
SPFlash Tool
https://spflashtool.com/
Harmony
List of confirmed working devices:
Kingwear KW68, KW88, KW88 Pro, KW98, KW99, KW99 Pro
Blocks Watch
Look Watch
Zeblaze Thor, Thor S
IQ I2
Diggro DI01
AllCall W1, W2
TWRP Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Here
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
InHarmony
List of confirmed working devices:
Diggro DI06
Older Diggro DI07
Lemfo LES1
TWRP Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Here
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
AntiHarmony
List of confirmed working devices:
Newer Microwear H2
TWRP Download: Here
TWRP Image Installer Download: Here
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt kernel (For now)
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open spflash tool
4. In the "Scatter-loading File" box choose the "MT6580M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch dock to the computer.
7. Plug your watch in and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Infinity
List of confirmed working devices:
Lemfo Lem7
Zeblaze Thor 4
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open the "SP_Flash_Tool_v5.1824_Win" folder and run "flash_tool.exe".
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch dock to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Unity
List of confirmed working devices:
Kingwear KW06
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open spflash tool
4. In the "Scatter-loading File" box choose the "MT6580M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch dock to the computer.
7. Plug your watch in and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Continuum
List of confirmed working devices:
Lemfo Lem5 Pro
Finow X5 Air
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open sp flash tool
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Expanse
List of confirmed working devices:
Zeblaze Thor Pro
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open sp flash tool
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
Wisp
List of confirmed working devices:
* X02S MT6580
* X01S Plus MT6580
TWRP Image Download: 3.2.2-0
TWRP Image Installer Download: 3.2.2-0
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Prebuilt Stock Kernel
Install Instructions:
If you have TWRP installed already:
1. Download the first link which is just the twrp image files
2. Copy the image file to your watch
3. Boot into twrp
4. Click install
5. Click install image
6. Navigate to the twrp image you copied over and select it
7. Find recovery in the list and select it
8. Swipe to confirm
9. Your done
If you don't have TWRP installed:
1. With your watch turned on, copy the file "TWRP_patcher.zip" to the /sdcard directory.
2. Turn off your watch.
3. Open sp flash tool
4. In the "Scatter-loading File" box choose the "MT6737M_Android_scatter.txt" file located in the "TWRP_image" folder.
5. Press on "Download".
6. Connect the watch to the computer.
7. Put the watch on your dock and wait until a green tick appears on the screen.
8. Pick up your watch and power it on. It will automatically boot to TWRP.
WARNING: the following step (9) will install the default boot.img for the stock rom of the device. If you have another rom installed, be sure to flash it after finishing this guide.
9. On the recovery, go to Install -> Install Zip and select the previously copied file "TWRP_patcher.zip"
10. Wait until it finishes and that's it!
S99
List of confirmed working devices:
Zgpax S99
TWRP Download: Here
TWRP Source Code: Here
Custom roms Download: Coming Soon
Kernel Source Code: Here
Install Instructions:
Load this scatter file
Turn off the watch
Press download only
Connect the watch via USB to the computer
Wait till the green checkmark
Unplug the watch and hold the power button until it boots up
Once booted replug in the watch
Do adb reboot recovery in a terminal to boot to twrp
Watch Bringup:
We are actively working on bringing up the following devices on aosp roms:
Harmony, InHarmony, antiharmony, s99, unity: Android 8.1
Infinity: Android 7.0
If anyone has a watch that would like to get a source built twrp on it please look at the contact us section. It must run full android aka not a mt2xxx
Timeline:
We don't have a timeline that is set in stone because this is all volunteer work but you can take a look at our current to-do/in-progress/done board here
The Team:
Carbon Rom:
@Myself5, @frap129
LineageOS:
@Alberto96, @jrior001, @forkbomb444 @deadman96385
Dirty Unicorns:
@jbats, @danjull
Independent devs:
@corvus, @CaptivateKing @iscle
Contact us:
We have a telegram support group for issues or if you would like to get your watch supported here
You can also PM here on xda if you don't/can't join the telegram
WWWWWWWWWWWWWOOOOOOOOOOOOOOOOOWWWWWWWWWWWWWWWW..! TWRP for watch..! Now that's coooooooool..!
This project looks really promising!
I wish I owned one of these watches, so If could play around with this.
Damm i was hoping for IQI I4 Pro support. Will it be in near future. :good:
Inverted version for DIGGRO DI06 (and others that feature an inverted touchpanel): https://www.androidfilehost.com/?fid=5862345805528050107
Device Tree containing all required changes: https://github.com/GearLabs/twrp_device_mediatek_inharmony
Is it worth while mentioning here that I managed to port an older version of TWRP to the Finow X5 AIR / LEMFO LEM5 Pro a few weeks ago? It's the 2Gb RAM version of the watch. It's over at RASC if anyone wants to have a look. CF
deadman96385 said:
Mine just in case
Click to expand...
Click to collapse
Well done I am very excited to see custom roms for android wear devices in the future hopefully with extra customization like what is present in feature rich roms like Ressurection remix and Aosp Extended.
Finnaly its live for the community
Awesome, cheers
Tutorial
Could someone explain step by step what to do for dummies like me ?
This project spawned out of an idea I had while working at blocks that we should open source some of the work we are doing so the community could benefit from it. Releasing twrp for these devices is just the first step, the primary goal of Openwatch is to get aosp roms on these watches that have been optimized for the smaller screen to replace the normally crappy stock os's. I will admit that there was twrps for a lot of these watches scattered around xda/roundandroidwatches but trying to find them was not an easy task and none of them provided source code to recompile the twrp. So we decided to make this project to put them all under one umbrella. On the note of the 2 different screen types this is the first time we are seeing it all the devices we have tested on so far work fine so if we can get a tester for the other variant we would be more then willing to make a version that supports it. We chose xda rather than round android watch because we all have more experience with it and it's historically been the centre of android development for most devices. We would be more than willing to work with you/others that are on roundandroidwatch just let us know our dev team is primarily rom devs from various rom teams, but also a few app devs. I think our work is coming off as a surprise because its one of the first times full android watches have gotten a lot of attention from xda/press. So people are excited about it especially with source built customs roms being a reality in the near future which was never really a thing in the past.
Is it expected to support a smartwatch with Snapdragon in the future?
deadman96385 said:
This project spawned out of an idea I had while working at blocks that we should open source some of the work we are doing so the community could benefit from it. Releasing twrp for these devices is just the first step, the primary goal of Openwatch is to get aosp roms on these watches that have been optimized for the smaller screen to replace the normally crappy stock os's. I will admit that there was twrps for a lot of these watches scattered around xda/roundandroidwatches but trying to find them was not an easy task and none of them provided source code to recompile the twrp. So we decided to make this project to put them all under one umbrella. On the note of the 2 different screen types this is the first time we are seeing it all the devices we have tested on so far work fine so if we can get a tester for the other variant we would be more then willing to make a version that supports it. We chose xda rather than round android watch because we all have more experience with it and it's historically been the centre of android development for most devices. We would be more than willing to work with you/others that are on roundandroidwatch just let us know our dev team is primarily rom devs from various rom teams, but also a few app devs. I think our work is coming off as a surprise because its one of the first times full android watches have gotten a lot of attention from xda/press. So people are excited about it especially with source built customs roms being a reality in the near future which was never really a thing in the past.
Click to expand...
Click to collapse
Thanks for the PM and sorry for causing any issues with my earlier posts.
It was not my intention to be so reactive.
We all have the same goal so I am seeking a way for us to work together.
Again - apologies for the previous posts.
Cheers
Pablo
mega-samu said:
Is it expected to support a smartwatch with Snapdragon in the future?
Click to expand...
Click to collapse
The base support is there, any watch that can boot aosp roms can use the Openwatch code. So watches with snapdragon would need to be brought up like phones or any other device.
Status update
So since we launched we have gotten quite a bit of activity from various developers and because of that, we have added support for a number of new devices. We are focusing on getting the changes to the OS done so we can start releasing alpha builds to the community.
Infinity:
List of confirmed working devices:
Lemfo Lem7
Zeblaze Thor 4
Source built twrp is up and running
Preliminary source built aosp is up and running
Tested by @iscle
Unity:
List of confirmed working devices:
Kingwear KW06
Source built twrp is up and running
Source built aosp has not been started
Tested by Yours truly
Continuum:
List of confirmed working devices:
Lemfo Lem5 Pro
Finow X5 Air
Source built twrp is up and running
Ported aosp up and running, will now work on source built
Tested by @CerebralFlex
Preview video of the ported rom on Continuum:
I would just like to say thank you all for doing this. Got a zeblaze Thor pro begging for a custom ROM
sephiroth555999 said:
I would just like to say thank you all for doing this. Got a zeblaze Thor pro begging for a custom ROM
Click to expand...
Click to collapse
Could you join the telegram group in the 2nd post, so we can see about supporting the zeblaze thor pro?
I will believe that open watch OS will support Bluetooth calling feature and steady connection.
What about supporting IOS IPhone devices I believe too.
Great idea look forward, I will support you guys
First...what a fantastic idea. Thank you!
I have been chatting to one of the admin over on Telegram, as I own a Smartwear H2 with MTK6580, 1GB Ram and 16GB storage. Unfortunately the Harmony/Inharmony TWRP does boot on the H2 and is correct orientation on the screen (unlike the one over on roundwatches) but the touch screen is unresponsive. The admin over on telegram tried to extract defconfig from the kernel for support, but has not found it possible at the moment. I have therefore emailed Microwear to see if they will provide this information/file.
By the way...the H2 TWRP Recovery over on roundwatches, the touch screen does work...but for some reason the screen and touch is inverted. Screen is upside down, and x/y axis reversed, so to press a button displayed at the bottom of the screen you have to press the top of the screen.
I have emailed Microwear about this too...as it could be they have changed components through production.
Good luck with the project! hopefully I can join the fun.
Yep, you need a recovery for the hehui screens.
We only have the early screen type so it has changed and no longer works.
I will supply the group with the HEHUI stock boot and recovery images for the H2.
Cheers
Pablo.
Sent from my BLA-L29 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:28 PM ----------
Here are the files that you need
https://goo.gl/i74K6F
Sent from my BLA-L29 using Tapatalk
UPDATE - Pixel Experience Official is out for Kenzo. Link attached below. Ongoing support for GSI users though.
https://forum.xda-developers.com/redmi-note-3/development/rom-pixel-experience-t3835648
-------------------------------------------
Disclaimer: I'm not responsible for bricked devices, flash at your own risk. I might be able to help with restoring your device though.
This is a guide to installing Android GSI on Redmi Note 3 (Kenzo)
---------------------------------------------------
What works-
RIL
GPS
Camera
Pretty much everything
What doesn't work-
Bluetooth
Hotspot
VoLTE(I couldn't test)
(NOTE - Bugs vary GSI to GSI)
---------------------------------------------------
Required files -
Grab these files first, and keep them on your SD card
TWRP Treble - https://androidfilehost.com/?fid=5862345805528059847
Android GSI(USE ARM64 A-ONLY) - for this tutorial, I'm using Phhusson's AOSP Pie GSI found here - https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
List of GSI's - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Pie GApps (If using Pie GSI) - https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141
Vendor Image - https://androidfilehost.com/?fid=1322778262903993757
Permissive SELinux Enabler - https://drive.google.com/file/d/1KFdPH2JGtvkXwt2emxPb-k7zdv2pLd-F/view?usp=drivesdk
Magisk 16.7 (minimum 16.7, you can use 17 as well)- https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Latest Firmware - https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361/page176
Optional - Digital Well-being (ONLY FOR PIE)
Digital Well-being apk (Download latest version) - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
Digital Well-being Magisk Module - https://drive.google.com/file/d/1AAFMWbAAK-febiP9h4iZMJONEHXopmEU/view?usp=drivesdk
--------------------------------------------
Assuming you have an unlocked bootloader, and know your way in and around Android, let's begin!
How to install -
1. First, flash the Treble enabled TWRP.
2. Reboot to recovery.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file and immediately flash the Permissive SELinux Enabler.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
8. Reboot to System.
9. Reboot to recovery.
10. Perform a factory data reset, and flash GApps
11. Reboot to System, and complete setup.
12. After completing setup, reboot to recovery and flash Magisk 16.7
13. Reboot to System
14 Reboot to recovery and flash firmware.
15. Profit!
If you want Digital Well-being (ONLY FOR PIE) -
16. Install Digital Well-being apk
17. Flash Digital Well-being Magisk Module through Magisk Manager
18. Reboot
19. Profit!
-------------------------------------------------------
Tested on Snapdragon version, don't know if it works on MTK.
Screenshots are attached.
Fixes -
If you have the QS toggles moving out of the header like the screenshot attached in #1, do the following steps
1. Enable Developer Settings,
2. Find Smallest Width setting
3. Increase the value by 20. (If it's 360, make it 380)
4. Profit!
------------------------------------------
Google Camera + Face Unlock fix.
If Google Camera/Face Unlock doesn't work for you, do the following -
1. Reboot to recovery
2. Mount system
3. Flash the zip file (download link below)
4. Clear cache
5. Reboot to system
This should make Face Unlock work again, and GCam work as well.
Download patch - https://drive.google.com/file/d/17OUBxhsfeK0625_pYe8aRNr5L6doKdAK/view?usp=drivesdk
------------------------------------------
Can't find Smart Lock in settings?
1. Go to Settings < Security and Location.
2. Scroll down and click Advanced.
3. Click Trust Agents.
4. Switch on Trust Agent for Smart Lock.
You should now have Smart Lock option below Fingerprint.
-------------------++++++++++++++++-----------------------
For Changing accent colours -
Download this file - https://t.me/kenzousersglobal/1169
1. Flash it in recovery
2. Reboot to system
3. Go to Settings - Display - Advanced. Scroll down to find "Colour Theme"
4. Select colour theme and select colour of your choice.
5. Profit!
---------------------------------
Custom kernels that currently work
Radon - https://drive.google.com/file/d/1LYggpHDVph1fvWctIKY4FqQwtRb6Svh0/view
---------------------------------
Review - after extensive testing, I found this to be daily driver material, with the only exception being Bluetooth, Hotspot, and VoLTE(I couldn't test it myself)
Special thanks to - @corkiejp
Is it possible to get an Overlay Patch for Mi 8?
NielsvdS said:
Is it possible to get an Overlay Patch for Mi 8?
Click to expand...
Click to collapse
I honestly have no clue. I have only gathered all the patches and files for Kenzo and made them into one guide.
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Work on kate devices?
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
sharan565 said:
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
Click to expand...
Click to collapse
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
corkiejp said:
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
Click to expand...
Click to collapse
Thanks man I will try
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
Click to expand...
Click to collapse
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
wxtester said:
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
Click to expand...
Click to collapse
1. You just need to make sure that all partitions are mounted.
2. You can restore the backup through Treble TWRP.
Happy flashing!
Hexvessel1992 said:
Work on kate devices?
Click to expand...
Click to collapse
I don't know, I need someone to test it. It should work, since the Vendor for Kenzo and Kate are the same.
corkiejp said:
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Click to expand...
Click to collapse
I'll update the thread with the right link
I think it is possible to dirty flash Open Gapps, but it might give bugs, always go for a clean flash
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
srishant said:
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
Click to expand...
Click to collapse
I had to forage through 4 complex guides, scourge through XDA and Telegram for all the patches, and hence could make such a simple guide. Apparently, devs on the Telegram channel are working on the Bluetooth and VoLTE fix I'll update once that happens!
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
amog787 said:
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
Click to expand...
Click to collapse
I did see that, but when I flashed it, it messed upy system and I had to reinstall the GSI. I don't know how to modify it for Treble, could you do it? I'm happy to test. I believe that fix is for Flashavle ZIPs, not for Treble GSIs.
Possible Gcam and stock working patch!
Posted this in AOSP Pie Rom thread, may also work for the GSI?
corkiejp said:
I found Gcam Pie Fix for another device in this thread.
Link to Gcam Pie Fix: - https://drive.google.com/file/d/1D5qvlA-QbQu6xoWpsLPyWquMkS3hxXi3/view
Gcam that I'm using: - https://androidfilehost.com/?fid=673956719939833577
^^^ From this thread, maybe newer versions available.
I was able to setup face unlock after flashing the above fix, you may also need to enable Smart Lock (Google) as a trusted agent.
It is buggy and the face option may not always trigger, plus you need to hold the phone far from you and swipe when the lock symbol appears (no fast unlock options xposed).
Another benefit of flashing another Camera (V 2.0.002) Started working as well. (Don't know if that is the default AOSP camera or something I restored from backup? Could be Snap Camera from LOS).
Click to expand...
Click to collapse
corkiejp said:
Posted this in AOSP Pie Rom thread, may also work for the GSI?
Click to expand...
Click to collapse
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Sid127 said:
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Click to expand...
Click to collapse
Not that I'm aware of, but this just places/replaces some Lib and Lib64 in system partition.
If your worried about it, back up your system partition, flash the this patch and wipe caches.
If you experience problems, just restore your system partition.
It was reported working by someone else here.
Code:
* Disclaimer
* 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 blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
HOW TO ROOT XIAOMI REDMI NOTE 6 PRO
Pre-Requisits
-Unlocked Bootloader
-Have a PC
This is an in general type to tutorial. You are expected to be able to understand some aspects of rooting an android phone
IF YOU ALREADY HAVE DEVELOPER OPTIONS ENABLED SKIP THIS PART
-Go to settings
-About Phone
-Tap MIUI Version 7 times until you get a floating notification that says "You are now a Developer!"
-Go back to main menu and go to additional settings
-Developer options
-Have USB DEBUGGING ENABLED
DOWNLOADS
-Download The latest stable Magisk https://github.com/topjohnwu/Magisk/releases/ Magisk-vXX.X.zip (You might want to do a quick check that the current version has no major bugs.)
-Download The latest version of Orange Fox recovery https://files.orangefox.tech/OrangeFox-Stable/tulip/ OrangeFox-RXX.X_XX-Stable-tulip.zip
-Download ADB-Platform tools https://www.xda-developers.com/install-adb-windows-macos-linux/
-Download the lastest LazyFlasher from https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
-Once you have all your files downloaded copy the folder in OrangeFox called sdcard to your sd. Put the magisk.zip and the no-verity-opt-encrypt.zip files in there aswell. Put the sdcard back in your phone
-Power off phone
-Boot to bootloader(Power + Volume Down)
-plug phone into computer
-open PowerShell and navigate to where your OrangeFox folder is using the cd command.
-
Code:
fastboot devices
Make sure there is something that show up for this
-
Code:
fastboot flash recovery recovery.img
-
Code:
fastboot boot recovery.img
or
Code:
fastboot reboot recovery
-Once OrangeFox is loaded navigate to the folder you put on your sd card previously
-Flash the zip called OF_initd.zip
-Navigate to menu tab -> Restart -> Recovery
-At this point your phone will have Orange Fox installed.
-Once OrangeFox is loaded navigate to where you placed your magisk.zip file
-Flash it
-Go back and flash no-verity-opt-encrypt.zip
-Navigate to menu and reboot to system
DONE!
worked !! thanks!!!
You're too early for the guide ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OrangeFox 11.1(1) UNOFFICIAL
———————————————————————
Based on: TWRP 3.6.2 (Android 11) | Author: iusmac | Kernel: 4.9.309
Summary:
Code:
Decrypt any Android and any encryption method (FDE or FBE) + Original features
*** DISCLAIMER ***
Code:
Your warranty is now void.
We're 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 recovery
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
Installation:
Spoiler
Using recovery:
Spoiler
1. Download the OrangeFox .zip file to your device
2. Boot into to an existing recovery
3. Install OrangeFox .zip file
4. The recovery should reboot automatically into OrangeFox
5. Enjoy!
Using Fastboot:
Spoiler
1. Download the OrangeFox .zip archive to your device and .img image to your PC
2. Connect your device to PC and enter into Fastboot Mode
3. Flash .img using the following commands:
Code:
fastboot erase recovery
fastboot flash {put-here-orangefox-recovery-file-name}.img
fastboot boot {put-here-orangefox-recovery-file-name}.img
4. After the last command your device should boot into OrangeFox
5. Install OrangeFox .zip archive
6. The recovery should reboot automatically
7. Enjoy!
Stock Features:
Spoiler
* Supports Treble and non-Treble ROMs
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Password protection
* Torch and LED
* Support for custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine allows to set: custom scheme/theme (black, dark, etc)
* Gesture navigation
* Backup OrangeFox settings to internal storage or SD card
* And many more!
New Features (added by author):
Spoiler
Spoiler: 1. FBE Encryption Toggler (FBE = File-Based Encryption)
Spoiler: How to Enable/Disable FBE Encryption
* Make sure that the "Enable FBE" button has changed to "Disable FBE" (or vice versa if disabling)
How it works:
Formatting is needed to erase all traces of full disk encryption (FDE) + we need a completely new file system (recovery will take care of this). Immediately after that, the recovery switches encryption type to FBE in the ROM's vendor.
Spoiler: What is this? What is it for?
Some definition:
Android 7.0 and higher supports file-based encryption (FBE). File-based encryption allows different files to be encrypted with different keys that can be unlocked independently.
https://source.android…/encryption/file-based
Click to expand...
Click to collapse
What does FBE encryption look like?
Spoiler
1. The contents and names of files/folders are encrypted using random characters:
2. Upon system startup, the device is absolutely usable and does not require to enter a password. FBE decryption is bound to Lock Screen and occurs at the time of unlocking using PIN/Password/Pattern.
At the time of writing this post, 100% of our devices use Full Disk Encryption (FDE). Traditionally, FDE encryption is enabled inside ROM's settings, and personally, I did not encounter problems with this type of encryption before Android 10. Unfortunately, on new Androids FDE is very unstable. Moreover, in Android 13 (T) it will be possible to encrypt only using FBE method because FDE method is officially deprecated and will be completely removed.
Android T (AOSP experimental) removes support for full-disk encryption entirely.
https://source.android…y/encryption/full-disk
Click to expand...
Click to collapse
Some FDE issues on Android 10+:
1. The device hangs on boot logo (requires formatting of /data to fix).
2. The device may boot up successfully and be detected as encrypted, but most of the installed applications and settings disappear forever.
3. The device boots correctly but is not detected as encrypted.
Having tried a bunch of ROMs, I have never encountered the problems above and have always been able to successfully encrypt the device with FBE method. Therefore, if you are interested in encryption, accustom yourself to encrypt immediately after ROM flashing, since everything is quite handy
Warning: decryption on Android 12+ and workaround | FIXED in OrangeFox R11.1(4)
Spoiler
FIXED in OrangeFox R11.1(4)
Unfortunately, all ROM's on Android 12+ for our device can successfully be encrypted/decrypted using FBE method, but decryption in recovery is problematic. This is an Android bug, which doesn't expose the decryption keys used by the recovery. Indeed, this is a recovery problem; Android 12 stores decryption keys elsewhere, so recovery can't find them. OrangeFox / TWRP devs are already in the process of adapting to the changes of Android 12. As soon as new recovery is ready I'll build a new release and everything will work. Fortunately, I found out that passwordless decryption works.
Temporary workaround:
1. Reboot to ROM
2. Remove the Lock Screen protection (PIN/Password/Pattern)
3. Reboot to recovery, the data will be automatically decrypted
4. When you're done, reboot to system and enable Lock Screen protection again
Note: you'll need to do this until the ROMs fix the decryption keys related issue.
If you don't remove the Lock Screen protection, then instead of the data you will get:
Spoiler: 2. GUI implementation for USB Storage Exporter by 0xCAFEBABE
This is a GUI implementation of usb-stor-export.sh script for geeks.
For the folks, I implemented a way to export entire eMMC memory. How to use this:
1. Disconnect from PC if connected
2. Go to Mount and swipe the slider
3. Connect the device to the PC
4. Your PC should detect a 16/32GB device, as if you connected an external hard drive
Now, all partitions are at your disposal. You can resize them to add to /data , or make an image of the entire eMMC memory (highly recommend) or backup a specific system partition and restore even on another device. Backup using recovery will not do this to you.
(!) DO EVERYTHING AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR YOUR ACTIONS ON SYSTEM PARTITIONS!
(!) EVEN IF YOU HAVEN'T TOUCHED ANYTHING, ALWAYS UNMOUNT THE DISK FROM THE OS AND ONLY THEN TAP "Unexport".
Spoiler: 3. eMMC Lifetime Used indicator
It displays life time estimation for your eMMC memory. The percentage means how many reserved blocks have been consumed.
The status can be:
- Undefined = The kernel driver cannot detect eMMC memory state
- Normal = Your eMMC memory is fine
- Warning = Your eMMC memory consumed about 80% of reserved blocks
- Urgent = Your eMMC memory consumed almost 100% of reserved blocks
- Reserved = Your eMMC memory consumed all 100% of reserved blocks and will put itself in read-only mode very soon
For geeks: tap on it to print all HEX values to the console.
Spoiler: 4. Enter to Fastboot Mode inside recovery
This is a hidden feature of OrangeFox itself that I've simply exposed. Unfortunately, important commands like fastboot boot exit with an error, because we are still in recovery and things are kind of busy ... But for something not used/static, like flashing partitions, it's working.
Spoiler: 5. fastboot binary
Now, using OrangeFox's embedded Terminal you can do everything you normally did using a PC.
* If you made a male-to-male USB using an USB-OTG cable, then plug the USB-OTG into the device that will send commands.
Illustration: Xiaomi helps Asus
Spoiler: 6. Dark/Light Theme Toggler accessible from anywhere
This is to make sure your eyes feel comfortable
7. Ability to reboot into Fastboot Mode
8. Binaries: nano, tar, sed and xz utils
9. Support mounting of NTFS drives via OTG
10. Handy aliases (l, ll, la, lo) for `ls` command
11. Colorful support for prompt string (PS1) and for `ls/grep/egrep/fgrep` commands when using ADB/AromaFM
12. VIM - Vi IMproved Editor
13. UI rendering at 60 FPS
14. Support Python
15. Semi-transparent Lock Screen background as in stock TWRP
16. Saving screenshots in /tmp/screenshots if /sdcard is not mounted
Miscellaneous:
Spoiler
Spoiler: Error 7. Failed to unmount: /system. No such volume.
Sometimes got this error when flashing old ROM's of Android 9 and lower. To fix it:
1. Open .zip archive and search for file:
Code:
META-INF/com/google/android/updater-script
2. Open it and remove parts where /system is mounted:
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup", "/system");
unmount("/system");
also this one
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system");
unmount("/system");
3. Save it and repack .zip archive
Spoiler: Red/Blue lines after flashing
Can be fixed by installing a more recent Firmware.
For rolex | For riva
* Firmware for riva is also available on Android 8, so experiment. The Firmware V10.1.1.0.NCKMIFI (Android 7.1) works 100%.
Changelog:
Spoiler
-- OrangeFox 11.1(5) --
* Synced with latest OrangeFox R11.1 sources (September 2022)
* Correct FBEToggler button position in some circumstances
* Handle FBE encryption toggling on Android 13+
* Added fastboot support when rebooting to fastboot from OS
* Moved nano editor to ZIP to save space in ramdisk
* Revert back to /sdcard1 path for Micro SDCard mounting
* Disabled APEX
* Removed logcat binaries to free space in ramdisk
* Updated ueventd from Android 11
* Fixed mke2fs issues when wiping
Thanks to @wisanggeni aka Ervan Kurnia for collaborating
* Updated kernel to 4.9.326-2.2-iusmac
* Updated Magisk to v25.2
-- OrangeFox 11.1(4) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 12.1)
* Fixed ABX format conversion on Android 12 ROMs
* Moved not vital dependencies to /persist partition after flashing recovery using .zip archive
* Added a 'missing dependencies' pop-up at start-up with an invite to flash recovery using .zip archive
* Added full FBE decryption support for Android 12 ROMs
* Removed extra languages (Chinese, Spanish, Hungarian) to free space in ramdisk
* Added to the console an invite to downgrade the recovery for those who use FBE encryption and Android 11 or lower
-- OrangeFox 11.1(3) --
* Upgraded built-in Magisk to v25.1
* Fixed some bugs
* Added to the console an invite to update the recovery for those who use FBE encryption and Android 12 or higher
-- OrangeFox 11.1(2) --
* Replaced 'Percent' with % for eMMC Lifetime Used value
* Added 'Back' button to FBE Encryption Toggler page
* Added synchronization of the fstab encryption flag with the /data encryption type
* Added battery temperature next to CPU temperature
* Enabled OTA by default
-- OrangeFox 11.1(1) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 11)
* Upgraded Linux kernel to 4.9.309 (from Android 12)
* Upgraded built-in Magisk to v25
* Added nano, tar, sed, xz utils binaries
* Fixed Full Disk Decryption (FDE) on Android 12+
* Added File Based Encryption (FBE) support
* Added NTFS support for OTG devices
* Added handy aliases (l, ll, la, lo) for `ls` command
* Added colorful support for prompt string (PS1) and for `ls/grep/egrep/fgrep` commands when using ADB/AromaFM
* Fixed nano non starting on OrangeFox's embedded Terminal due to missing terminal info
* Added prebuilt VIM - Vi IMproved Editor v8.2.1643
* Added FBE Encryption Toggler to Partition Manager page
* Enabled reboot to 'Fastboot' item unconditionally
* Labeled /dsp partition as 'DSP'
* Moved MicroSD card mount point from /sdcard1 to /external_sd
* Added GUI implementation for USB Storage Exporter by 0xCAFEBABE to Mount page
* Added eMMC Lifetime Used indicator to Partition Manager page
* Add entering to Fastboot mode page to Main menu
* Added fastboot v29.0.6
* Increased UI rendering to 60 FPS
* Added Python v3.10.4
* Added Dark/Light Mode Toggler
* Made the lockscreen background semi-transparent as in stock TWRP
* Added support for saving screenshots in `/tmp/screenshots` if `/sdcard` is not mounted
* Removed Splash changing (it requires ramdisk repacking in recovery.img which exceeds bootloader limit)
Spoiler: (Important) Which OrangeFox version you should choose
CaseR11.1(3) or olderR11.1(4) or newerLatest versionMy ROM is not encryptedXI have an encrypted MIUIXMy ROM was encrypted using ROM's settingsXMy ROM is Android 11 (or lower) and it's encrypted with FBE methodXMy ROM is Android 12 (or higher) and it's encrypted with FBE methodX
Download latest OrangeFox release | Find all OrangeFox releases
OrangeFox 11.1(2) Update
Code:
* Replaced 'Percent' with % for eMMC Lifetime Used value
* Added 'Back' button to FBE Encryption Toggler page
* Added synchronization of the fstab encryption flag with the /data encryption type
* Added battery temperature next to CPU temperature
* Enabled OTA by default
Download latest OrangeFox release | Find all OrangeFox releases
OrangeFox 11.1(3) + OrangeFox 11.1(4) Update
Spoiler: (Important) Which OrangeFox version you should choose
CaseR11.1(3) or olderR11.1(4) or newerLatest versionMy ROM is not encryptedXI have an encrypted MIUIXMy ROM was encrypted using ROM's settingsXMy ROM is Android 11 (or lower) and it's encrypted with FBE methodXMy ROM is Android 12 (or higher) and it's encrypted with FBE methodX
Code:
-- OrangeFox 11.1(4) --
* Synced with latest R11.1 sources based on TWRP 3.6.2 (Android 12.1)
* Fixed ABX format conversion on Android 12 ROMs
* Moved not vital dependencies to /persist partition after flashing recovery using .zip archive
* Added a 'missing dependencies' pop-up at start-up with an invite to flash recovery using .zip archive
* Added full FBE decryption support for Android 12 ROMs
* Removed extra languages (Chinese, Spanish, Hungarian) to free space in ramdisk
* Added to the console an invite to downgrade the recovery for those who use FBE encryption and Android 11 or lower
-- OrangeFox 11.1(3) --
* Upgraded built-in Magisk to v25.1
* Fixed some bugs
* Added to the console an invite to update the recovery for those who use FBE encryption and Android 12 or higher
Download latest OrangeFox release | Find all OrangeFox releases
mtp mode not working in v11.1.4 in rolex
Hello, I have problem with booting recovery. After installing and booting into it that is happens
Max1mus said:
Hello, I have problem with booting recovery. After installing and booting into it that is happens
Click to expand...
Click to collapse
Solved this problem with installing via fastboot miui with android 7 onboard.
Max1mus said:
Solved this problem with installing via fastboot miui with android 7 onboard.
Click to expand...
Click to collapse
read the post better...
https://imgur.com/nuaM3DW
OrangeFox 11.1(5) Update
Code:
* Synced with latest OrangeFox R11.1 sources (September 2022)
* Correct FBEToggler button position in some circumstances
* Handle FBE encryption toggling on Android 13+
* Added fastboot support when rebooting to fastboot from OS
* Moved nano editor to ZIP to save space in ramdisk
* Revert back to /sdcard1 path for Micro SDCard mounting
* Disabled APEX
* Removed logcat binaries to free space in ramdisk
* Updated ueventd from Android 11
* Fixed mke2fs issues when wiping
Thanks to @wisanggeni aka Ervan Kurnia for collaborating
* Updated kernel to 4.9.326-2.2-iusmac
* Updated Magisk to v25.2
Download latest OrangeFox release | Find all OrangeFox releases
THE BEST RECOVERY FOR RIVA
#RECOMMENDED #1
Hello, does OrangeFox Recovery use Android 7.1 or 8.1?
liaotingwei said:
Hello, does OrangeFox Recovery use Android 7.1 or 8.1?
Click to expand...
Click to collapse
You need latest nougat firmware to run it.