Database Develop

Bring light into the darkness of encryption

Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?

You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.

SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.

Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?

SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.

Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?

How to Revert back to Pie custom ROM from 10 custom ROM?

I've tried a couple of 10 ROM but, as far as i see, there're still too many bugs that makes very unpractical for me to use android 10 as a daily driver.
I'm planning to revert back to a pie custom ROM but I'm worried that I might overlook something.
I know that I have to backup some partiotins (persist? EFS? something else? in 10 in order to restore them in Pie, but I'm not sure wich partiotions and how to restore them (before flasing the new ROM, after flashing the new ROM, should I change the active slot?)
Can someone please give me some advices?
Thank you in advance

Don't do anything you Use mi flash tool for android 10 to move android 9 i do tow time and it working for me know am using android 9 pie.

Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you

Malobestino said:
Thank you for your answer, but I'm not really sure if using miflashtool fits my case.
Isn't miflash tool designed to flash only stock ROM?
If it's not, can you please provide me a link to a guide or some explanation on the usage of miflashtool? I'm not very confortable using automated tools to flash ROM
Thank you
Click to expand...
Click to collapse
to start backup everything and put on pc with usb cable ..
better just flash a recovery.zip of miu pie or oreo or even custom
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
custom pie and stock pie are pretty stable ..
remember if going for miu get recovery flashable zip and flash twrp image again after flashing rom..boot straight into recovery ...flash magisk ..use stock

Thank you for your detailed answer
Just a couple of more questions
KevMetal said:
better just flash a recovery.zip of miu pie or oreo or even custom
Click to expand...
Click to collapse
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
but if you go full stock with miflash be careful*
dont get rom with ARB activated or delete the firmware upgrade folder
Click to expand...
Click to collapse
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
also when downgrading from 10 to 9 or 9 to 8 your persist partition will get corrupted
look in the official Telegram to get a recovery flashable persist restore zip
Click to expand...
Click to collapse
Can I just restore my persist backup from within TWRP?
Thank you again for your patience

.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries

KevMetal said:
.........Just a couple of more questions
@Malobestino
Can I just use the recovery I have now (TWRP) or, if not, flash a TWRP.img from fastboot?
*You can use twrp but just make sure you have the latest . The best one is an unofficial one that supports encryption/decryption from 4pda. I use Orange Fox . Lots of people recommend pitch black.
I intend to flash a custom ROM so shouldn't be any issue with anti rollback
*Yes you are right, then it won't be an issue.
Can I just restore my persist backup from within TWRP?
*Maybe , yes& no . Some twrp recoveries don't support flashing persist or even backing it up ..if the version you are using does that, you can backup your persist partition ...
*There are recovery flashable zips of persist for Wayne and Jasmine on the support groups in Telegram too.
Thank you again for your patience
*No worries
Click to expand...
Click to collapse
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help

Malobestino said:
Thanks to your indications I successfully downgraded from custom 10 (lineage 17) to custom 9 (havoc 2.8)
As you predicted I had some difficulties restoring the persist partition and flash persist.img
However I found a persist flashable zip on a telegram channel as you suggested and I successfully flashed from TWRP.
This is what i did:
- reboot to previously installed TWRP 3.3.1.0
- wiped system, dalvik, cache, data and external data
- switched to other slot and rebooted to recovery (recovery was already flashed to both slots from previous ROM flashing)
- wiped system, dalvik, cache, data and external data
- flashed havoc 2.8
- flashed flashable_persist.zip
- switch to other slot reboot to recovery (no recovery flashing as Havoc has built in TWRP)
- flash gapps
- flash magisk
- reboot to system
For the time being everything seems to work correctly. I checked the sensors with an app and everything seems fine.
Only issues I'm having are that autobrightness doesn't seems to work even if it's active, and that, after restoring its own backup, I cannot change notification sounds in whatsapp (?!?). Every time I try it crashes from within whatsapp settings
This issue is really strange. If i just install the app without restoring the backup from gdrive, I can change the notification sound just fine, but if I resotore the backup it crashes every time I try to access to notification submenu in whatsapp settings (every other setting works just fine).
Again, thank you for your help
Click to expand...
Click to collapse
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .

KevMetal said:
I'm glad everything worked well. The auto brightness is most likely a rom bug ..check on Havoc thread ..
Maybe it could be fixed with a custom kernel ...kangmeng or something like that
Click to expand...
Click to collapse
Im' also quite convinced that is something related to the ROM or the kernel. Fro the time being isn't that big of an issue. I will look into it in the next days
As for restoring ...it is amazing the amount of strange behaviours it can cause .
Try this : ... Before backing up whatsapp change the notification to stock behaviour ..default notifications ..do backup ..
When you restore ...clean install whatsapp ..restore only data with titanium por from google drive..dont use ...just exit.. force stop ..clear cache ..open and use like normal ..will fix this problem i think .
Click to expand...
Click to collapse
Apparently this issue resolved during nightime by itself.
My theory is that the autobackup during last night realigned automagically the app (which doesn't make a lot of sense, but I don't really know how whatsapp's backup works, what it writes or read to the gdrive backup).
Anyway I really appreciated your help, thank you again

GUIDE How to Instal GSI ROM- Havoc-OS-v4.X-Official Android 11 On Redmi 8

Here I bring to you the official Havoc-os 4.X ROM Android 11 and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
Remember I am not a developer, if you are presenting any bugs let us know and you can contact the Havoc team on Telegram
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32, the version that i tested Havoc-OS-v4.5-20210208-Official-arm64-ab.img.xz
Bugs
videos recorded with the default camera do not play
Update: Install the NGCam_7.4.104-v1.8-fix.apk Once the application is installed open it take a photo close the application, this will create a folder in the SD called Gcam, inside the Gcam folder create a folder and call it Config7 and inside this place the XML file Redmi 8 GCam 7.4.104.314953318 G_Modder.xml restart the application and you're done
the only bugs that have is slow motion record not work for now
Automatic brightness does not work
Update: to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 ( use root explorer ) and reboot ..... problem solved
the necessary files are at the end of the tutorial
Steps
Note: I did the installation coming from Mui 12.EU, and there was no problem in the installation process or in the boot process
If you come from Miui12 .EU or any other GSI Rom go to step 4, if you come from the Rom stock follow the this steps
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Install a custon recovery, if you dont know how to, follow this post: https://c.mi.com/thread-2850424-1-0.html
4- Make wipe only to Cache, Dalvik, System, Data and Internal SD
5- Format data,( if it doesn't format the data you will have bootloop) then Reboot into Recovery
6- Copy all the files to the phone (Havoc-OS-v4.X-20200522-Official-arm64-ab.img you can find it by unpacking the zip), Magisk,Magisk Path Fix, Permisiver, Certification Patch.zip, opengapp (recommended nano or pico)
7- Install system image to system partition (on TWRP go to install-Install image-System) .
8- Flash Permisiver v5 (on TWRP go to install selec permisver_v5.zip)
9- Resize system partition to flash opengapps (on TWRP go to Wipe-Advanced Wipe-Select System on the list-Repair or Change File System-Resize)
To Root
once you have installed an resized the system
10- Flash the Magisk path fix (on TWRP go to install selec MagiskA11_PATH_fix.zip)
11- Flash Magisk (on TWRP go to install selec Magisk-v23.0.zip)
12- Flash Opengapps
1-Flash Certification Patch
1 - Make a wipe to Cache and Dalvik
1- Reboot
The boot process takes 5 to 10 minutes the first boot, in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image:
arm64-ab • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGapss Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/20210130/
Magisk:
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com

Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer

letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
Don't mind it, I haven't read all the article....

letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery

D
letouvetpierre said:
Don't mind it, I haven't read all the article....
Click to expand...
Click to collapse
Dont worry

Darth Inferno said:
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
Click to expand...
Click to collapse
Okay thanks I think I will try this in the few days. Thanks for your guide !

Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer

UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...

letouvetpierre said:
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
Click to expand...
Click to collapse
Hi, I need to know some things to help you, what ROM did you have before flashing Havoc? do you have the bootloader unlocked? When did you use My flashtool, what method did you use?

letouvetpierre said:
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
Click to expand...
Click to collapse
In my particular case it was not necessary to flash vbmmeta as I comment in the OP I come from Miui12.eu, but it is necessary to avoid problems whatever the ROM you have before installing Havoc is to have the latest version of TWRP and have configured a lock pattern security in ROM access and in the flashing process I didn´t have problems

Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...

letouvetpierre said:
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
Click to expand...
Click to collapse
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)

Darth Inferno said:
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Click to expand...
Click to collapse
Hey!
I thought about something this afternoon : if I flash HavocOS with adb and fastboot, we also haven't any problems with TWRP installation ! But the problem is that I haven't found any wiki to do that and i won't transform my phone to a beta tester....
Thanks a lot for your help but I think i will wait until a custom rom of LineageOs or HavocOs...

Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .

Dragonnuu said:
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Click to expand...
Click to collapse
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can help.

letouvetpierre said:
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can hel
Click to expand...
Click to collapse

Thanks for replying and trying to help but last night I managed to get havoc 4.1 is installed by flashing lineage first (using another guide from this category). I will try again to get havoc 4.1 working without flashing lineage as soon as posible because I am curious .

Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?

mwaseem851 said:
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
Click to expand...
Click to collapse
Magisk doesn't work on Android 11

letouvetpierre said:
Magisk doesn't work on Android 11
Click to expand...
Click to collapse
Finally managed to flash Magisk on Havoc 4.1 with the help of youtuberking (telegram and YouTube).
How: just flash Magisk path fix before magisk and it's good to go.

TWRP Bootloop

When I try to install a ROM, no problem installing TWRP and flashing a ROM.
But when I restart, whatever the ROM it systematically restarts on TWRP.
Everything is back to normal when I reinstall the MiUi ROM.
I installed vbmeta, TWRP is kept even with the MiUi ROM.
I tried to install a ROM on MiUi but nothing happened, TWRP is launched systematically after restarting.
I tried with several versions of TWRP but nothing worked.
Also with LOLz kernel with and without; and Magisk too.

Sleep on it !
you have to format DATA and not Wipe !

Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.

1999romelx said:
Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.
Click to expand...
Click to collapse
wrong subforum, heres the poco x2 subf
Xiaomi Poco X2
The Xiaomi Poco X2 is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm SDM730 Snapdragon 730G chipset is paired with 6/8GB of RAM and 64/128/256GB of storage. The main camera is 64+8MP and the selfie camera is 20+2MP. The battery has a 4500mAh capacity.
forum.xda-developers.com
sounds like your data got wiped, thats why theres only a twrp folder in internal. you should prolly full flash a fastboot rom since you mightve missed a few important steps

Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?

johndaog said:
Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?
Click to expand...
Click to collapse
sorry for the super late response
its supposedly for bypassing android verfied boot (avb). it blocks unauthorized roms from booting. if you search for 'what is vbmeta', we literally get no info at all and mainly speculations (no official docs etc). imho it does seem true

flashing custom rom ( pixel experience plus edition) Keep Booting Into TWRP Recovery

I was using pixel experience ROM for some time and I tried to update to the latest plus edition. The installation guide recommended full format data and flashing. I did as instructed. Now I'm stuck in booting into TWRP recovery. I looked up a few kinds of stuff and none of them worked. Is anyone else facing the same problem? has anyone got a working fix? I tried removing the TWRP folder, re-flashing TWRP with TWRP and orange fox recover, and then flashing ROM. non helped. got a broken phone now any help is appreciated.

basukala said:
I was using pixel experience ROM for some time and I tried to update to the latest plus edition. The installation guide recommended full format data and flashing. I did as instructed. Now I'm stuck in booting into TWRP recovery. I looked up a few kinds of stuff and none of them worked. Is anyone else facing the same problem? has anyone got a working fix? I tried removing the TWRP folder, re-flashing TWRP with TWRP and orange fox recover, and then flashing ROM. non helped. got a broken phone now any help is appreciated.
Click to expand...
Click to collapse
Use the correct TWRP if the rom is in A11 use A11 TWRP etc..
https://androidfilehost.com/?w=files&flid=318260
Twrp/wipe/format data write yes reboot Twrp/flash rom.

what do you mean by rom is in A11? I have redmi k20 pro raphael phone. I am using twrp for raphael code name.

basukala said:
what do you mean by rom is in A11? I have redmi k20 pro raphael phone. I am using twrp for raphael code name.
Click to expand...
Click to collapse
AOSP roms can be under ANDROID 11 or 12 or 13.
PixelExperience​
Android OS version: 11.0.0_r40
The first version is in A11 and since August in A12
Version: 12
File name: PixelExperience_raphael-12.1-20220820-1826-OFFICIAL.zip

I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.

basukala said:
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
Click to expand...
Click to collapse
Do you use this TWRP?
twrp-3.6.2_9-0-raphael-TeamWin.img​Twrp
wipe/format data write yes reboot twrp
flash the rom

Use this O.F https://androidfilehost.com/?fid=15664248565197208249

basukala said:
I had A12 then. I flashed pixel experience 12.1 on May 28(PixelExperience_Plus_raphael-12.1-20220528-1605-OFFICIAL.zip) and it went thru just fine. Now the updates of 8/20 bricked the phone.
After format data, I get the Readonly info screen, I swipe to allow modification, side loads the latest download PixelExperience_Plus_raphael-12.1-20220820-1448-OFFICIAL.zip, and restart, but back to TWRP recovery.
Some things I tried
0. https://wiki.pixelexperience.org/devices/raphael/install/
1. https://www.getdroidtips.com/keep-booting-twrp-recovery/
2. https://forum.xda-developers.com/t/pixelexperience-stuck-in-bootloop.4435533/ ( it's shown for beryllium but I did for Raphael code with all files related to Raphael version such has recovery and pixel exp. img file
Any other flow I can try to get it fixed ?
I'm thinking to reverting back to MIUI is nth works.
NOSS8 said:
Do you use this TWRP?
twrp-3.6.2_9-0-raphael-TeamWin.img​Twrp
wipe/format data write yes reboot twrp
flash the rom
Click to expand...
Click to collapse
Wipe everything, system, vendor, internal storage, dalvik, cache via advanced wipe, then flash firmware and vendor or if your rom has included firmware then just flash the rom directly. Try to boot into OS if it still bring back to twrp then again repeat the above steps and this time flash stock vendor and firmware from mi website and try to boot into OS.
Click to expand...
Click to collapse
All the best

yes using the team win version of TWRP. Used Orange Fox recovery. ( nice look and feel and features btw). But they didn't work either. What could I try more? Could I be able to revert back to MIUI stock ROM ? let me know if you have good resources. Thank you very much for your time and efforts

basukala said:
yes using the team win version of TWRP. Used Orange Fox recovery. ( nice look and feel and features btw). But they didn't work either. What could I try more? Could I be able to revert back to MIUI stock ROM ? let me know if you have good resources. Thank you very much for your time and efforts
Click to expand...
Click to collapse
Back to MIUI
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

flashed stock miui rom for now. Will tap into pixel rom in few days.

now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?

basukala said:
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
Click to expand...
Click to collapse
Xiaomi has stopped updating on Android version 11.
Which rom do you want to install?

basukala said:
now that I think, I think I did a blunder, thinking I was in A12. Can you point me to A12 firmware for Redmi k 20 pro? I"m looking into https://miuirom.org/phones/xiaomi-12, but they seem to be recovery and not firmware. I'm not sure if recovery comes with firmware. As I need to format to install, will the firmware stay or not?
Click to expand...
Click to collapse
Why bothering to manually search here and there for official ROMs
Install the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
and the app will show you links to download the latest Global, EEA, etc, zip/recovery or tgz/fastboot, or you can scroll through the older versions and pick an older if you wish
Btw, latest are MIUI 12.5, A11 - there are no official A12 ROMs for Mi 9/Redmi K20 line of models
Even if they receive MIUI 13, it will be (for some already released, but eg China only, etc) it will be A11

Same issue, I guess this is it for me. Time to buy a new phone rather than accidentally losing data from time to time with custom ROMs. I wonder if they didn't know such issue exists before releasing it to the public.