Database Users

[ROM-sGSI] [ZUI 10.0]/[ZUI 5.0] From Z5 FOR Z2 Plus [Oreo]

What is this?
- sGSI of ZUI 10.0/ 5.0 from Lenovo Z5pro/Z5, based on Android 8.1.0, June 1,2018 security patch.
Since this was requested in some comments, I flashed it and found working for our device flawlessly, with some bugs.
Features?
-All features of ZUI 4 + Soft Charge, gestures, multi space ( dual apps ) etc. Split Screen is also available.
How to flash?
ZUI 10 :
1. Download the flashable zip from the links.
2. Boot to twrp, and wipe dalvik, cache, data, system and vendor.
3. Flash the zip.
4. Reboot.
ZUI 5:
Method 1 : (Recommended)
- 1. Download any treble based 8.1.x rom and ZUI5.0-sGSI.zip (link below).
[Please use MIUI 10 8.11.1 by Narshi Shukla as base ROM, as it seems it's Vendor is most compatible.]
2. Extract the zip in your storage. You will get three files ( two flashable zips and one folder "sGSI.....". [Folder name might differ, there will be only one folder, so no worries])
3. Boot into recovery and take a backup.
4. Clean flash treble based Oreo ROM that you downloaded.
5. From your twrp, use file manager to move " sGSI...." folder to backup folder of Twrp.
6. Mount system and vendor and wipe cache/delvik, data and system.
( Don't wipe firmware and Vendor )
7. Goto restore in your twrp and restore the system from "sGSI....." folder.
8. Flash the remaining two zips.
9. Flash magisk if needed.
10. Wipe cache/delvik and reboot. Done.
Method 2 : https://forum.xda-developers.com/showpost.php?p=78389810&postcount=320
(You need treble based twrp, search if you don't already have).
After following all these steps, if your phone is stuck in Lenovo powered by android screen for long, then force reboot the phone and it will boot up to system.
What works?
-Here:
Call,SMS, VOLTE, Data, play store, Utouch, Fingerprint , Navigation, Double touch to wake, GCAM, Face Unlock, Hotspot, Banking apps, nearly everything.
What doesn't work?
- ROM specific. Bugs depend upon the treble ROM that you used as base. In some ROM, system sounds does not work. In MiUI 10, video recording might not work. Game Mode has some issues with global apps.
*FOR VIDEO RECORDING - see this : https://forum.xda-developers.com/showpost.php?p=78219358&postcount=93 ****
*Update GPU drivers for VULKAN support. Link in the links section.***
Performance?
- Better than ZUI 4, smooth as butter, no stutter playing games like PUBG, notifications on time, decent SOT.
Can it be used as daily driver?
- Yes, if you can live with some Chinese texts in certain apps.
Any other thing?
- Because the ROM is ported from Z5 which has a notch, total area of the notification bar cannot be used. To see things like real time network speed and battery "percentage" you have to pull down the notification bar.
What should I do first after booting the device?
- Install play store from App center. Install magisk to remove bloat wares. Install any music app, since there is none. This will make the system optimal for us.
Also, Turn "True Full Screen Mode" ON in display settings for full screen in Apps.
Install Magisk and download and install "SafteyPatch V2" within Magisk to pass safetynet and hide banking apps in magisk hide to use them.
Open security app and give all important permissions to the apps you use, including system apps. Also include them in autorun/whitelist section.
Links?
-Here
ZUI 10
https://drive.google.com/open?id=17lyWnAl0Kjkv5S89wdtw7HglF2072zP5
ZUI 5
Mega link :
https://mega.nz/#!FyxSiI7Y!iZmmVufR6pipX3mwv_-I3HqI714YAMJN1a2zIysinmc
Gdrive link:
https://drive.google.com/open?id=1F_Ou6x2bj26hhdffw45uo4r9qlJuaDb5
MiUi 10 8.11.1 Narshi Shukla - Full Rom
https://androidfilehost.com/?fid=11410932744536996684
MIUI 10 8.11.1 Narshi Shukla - Vendor for twrp recovery: @(THIS VENDOR isnt compatible with all roms, if facing random reboots, use the complete MIUI 10 ROM for the Gsi)
https://drive.google.com/drive/u/0/folders/15QHEUfLMagMV9jZTmlUHa4hkhkNTF-RC
Working GCAM link :
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_6.1.021_FINAL_V1a_A8.1+.apk
VULKAN enabled open GL 3.2 driver link :
https://drive.google.com/folderview?id=11_atz5CDK9bHG4K_ME2LSRFFnxxKqWw2
Credits:
Not my work, I am just sharing it since I found it working.
All credits goes to this Xiaomi thread and bugrevealingbme.
https://*************/threads/zui-5-0-a-only-treble-rom.226/
******************************** FLASHING ISSUE ******************
While flashing this ROM, try to follow the guide above as strictly as possible. Use the ROM that is recommended.
If you are facing bootloop, download the vendor that is provided and restore it in twrp and then flash patch 1 and 2.
Also remember, during each and every step, your TWRP should have system and Vendor mounted. Check after every step.
Your phone might reboot once or twice during first boot, which is not an issue.
How to know if you flashed it correctly?
-If your phone boots into the system with "Lenovo bootanimation" , you flashed it correctly.
If your phone is stuck in "Lenovo - powered by android" splash image for more than 5 minutes, you got something wrong.
*********************************************************************
Screenshots attached :

what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?

I have one question. If i install a sgsi rom can i back to trenle, non-treble rom just with a simple flash method?

muujeeb said:
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
Click to expand...
Click to collapse
gcamera is working on redmi note 5 pro. should work also here.

muujeeb said:
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
Click to expand...
Click to collapse
GCAM is working.
Notification bug is not there. Only sometimes, it seems that we get late notification.
You have to flash it over Oreo because the GSI is Oreo based. Flashing over pie should work as well, since treble ROM is required. Take a backup of your system so you can restore easily, if you face any issue.

nonamesry said:
I have one question. If i install a sgsi rom can i back to trenle, non-treble rom just with a simple flash method?
Click to expand...
Click to collapse
Yes, you can get back to the ROM you want with simple flash, no problem.

Custom kernel flashable?

ashwinonm said:
Custom kernel flashable?
Click to expand...
Click to collapse
Haven't tested, but should be flashable.
Edit : Custom kernel might brick the device. Will test and update.
Donot flash custom kernel, it causes self restart of device.
Note: Moxie kernels can be flashed, you should flash patch2 after flashing kernels. But, MIUI 10 comes with moxie R5.1 so no use flashing Moxie again.

link not working

Wow it's so beautiful!

I used Arrow OS 8.1 but it got stuck in bootloop and does'nt boot at all.. I followed all the steps accordingly but it did not boot up even after i kept my phone overnight to let it boot. I don't know where i did wrong.

muujeeb said:
I used Arrow OS 8.1 but it got stuck in bootloop and does'nt boot at all.. I followed all the steps accordingly but it did not boot up even after i kept my phone overnight to let it boot. I don't know where i did wrong.
Click to expand...
Click to collapse
Use MIUI 10 port of Narshi Shukla latest build. It works.
May be Arrow OS cannot be used.
You can also try using Vendor of MIUI 10 once. Restore this vendor and the system image of ZUI.
Here is the vendor:
https://drive.google.com/drive/mobile/folders/15QHEUfLMagMV9jZTmlUHa4hkhkNTF-RC?usp=drive_open

kany1 said:
link not working
Click to expand...
Click to collapse
Link is working fine.

jebish7 said:
Link is working fine.
Click to expand...
Click to collapse
yes it is working with mega app

I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------
ok i try to flash it again and boot successflly

marclevine said:
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
Click to expand...
Click to collapse
I think only MIUI 10 rom works flawlessly for this GSI. I will update the main page details and ask to use MIUI 10 only.
You couldnot flash patch 2 because it requires vendor, and may be your vendor is now messed up.
So use MIUI 10 port, it works without any issue.

marclevine said:
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------
ok i try to flash it again and boot successflly
Click to expand...
Click to collapse
Glad To hear.

So in whatever rom I am in Oreo , I can use that firmware if I use vendor only from your backup? And shouldn't wipe it?

ashwinonm said:
So in whatever rom I am in Oreo , I can use that firmware if I use vendor only from your backup? And shouldn't wipe it?
Click to expand...
Click to collapse
Well, that's how some people got this working, so yes, it's working that way as well. ( Your ROM should be treble based though )
I will attach the "Vendor" file in the main post as well, so other members can use it too.

custom kernel possible,mine running in moxie

[RECOVERY][3.4.0-14][toco]Unofficial TWRP Xiaomi Mi Note 10 Lite (TEST)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* 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 features included in this ROM
* 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.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-13 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_toco
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-05-29

Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!

Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you

Did anyone boot it?
hello, work boot it?
fastboot boot twrp.XXXX.img

StanGumn said:
hello, work boot it?
fastboot boot twrp.XXXX.img
Click to expand...
Click to collapse
Yes

iron maiden said:
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Click to expand...
Click to collapse
Let us hope so.

I would like to apologize in advance as I am a noob when it comes to the recent changes made by Google to android. So on a lot of the recent devices launched with android 10, an essential step before flashing Magisk is to disable the vbmeta partition by flashing the "vbmeta.img" using a fastboot command with the --disable-verify and --disable-verification argument. My question is that is the "vbmeta.img" modified by developers or is this the same identical file found in the stock firmware files?
I do apologize if this is the wrong thread but there's not many resources online or even on xda for this device.

Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.

Reanimax said:
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Click to expand...
Click to collapse
ask to xda to make a dedicated section and i will ask to move this thread

mauronofrio said:
ask to xda to make a dedicated section and i will ask to move this thread
Click to expand...
Click to collapse
Yes. You right about it.

Kediraksith said:
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Click to expand...
Click to collapse
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
Update: 5/16/2020
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY. ***This is only if OP asks to flash VBMETA PATCHER, otherwise skip to Step 5***
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM. ?
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.

Wmateria said:
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY.
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM.
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Click to expand...
Click to collapse
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!

cerme said:
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
Click to expand...
Click to collapse
The root and flash process is basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.

Wmateria said:
The root and flash process is basically basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Click to expand...
Click to collapse
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties

cerme said:
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
Click to expand...
Click to collapse
Same here, i was on the Mi 9T before, I didnt understood the whole new flashing process and carefully updating from EU Rom to AOSP Roms and back, I think i was messing with with thwe wipe and change partition feature (f2fs to ext 4 with an EU Rom) - then the Mi 9T bricked big time. Never recovered after that, luckily got it refunded for it but not many may have that second chance. After learning how to flash propeely and root, ect. I try to help out here when needed and ask too. I just got my Mi Note 10 2 weeks ago and rooted a week ago. So if anything, am willing to help out and repeat the following flash process or any changes in the future and feedback on future Roms.

Was thinking about which rom to use... does xiaomi.eu is stille faster with providing updates? what about the situation with OTA with that.
Now I have the phone with global rom, I want at least flash the EEA rom. But I also know that at some point i want to root, install magisk and get nice features. Still don't want to update manually everytime for an update...

will be watching this thread with much interest..
I recently bought this device (Global version) for use here in Australia.
my first time owning a Xiaomi - quite happy with it so far.
would be nice to have the themeing stuff work properly - I have used MIUI based ROMs back a LOoonggg time ago, in the days of the Nexus S and Galaxy Nexus etc.
used to have a new ROM flashed every couple of days lol, back then. But recent years I've stopped all that, no cool ROMs no snazzy kernels TWRP no nothing not even root lol, very boring!
anyway thanks for posting I hope to try this sometime soon

Hello is there any Eu rom for Mi note 10 lite?

Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
yes, there is the EEA ROM you can find on miui website. You can flash it after unlocking bootloader with miFlash

Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
I'm not sure if you mean the official ROM or xiaomi.eu.
The link to the official EEA(EU) ROM:
Recovery: https://bigota.d.miui.com/V11.0.7.0.QFNEUXM/miui_TOCOEEAGlobal_V11.0.7.0.QFNEUXM_7926bf9c02_10.0.zip
Fastboot: https://bigota.d.miui.com/V11.0.7.0...EUXM_20200508.0000.00_10.0_eea_4eb1c694c9.tgz
I have yesterday seen a xiaomi.eu Stable build for toco which is based on Global Stable ROM:
https://sourceforge.net/projects/xi...e10LITE_V11.0.4.0.QFNMIXM_v11-10.zip/download
I can not promise that it's working.

A Guide To Install Android 10 (With Fixes) on Redmi 7a

Hello,
I know that ROM developement on redmi 7a has been extreemly slow, but we all know that redmi 7a is a treble enabled device and therefore we can install every android GSI as long as it is ARM32-BINDER64-AB, yes and i wouldn't explain it here you can read it over here here.
So i thought that i should give you guys a little guide on how to install GSIs and custom ROMs and yeah with volte fix too
NOTE - I AM NOT RESPNSIBLE IF YOUR DEVICE GETS BRICKED OR THERMONUCLEAR WAR TAKES PLACE, YOUR WARRANTY IS VOID FROM THIS STEP ON, I AM NOT RESPONSIBLE IF YOUR DEVICE GETS BRICKED MAKE SURE YOU HAVE MOVED YOUR DOWNLOADED ROMS AND GAPPS TO A PC OR A SD CARD I AM NOT RESPONSIBLE FOR ANYTHING
1] The very important first step is to unlock your bootloader.
2]The second step is to patch your boot image (if you want to root it with magisk)
3] Install the custom recovery of your choice
Download the TWRP file from here
you also can install TWRP forks like
PICTHBLACK RECOVERY PROJECT or PBRP from here
SHRP RECOVERY from here (i wouldn't recommend this one if you are flashing this for the first time)
If you have your device drivers installed but you dont have adb installed then please download this file and extract it to a suitable folder where your downloaded recovery is extracted and run cmd-here and follow these steps given below
Code:
fastboot devices
this will show you if your device is connected or not.
Code:
fastboot flash recovery (your recovery name.img)
Code:
fastboot reboot
you have to keep pressing you volume increase button to reboot to recovery
4] You have to wipe DATA first then, reboot to recovery and go to mount select system (if it's unchecked)
5] Go to WIPE -> ADVANCED WIPE -> Select SYSTEM - DALVIK CACHE - CACHE - INTERNAL STORAGE
6] The list for the available GSIs or ROMs is ----
1) LineageOS thanks to ExpressLuke (GSI) (You might have to downgrade your miui to be able to boot)
2) HavocOS thanks to Skulshady (GSI) (Boots just fine with any version of miui volte patch is needed)
3) Mokee thanks to GuaiYiHu (ROM) (No worries about anything)
4) AOSP Special thanks to Phhusson (GSI) (Boots just fine without any hiccups volte patch is needed)
5) CAOS by Erenmitein (GSI) (Not tested)
6) CrDroid By Erenmitein (GSI) (tested needs the bolte fix patch. please follow the steps given below)
7] Move your GSI img (extract the .xz file) the extension is going to be .img and will not visible in TWRP or it's forks unless you select the INSTALL IMAGE option in the FLASH section and GAPPs
8] Flash your GSI as a System Image
9] Reboot to recovery again and flash your GAPPS ignore if it says no OS installed when rebooting to recovery
10] The fix for VOLTE is here thanks to Khushraj Rathod
you just have to flash it from TWRP or its forks
11] The first reboot will take some time and voila your GSI has been installed (flashed).
12] For Mokee, personaly i love Mokee rom with its boot animation, you can just flash your zip through twrp with gapps.

Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?

