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.
C A O S(Note, I did not make this rom. This is a Generic System Image (GSI) made by Caos' devs. so it is not specifically built for the A51, but it's really stable and I am using it now. ALL CREDIT GOES TO CAOS' DEVS!)
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. Pleasedo some research if you have any concerns about features included in this ROMbefore flashing it! YOU are choosing to make these modifications, and ifyou point the finger at us for messing up your device, we will laugh at you
CAOS (Custom AOSP OS) is a project which is based on @phhusson's Treble GSI AOSP 10. CAOS' devs began it because ASOP has stability, speed and support but also some issues and limitations - pure AOSP's code has some bugs and it doesn't have much useful things and it's hard to pull it. So CAOS' devs did this fork. System can run with SELinux enforced state, as an original Phh AOSP GSI. Fully compatible with PHH-Treble patches exclude few low level changes: no root app, no "su" binary in system; by default exist file /system/phh/secure (for Google Certification PASS), so if you can boot AOSP GSI, but can't boot CAOS - try to removing that file
UPDATE VERSION
latest build: 2020.10.29
treble patches: v222+
SPL: 5 Oct 2020
File Downloads/InstallationTHINGS THAT YOU NEED ON YOUR WINDOWS COMPUTER.
Odin
Unzip the file. There is a EXE file in it. Double click it to launch. There will be a pop up, just press ok.
FILES THAT YOU NEED TO FLASH THE ROM.The rom itself
Make sure you have 7-zip installed. Right click it and click extract files. Go into the unzipped folder and rename the file inside to "system.img"
TWRP Decrypter
Just leave this file as a zip. Don't unzip it.
ChonDoe Flasher
Just leave this file as a zip, Don't unzip it.
INSTALL RECOVERY AND UNLOCK BOOTLOADER (SKIP THIS PART IF YOU ALREADY HAVE TWRP.)I have made a reddit post on twrp. DO NOT DO THE MAGISK PART.
FLASHING THE FILESGo into TWRP. Press wipe and go into format data. Type in yes and wipe your data. Press the home button in your nav bar and go back into Wipe. Press advanced wipe, tick "data", "Dalvik / ART cache" and "Cache". Format it.
Press the home button in the nav bar again. Now, go into reboot and click recovery. Don't do anything. Once it's back into TWRP, plug your phone into the pc if you haven't already.
On your Windows PC, go into File Explorer, This PC, A515F and then internal storage. Take the "system.img" file and drag it into there. Do the same with "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and "ChonDoe_Flasher.zip"
Once all of them are copied, go onto your phone. Click install and you should see your files. If you don't, go into /sdcard. Flash "ChonDoe_Flasher.zip". Once it's done, flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip". Press "Reboot System" once "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" is installed.
If this looks really confusing to you, there is a tutorial for this. However, it's for HavocOS. But everything is the same except the rom. But the steps are the same. Watch it here.
Congrats! You have installed Caos!
CONTACTS
> telegram group
> project page
KNOWN BUGS:
• excluding fixes, the same as on AOSP Quack (in some cases doesn't work: broadcasting on TV, calls via BT; offline charging does not work normally fingerprint doesnt work; problems with GPS etc etc)
NOTE: always test ROM first without Magisk (with clean boot ramdisk). and don't send me bug reports if you have:
a) Magisk installedb) modified/custom vendor or kernelc) dirty flashing rom without wiping data
CREDITS
persons: @phhusson
projects: TrebleGSI • BlissROMs • crDroid • PixelExperience • ION • neon-OS • Havoc-OS • LineageOS • Evolution-X • LiquidRemix • ExtendedUI • GrapheneOS • abc rom
Hello there, I've never rooted a phone before but would love to try it with Android 12 finally coming out as stable on the OnePlus 8 Pro. So as a complete noob, can anyone walk me through it, or does anyone have a handy thread that takes me through all of it? Thank you!
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
dangtoi1993 said:
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
Click to expand...
Click to collapse
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
andylmfao said:
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
Click to expand...
Click to collapse
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
dangtoi1993 said:
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
Click to expand...
Click to collapse
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
andylmfao said:
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
Click to expand...
Click to collapse
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
xtcislove said:
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Oh wow, thank you! How do i flash it via fastboot?
andylmfao said:
Oh wow, thank you! How do i flash it via fastboot?
Click to expand...
Click to collapse
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
xtcislove said:
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
Click to expand...
Click to collapse
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
andylmfao said:
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
Click to expand...
Click to collapse
I hope it works for you now. Have fun.
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
paq1170 said:
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
Click to expand...
Click to collapse
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
omega552003 said:
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
Click to expand...
Click to collapse
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
xtcislove said:
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
Click to expand...
Click to collapse
Well that how yo'd normally do it, but for some reason when you do that on the OOS12 upgrade its get really weird.
xtcislove said:
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
Click to expand...
Click to collapse
Do you have C.20 version?
gzyms said:
Do you have C.20 version?
Click to expand...
Click to collapse
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Edit: That is the payload dumper im using.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
xtcislove said:
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
Click to expand...
Click to collapse
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
You are right. I posted the wrong payload dumper.
I am using the one from here and it worked with every payload i tried.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
I guess the other one is quicker but im using this and it works. I edit my old post.
Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
Can we use this attached boot img on IN2011_11_C.20 (India)?