Development [ROM][Android 12L][OFFICIAL] LineageOS 19.1 for Xiaomi 11 Lite 5G NE / Mi 11 LE [lisa]

[shineburst]

Thanks for that heads up, so it looks like going backwards to a Miui ROM is probably more hazardous than it's worth at this point. Worst case scenario I do end up bricking the phone (if I haven't already) and have to send it to someone with an EDL to fix.

The article mentions something about having to flash a dummy image to pass something to antirollback before TWRP can be successfully run. I wonder if this is why I can't successfully boot into recovery?

No idea, all I know is this is a bigger PITA than any of the other phones I've ever flashed, and the first one that I may have bricked.

Agree. I have been modding my phones for years becuz of google and other companies doing things like the anti-rollback, no way to unlock bootloader, and others. It getting difficult to do so.

If all you did was flash the boot/recovery, you should be fine. I was in the same state. As I said, download the PixelOS recovery and do

fastboot set_active a
fastboot flash boot recovery <PixelOS recovery file path>
fastboot reboot recovery

and see if that works. Then, you can at least adb sideload images.

 

[Old_Mil]

Thanks for that heads up, so it looks like going backwards to a Miui ROM is probably more hazardous than it's worth at this point. Worst case scenario I do end up bricking the phone (if I haven't already) and have to send it to someone with an EDL to fix.

The article mentions something about having to flash a dummy image to pass something to antirollback before TWRP can be successfully run. I wonder if this is why I can't successfully boot into recovery?

No idea, all I know is this is a bigger PITA than any of the other phones I've ever flashed, and the first one that I may have bricked.

Agree. I have been modding my phones for years becuz of google and other companies doing things like the anti-rollback, no way to unlock bootloader, and others. It getting difficult to do so.

If all you did was flash the boot/recovery, you should be fine. I was in the same state. As I said, download the PixelOS recovery and do

fastboot set_active a
fastboot flash boot recovery <PixelOS recovery file path>
fastboot reboot recovery

and see if that works. Then, you can at least adb sideload images.

Tried it with a, didn't work. Tried it with ab didn't work.

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_ab boot-lisa-20220513.img

Sending 'boot_ab' (196608 KB) OKAY [ 4.714s]

Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully

(bootloader) Partition boot_b flashed successfully

OKAY [ 0.933s]

Finished. Total time: 5.700s



C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery

Rebooting into recovery OKAY [ 0.003s]

Finished. Total time: 0.014s

[This is where the phone once again rebooted, the white square Mi logo flashed on the screen briefly, and it again entered fastboot mode.]

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot continue

Resuming boot FAILED (remote: 'Failed to load image from partition: Load Error')

fastboot: error: Command failed

 

[fjw77]

@Its_Vixano
I keep having problems with SafetyNet, it just won't pass. I tried reinstalling LOS several times after recreating a clean starting position by reinstalling MIUI, but it keeps saying that the test failed.
Then I installed PixelOS, and SafetyNet immediatly works fine...
I really would like to use LOS. What could be causing this problem and can it be fixed?

 

[Its_Vixano]

@Its_Vixano
I keep having problems with SafetyNet, it just won't pass. I tried reinstalling LOS several times after recreating a clean starting position by reinstalling MIUI, but it keeps saying that the test failed.
Then I installed PixelOS, and SafetyNet immediatly works fine...
I really would like to use LOS. What could be causing this problem and can it be fixed?

Hi

Check out https://t.me/giostuffs/23699

Tried it with a, didn't work. Tried it with ab didn't work.

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_ab boot-lisa-20220513.img

Sending 'boot_ab' (196608 KB) OKAY [ 4.714s]

Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully

(bootloader) Partition boot_b flashed successfully

OKAY [ 0.933s]

Finished. Total time: 5.700s



C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery

Rebooting into recovery OKAY [ 0.003s]

Finished. Total time: 0.014s

[This is where the phone once again rebooted, the white square Mi logo flashed on the screen briefly, and it again entered fastboot mode.]

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot continue

Resuming boot FAILED (remote: 'Failed to load image from partition: Load Error')