kra_ppo said:
Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?
Click to expand...
Click to collapse
No.

A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.

Havoc (an Mokee - but I dont like it) was finally successfull, but only by formating Data and not to wipe internal Storage....

kra_ppo said:
A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.
Click to expand...
Click to collapse
Flash vbmeta

Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work

how to get back to stock ROM ?

idcamper said:
Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work
Click to expand...
Click to collapse
You flashed floor miui 10.0.2.5.?

can't i do this with twrp? Tutorial ?

Flammenschwert1337 said:
Flash vbmeta
Click to expand...
Click to collapse
Did you find solution?

lslayer4231 said:
Did you find solution?
Click to expand...
Click to collapse
Start with miui 10.0.2.5.
Then go on.

My phone bootloops to redmi logo and recovery after flashing, any help from this?

After installing latest havoc 3.7 gsi the call recording feature not working though normal sound recording works... Any fix?

Hey, guys!
Havoc OS GSI is selinux permissive or enforced?
Is it possible to go back to stock rom by doing a backup using twrp?
I'm sorry if I'm being dumb, but as you already noticed, I'm newbie.

MEMO#22 said:
My phone bootloops to redmi logo and recovery after flashing, any help from this?
Click to expand...
Click to collapse
Switch back to miui 10 global version and install twrp

Has anyone else got media playout over bluetooth OK and if so, which GSI or ROM and which base firmware, please? It does not work for me with AOSP on latest EU firmware. Only calls go to BT.

