Develop Bugs

Flasing GSI in realme 3 [Guide][Updated:21-08-19]

Note:
Please take full twrp backup of your phone before you proceed with the below steps
Steps to Flash GSI:
You can follow one of the two methods to flash GSI in Realme 3
Fastboot Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2a. Commands to execute in fastboot mode:
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
fastboot reboot
TWRP Method:
1. Install TWRP:
Follow this guide on installing TWRP on your phone:
https://forum.xda-developers.com/realme-3/development/screen-doesnt-twrp-realme-3-t3944022
2. Copy system.img file to your sdcard.
3. Boot your phone to TWRP.
4. Press Install - > Install Image button -> Select the System.img file -> Select System Image-> Swipe to Flash
5. Format Data and then Wipe Cache, Dalvik Cache
6. Reboot, Done.
I used gsi from here (use aosp_arm64, download aosp_arm64-img.zip from artifacts tab and extract and flash system.img only):
https://ci.android.com/builds/branches/aosp-pie-gsi/grid
{
"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"
}
Incase you want to go back to stock follow the same process and flash stock system.img instead of gsi system.img
stock system image: https://www.androidfilehost.com/?fid=1395089523397966778
GSI List(use ARM64 AB or A/B images):
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
ADB Installer tool: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445

what Custom rom did you user sir ?

jeffalaiza said:
what Custom rom did you user sir ?
Click to expand...
Click to collapse
AOSP

fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i flash the gsi rom in gsi list of a-only partition ?

jeffalaiza said:
can i flash the gsi rom in gsi list of a-only partition ?
Click to expand...
Click to collapse
You have to use ab gsi for realme 3 phone, but if you are downloading from ci.android.com, use aosp_arm64

fawazahmed0 said:
AOSP
Click to expand...
Click to collapse
can i use this rom for daily driver that less of bugs ?

myeganz said:
can i use this rom for daily driver that less of bugs ?
Click to expand...
Click to collapse
I have not used that aosp gsi for much time, so not sure whether it is good for daily usage or not.
You can give it a try and see

What the meaning of veritydecrypt?

jeffalaiza said:
What the meaning of veritydecrypt?
Click to expand...
Click to collapse
Its a file ,link is there in the OP,
https://www.androidfilehost.com/?fid=6006931924117905745

How can i know my device use A,B, or AB ?

Link A.14 .ozip
@fawazahmed0 please link a.14 ozip file? thanks

My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
Click to expand...
Click to collapse
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata

After flashing any rom i lost my cellular network did not showed sim card, i tried to flash stock back, but it was same,
I tried doing fastboot erase nvdata and nvram, now it recognises sim but no network coverage. Is there something I'm missing?

krimstix01 said:
My baseband becomes unknown (no network signal) everytime I flash disable-dm-verity.
---------- Post added at 02:45 AM ---------- Previous post was at 02:37 AM ----------
Fixed it lol. Just run
Code:
fastboot erase nvram
fastboot erase nvdata
Click to expand...
Click to collapse
android Q ba yung GSI na to bro?