fastboot: error: Command failed

Update your adb & fastboot tool from the provided guide and avoid messing with slots (if you don't want to brick it)

 

[Syluan2]

Tried it with a, didn't work. Tried it with ab didn't work.

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_ab boot-lisa-20220513.img

Sending 'boot_ab' (196608 KB) OKAY [ 4.714s]

Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully

(bootloader) Partition boot_b flashed successfully

OKAY [ 0.933s]

Finished. Total time: 5.700s



C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery

Rebooting into recovery OKAY [ 0.003s]

Finished. Total time: 0.014s

[This is where the phone once again rebooted, the white square Mi logo flashed on the screen briefly, and it again entered fastboot mode.]

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot continue

Resuming boot FAILED (remote: 'Failed to load image from partition: Load Error')

fastboot: error: Command failed

You download the latest mi stock rom here:

I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.

Ran into a bit of a problem following the flashing guide.

Downloaded the following files:

• boot.img
  192 MB17 days ago
• dtbo.img
  24 MB6 days ago
• lineage-19.1-20220824-UNOFFICIAL-lisa.zip
  1.1 GB17 days ago
• vendor_boot.img
  96 MB17 days ago

From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.

I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.

Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).

Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.

you download the latest mi stock rom herehttps://mifirm.net/download/7876

I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.

Ran into a bit of a problem following the flashing guide.

Downloaded the following files:

• boot.img
  192 MB17 days ago
• dtbo.img
  24 MB6 days ago
• lineage-19.1-20220824-UNOFFICIAL-lisa.zip
  1.1 GB17 days ago
• vendor_boot.img
  96 MB17 days ago

From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.

I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.

Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).

Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.

You download the latest mi stock rom here: https://mifirm.net/download/7876
Please follow the instructions here: https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/
I also faced the same situation as you. I did it this way and my phone booted into miui without any problem.

 

[Urban03]

MicroG is included or I have to install it separately?

 

[kunglao1]

Currently on xiaomi.eu 13.0.2 Stable, I'm thinking of pulling the trigger and installing this ROM. Has anyone who had MIUI 13 on their phones before (either stock or .eu) had any issues with installing this or any other AOSP ROM?

 

[by_BenjamiN]

Can we make google photos unlimited ?

 

[ashish289]

I think this is bricked..I disconnected it from the computer and held down the power button to try and turn it off. It turned off momentarily and then booted back into fastboot mode after momentarily flashing the Mi logo.

I ran the commands fastboot boot with boot.img from here and with the Orangefox recovery and both commands failed.

Any recommendations on where to go from here? It would be nice to at least (1) get a functioning Miui OS back on there and (2) not re lock the bootloader while doing it. Preferrably with Miui 12.5

Even if phone anti ver and miui anti ver are same MIflash gives anti version due to some reason.
To solve this problem you need to copy fastboot rom to c drive root folder and then flash with miflash.

Just make sure anti version of phone and fastboot roms are same.

 

[MyNameDuck]

Hey Vixano, love your work! But it seems like 90Hz aren't working properly. Do you have any idea?
Edit: Nvm it was Battery Saver, it force 60Hz. Is there a way to turn on Battery saver while have 90Hz enabled?

 

[Its_Vixano]

Hey Vixano, love your work! But it seems like 90Hz aren't working properly. Do you have any idea?
Edit: Nvm it was Battery Saver, it force 60Hz. Is there a way to turn on Battery saver while have 90Hz enabled?

No, that's on purpose

 

[GN-z11]

I would really love to use this ROM as my daily driver. However, safetynet not passing is really holding me back since I use banking apps. And also I think the kernel needs some tweaking as the notification panel lags a lot most of the time specially if I have a media player playing. I'll retry this one and maybe build a custom kernel to try and fix the stutters.

 

[by_BenjamiN]

Google photos backup unlimited ?

 

[Juroujin]

i want to try to create my own rom. Do you have "besides" the lineageos guides "device" specific steps of srcipt wich i could use. Its very unclear how to build/compile for devices not. Can you point me into a good direction

 

[Juroujin]

Hi,