RUI 2.0 | F.14 | A11 | Easy Update from C.38 A10 | Magisk Root | Safetynet Fix | Global or India Variant |

~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Easy way to update your Realme X2 Pro Global or India Variant from C.38 to F.14 (Android 10 to Android 11) [with Magisk root]
Update your Realme X2 Pro with C.38 download the file specific for your device IN/Global
Make sure the bootloader is unlocked. click here for Unlock Procedure​
Boot to recovery (power off device and then hold vol- and power together)​
Must check if this version is installed OrangeFox-R11.0_2-Beta-RMX1931
Download: OrangeFox @4j17h​
Install RUI 2.0 (F.11) with OrangeFox - Dont format anything
Download: RUI 2.0 (F.11) India​
Download: RUI 2.0 (F.11) Global/EU
------------------------------------------​
Download: RUI 2.0 (F.14) Zip (Region -Unknown)​
Download: RUI 2.0 (F.14) Global/EU​
Do not restart to System now if you need custom recovery.​
Install OrangeFox Beta img (RUI2.0) for Android 11 & select recovery partition.
Download: OrangeFox Beta RUI 2.0 for Android 11 Thanks @Jerry08, @4j17h​
Install Patched vbmeta img & select vbmeta partition.
[This step is essential to have recovery persistent by not getting replaced with stock recovery and also to avoid bootloop]
Code:
fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img
Download: Patched vbmeta​
If needed Stock Recovery -
Rich (BB code):
fastboot flash recovery stock_recovery_RUI2_A11.img
MUST Wipe DATA after 4 digit code in stock recovery
[Skip this step, Only Experimental for testing]
Install Magisk Canary - Rename apk to zip and flash with USB OTG (Optional only if root is required) ​
Reboot to System (May take 5-7 minutes to complete booting)​
Enjoy RUI 2.0 updated with all your apps and data intact. ​
Realme has restricted access of Data in Beta phase which means we cant access Data partition and most of files with OrangeFox.
Your "usrdata" partition or the standard sdcard folder having your Contents, photos, videos, files, songs etc will be accessible as you will use normally after restarting in RUI2.0.
Dont ask steps for Roll back to old version. Will lose all data and will be formatted when roll back.
Any issues, feel free to discuss and help out each other politely.

