Related
Hello, I am poised to start customising my Redmi Note 8T. I've done loads of reading and have an outline plan but would appreciate a sanity check / review of this in case I am either missing something or doing something I shouldnt. Phone is currently encrypted, TWRP can unlock it fine. I want to end up with an encrypted device but there is nothing precious on the phone at the moment (stock MIUI as delivered, pretty much unused since the unlock factory reset).
Here's what I have following my research on other threads here:
First, what I have done already:
0. get phone Redmi 8T willow 128GB with stock MIUI (DONE)
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it when I rebooted)
3. Backup from TWRP (DONE)
Next, the to-do list:
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
11. reboot into TWRP (fastboot reboot, hold volume up + power)
12. flash magisk zip (Magisk-v20.3.zip)
13. flash disable_dm_verity zip (Disable_Dm-Verity_ForceEncrypt_02.24.2020.zip)
14. reboot & test
15. Install via magisk manager the SQLite3 binary (SQLite3.Universal.Binaries.v1.0.zip)
16. Reboot
17. Install vis magisk manager the GPay SQLite fix (GPay.SQLite.Fix.v2.0.zip)
18. Reboot
Thanks very much in advance.
Hey @ogpog, at step 4, where you find vbmeta to flash?
Thanks
ogpog said:
Hello, I am poised to start customising my Redmi Note 8T. I've done loads of reading and have an outline plan but would appreciate a sanity check / review of this in case I am either missing something or doing something I shouldnt. Phone is currently encrypted, TWRP can unlock it fine. I want to end up with an encrypted device but there is nothing precious on the phone at the moment (stock MIUI as delivered, pretty much unused since the unlock factory reset).
Here's what I have following my research on other threads here:
First, what I have done already:
0. get phone Redmi 8T willow 128GB with stock MIUI (DONE)
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it when I rebooted)
3. Backup from TWRP (DONE)
Next, the to-do list:
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
11. reboot into TWRP (fastboot reboot, hold volume up + power)
12. flash magisk zip (Magisk-v20.3.zip)
13. flash disable_dm_verity zip (Disable_Dm-Verity_ForceEncrypt_02.24.2020.zip)
14. reboot & test
15. Install via magisk manager the SQLite3 binary (SQLite3.Universal.Binaries.v1.0.zip)
16. Reboot
17. Install vis magisk manager the GPay SQLite fix (GPay.SQLite.Fix.v2.0.zip)
18. Reboot
Thanks very much in advance.
Click to expand...
Click to collapse
flashing vbmeta is not really needed..however keep it just in case.
iaio72 said:
Hey @ogpog, at step 4, where you find vbmeta to flash?
Thanks
Click to expand...
Click to collapse
in fastboot rom inside images folder
ok solved thanks
the_weird_aquarian said:
flashing vbmeta is not really needed..however keep it just in case.
Click to expand...
Click to collapse
Well I tried without vbmeta and ended up with the panic-inducing "The system is destroyed" screen. I went back to fastboot and flashed vbmeta and twrp again, then installed the cutom rom, set it all up, then went back and installed magisk.
in fastboot rom inside images folder
Click to expand...
Click to collapse
I got vbmeta from reading https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196 and downloaded from https://t.me/rn8updates/80
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears
ogpog said:
Well I tried without vbmeta and ended up with the panic-inducing "The system is destroyed" screen. I went back to fastboot and flashed vbmeta and twrp again, then installed the cutom rom, set it all up, then went back and installed magisk.
I got vbmeta from reading https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196 and downloaded from https://t.me/rn8updates/80
Click to expand...
Click to collapse
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears.
You did well with the steps outlined above??
nothing is clear, not really..to many gray areas..like can i backup rom to external sd card, why exactly in twrp do you backup rom wise, and Disable_Dm-Verity_ForceEncrypt_, iv read its two files in one, new roms are not like the old days ie marshmallow kitkat, i used all in one tool flashed twrp..all went well then flashed then flashed magisk and then the dm-verty thing, ended up in a bootloop, then tried to use mi flash tool to put original firmware back, error error, got back using twrp and using eea recovery rom, although i was on on global, remember fast boot rom is not the same as recovery rom, same rom though, all very confusing...for me anyway.
Juanlufer4 said:
The same thing happened to me and I'm still not clear on the steps to follow to fix it and be able to install a custom rom. Destroyed system appears.
You did well with the steps outlined above??
Click to expand...
Click to collapse
Just looking back over my notes from when I did it. Here is what I wrote:
A modified vbmeta.img disables verify boot on devices using Android Verified Boot. You need to disable dm-verity on the fastboot command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
source https://forum.xda-developers.com/showpost.php?p=81591273&postcount=196
(the above is a command-line given on your computer connected to your phone which has been booted in fastboot mode (boot phone with power+volume down). You need the fastboot command on your computer (I use Linux and it's in a package called "android-tools").
If you forget to flash vbmeta, you'll see a message "the system hass been destroyed". Just go back to fastboot mode and flash it.
This is the process I recorded, but please verify it rather than folllwing it blindly, and bear in mind that later versions are available now .
Code:
0. get phone Redmi 8T with stock MIUI
1. unlock phone (DONE, 7 day wait!)
2. flash TWRP (DONE, used 3.3.1-1 official version, but MIUI overwrote it)
3. Backup (DONE)
4. flash vbmeta (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
5. flash TWRP 3.3.1-10 version (fastboot flash recovery twrp-3.3.1-10-ginkgo-willow-mauronofrio.img)
6. reboot into TWRP (fastboot reboot, hold volume up + power)
7. Wipe /system, /data, and /cache
8. flash Havoc-OS-v3.2-20200229-willow-Official.zip
9. flash open_gapps-arm64-10.0-pico-20200229.zip
10. reboot & test
bluefender said:
nothing is clear, not really..to many gray areas..like can i backup rom to external sd card, why exactly in twrp do you backup rom wise, and Disable_Dm-Verity_ForceEncrypt_, iv read its two files in one, new roms are not like the old days ie marshmallow kitkat, i used all in one tool flashed twrp..all went well then flashed then flashed magisk and then the dm-verty thing, ended up in a bootloop, then tried to use mi flash tool to put original firmware back, error error, got back using twrp and using eea recovery rom, although i was on on global, remember fast boot rom is not the same as recovery rom, same rom though, all very confusing...for me anyway.
Click to expand...
Click to collapse
I get your sentiment - it's feels hard doing this on any Android despite having decades of expert level professional computer experience. But it's really a miracle we can do it at all and we have the good people providing roms and the information needed to install them to thank for that. I think the "brick fear" makes it worse due to the lack of a console port or bios to fall back to like you have on a computer. I think the first post in the thread should contain all the information needed to install the rom but it's a moving target so I guess it's a difficult call to expect it to be maintained.
If I were to call out for one thing, it would be for that page to also include instructions for Linux. Android is Linux after all
(sorry I just realised I wasn't on the havoc thread where the "first page" is - https://forum.xda-developers.com/redmi-note-8/development/rom-havocos-3-1-t4043973 )
Thanks for your interest, I just wanted to know if the steps you describe were correct. I had 2 systems destroyed and it's not funny. Hopefully it works
---------- Post added at 03:56 PM ---------- Previous post was at 03:47 PM ----------
the_weird_aquarian said:
flashing vbmeta is not really needed..however keep it just in case.
in fastboot rom inside images folder
Click to expand...
Click to collapse
A doubt? started the rom well or encrypted?
Is there any YouTube videos showing the steps for the Redmi Note 8T ?
How to install rom gsi for Redmi note 8t
chakkrit_pond said:
How to install rom gsi for Redmi note 8t
Click to expand...
Click to collapse
+1 I'm trying to test GSIs on Note 8 (ginkgo) and I'm not succeeding in any way. Phone stuck on bootanimation (or, sometimes, reboot into TWRP).
Does anyone have the steps to success? Thanks.
I can start from scratch (MIUI 11).
Trying to flash a/b gsis of Android 10.
Edit: Got it working. All I had to do was check both checkboxes on AVB 2.0 and also check both in RM Forceencrypt.
Hi! I recently tried to install a custom ROM (LineageOS, Pixel Experience, CesiumOS), but every time I tried I got stuck at boot animation.
I'm on MIUI 11 V11.0.3.0 PGGEUXM Android 9 (Should I flash V11.0.6.0 PGGMIXM Global? )
What i did:
1.Unlocked bootloader
2.Flashed factory preloader from the Megathread
3.Flashed TWRP (by wzsx150)
4.Formated Data (in TWRP) and then Dalvik, Cache and System
5.Transferred ROM and vendor.img (and Magisk 20.4) to /sdcard/ (I got vendor.img from CesiumOS thread)
6.Flashed vendor.img
7.Flashed ROM (LineageOS, Pixel Experience, CesiumOS) (and Magisk)
8.Cleared Dalvik
9.Closed AVB 2.0 (first checkbox)
10.Rebooted to system
11.Got stuck at boot animation
12.Went back to stock ROM (11.0.3.0 PGGEUXM )
13.Went to step 2 and tried another ROM
Every time I flash an official ROM I need to flash lk and preloader from the Megathread and when I deleted lk and preloader.bin from the official ROM MiFlash instantly said failure
I'd also like to add that this is the first phone that I rooted and tried a custom ROM on
I got my ROMs from here:
LineageOS - https://forum.xda-developers.com/redmi-note-8-pro/development/rom-lineageos-17-1-t4072137
CesiumOS - https://forum.xda-developers.com/redmi-note-8-pro/development/rom-cesiumos-v2-5-1-t4059543
Pixel Experience - https://forum.xda-developers.com/redmi-note-8-pro/development/rom-pixel-experience-t4059977
MIUI 11 V11.0.3.0 PGGEUXM - https://c.mi.com/oc/miuidownload/detail?device=1900375
And TWRP from here:
TWRP - https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
just curious, youre clicking vendor img bubble when flashing a vendor img right? was having the same problem because i was flashing vendor img with system image..
shoeprano27 said:
just curious, youre clicking vendor img bubble when flashing a vendor img right? was having the same problem because i was flashing vendor img with system image..
Click to expand...
Click to collapse
Thanks for reply!
Yes, i was clicking that. Got it working, i just had to check both checkboxes on AVB 2.0 and also check both in RM Forceencrypt.
Hi everyone!
I've been testing installing Lineage 17.1 custom ROMs on merlin, here are the steps I followed plus a LOS 17.1.
I found out that this ROM works better than MIUI and its very stable as a daily driver.
Tested on Redmi Note 9 Global (merlin) - CPU (Helio G85) - ROM/RAM: 64GB/3GB, initialy flashed over MIUI 12.0.3 Global
This are the steps I followed:
Unlock bootloader (of course)
Backup all sensitive data (it maybe lost if things go wrong)
For you in case things go wrong, also download the exact fastboot rom of the MIUI version you are using from xiaomifirmwareupdater.com (it has to be fastboot ROM becouse it contains stock recovery)
Flash a TWRP with new MIUI kernel support
Download TWRP build by wzsx15, for example
Download a modifed vbmeta.img, like the one provided in this thread
Flash like this:
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Test TWRP, at least verify it can mount and read /data.
Wipe data, cache and dalvik
Flash LOS 17.1 for merlin (details below), or anything you want to test
Details about provided LOS 17.1:
LineageOS 17.1 - UNOFFICIAL | A10.
Released : 11/02/'21
By @CosmoFreak001 & @chcepizze
SElinux permissive
Changelog:
• Fixed VoLTE
• Fixed Brightness bug
• Fixed all major bugs
• Fixed Double tap to wake
• Fixed Offline Charging
Download
Source (build using generic kernel for Mediatek Helio G85)
Works at least over:
MIUI 12.0.4 Global and less
MIUI 12.0.1 Indonesia and less
--------------
⚠WARNING⚠
MIUI 12.0.5 Global (and 12.0.2 Indonesia) and any higher version, would probably need a downgrade.
--------------
In case things go wrong:
TWRP dosen't work correctly and now my system can't boot
Restore stock recovery, vbmeta and boot partition
Go to fastboot
Extract recovery.img file from your stock fastboot ROM and flash it like this
Code:
fastboot flash recovery recovery.img
Reboot, if system dosen't boot, go to next step
Extract vbmeta.img file from stock fastboot ROM and flash it like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot, if it can't boot, go to next step
Extract boot.img file from your stock fastboot ROM and flash all (recovery, vbmeta and boot partition) it like this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
TWRP ask's me for a passoword
It's the first PIN number of the lockscreen you set when you first run the system
My PIN doesn't work or my phone never had a PIN and still asks me for one
Maybe /data is not accesible (TWRP compatibility problem)
Try mounting /system and /vendor partition
Navigate through them and verify you can see files and folder
If TWRP is unable to mount any partition restore stock recovery partition
If TWRP can see and mount partitions other than /data:
You can format /data (you are losing ALL data including internal storage)
I don't wont to lose all my data!
Restore stock recovery
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Communos said:
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Click to expand...
Click to collapse
Thanks. You are right I will add those comments.
thanks for this
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some members the solution
One other question is where to get the Gapps for this rom 17.1 lineage merlin mt 6768
gruka said:
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some memmbers the solution
Click to expand...
Click to collapse
Misc.bin isn't necessary for flashing twrp,
And what do you mean by "that to set the email it's not working"?
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
gruka said:
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
Click to expand...
Click to collapse
Pico Open Gappa or flame Gapps basic, both are fine.
And it's the stock email app, I never used it, so I don't know about that.
Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Tried Potato OS, same, stuck on startup potato logo.
crDroid, same, stuck on startup logo.
Now the only thing working on this piece of metal is TWRP, what to do?
Here are the logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.
asaeles said:
Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Tried Potato OS, same, stuck on startup potato logo.
crDroid, same, stuck on startup logo.
Now the only thing working on this piece of metal is TWRP, what to do?
Here are the logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.
Click to expand...
Click to collapse
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Ok, I've downloaded an unofficial PixelOS for Samsung Galaxy A10, but inside the ZIP file I can't find something called vbmeta, where can I find it? Also if you have a specific A10 ROM in mind, please indicate.
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Also why A10 specifically? I mean this is a Xiaomi device after all, so is this vbmeta thing generic? Same across all devices?
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
It worked
loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Now Pixel Experience is working, but up till now I have two major issues:
1) SIM card is not working (it's saying network disconnected)
2) This mobile is for my kid and Google Family Link for children was working fine and now it is saying "Can't set up supervision on this device", so the issue is not with my son's google account it's now with the device itself.
Does Google sense rooting? Is Pixel OS rooted out of the box?
I mean my daughter has the same model and I unlocked OEM installation and flashed TWRP and Google Family link is working
asaeles said:
Now Pixel Experience is working, but up till now I have two major issues:
1) SIM card is not working (it's saying network disconnected)
2) This mobile is for my kid and Google Family Link for children was working fine and now it is saying "Can't set up supervision on this device", so the issue is not with my son's google account it's now with the device itself.
Does Google sense rooting? Is Pixel OS rooted out of the box?
I mean my daughter has the same model and I unlocked OEM installation and flashed TWRP and Google Family link is working
Click to expand...
Click to collapse
try another rom (the rom i suggest is RRos)
and see if the sim network is connected (if not, it might be a sensor problem)
about google things = i don't know, i hate google ...
Connectivity problems lead me to suspect it could be a firmware issue: either start from the beginning by going back to stock with MiFlash or try changing the firmware (see https://xiaomifirmwareupdater.com/firmware/ginkgo/).
loopypalm said:
try another rom (the rom i suggest is RRos)
and see if the sim network is connected (if not, it might be a sensor problem)
about google things = i don't know, i hate google ...
Click to expand...
Click to collapse
Thanks, here's a gift ;-) https://i.pinimg.com/originals/74/c0/e5/74c0e55d1fe725793e18758dcef11f72.png
Team Win Recovery Project version 3.5.2_10.0 with support dynamic partitions for OnePlus Nord N100 (Android 10 Only).
Everything works, except for:
MTP and decryption of the Data section.
You can both boot (fastboot boot twrp.img) and flash (fastboot flash recovery_a twrp.img and fastboot flash recovery_b twrp.img).
I ask you to answer about all the problems found and write either to me personally or in this topic.
any roms for this device?
Naksuhd said:
any roms for this device?
Click to expand...
Click to collapse
At the moment, only GSI firmware based on Android 10-12.
I tried to install android 11 OTA update using TWRP because android 10 do not use swap aggressively, it stops at 62 mb, the twrp started the update on slot b but the process never ended