2 questions:

1. Can we expact new release with latest merge and security patches. This build has security patch from August 8.
2. Do you have the build part publicly available ?
- Nevermid found it !

 

[Suvadeepnag]

Tried it with a, didn't work. Tried it with ab didn't work.

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_ab boot-lisa-20220513.img

Sending 'boot_ab' (196608 KB) OKAY [ 4.714s]

Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully

(bootloader) Partition boot_b flashed successfully

OKAY [ 0.933s]

Finished. Total time: 5.700s



C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery

Rebooting into recovery OKAY [ 0.003s]

Finished. Total time: 0.014s

[This is where the phone once again rebooted, the white square Mi logo flashed on the screen briefly, and it again entered fastboot mode.]

C:\Users\System Administrator\Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot continue

Resuming boot FAILED (remote: 'Failed to load image from partition: Load Error')

fastboot: error: Command failed

I have faced the same problem...what I did is reflashed stock rom using miui flash tool ..then using pixel recovery and flashed a custom rom !! Still can't flash anything from recovery for some error !!

 

[cougar_anne]

I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.

Ran into a bit of a problem following the flashing guide.

Downloaded the following files:

• boot.img
  192 MB17 days ago
• dtbo.img
  24 MB6 days ago
• lineage-19.1-20220824-UNOFFICIAL-lisa.zip
  1.1 GB17 days ago
• vendor_boot.img
  96 MB17 days ago

From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.

I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.

Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).

Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.

i believe i had a similar prob. turned out i had no boot recovery. i reflashed boot.img in fastboot and was ableto proceed to recovery from there

edit. sorry i believe it was the flash recovery img you need. not the boot.img. but id do it all over from the beginning

 

[Juroujin]

i believe i had a similar prob. turned out i had no boot recovery. i reflashed boot.img in fastboot and was ableto proceed to recovery from there

edit. sorry i believe it was the flash recovery img you need. not the boot.img. but id do it all over from the beginning

I also had this problem:

first of all i have the model which has 2 boot partitions. they call this a/b partition i guess.

what i did to fix this (if i remember correctly) is restore original boot (orginal boot.img): using ADB

1. download original fastboot rom. Make sure it's the version you have or had installed on your phone just to be sure (this contains boot.img, you can extract this using 7zip. This is an .tgz file, extract it. then extract the .tar. You can find boot.img in the "images folder")
2. copy this to your adb.exe folder (so copy to the folder which holds adb.exe)
3. using powershell and your phone connected (in fastboot mode): .\fastboot flash boot_ab .\boot.img (if you dont have a/b partition i guess it would be: .\fastboot flash boot .\boot.img )
4. reboot phone: .\fastboot.exe reboot
5. Phone should boot normal (if this was the only thing you f'd up)

Now you should start flashing guide from beginning: https://guide.itsvixano.me/flashing/

 

[cougar_anne]

I also had this problem:

first of all i have the model which has 2 boot partitions. they call this a/b partition i guess.

what i did to fix this (if i remember correctly) is restore original boot (orginal boot.img): using ADB

1. download original fastboot rom. Make sure it's the version you have or had installed on your phone just to be sure (this contains boot.img, you can extract this using 7zip. This is an .tgz file, extract it. then extract the .tar. You can find boot.img in the "images folder")
2. copy this to your adb.exe folder (so copy to the folder which holds adb.exe)
3. using powershell and your phone connected (in fastboot mode): .\fastboot flash boot_ab .\boot.img (if you dont have a/b partition i guess it would be: .\fastboot flash boot .\boot.img )
4. reboot phone: .\fastboot.exe reboot
5. Phone should boot normal (if this was the only thing you f'd up)

Now you should start flashing guide from beginning: https://guide.itsvixano.me/flashing/

So is it possible to put anything else on A/partition? And is there any point in doing so? Could you have two different roms?

 

[Juroujin]

So is it possible to put anything else on A/partition? And is there any point in doing so? Could you have two different roms?

im not an expert on this topic. But in theorie yes. With abd or in recovery you could set the active partition (a or b). But in not sure if current recovery support this for this device.