After read all bugs i am happy with android 10

anang1979 said:
After read all bugs i am happy with android 10
Click to expand...
Click to collapse
Hell yeah, I'll happily stay on RUI 1 with that issues list lol

I am using RUI 2.0 F.10 as my daily driver for normal use. I find it to be good and only not having root is my current issue.
Games and other performance is fine, issues happen with extreme settings or over long time usage on battery.
No one actually needs to lock bootloader or need DRM L1 unless have to watch OTP (Netflix, prime,etc) in high resolution or HDR.

Sir Thanks Soo Much But For ur Keen And Kind Information Bootloader Is Currently Not Unlocking Due To Some Network Error If U Really A Developer Fix That ...... Everyone Will Appreciate U For That Believe Me..

hack-os said:
I am using RUI 2.0 F.10 as my daily driver for normal use. I find it to be good and only not having root is my current issue.
Games and other performance is fine, issues happen with extreme settings or over long time usage on battery.
No one actually needs to lock bootloader or need DRM L1 unless have to watch OTP (Netflix, prime,etc) in high resolution or HDR.
Click to expand...
Click to collapse
Same here, the only thing stopping me from updating now is that there is no root. Don't care about DRM.

Root I use for adaway and AccA. I have found temporary alternatives for them. Instead of adaway now I use adguard and enabled optimised night charging feature of Android 11 instead of AccA.
This open beta F.10 could be the preview of final stable release as informed by Realme
"The latest Open Beta version will be chosen as the stable version and rolled out to all users,there is no difference if you have already joined the Open Beta program." Source: Realme Support Forums.

