Database Develop

Complete setup of Lineage OS

Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Unlock and flash recovery
Backup
Format Data! (It's important if you come from Miui)
Install Q Firmware + vendor
Install LineageOS followed by gapps
Reboot into system and setup device.
Reboot into recovery and flash magisk
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
I also dont know if its possible to get recovery and rom on android 10 versions.
Thanks

Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk

BJack0 said:
Since in my last post I made a complete mess out of my first time trying to root my K20 and install lineage I wanted to my make a separate post so that I can list all the steps I need to take to correctly setup my phone how I want it.
What I actually want
A rooted device
Lineage OS
Minimal excess files (A clean Install)
Current Steps
Flash a custom recovery
Create a backup
Root???
Install LineageOS
Profit???
Feel free to tell me how stupid I am and what I need to add to the list or steps I should take to make this process better.
Thanks
Click to expand...
Click to collapse
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
You could also check LOS thread: Here and here
Remember:
Chinese firmware: Widevine L3 and NFC support
Indian firmware: Widevine L1 but no NFC support

ishaqtkr said:
Did these steps not work?
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
They may work as it but I was just wondering if anyone could go into more detail or if there was a better approach and from what Kollachi said there clearly is a better way that what I said.

Since I'm in stock ROM and haven't ever flashed AOSP ROM in this phone I'll just back off lol
Sent from my Redmi K20 Pro using Tapatalk

Kollachi said:
1. Unlock and flash recovery
2. Backup
3. Format Data! (It's important if you come from Miui)
4. Install Q Firmware + vendor
5. Install LineageOS followed by gapps
6. Reboot into system and setup device.
7. Reboot into recovery and flash magisk
Click to expand...
Click to collapse
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it

Any of the two recoveries will work. Q firmware means Android Q. Wile data/cache dalvik that's it. Regarding firmware, there's a clear topic of Lineage OS in K20 Pro forum which is still in unofficially state
Sent from my Redmi K20 Pro using Tapatalk

BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
1. You can take what you want. Orangefox is based on TWRP.
2. Format data is needed if you come from miui. If you did it you are good to go. But it wouldn't be false to wipe system, dalvic, cache
3.https://downloads.akhilnarang.me/MIUI/raphael/ --> Take 10.4.6.0 or 10.4.8.0 (Android 10 = Q)
4. No there is no specific version.

BJack0 said:
I like the details steps but I have a few questions.
(Unlock and flash recovery) From what I can tell there are two recovery's Orange fox and TWRP
(Format data) Just format data or are there other sections I should format/wipe
(Install Q Firmware + Vendor) I have no idea what Q firmware is or what vendor you are referring to
(Install Lineage + gapps) Is there a specific version from the Mi 9T pro since the official site doesn't list it
Click to expand...
Click to collapse
I would recommend the latest TWRP from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
https://forum.xda-developers.com/k20-pro/development/rom-lineageos-17-0-t3976469/post80406191

Robbo.5000 said:
I would recommend the latest TWRP from here
The dev is an official TWRP dev, so this version, or something very close to this, is likely to become official in the future.
OrangeFox is a heavily modified TWRP and has a lot of added functionality specific to MIUI. If you wanted to stay on stock MIUI, but debloat and have root, etc. then OF would be the better choice, as it has functionality that lets it play nicely with MIUI (it can remain installed when OTA updates are installed)
As someone new to flashing on Android, I would suggest downloading a 10.4.x fastboot ROM from the site I pointed to in your other post, then follow the same procedure to flash the ROM.
Make your choice based on Kollachi's info and what's important to you (HD Netflix - choose Indian, or a working NFC - choose Chinese)
However you MUST change the flash option to 'clean all'.
At this point you've got a nice squeaky clean starting point.
Boot into the ROM at least once, though it's not necessary to go through all the setup.
After that follow Kollachi's steps but you can now ignore the step to flash vendor and firmware as it's all part of the fastboot ROM already flashed.
Wipe cache and dalvik, format data.
There is no official LOS for this phone yet. Hopefully it will go official in the future.
For now just get the current Android 10 based LOS from here.
Click to expand...
Click to collapse
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE

BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.

Kollachi said:
I just told you what I have done and I'm running it so far without issues.
Robbo just said you should flash the whole Chinese or indian rom but I don't like his steps because:
1. File is much bigger
2. MiFlash is just meh
3. If you forgot to change the flash process you are bricked if you don't take the correct firmware for your phone.
Default option in Miflash is set to "Clean all and lock". Every time you use it, you will need to change it into "clean all" or something other.
Click to expand...
Click to collapse
Yes flashing the whole fastboot ROM does add the risk, if you forget to change the flash option, but you are guaranteed a clean slate and so less likely to have any niggling issues that nobody else has. I would bet large sums of money that many of the issues you see on here, where only one person has some problem and everyone else is fine, would be solved by fastboot flashing MIUI before installing the ROM of choice.
If you know what you're doing and know when you'll be OK with what you've got and know when it's best to start clean, then going with the vendor and firmware is easier.
But if your unsure and new to flashing on Android phones, I will always suggest go with the overkill and know you've got the clean slate to start with.
---------- Post added at 10:56 AM ---------- Previous post was at 10:36 AM ----------
BJack0 said:
When ever I think I have the process memories and I follow the steps on my screen I still somehow **** this up and I cant understand how.
My current steps include
Flash the fastboot with the ROM that you linked me in my first post
Flash the recovery with TWRP (Every time I have then tried going back into TWRP is failed to work and prompted the original MIUI recovery)
Install the TWRP zip from custom recovery to try and fix the issue above (Only had this work once on orangefox and then never had success again)
So now I try to just flash the recovery and boot to it using CMD and it works fine
Move the lineageOS files from my PC to the phone SDCard
If I wipe data and the caches as suggested then the lineageOS zip is now go and I am back to flashing the fastboot ROM to restart the process
I know this might seem like im either stupid or just not getting it but could you or anyone else please make a bullet pointed list with links to what I have to download in order to actually achieve this since I cant do anything correctly even when trying to follow the steps.
(Im going to sleep since I have been trying to do this for hours now and I will check reply's in the morning.
Thanks for the help so far EVERYONE
Click to expand...
Click to collapse
It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.

It's sounds like the main issue is stock recovery is being restored. This is something that MIUI will do when it boots up.
When you first install TWRP you cannot boot into MIUI before booting to TWRP as you instantly lose TWRP. So you need to boot into TWRP first in order to do something to prevent it being overwritten.
Options are
1
Code:
fastboot boot TWRP.img
2 Use the button combo whilst still in fastboot - power and vol+, hold both until the phone vibrates and the initial logo appears.
Now to keep TWRP you need to either flash a custom ROM, flash Magisk or flash the dm-verity script.
In your case you want to flash LOS, so now you've booted into TWRP go ahead and continue with the steps given.
Also, wait until after you've formatted data before copying everything over. You can access the phone as an MTP device when in TWRP, so you'll be able to connect it to a PC and drag everything across, or you can stick everything on a USB OTG pen, if you have one, TWRP can read data from them too.
Click to expand...
Click to collapse
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.

BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
You connect your phone to computer while in recovery to transfer the OS zip
Sent from my Redmi K20 Pro using Tapatalk

BJack0 said:
The exact problem I have is that I cant transfer any files to the device after formatting the data. I follow the steps correctly and I get into TWRP successfully and then everyone has told me to format the data then install lineage but I cant install the OS if formatting the data removes it.
Get device into fastboot
Flash revocery with TWRP
power the device off
hold volume up and power
boot into custom recovery
format data
move lineageOS onto my device
install lineageOS
reboot
done.
This is the list of exact actions I am doing with no results is there something I am missing or something that is in the wrong order.
Click to expand...
Click to collapse
After format data, reboot your device into recovery again and transfer LOS, gapps and all files you need.
Format data kills the storage.

I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.

Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes I did that and it worked, unmounting and remounting helps detect the storage in PC
Sent from my Redmi K20 Pro using Tapatalk

Robbo.5000 said:
I always used to reboot from TWRP back in to TWRP after formatting data, but I've recently seen someone saying that they just unmount data then remount it again. I haven't tried it myself but it certainly makes sense and would be quicker too.
Click to expand...
Click to collapse
Yes that works. Tried it myself but prefer to reboot into recovery again.:laugh:

Finally Successful
After a long post I have finally finished the process successfully. This was pretty educational for me since I didn't understand any of this at the start I would like to thank everyone who reply's and all the information that you have provided.

need help guys, i stuck in bootloop.
- fastboot rom global china V10.3.17.0 PFKCNXM
- fastboot twrp 3.3.1
- format data
- flash vendor image cn 10.4.6.0
- wipe cache/dalvik
- flash lineage os
- flash gapps nano
- reboot
- stuck bootloop

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.

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing

Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!

Reserved

Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why

Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake

Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use

Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing

Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.

Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.

kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...

double tap to wake works while aod is on?

I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.

GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.

Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.

Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.

Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting

All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.

Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix

Question Downgrading from stock A12 to Xiaomi EU A11

I'm planning to go from stock 13.0.2 A12 to Xiaomi EU 13.0.10 A11. Based on what I read, this is what I have to do:
- Unlock bootloader (which will factory reset the phone).
- Start fastboot mode.
- Connect to PC.
- Download the ROM (Recovery for RN11, since it's downgrade I'll have to factory reset but it'll already be done during bootloader unlock)
- Run first_time_installation.bat (or something like that).
Are these steps correct? This will be the first time I flash a ROM and I really don't want to mess it up. Thanks in advance!

The first step is correct, you must unlock the booloader. However, you can't install Xiaomi.eu ROM on fastboot mode, that's only for stock ROMs. If you try to do that using a custom ROM, it could brick your phone. For Xiaomi.eu (or any other custom ROM) you need to install first a custom recovery like TWRP: first downlaod the custom recovery file, then copy it into the storage and then install it. You can do the last 2 things with CMD commands . Then copy the custom ROM file like any other file into the phone's storage, restart the phone on recovery mode and install the ROM from the TWRP interface. I did it like a month ago, I don't remember all the details though. Just look for a tutorial, it's not that hard.
Good luck.

lenny73 said:
The first step is correct, you must unlock the booloader. However, you can't install Xiaomi.eu ROM on fastboot mode, that's only for stock ROMs. If you try to do that using a custom ROM, it could brick your phone. For Xiaomi.eu (or any other custom ROM) you need to install first a custom recovery like TWRP: first downlaod the custom recovery file, then copy it into the storage and then install it. You can do the last 2 things with CMD commands . Then copy the custom ROM file like any other file into the phone's storage, restart the phone on recovery mode and install the ROM from the TWRP interface. I did it like a month ago, I don't remember all the details though. Just look for a tutorial, it's not that hard.
Good luck.
Click to expand...
Click to collapse
Haha thanks for your reply! This came a bit late, it has been exactly a month since I flashed but I hope this could help someone else. Spes/spesn is listed as recovery on the list but the Android 11 versions only come in Fastboot. When I unlocked bootloader, I had already prepared Pixel Experience and Xiaomi.eu ROM. PE's recovery gave me bootloop so I used the next thing available and flashed Xiaomi.eu .bat file.
I was a bit worried when it was stuck on the same screen for 15 minutes but then it loaded with no problem. Not really sure if I did the right thing or I was just lucky

Indonesia global rom work call recording mi dialer and step counter intalled in eea and no problem