(This problem is solved now, it's just for future reference)
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot

fawazahmed0 said:
Hi, I just came to know that Disable_Dm-Verity_ForceEncrypt.zip by @Zackptg5, was causing null imei or no network issue (I have raised an issue at github for this), if you have backup of nvdata, then go to fastboot mode and do:
fastboot flash nvdata nvdata.img
I know most of the guys will not have that backup.
I tested the Disable_Dm-Verity_ForceEncrypt.zip, when my phone didn't have sim cards in it. So I never came to know about the sim problem. I am really sorry for you guys.
And one more thing, some people are suggesting to do:
fastboot erase nvram
fastboot erase nvdata
NEVER DO THAT, I REPEAT NEVER DO THAT
you are erasing the partitions, then the phone will never recover.
Thats why it is very important to take complete twrp backup of all partitions. (currently there is no twrp for realme3 which allows backup for all partitions)
So I request twrp, pbrp etc developers to modify their device tree fstab to include all the partitions in this phone and also add backup flag for all partitions (also include preloader partitions)
Here is the list of all partitions in realme 3
https://www.androidfilehost.com/?fid=6006931924117922953
For those guys who have erased their nvram and nvdata partitions, please go to service center, nothing much can be done from my side , maybe someone else can help you out.
So, guys who are having network issue after flashing Disable_Dm-Verity_ForceEncrypt.zip and have not erase their nvram and nvdata, please do the following:
1. boot to custom recovery (twrp, pbrp etc)
2. connect your phone to pc/laptop
3. execute these commands:
adb shell mkdir test
adb shell mount /dev/block/by-name/nvdata test
adb shell chcon ubject_r:nvdata_file:s0 /test/fstab.mt6771
adb shell reboot
Click to expand...
Click to collapse
Is magisk root now stable?

yametekudasai said:
Is magisk root now stable?
Click to expand...
Click to collapse
yeah

Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.

my realme 3 1821 is only black screen .. can you tell me why?

Tấn Ho said:
Does anyone try to flash Havoc Os? It's stable or not ? And does Bluetooth,Fingerprint,... work well? Or you have tried to flash another gsi rom is stable, please share.
Click to expand...
Click to collapse
I tried many GSI ROMs, but VoLTE and Fingerprint works in none of them, execept for these two, everything else seems to work, in Havoc OS atleast

Question GSI

Are there any owners who are sitting on GSI? What is the processor architecture? I really want to get away from OneUI. Judging by the asset, AOSP is not expected soon
Release Pixel Experience 11.0 v312 · ponces/treble_build_pe
Fix Extreme Battery Saver Linux denials Sync with Phh's AOSP v312 Sync with August sources of PE
github.com
UPD: I figured out the architecture of ARM64 A. Now, as I understand it, the vendor is first flashed and only then GSI ? There are generally people who use GSI, why not make an instruction?

Anyone with any GSI?

caffezim said:
Anyone with any GSI?
Click to expand...
Click to collapse
Yes. I have many other GSI.
We have arm64 a or ab, but everyone is talking about ab. The fact is that it will not be possible to simply put it. We have a dynamic section (super). I previously worked only with Vendor and that's it. Here is a completely different situation and I am powerless. I'm just in a stupor.

This phone uses arm64 cpu and a only partiton scheme, but because this phone is android 10+ only a/b GSI working.
Im flashing GSI by using these commands in TWRP:
1. This command sets system block device in r/w mode
Code:
blockdev --setrw /dev/block/dm-0
2. Using this command im flashing raw system.img
Code:
dd if=/external_sd/system.img of=/dev/block/dm-0 bs=256M
Or this command if system image is simg
Code:
simg2img /external_sd/system.img /dev/block/dm-0
3. Wipe data.
4. Reboot to system or flash gapps.
Also because this phone has android 11 only android 11+ GSI works ,excluding google android betas they never booted for me(maybe selinux issue)
I hope TWRP devs will add support for flashing system partition inside super partition like orange fox recovery already does.

map220v said:
Im flashing GSI by using these commands in TWRP
Click to expand...
Click to collapse
But how does it work without a vendor? I don't quite understand. Have you done a full wipe or not?

Realees56 said:
But how does it work without a vendor? I don't quite understand. Have you done a full wipe or not?
Click to expand...
Click to collapse
Android 8+ devices already have vendor partition provided by OEM. This device has VNDK version 30.
Yes i did full wipe (format data) it's should format userdata partition to f2fs (if it's formats to ext4 then use stock recovery to wipe data it's also wipes metadata)
Also it's seems this TWRP doesn't format metadata, use this command to format metadata after "format data":
Code:
mke2fs -t ext4 /dev/block/by-name/metadata

map220v said:
dd if=/external_sd/system.img of=/dev/block/dm-0 bs=256M
Click to expand...
Click to collapse
nothing happens after this command
upd:
I waited a little and the process was completed, I had to wait. I tried to put gaps - 70 error. Yes, and it does not load into the system. It constantly reboots, as if the system is not there. I downloaded this (underlined) Perhaps you need to download from vndklite?
Spoiler
{
"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"
}

Realees56 said:
nothing happens after this command
upd:
I waited a little and the process was completed, I had to wait. I tried to put gaps - 70 error. Yes, and it does not load into the system. It constantly reboots, as if the system is not there. I downloaded this (underlined) Perhaps you need to download from vndklite?
Spoiler
View attachment 5405433
Click to expand...
Click to collapse
I think vndklite is for android 8 devices.
Try flashing system.img using this command:
Code:
simg2img /external_sd/system.img /dev/block/dm-0
If it's flashed without errors then system.img was simg.

map220v said:
I think vndklite is for android 8 devices.
Try flashing system.img using this command:
Code:
simg2img /external_sd/system.img /dev/block/dm-0
If it's flashed without errors then system.img was simg.
Click to expand...
Click to collapse
No, it's an error right away. But the fact is that the phone writes the size of 3.3 Gb after the substitution. I'm doing Format data and reboot. But the phone is still an eternal reboot

Realees56 said:
No, it's an error right away. But the fact is that the phone writes the size of 3.3 Gb after the substitution. I'm doing Format data and reboot. But the phone is still an eternal reboot
Click to expand...
Click to collapse
I think TWRP on this device has some problems with formatting data. I used wipe data in stock recovery to make gsi boot(also i had magisk flashed)

Does anyone teach step by step how to install a gsi please?

I am also interested in step-by-step instruction.
@Realees56 @map220v did you finally managed to make it run? I am tempted to try it with instructions above and write it down if I can get any support from you guys
If I will not like it, is it possible to go back to "stock" by flashing all packages with Odin, or TWRP, or there may be some complications?

madseason.live said:
I am also interested in step-by-step instruction.
@Realees56 @map220v did you finally managed to make it run? I am tempted to try it with instructions above and write it down if I can get any support from you guys
If I will not like it, is it possible to go back to "stock" by flashing all packages with Odin, or TWRP, or there may be some complications?
Click to expand...
Click to collapse
I have not been able to launch it, I need a more advanced recovery. And what we have now does not work well with partitions

With a little bit of agony I was able to install the GSI. The speed is impressive.
But not without bugs, a lot depends on the vendor

Development [UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_A12 (Support Android 12+)

OrangeFox Recovery Project​
{
"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"
}
Downloads OrangeFox-R12.1​
Installation (for Stable roms )
Code:
fastboot boot OrangeFox-12.1-lisa.img
After booting into the recovery, flash OrangeFox-12.1-lisa.zip, it will reboot.
​
Installation method 2 (If you firmware based on weekly China Beta (xiaomi.eu and other)
[UNOFFICIAL][RECOVERY] OrangeFox Recovery R11.1_A12 (Support Android 12+)
OrangeFox Recovery Project Downloads OrangeFox-R12.1 Installation (for Stable roms ) fastboot boot OrangeFox-12.1-lisa.img After booting into the recovery, flash OrangeFox-12.1-lisa.zip, it will reboot. Installation method 2 (If you...
forum.xda-developers.com
NEW: OrangeFox Recovery | Build in Cloud
Version Information
Status: Beta ( Unofficial )
Current Beta ( Unofficial ) Version: R12.1
Release Date: 10-June-2022
Spoiler: for Donate:
BTC Wallet :
bc1qepm8lmd6228dhdpn9e0rjkplpq7yftdhkxywcp
​

is it gonna work with Android 12?

neoxcool said:
is it gonna work with Android 12?
Click to expand...
Click to collapse
yes, this recovery is built to work with a12+ (a11 is compatible)
(some little things need to be completed, but this will be later)

I have actually a Xiaomi 11lite 5G NE with Xiaomi.eu rom (a11: version 12.5.9, rooted with magisk 15.1) and twrp-3.6.0_11-0-lisa. I am very happy with them but I would like to try this recovery. Can I install it over TWRP using "ramdisk install"?
Must I reinstall from Platform tool?
I appreciate very much that you are working on a android 12 compatible version!

Doesn't work ... after sending recovery with 'fastboot boot OrangeFox-12.1-lisa.img' command it gives a little vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all ....

neoxcool said:
+++ Installation method 2
Click to expand...
Click to collapse

quasyl said:
Installation method 2
Click to expand...
Click to collapse

I did it with 1st method but will try 2nd later ...

Even after following method 2 commands, it still gives a slight vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all... I am on MIUI 13 by Papp54 (22.7.7 Beta) (https://forum.xda-developers.com/t/xiaomi-11-lite-5g-ne-by-papp54-r.4449665/)

neoxcool said:
Doesn't work ... after sending recovery with 'fastboot boot OrangeFox-12.1-lisa.img' command it gives a little vibration and the screen goes blank. when forced reboot to recovery there's MIUI recovery 5.0 that's all ....
Click to expand...
Click to collapse
Same for me (black screen after fastboot boot ...)
I have stock MIUI 12.5.8 (A11) and so far I used SHRP from HimanshuRaj (another thread here) and OrangeFox-R11.1_0-Unofficial-lisa (I also picked up here on XDA) and I was always able to fastboot boot ... to either of them (and then to install one or another permanently to the Ramdisk - actually I later Installed magisk together, too, everything works perfectly)
Don't know nwhy now this OF 12..1 fails to boot (black screen) - I had to reboot to my older OrangeFox-R11.1_0-Unofficial-lisa
---
Also, do I really need to disable VBMETA verification?
So far I used both SHRP and OF 11.1 (and patched the Magisk to the boot img), but never ever had to play with/disable VBMETA verification. Everything worked fine (also passing SafetyNet with the USNF module)
---
Also, Lisa is A/B device. Doesn't that mean that (if disabling verity in vbmeta is neccessary) instead of
fastboot flash vbmeta ...
fastboot flash vbmeta_system ...
we have to use (depending on which slot is currently active):
fastboot flash vbmeta_a ... or fastboot flash vbmeta_b ...
fastboot flash vbmeta_system_a ... or fastboot flash vbmeta_system_b ...
(or fastboot will correctly flash to the active slot just by using vbmeta and vbmeta_system, resp, as in the OP post #1)
Sorry for asking that, as I said I used two other custom recoveries with my MIUI 12.5.8 so far, and didn't need to touch vbmeta

Same issue as above. Unable to boot to recovery. However, I was able to install via TWRP. I tested OTG, backup/restore, flashing and sideload. All working. The only thing that does not seem to be working is mounting external sd. Other than that, great work. Thanks!

Eliliyah said:
Same issue as above. Unable to boot to recovery. However, I was able to install via TWRP. I tested OTG, backup/restore, flashing and sideload. All working. The only thing that does not seem to be working is mounting external sd. Other than that, great work. Thanks!
Click to expand...
Click to collapse
You tested on MIUI 13/A12 or MIUI 12.5/A11?

If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
plz check
fastboot boot recovery.img
Click to expand...
Click to collapse
Hi, Yes. This recovery.img worked. I flashed the ofox recovery now. I'm on papp54 22.1.13 rom. Thank you

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Thanks, it works now. Please update the instructions and download links in your main post.

zgfg said:
Same for me (black screen after fastboot boot ...)
I have stock MIUI 12.5.8 (A11) and so far I used SHRP from HimanshuRaj (another thread here) and OrangeFox-R11.1_0-Unofficial-lisa (I also picked up here on XDA) and I was always able to fastboot boot ... to either of them (and then to install one or another permanently to the Ramdisk - actually I later Installed magisk together, too, everything works perfectly)
Don't know nwhy now this OF 12..1 fails to boot (black screen) - I had to reboot to my older OrangeFox-R11.1_0-Unofficial-lisa
---
Also, do I really need to disable VBMETA verification?
So far I used both SHRP and OF 11.1 (and patched the Magisk to the boot img), but never ever had to play with/disable VBMETA verification. Everything worked fine (also passing SafetyNet with the USNF module)
---
Also, Lisa is A/B device. Doesn't that mean that (if disabling verity in vbmeta is neccessary) instead of
fastboot flash vbmeta ...
fastboot flash vbmeta_system ...
we have to use (depending on which slot is currently active):
fastboot flash vbmeta_a ... or fastboot flash vbmeta_b ...
fastboot flash vbmeta_system_a ... or fastboot flash vbmeta_system_b ...
(or fastboot will correctly flash to the active slot just by using vbmeta and vbmeta_system, resp, as in the OP post #1)
Sorry for asking that, as I said I used two other custom recoveries with my MIUI 12.5.8 so far, and didn't need to touch vbmeta
Click to expand...
Click to collapse
Dkpost3 will answer your query, mate ...​

Dkpost3 said:
If you firmware based on weekly China Beta (xiaomi.eu and other)
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Works on Xiaomi.eu 22.7.13. Thanks mate!

Thanks for this. I'm using PixelOS flashed the zip file via adb sideload and it works!

MAT.PH said:
Thanks for this. I'm using PixelOS flashed the zip file via adb sideload and it works!
Click to expand...
Click to collapse
Newest PixelOS build?

[email protected] said:
Newest PixelOS build?
Click to expand...
Click to collapse
Yes
PixelOS_lisa-12.1-20220712-0056

Question Unable to install Custom rom on mi 11 lite 13.0.7.0 SKOINXM

Hi,
Everytime I try to install recovery device stucks in fastboot screen the only way to get out of it is to install miui thru mi flash
Guide me through how to install custom rom on miui 13.0.7.0
Thanks in advance

Crazymods said:
Hi,
Everytime I try to install recovery device stucks in fastboot screen the only way to get out of it is to install miui thru mi flash
Guide me through how to install custom rom on miui 13.0.7.0
Thanks in advance
Click to expand...
Click to collapse
Installed the correct firmware before flashing.
for example for this rom
https://forum.xda-developers.com/t/rom-12-1-official-pixelos-aosp-stable-15-08-2022.4392297/
This firmware
https://sourceforge.net/projects/pixelos-releases/files/twelve/lisa/firmware/
Most often it is global or CN firmware.

NOSS8 said:
Installed the correct firmware before flashing.
for example for this rom
https://forum.xda-developers.com/t/rom-12-1-official-pixelos-aosp-stable-15-08-2022.4392297/
This firmware
https://sourceforge.net/projects/pixelos-releases/files/twelve/lisa/firmware/
Most often it is global or CN firmware.
Click to expand...
Click to collapse
Thanks for the quick reply
I wanted to install CorvusOs also tried but failed, everytime I try to install recovery it mess ups my firmware

Crazymods said:
Thanks for the quick reply
I wanted to install CorvusOs also tried but failed, everytime I try to install recovery it mess ups my firmware
Click to expand...
Click to collapse
Can you post the rom link?

NOSS8 said:
Can you post the rom link?
Click to expand...
Click to collapse
Thread '[SHARED] CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | Updated: 2022/08/22' https://forum.xda-developers.com/t/...12l-vanilla-gapps-updated-2022-08-22.4484681/

Crazymods said:
Thread '[SHARED] CorvusOS 4.0-L v12.1 - UNOFFICIAL | Android 12L. Vanilla/GApps | Updated: 2022/08/22' https://forum.xda-developers.com/t/...12l-vanilla-gapps-updated-2022-08-22.4484681/
Click to expand...
Click to collapse
Seems this ROM is for Renoir device
{
"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"
}

Think I should flash pixelos

Crazymods said:
Think I should flash pixelos
Click to expand...
Click to collapse
Yeap, try this rom.
Flashing the correct firmware with the TWRP but sometimes it does not work, the method that works 100% is to use Miflash(without relocking the bootloader) and let the phone restart then switch to fastboot mode once arrived at the request of the Xiaomi account.
Install TWRP
Twrp
Wipe/format data type yes
reboot twrp
put the rom in internal storage or use Otg
Flash rom
• After installation complete, Reboot system
if bootloop format data and reboot system.
This method differs from that recommended by the OP but remains the most common one, you can use that of the OP, at your choice.
In any case, formatting the data does not erase the previously installed firmware.
.Use 12 version
https://pixelos.net/download/lisa

NOSS8 said:
Yeap, try this rom.
Flashing the correct firmware with the TWRP but sometimes it does not work, the method that works 100% is to use Miflash(without relocking the bootloader) and let the phone restart then switch to fastboot mode once arrived at the request of the Xiaomi account.
Install TWRP
Twrp
Wipe/format data type yes
reboot twrp
put the rom in internal storage or use Otg
Flash rom
• After installation complete, Reboot system
if bootloop format data and reboot system.
This method differs from that recommended by the OP but remains the most common one, you can use that of the OP, at your choice.
In any case, formatting the data does not erase the previously installed firmware.
.Use 12 version
https://pixelos.net/download/lisa
Click to expand...
Click to collapse
Can you guide more briefly because I messed my os everytime I use adb command

Crazymods said:
Can you guide more briefly because I messed my os everytime I use adb command
Click to expand...
Click to collapse
No ADb command performed.
where are you with the method?

NOSS8 said:
No ADb command performed.
where are you with the method?
Click to expand...
Click to collapse
The moment I type "fastboot flash boot" Drag and drops file I get stuck at bootloop

Crazymods said:
The moment I type "fastboot flash boot" Drag and drops file I get stuck at bootloop
Click to expand...
Click to collapse
Clean flash (coming from a different ROM):
• Reboot to bootloader (fastboot)
• Connect phone to PC
• fastboot flash boot boot.img
• fastboot reboot recovery
• Select Wipe data/factory reset & confirm
• Go back and select Apply update from ADB
• adb sideload PixelOS*.zip
• Flash latest firmware from the link above
• adb sideload fw_lisa*.zip
• After installation complete, Reboot system.
or use my method with twrp.

NOSS8 said:
Clean flash (coming from a different ROM):
• Reboot to bootloader (fastboot)
• Connect phone to PC
• fastboot flash boot boot.img
• fastboot reboot recovery
• Select Wipe data/factory reset & confirm
• Go back and select Apply update from ADB
• adb sideload PixelOS*.zip
• Flash latest firmware from the link above
• adb sideload fw_lisa*.zip
• After installation complete, Reboot system.
or use my method with twrp.
Click to expand...
Click to collapse
Thanks I, ll get back to you

Crazymods said:
Thanks I, ll get back to you
Click to expand...
Click to collapse
In case that doesn't work, detail what you did.

so heres what i did till now
1-i tried to flash twrp and orange fox but unable to boot them i`m stuck at fastboot now

Crazymods said:
so heres what i did till now
1-i tried to flash twrp and orange fox but unable to boot them i`m stuck at fastboot now
Click to expand...
Click to collapse
What command did you use?

NOSS8 said:
What command did you use?
Click to expand...
Click to collapse
"fastboot flash boot" drag and dropped file

Crazymods said:
"fastboot flash boot" drag and dropped file
Click to expand...
Click to collapse
Command is" fastboot boot twrp.img' phone in fastboot mode.
then in Twrp go to Advanced -> flash current TWRP

NOSS8 said:
Command is" fastboot boot twrp.img' phone in fastboot mode.
then in Twrp go to Advanced -> flash current TWRP
Click to expand...
Click to collapse

Rename to twrp.img.
The command from the folder where the img is.
You must have flashed the xiaomi rom first to be on the correct firmware. How did you proceed?

How To Guide How to install pixel experience plus (GSI) for your poco f5

Warning: this topic is about installing an GSI (Generic System Image).
It's not optimized for specific device and not good for daily drive.
You might run into some serious bug like: 3.5mm jack not working, not receiving SMS, can't make phone call.
Introduction
Since ximi doesn't release the kernel source for this phone. There is no custom rom for Poco F5 atm. So the only way to get away from stinky MIUI is install GSI.
Requirement
To preform this, you will need(to know):
- a Poco F5 with unlocked bootloader
- a PC
- stable internet connection.
- Poco F5 is an virtual A/B arm64 device.
Let's do it.
1. Go to GSI list by phhusson chose your favorite rom and download it. And then download a fastboot MIUI rom, we will need it later.
After all download is finished, we will need to disable the verification of vbmeta partition. extract the fastboot MIUI stock rom, then find the vbmeta.img in the /fastbootROMname/images/
2. reboot your phone into bootloader, connect it to your PC and flash the vbmeta.img you just found by using command
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
After the flashing, the verification will lifted.
3. Now we get into FASTBOOTD mode by using command:
Code:
fastboot reboot fastboot
After few seconds you should able to see a FASTBOOTD on the phone screen.
4. And then we need to delete a logical partition to free up some space. Use command
Code:
fastboot delete-logical-partition product_a
to achieve that.
5. Now flash the GSI by using command
Code:
fastboot flash system {your image}
It should take 3-4 mins. After flashing is done, use
Code:
fastboot -w
to do a factory reset **This will delete all data!**
6. Reboot your phone
Congrats, you are on AOSP now!
But soon you will found out the status bar height is weird and auto brightness is broken.
To fix that, download HW overlay file and place it in /system/product/overlay/ **Root needed**
And you can fix BT audio by turning Settings - Phh Treble Settings - Misc features - "Disable audio effects" & "Use System Wide BT HAL"
Spoiler: Screenshot
{
"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"
}

Raymond.William said:
Warning: this topic is about installing an GSI (Generic System Image).
It's not optimized for specific device and not good for daily drive.
You might run into some serious bug like: 3.5mm jack not working, not receiving SMS, can't make phone call.
Introduction
Since ximi doesn't release the kernel source for this phone. There is no custom rom for Poco F5 atm. So the only way to get away from stinky MIUI is install GSI.
Requirement
To preform this, you will need(to know):
- a Poco F5 with unlocked bootloader
- a PC
- stable internet connection.
- Poco F5 is an virtual A/B arm64 device.
Let's do it.
1. Go to GSI list by phhusson chose your favorite rom and download it. And then download a fastboot MIUI rom, we will need it later.
After all download is finished, we will need to disable the verification of vbmeta partition. extract the fastboot MIUI stock rom, then find the vbmeta.img in the /fastbootROMname/images/
2. reboot your phone into bootloader, connect it to your PC and flash the vbmeta.img you just found by using command
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
After the flashing, the verification will lifted.
3. Now we get into FASTBOOTD mode by using command:
Code:
fastboot reboot fastboot
After few seconds you should able to see a FASTBOOTD on the phone screen.
4. And then we need to delete a logical partition to free up some space. Use command
Code:
fastboot delete-logical-partition production_a
to achieve that.
5. Now flash the GSI by using command
Code:
fastboot flash system {your image}
It should take 3-4 mins. After flashing is done, use
Code:
fastboot -w
to do a factory reset **This will delete all data!**
6. Reboot your phone
Congrats, you are on AOSP now!
But soon you will found out the status bar height is weird and auto brightness is broken.
To fix that, download HW overlay file and place it in /system/product/overlay/ **Root needed**
And you can fix BT audio by turning Settings - Phh Treble Settings - Misc features - "Disable audio effects" & "Use System Wide BT HAL"
Spoiler: Screenshot
Click to expand...
Click to collapse
To fix screen issue without HW overalay, you can enter Phh settings and set screen hz manually to 60

migueltb01 said:
To fix screen issue without HW overalay, you can enter Phh settings and set screen hz manually to 60
Click to expand...
Click to collapse
if you are using Pixel experience plus, lock refresh rate to 60 via phh settings will make your screen turn black every 2-3 seconds

Does anyone know why this happens?
C:\Users\Admin\Desktop\ROM\platform-tools>fastboot --disable-verification flash - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
I'm moving from MIUI Global.. and i tried with several GSI files and isn't working

RAD! said:
Does anyone know why this happens?
C:\Users\Admin\Desktop\ROM\platform-tools>fastboot --disable-verification flash - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
I'm moving from MIUI Global.. and i tried with several GSI files and isn't working
Click to expand...
Click to collapse
delete product_a
not production_a

huyizheng said:
delete product_a
not production_a
Click to expand...
Click to collapse
thx for correcting me

I also tried installing.
I had problems with calls and had to turn on
"Phh Treble Settings" - "Qualcomm features" - "Disable stereo support on VoIP"

4. And then we need to delete a logical partition to free up some space. Use command
fastboot delete-logical-partition product_a
Click to expand...
Click to collapse
'product_a' didn't work because my current slot is 'b'

RAD! said:
Does anyone know why this happens?
C:\Users\Admin\Desktop\ROM\platform-tools>fastboot --disable-verification flash - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
I'm moving from MIUI Global.. and i tried with several GSI files and isn't working
Click to expand...
Click to collapse
Did you unlock the bootloader?

I've tried many gsi roms provided here. The only one that really stable for me is Pixel OS.
download
edit: redmi note 12 turbo btw

KazuShi998 said:
I've tried many gsi roms provided here. The only one that really stable for me is Pixel OS.
download
edit: redmi note 12 turbo btw
Click to expand...
Click to collapse
any bugs?

deepx94 said:
any bugs?
Click to expand...
Click to collapse
just one i found. for now. i cant receive sms from outside. i do can send sms to others. not a groundbreaking bug but troublesome enough if you do use the sms for receiving transaction codes from bank and 2FA for account logins.

KazuShi998 said:
just one i found. for now. i cant receive sms from outside. i do can send sms to others. not a groundbreaking bug but troublesome enough if you do use the sms for receiving transaction codes from bank and 2FA for account logins.
Click to expand...
Click to collapse
Spark os is same bugs too