hack-os said:
~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Easy way to update your Realme X2 Pro Global or India Variant from C.37 to F.10 (Android 10 to Android 11) [will lose Magisk root]
Update your Realme X2 Pro with C.37 download the file specific for your device IN/Global
Make sure the bootloader is unlocked. click here for Unlock Procedure​
Boot to recovery (power off device and then hold vol- and power together)​
Must check if latest OrangeFox is installed [email protected]_1.zip
Download: OrangeFox Thanks @Jerry08, @4j17h​
Install RUI 2.0 Beta (F.10) with OrangeFox - Dont format anything
Download: RUI 2.0 Beta (F.10)​
Do not restart to System now if you need custom recovery.​
Skip this step if you dont want custom recovery
Install OrangeFox Beta img (RUI2.0) for Android 11 & select recovery partition.
Download: OrangeFox Beta RUI 2.0 for Android 11 Thanks @Jerry08, @4j17h​
Install Patched vbmeta img & select vbmeta partition.
[This step is essential to have recovery persistent by not getting replaced with stock recovery and also to avoid bootloop]
Download: Patched vbmeta​
[Skip this step, Only Experimental for testing]
Install Magisk Canary - Rename apk to zip and flash with USB OTG (Optional only if root is required) ​
Reboot to System (May take 5-7 minutes to complete booting)​
Enjoy RUI 2.0 updated with all your apps and data intact. ​
Realme has restricted access of Data in Beta phase which means we cant access Data partition and most of files with OrangeFox.
Your standard sdcard folder having your Contents, photos, videos, files, songs etc will be accessible as you will use normally after restarting in RUI2.0.
There are couple of issues with the current RUI 2.0 Beta.
No ROOT - installing Magisk is difficult and root doesn't work
Cant safely lock bootloader
Widewine DRM L3 due to bootloader unlock
Battery,Camera, Audio performance poor
General usage and Games performance will be average.
Need to report any bugs identified in open beta phase.
Dont ask steps for Roll back to old version. Will lose all data and will be formatted when roll back.
Any issues, feel free to discuss and help out each other politely.
Click to expand...
Click to collapse
I've followed exact same instructions and I'm now stuck in boot splash. not even boot animation.
First I updated from C32 to C37 and then I updated to RUI 2.0 accordingly. But now I'm stuck in Boot splash. BL is unlocked. Followed exact same instructions. Please help me out I have some very important personal data in storage

ImperoDroider said:
I've followed exact same instructions and I'm now stuck in boot splash. not even boot animation.
First I updated from C32 to C37 and then I updated to RUI 2.0 accordingly. But now I'm stuck in Boot splash. BL is unlocked. Followed exact same instructions. Please help me out I have some very important personal data in storage
Click to expand...
Click to collapse
Fixed it!!!
Okay I think I've found the solution.
I never wanted custom recovery so I skipped flashing OFOX for RUI2 version.
But as I've mentioned above I was stuck in Realme, powered by android Spash screen and nothing more.
I have tried several things but nothing worked and then I did following steps and Voila! it worked.
1. Flashed ofox recovery for RUI 2.0 with fastboot.
2. flashed patched_vbmeta with following commad (use without quotes) "fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img"
3. executed "fastboot reboot" command in CMD fastboot.
Now I have a fully functional system and it took only 2 minutes for my first boot (data not wiped)
Thank you @hack-os for his amazing guide and anyone who stuck in splash like me, follow above steps and you'll be out

Hello, I am not a beta tester or part of open beta. Yesterday I just checked software update and there is no update. I just opened Realme Trail and I can see there is an optional update to RUI 2 and I said yes.
Today I got the update for RUI2 and I am from India.

ImperoDroider said:
Fixed it!!!
Okay I think I've found the solution.
I never wanted custom recovery so I skipped flashing OFOX for RUI2 version.
But as I've mentioned above I was stuck in Realme, powered by android Spash screen and nothing more.
I have tried several things but nothing worked and then I did following steps and Voila! it worked.
1. Flashed ofox recovery for RUI 2.0 with fastboot.
2. flashed patched_vbmeta with following commad (use without quotes) "fastboot --disable-verity --disable-verification flash vbmeta patched_vbmeta.img"
3. executed "fastboot reboot" command in CMD fastboot.
Now I have a fully functional system and it took only 2 minutes for my first boot (data not wiped)
Thank you @hack-os for his amazing guide and anyone who stuck in splash like me, follow above steps and you'll be out
Click to expand...
Click to collapse
Skipping custom recovery to have stock needs unpatched vbmeta. That why your boot got corrupted. Glad you fixed the issue with fastboot. The guide is mainly made to upgrade only with custom recovery and not using PC for fastboot.
You could still replace your recovery to stock recovery img in fastboot and flash RUI 2.0 A11 stock vbmeta
fastboot flash recovery stock_recovery_RUI2_A11.img
Could give it a try. Even i haven't tried this but that should work.

But I could not unlock the phone after the update. the phone became useless. all I can see on the phone screen is network icons and a strange lock symbol at the centre of the status bar on top of the screen. nothing worked, like hard reboot, wipe data in recovery but wipe data with format worked but I lost all data for which I am not ready.
finally, format the device from Recovery and could boot properly and experiencing RUI 2.0 with Android 11. there are no issues when compared to C37, it is working like a charm.

Does this work on locked bootloader and stock recovery?

Rahulfere1 said:
Does this work on locked bootloader and stock recovery?
Click to expand...
Click to collapse
you can update directly by flashing the zip given with your custom recovery.
This guide is only for unlocked bootloader and phones with orange fox as custom recovery with zip file.

satish.yarramsetti said:
But I could not unlock the phone after the update. the phone became useless. all I can see on the phone screen is network icons and a strange lock symbol at the centre of the status bar on top of the screen. nothing worked, like hard reboot, wipe data in recovery but wipe data with format worked but I lost all data for which I am not ready.
finally, format the device from Recovery and could boot properly and experiencing RUI 2.0 with Android 11. there are no issues when compared to C37, it is working like a charm.
Click to expand...
Click to collapse
Updating from c.37 to F.10 Rui 2.0 does not have any issues when the instructions are followed right. It's weired to get issues to unlock the screen after updating to Rui 2.0. Share any screenshots of the strange lock symbol if it was taken. Glad, you found a way fix your problem.

hack-os said:
Updating from c.37 to F.10 Rui 2.0 does not have any issues when the instructions are followed right. It's weired to get issues to unlock the screen after updating to Rui 2.0. Share any screenshots of the strange lock symbol if it was taken. Glad, you found a way fix your problem.
Click to expand...
Click to collapse
Yes, it is strange. I did not do it manually from xda to follow instructions. I have received the update from Realme itself and the phone became unusable after the update until I format the device.

Rahulfere1 said:
Does this work on locked bootloader and stock recovery?
Click to expand...
Click to collapse
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.

satish.yarramsetti said:
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
Click to expand...
Click to collapse
You may be getting it officially in India, but European and UK users have never had the option to take part in any of the beta programs.
My big worry is that when Realme eventually decide to include Europe in the rollout of the update then there is massive potential for all of the various online banking apps etc that are specific to each European country might not work, meaning that we'll have to stay on Android 10.

satish.yarramsetti said:
Yes, not related to this thread. we are getting officially from realme . go to settings, software update, trail, and register. you will get it in 24 hours. not sure if slots are full. somewhere I have seen there are 50,000 slots.
Click to expand...
Click to collapse
Same update is done here without wait or approval

Mod machine translation:
good evening anyone please try to install the rui 2.0 firmware on the European version with locked bootloader and stock recovery? Thanks for your answers
*****************************
bonsoir quelqu'un s'il vous plaît essayez d'installer le firmware rui 2.0 sur la version européenne avec bootloader verrouillé et récupération de stock? Merci pour vos réponses

[GUIDE] [TB-X606F] [Lenovo M10 Plus FHD] How to flash TWRP, Generic System Image (Android 11, Android 12), and Root with Magisk

Hi, I'm a long-time lurker on these forums but recently had some success flashing a GSI and rooting the Lenovo Tab M10 Plus (FHD) (X606F) with TWRP, and wanted to share my exact steps here. This device is awesome for the price point but unfortunately not popular enough to have many guides available. The tablet is Project Treble compatible and uses A/B roms (although it is not an A/B device in terms of OTA updates). You can use the Treble Info app to confirm that the devices uses an ARM64 A/B operating system. This was tested with the CAOS 11 GSI based on Android 11; it may work on other GSIs and other Android versions but I have not tested those (NOTE: user below confirms working on Android 12). I've written this guide at a bird's-eye-view meant for users familiar with flashing.
A couple useful notes before we begin:
- Hardware force off: hold down both volume buttons + power button
- Hardware boot into bootloader: while powered off, hold volume down + power button
- Hardware boot into recovery: hold down both volume buttons + power button
- While in fastboot mode, the command `fastboot reboot recovery` does not work for me on this device. You may have to hardware boot into recovery using the hardware steps above (power off completely then hardware boot). [This command may work for some people. It does not work for my device.]
Obviously, make sure your bootloader is unlocked before starting.
1. I used Ubuntu since Windows was having trouble recognizing the device in fastboot mode; linux drivers seem to be better developed for this particular device. I used `sudo apt install android-sdk` to get the drivers. Much easier than the nonsense that you have to do on Windows to get this device to work. Unfortunately, the Lenovo rescue app is available only for Windows, so you'll need access to Windows to gain access to vbmeta.img for installing TWRP (below).
2. Install TWRP following this guide: https://forum.xda-developers.com/t/...rp-3-5-x-for-lenovo-tab-m10-fhd-plus.4222887/. It is important that you follow all these steps. After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data.
3. In TWRP, flash CAOS 11 GSI: https://forum.xda-developers.com/t/official-aosp-r-mod-caos11.4265059/. You can try with other GSIs - it will probably work - but I've only tested this particular one, and can attest for the stability of CAOS 11 on this device. The image you'll want is named with -arm64-bgZ. If you use another GSI, make sure to use the A/B arm64 image. CAOS 11 has gapps included, so no need to flash here; if you use another GSI that does not have, you'll need to flash the appropriate gapps yourself. You can also opt for the non-gapps download if you don't want Google spying on you.
4. (Optional/No longer necessary) In TWRP, flash to disable dm-versity: https://zackptg5.com/android.php#disverfe.
5. (Optional - many GSIs come with root) In TWRP, flash standard Magisk.zip: https://github.com/topjohnwu/Magisk. I didn't need to use Magisk-Phh.
6. Reboot system.
7. You may or may not get errors from Google Play saying that the device is not certified. Follow these steps:
- Sign into Google account on device via settings
- Download and install the Get ID app: https://f-droid.org/en/packages/makeinfo.com.getid/
- Open the app and Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign in and paste the copied value to it, register
- Reboot (this actually took me a few tries to get working, I believe the key is to make sure you're signed into your Google account)
- Google Play should be working
Feel free to ask any questions here.

I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.

dpn982 said:
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
Click to expand...
Click to collapse
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.

shnioob said:
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
Click to expand...
Click to collapse
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.

dpn982 said:
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
Click to expand...
Click to collapse
I think this tablet has always had an issue with Netflix due to lack of DRM or something of that nature - I wasn't able to get Netflix on the stock version. Disney+ is probably the same issue.
If you have some free time, it would be great if you can outline your steps for getting safetynet to pass. I haven't bothered with it.

Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error

emilio666 said:
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
Click to expand...
Click to collapse
NEVERMIND, it got solved by just waiting a couple of hours after using the Google website: https://www.google.com/android/uncertified/

Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks for the clarifying info, updated the OP a bit. And thanks for providing us with a TWRP to make this possible. Otherwise this awesome tablet would be stuck on Android 10 forever.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Happy to help, glad it worked for you. I tried installing some other GSIs with and without flashing Magisk - LineageOS 12 boots but is very buggy, after reboot I was unable to get past the lockscreen. PixelExperience 11 and 12 cause a bootloop. If anyone has had success with PixelExperience I would love to get your input.

Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.

jebise101 said:
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
Click to expand...
Click to collapse
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.

shnioob said:
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
Click to expand...
Click to collapse
How do you go back to stock in case this does not work?
Is there a factory image?

jebise101 said:
How do you go back to stock in case this does not work?
Is there a factory image?
Click to expand...
Click to collapse
you can download the stock ROM from LMSA

I also have Lenovo tab m10 fhd plus but it is tb-x606v. Can I flash x606f rom on this device and flash twrp after.i don't want my device to be bricked.

vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Hi, I'm trying to follow what you did, but I'm having issues with the Gapps, do you have some pointers to solve it? Thank you in advance

Hello everybody!
I finally installed CAOS 11 and it's working like a charm. Gapps are definitely working as excpected and system seems to be stable as possible.
I have two question to those that installed it to :
Is anyone kow why some widgets on X606F are not clickable, an do not actualize till reboot?
Am I the only one that lost double tap to wake on CAOS?
Thank you all

I tried AOSP V412 12L too, we lost fingerprint sensor and face unlock, widevine DRM. There is some troubles on wifi, beside of this it is pleasant. Of course this not as smooth as android 10. I do not recommend it for daily basis.

I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.

garconblair said:
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
Click to expand...
Click to collapse
Thanks for the feedback. What about Widevine L1 and SafetyNet test with CAOS11? Are you able to play content at 1080p resolution with the Netflix App?