Database Users

How to flash GSI-s on ATU-Lxx after the April 2019 security patch?

Code:
*** I'm not responsible for dead sd cards, thermonuclear war, getting you fired because the alarm has failed. Your warranty is void if you continue! ***
Code:
*** Everything you read here was a success for my ATU-L21 variant of the Huawei Y6 (2018). Don't be alarmed, the files mentioned here are 100% compatible with the phone ***
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Code:
fastboot flash kernel /path/to/KERNEL.img
Flash the recovery you downloaded with
Code:
fastboot flash recovery_ramdisk /path/to/recovery.img
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with
Code:
adb reboot recovery
, the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).

hawkhu said:
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Flash the recovery you downloaded with
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with , the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).
Click to expand...
Click to collapse
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)

dj 77mx said:
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)
Click to expand...
Click to collapse
System.img goes to the system partition, obviously.

This worked flawlessly, the only difference is that I couldn't flash Kernel.
The ROM I used: PHH Treble 9.0 github.com/phhusson/treble_experimentations/releases/tag/v117
The steps I took:
- Factory reset phone
- Backup stock recovery_ramdisk
- Download kernel (unused) and vendor
- Boot fastboot
- Flash twrp in recovery_ramdisk
- Boot twrp
- Flash vendor, flash system
- Clean caches
- Reboot fastboot
- Flash stock recovery_ramdisk
- Reboot
erecovery did not complain, everything was ok there

Anyone tried this at atu l22 latest build?

UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
Since the ATU-L21 and L22 is the same hardware wise it should work without any problems.

i keep either getting a black screen or vendor not mount or system not mount if not vendor ( ATU-L22 Y6 2018 )

UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
.REPLYING--- Hey bro have you tryed flashing custom rom to the Atu-L22 with any luck?

Still trying to flash a custom system.img to my Atu-L22 after weeks of no success but flowing thru with countless amounts of tutorials, Anyone have any ideas for this phone, any help much appreciated haha?

I'm stuck in a boot splashscreen... This phone is really not easy to work with x(
edit : Narrowing it down, apparently, I don't have a vendor partition to flash the vendor to... I am starting to loose hope.

I need stock recovery_ramdisk.img . Anyone have? (Im sorry for my bad English )

[RECOVERY][3.3.1-17][laurel_sprout]Unofficial TWRP recovery for Xiaomi Mi A3 (Test)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- TWRP boots
- TWRP seems has problems with external sdcard and otg
- Magisk Flash works
Install guide :
Remember to use the appropriate .img version
https://forum.xda-developers.com/showpost.php?p=80168528&postcount=16
Other Install guide :
1. Follow this guide to root your device
2. Flash the TWRP installer like a magisk module
3. Flashing the TWRP installer you will lose the root, so you will need to flash magisk again from magisk manager before reboot the device or you can reboot the device and flash magisk in twrp
HOW TO UPDATE a ROM and KEEP TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk;
- Reboot.
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.3.1-17 Unofficial by mauronofrio (Guide included in the link)
Source code:
https://github.com/mauronofrio/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_laurel_sprout
Precompiled Stock Kernel
Donations:
Credits:
Thanks to Jyotiraditya Panda for the help with the tree
Thanks to @mdeejay for the hard testing
Created 2019-08-31

Bug
https://imgur.com/Y83Xhw2installed this TWRP but I'm with this bug, there are a way to fix this?

mauronofrio said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features:
- TWRP boots
- TWRP seems has problems with external sdcard and otg
- Magisk Flash works
Install guide :
1. Follow this guide to root your device
2. Flash the TWRP installer like a magisk module
3. Flashing the TWRP installer you will lose the root, so you will need to flash magisk again from magisk manager before reboot the device or you can reboot the device and flash magisk in twrp
HOW TO UPDATE a ROM and KEEP TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk;
- Reboot.
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.3.1-15 Unofficial by mauronofrio
TWRP 3.3.1-15 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_laurel_sprout
Precompiled Stock Kernel
Donations:
Credits:
Created 2019-08-31
Click to expand...
Click to collapse
Screenshots please

Rajendran Rasa said:
Screenshots please
Click to expand...
Click to collapse
For what, have you never seen TWRP?

nelinthon said:
https://imgur.com/Y83Xhw2installed this TWRP but I'm with this bug, there are a way to fix this?
Click to expand...
Click to collapse
The TWRP asked you for pattern or password when it started?

mauronofrio said:
The TWRP asked you for pattern or password when it started?
Click to expand...
Click to collapse
Can I directly flash twrp in fastboot??
fastboot flash recovery twrp.img
Because some mi devices won't boot to system after entering twrp

Thanks for your work! Is a big start for our phone!
Grazie dall'Italia!

mauronofrio said:
The TWRP asked you for pattern or password when it started?
Click to expand...
Click to collapse
yes

Rajendran Rasa said:
Can I directly flash twrp in fastboot??
fastboot flash recovery twrp.img
Because some mi devices won't boot to system after entering twrp
Click to expand...
Click to collapse
Recovery partition doesn't exist, so you can't flash it. The installation guide is explained in the first post

mauronofrio said:
The TWRP asked you for pattern or password when it started?
Click to expand...
Click to collapse
I fix it, just put the device password, so easy hahaha

nelinthon said:
I fix it, just put the device password, so easy hahaha
Click to expand...
Click to collapse
Yes that is for decryption

mauronofrio said:
Recovery partition doesn't exist, so you can't flash it. The installation guide is explained in the first post
Click to expand...
Click to collapse
That's not a guide
Explain with step 1,2,3
I have downloaded both the files given in op
Then how to flash twrp?? In fastboot
after flashing twrp do I need anything to flash for booting stock ROM
---------- Post added at 04:12 PM ---------- Previous post was at 04:07 PM ----------
Give the detailed step-by-step instructions for flashing twrp with usb drivers and adb fastboot files

Another problem
I tried to flash a GSI rom and STOCK rom but appears an error: UPDATER PROCESS ENDED WITH SIGNAL 4

Pls for cc9e also twrp

Install method explained
Hello!
Since the install steps provided on OP maybe confusing I thought on sharing here the steps I've made in order to get TWRP working....let's call it a "noob friendly guide", ok?
Here he we go:
0 - Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
1 - Download both twrp-3.3.1-15-laurel_sprout-mauronofrio.img and twrp-3.3.1-15-laurel_sprout-mauronofrio-installer.zip files present on OP
2 - Download latest Magisk Installer, Magisk Uninstaller and Magisk Manager from HERE.
3 - Copy all of the above to your phone internal memory (since current TWRP doesn't allow sdcard nor USB OTG yet...)
4 - Connect the phone to your PC
5 - Reboot to bootloader
Code:
adb reboot bootloader
6 - Check your current active slot
Code:
fastboot getvar current-slot
7 - Flash TWRP image into the current inactive slot (we do this just to leave the current active slot with no changes...at least for now)
If your current active is slot b, then run:
Code:
fastboot --set-active=a
Or, if your current active is slot a, then run:
Code:
fastboot --set-active=b
And afterwards, run:
Code:
fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img
(of course that img file must be on the same path where you have adb and fastboot...)​8 - Reboot to TWRP:
Code:
fastboot reboot
NOTE: Long press Vol+ button before hitting "ENTER" and leave it pressed until you see the Android One logo (just to force boot into recovery)​
Just a heads up:
Now we are on TWRP booted on the "previously inactive slot". The "previously active slot" continues unchanged. Nothing "bad" really happened until what we decide to do next. If we want, we can just make a TWRP backup of the current slot and nothing else. Afterwards, we could always reboot to bootloader, change to the "previously active slot" again and boot system. If we do this, we continue without TWRP and root but we would now have a TWRP backup of the system present on the "inactive slot". Anyway let's presume you really want to permanently install TWRP and ROOT your device....so let's continue.
9 - While on TWRP, install twrp-3.3.1-15-laurel_sprout-mauronofrio-installer.zip
Note that, by doing this, TWRP will be permanently installed into both slots. This means that, if someday, you want to revert to stock, you'll need to reflash stock boot.img on, at least, one of your slots.​10 - After installing TWRP zip, go to reboot menu, change to the active slot (the one you had on the beginning of these steps) and reboot to TWRP
11 - After TWRP reboots, install Magisk installer zip
12 - Finally, reboot to system
13 - Enjoy
Thank you @mauronofrio and Jyotiraditya Panda for your work on bringing TWRP to Mi A3 (laurel_sprout).
I just hope you're able to fix USB OTG and SDCard bugs and, of course, make this TWRP official.
Cheers!

rom.zip
where is rom.zip

I wonder if it can work on Mi CC 9e......

Crosstyan said:
I wonder if it can work on Mi CC 9e......
Click to expand...
Click to collapse
This will not work on Mi CC 9e

Uninstall method explained (aka revert to stock)
Get boot.img, system.img and vendor.img from your stock ROM build type (EU or Global) and store them on the same folder you have adb and fastboot
Uninstall all Magisk Modules you have installed (do the same for Substratum themes, if any)
Reboot to TWRP
While on TWRP, Flash Magisk Uninstaller Zip
Reboot to bootloader
Code:
fastboot getvar current-slot
(just to make sure which slot is currently active)
Code:
fastboot flash boot boot.img
(from your stock ROM build type)
Code:
fastboot set_active [B]b[/B]
(or a, if you were on slot b)
Code:
fastboot erase boot
Code:
fastboot erase system
Code:
fastboot erase vendor
Code:
fastboot flash vendor vendor.img
(from your stock ROM build type)
Code:
fastboot flash system system.img
(from your stock ROM build type)
Code:
fastboot flash boot boot.img
(from your stock ROM build type)
Code:
fastboot reboot
By doing this your phone will now boot to the previously inactive slot, where an older system build is installed, with all your userdata preserved.
Now you just have to wait for the OTA to arrive and install it in order to have the latest stock Rom build installed without TWRP and Magisk.
NOTE:
This procedure is also intended for everyone that want to install latest stock OTA without losing userdata. The Magisk OTA Installation Tutorial could fail if you tampered with system or vendor partitions, that's why I've decided to share this procedure

There's a way to relock the bootloader???

[RECOVERY][STABLE]Unoffical TWRP for Xiaomi Mi A3[laurel_sprout]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.
HOW TO UPDATE a ROM and Keep TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk(recommend to use Magisk v19.4);
- Reboot.
Download:
TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
TWRP 3.3.1-2 Unofficial by Nikesh Kataria
Donations:
Credits:
Thanks to @mauronofrio for a great help to make a stable recovery
Thanks to @Typhus_ for hardcore testing
Thanks to @prakash78 for testing
Contributors
Nik001
Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp
Version Information
Status: Stable
Created 2019-10-21

Reserved

This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!

Typhus_ said:
This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!
Click to expand...
Click to collapse
Welcome and thank you for testing twrp.:fingers-crossed:

Thank u peru sir

A3 real modding let's start

Good Job @Nik001

Anyone tell how to flash twrp... proper commands
Please
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Is that tested anyone.

Stock fw 10.3.8 (global) not booting with this twrp - in 10.3.8 audio modules have strange dependence "saved_command_line" symbol from kernel. For loading this modules need patch kernel sources -
diff --git a/init/main.c b/init/main.c
index 6d1880f0b852..2106f54a7008 100644
--- a/init/main.c
+++ b/init/main.c
@@ -128,6 +128,7 @@ void (*__initdata late_time_init)(void);
char __initdata boot_command_line[COMMAND_LINE_SIZE];
/* Untouched saved command line (eg. for /proc) */
char *saved_command_line;
+EXPORT_SYMBOL_GPL(saved_command_line);
/* Command line for parameter parsing */
static char *static_command_line;
/* Command line for per-initcall parameter parsing */
Click to expand...
Click to collapse

Proper install method explained
Hello!
Please, @Nik001, update the OP with the install method that I'm going to describe next, ok?
It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for "not that experienced users".
Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
When TWRP recovery boots, if you have a stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the TWRP zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Why do I suggest this?
By doing this method (which seems more complicated but, trust me, it's how it should be done) we will flash TWRP img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When TWRP boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the TWRP img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition.
On the other hand, if we have a stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching TWRP img and boot.img).
Cheers!

Sapper Morton said:
The method Typhus shared works 100% of the times; however I must say, I don't use it, just preference; as it follows, instead of flashing into the inactive slot, I flash the pre_patched boot image into the active slot, this of course will mostly like break network and other components on the ROM, if you mismatch image versions; however, if you flash the stock boot image (using install button, inside TWRP, tapping into 'images', select your stock boot.img) and then patch it using the TWRP Installer right after, you will be using the right image, so no problem will occur, and mostly important, no slot change is needed. Both methods works, choose what you prefer, just read it carefully and I repeat, always use the same boot image from your firmware, a lot of confusion comes to the fact, that when you uses TWRP.img or Magisk.img they aren't boot images, but they are; A/B partition scheme doesn't use some individual partitions anymore, as /recovery, thus is extremely important to patch your boot image, where the recovery, kernel and other components now lives.
Click to expand...
Click to collapse
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!

Typhus_ said:
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!
Click to expand...
Click to collapse
As someone who just wants to root his phone with TWRP and few magisk modules, and not miss out on OTAs, seeing these many methods is so confusing and overwhelming ?

After flashing recovery from pc..then go for fastboot reboot from minimal adb and " volume+ key" i saw error in my phone "no command"

Sapper Morton said:
Use the method Typhus explained, it's more simple in the long run; there will be no need to manually flash stock boot image afterwards, since Magisk will have done a proper backup, thus, you will only need to use 'restore image' feature inside Magisk Manager; When taking an OTA, make sure to read the complete Magisk documentation before proceeding:
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
Thank you! I will do that. But one more thing I'd like to ask. Do you know where I could find the boot image for 10.3.8.0.PFQMIXM? I checked git for dumps, but I couldn't find the boot image for this one.

Sapper Morton said:
Sure, read the OP; Typhus has linked a couple of boot images, including 10.3.8.0 PFQMIXM.
https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509
Click to expand...
Click to collapse
Sick! Thank you very much, sir!

What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
Just flash the zip in twrp that you have.
That's what I did and it worked no problem on pe ROM

Typhus_ said:
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.
Click to expand...
Click to collapse
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?

Makishima said:
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?
Click to expand...
Click to collapse
Yes, that's right.

[RECOVERY][UNOFFICIAL] OrangeFox R10.1

Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
OrangeFox R10.1
Working features
Android 10 ROM flashing
Internal storage decryption
Data partition backup
Consistent A/B slots flashing - local zip files always flash to ACTIVE slot, except sideload - adb sideload flashes ROM to INACTIVE slot
Known issues
You can't encrypt backups right now
Splash screen is not saved (visual bug)
Installation
If you don't have custom recovery installed
Download recovery image and installer zip
Reboot to fastboot
fastboot set_active b
fastboot flash boot OrangeFox_laurel_sprout_22-03-2020.img
Hold volume up button before executing fastboot reboot, release button after you see OrangeFox logo
Flash recovery installer zip, reboot to recovery
If already have custom recovery installed
Download recovery installer zip
Flash recovery installer zip
Update
Download recovery installer zip
Flash recovery installer zip
Downloads
22.3.2020
Image
Installer zip
Older builds
21.3.2020
Image
Installer zip
Sources
Recovery
Device tree
Credits
OrangeFox team - ROM
@nik001 - device tree and installer
@oddlyspaced
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] OrangeFox R10.1, Tool/Utility for the Xiaomi Mi A3
Contributors
Golbinex
Version Information
Status: Stable
Created 2020-03-21
Last Updated 2020-03-22

Reserved
Changelog
22.3.2020
You can backup internal storage now (you need sd card/usb flash for this, also you need to mount internal storage first)
Round corners
Less logs
21.3.2020
Initial build

Works for last android 10 stock?

facundonak said:
Works for last android 10 stock?
Click to expand...
Click to collapse
Yes, you can flash stock a10.

i tried flash from fastboot stock android 10 and the phone go direct to fastboot

New build is up.
You can backup internal storage now (you need sd card/usb flash for this, also you need to mount internal storage first)
Round corners
Less logs

facundonak said:
i tried flash from fastboot stock android 10 and the phone go direct to fastboot
Click to expand...
Click to collapse
There is no official stock A10 fastboot ROM yet, flash stock fastboot a9 and flash stock a10 via ota zip.

Flash from USB OTG supported ?

kosmasgr said:
Flash from USB OTG supported ?
Click to expand...
Click to collapse
Flash from SD card works. I can't test usb drive, because I don't have a USB-C adapter.

Thank you for your hard work!
Do you know what is the error 127?
/sbin/foxstart.sh process ended with ERROR: 127

Please help
i followed this tutorial but my phone restart always on fastboot logo
Is there a solution to restore any things please

moyses said:
Please help
i followed this tutorial but my phone restart always on fastboot logo
Is there a solution to restore any things please
Click to expand...
Click to collapse
Switch to the slot you wasn't tampering with. (find current slot with fastboot getvar current_slot, then change to inactive with fastboot set_active [slot letter].

Golbinex said:
Switch to the slot you wasn't tampering with. (find current slot with fastboot getvar current_slot, then change to inactive with fastboot set_active [slot letter].
Click to expand...
Click to collapse
It did not work, any one with stock boot image please, my phone is out

What the difference between your build and the offcial one from Orange Fox site?

moyses said:
It did not work, any one with stock boot image please, my phone is out
Click to expand...
Click to collapse
If you have pie, you can flash only boot image from fastboot stock ROM
inouext said:
What the difference between your build and the offcial one from Orange Fox site?
Click to expand...
Click to collapse
Newer version (R10.1), also installing a10 ROMs didn't work for me on that one.

It doesnt worrrrrrrrrrrrrrrrrrrrrrrrrrkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk!!

doesnt work, on both slots.

cldkrs said:
doesnt work, on both slots.
Click to expand...
Click to collapse
It does.
You are probably on android 10 yes?
This recovery.img is built with pie kernel so only works on android 9 pie.
The recovery.installer.zip will work on both android 9 and 10.
Flash twrp.img for android 10 and then use ofox installer.zip to install ofox.
---------- Post added at 11:22 AM ---------- Previous post was at 11:22 AM ----------
Noexcusses said:
It doesnt worrrrrrrrrrrrrrrrrrrrrrrrrrkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk!!
Click to expand...
Click to collapse
Read above. It does work please edit your comment to reflect this

How can i flash persist.img because my fingerprint doesnt work
Mi A3 cihazımdan Tapatalk kullanılarak gönderildi

What's happening? I can not flash any recovery on Android 10, always fastboot.

[ROM][STABLE] LineageOS 18.0 [MI A3] [laurel_sprout]

{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS 18.0 based on Android 11.0
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
WHATS WORKING :-
- RIL
- WiFi
- Bluetooth.
- Camera
- Audio
- Sensors
- Flash
- GPS
- VoLTE
- FOD (Fingerprint on display)
- Face unlock.
- DT2W.
- Proximity in calls.
- FBE.
WHAT DOESN'T :-
- You tell.
HOW TO FLASH :-
1) Download ROM zip and Gapps (optional).
2) Reboot to Recovery.
3) Wipe Data, System, Cache.
4) Format data. (It might work without this too but its recommended to format data to boot successfully. If stuck on splash or boot animation or reboots back to fastboot or recovery, format data)
5) Flash ROM + Recovery installer (any as per your choice).
6) Reboot to Recovery.
7) Wipe cache.
8) Reboot and enjoy.
IMPORTANT INSTRUCTIONS :-
- The build is based on OSS vendor. Firmware is included in the ROM zip. No need to flash any firmware.
- Fingerprint works fine with no flicker. (Accuracy is improved.)
- Face unlock works.
DOWNLOADS :-
ROM :- LineageOS 18.0
GAPPS :- GAPPS (optional)
DONATION LINKS :-
PLEASE DONATE ME IF YOU LIKE MY WORK
PayTM : [email protected]
Paypal : http://paypal.me/pms2299
GPay : [email protected]
I can't build continuously on my laptop and I need a server to build. Consider donating for continuous support. I will be able to provide bug fixes sooner if I get a server. Please donate if you can. Thanks
SUPPORT GROUP :-
LineageOS Support group :- Telegram
SOURCES :-
KERNEL
XDA:DevDB Information
LineageOS, ROM for the Xiaomi Mi A3
Contributors
PrathameshMS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 18.0
Stable Release Date: 2020-10-10
Created 2020-10-10
Last Updated 2020-10-10

Thank you so much

Great, and I mean, GREAT job!!
As usual....
Thank you for your hard work.

You're my [email protected]|<ing idol!
Starting download rigth now

So it is based on Android 11 or 10?

r3pairer said:
So it is based on Android 11 or 10?
Click to expand...
Click to collapse
It's based on 11

Can it be used daily?

i dont know is it only me or not
when im in a call (in discord or any other apps) others say that they can hear my phone sound like instagram or any other thing
i have this problem with any other roms so as lineage
please fix it thanks i realy want to use android 11

Great work. Fod is better than stock to recognize my finger, it has just a small and quickly brightness flickering but is almost unnoticeable.
SElinux is permissive and FM radio is missing but they aren't a big issues for me.
Thanks for this rom.

Hi! Does LOS18 supports signature spoofing? Thanks!

Step by step install procedure for LOS18
1 - Turn your phone into fastboot mode (run adb reboot bootloader or shutdown the phone and turn it on again while pressing Power + Vol- keys)
2 - On fastboot mode set a as the active slot by running the command:
Code:
fastboot set_active a
3 - Now, flash latest STOCK FASTBOOT ROM using flash_all.bat (or flash_all.sh if you're using Linux)
4 - Wait for the installation to finish and, after seeing the welcome screen, go to fastboot mode again
5 - Now run these commands:
Code:
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
(keep pressing Vol+ key to force the phone into recovery mode)​
6 - We're on TWRP Recovery using slot B. Do this:
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery
Format Data with "yes"
Install lineage ROM zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip (yes, again...)
Reboot to Recovery​
7 - Now we're on TWRP Recovery using slot A. Do this:
Install NikGApps Core version. (This is optional! The ROM works fine without any GApps but if you want them, use CORE version!)
Install Magisk (This is also optional! The ROM works fine without it but if you want it, get the MagiskR zip you'll find on the telegram support group!)
Reboot to fastboot and run:
Code:
fastboot flash dtbo dtbo.img
Code:
fastboot reboot
Your device will now reboot to System and you may enjoy LineageOS 18!​
NOTES:
By doing this procedure you will have LineageOS 18 system installed only on slot A!
If your device fails to boot, you should just start all over again! Trust me, it's easier than trying other flashing methods.
You can now install a different Recovery if you like, for example, SHRP Recovery. Simply go to TWRP and flash SHRP installer zip.
You can, also, install a different Kernel. Check the Telegram support group, there are other kernels compatible with this ROM (I'm using No. 192 OSS Batt version, for instance).
All files mentioned on this post can be found on the Telegram support group (including latest ROM build, MagiskR version, twrp and dtbo.img)
Cheers!

wifi does not work

Etzio_Auditore said:
wifi does not work
Click to expand...
Click to collapse
Did you use the correct procedure right before your post? I feel like the developer won't answer you lol

Does anyone got any issues ussing screen share? My device restart once I choose my tv, I've not tried it with a chromecast, Its a LG smart tv

Typhus_ said:
1 -
Turn your phone into fastboot mode (run adb reboot bootloader or shutdown the phone and turn it on again while pressing Power + Vol- keys)
2 - On fastboot mode run the command:
Code:
fastboot set_active a
3 - Now, flash latest STOCK FASTBOOT ROM using flash_all.bat (or flash_all.sh if using Linux)
4 - Wait for the installation to finish and as soon as you see the welcome screen on stock, go to fastboot mode again
5 - Now run these commands:
Code:
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
(keep pressing Vol+ key to force the phone into recovery mode)​
6 - Now we're on TWRP Recovery using slot B. Do this:
Wipe Dalvik, System and Data
Install lineage-18.0-20201010-UNOFFICIAL-laurel_sprout.zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery​
7 - Now we're on TWRP Recovery but on slot A. Do this:
Wipe Dalvik, System and Data (Yes, again. I'm not Stupid, trust me.)
Install lineage-18.0-20201010-UNOFFICIAL-laurel_sprout.zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery​
8 - You will be on slot B again. Change it back to slot A and reboot to Recovery. Now Format Data with "yes" option to remove stock encryption
9 - Reboot to Recovery again
10 - Install GApps (This is optional! The ROM works fine without any GApps. If you really want GApps you may install any version but I recommend just Core version)
11 - Reboot to bootloader and flash the dtbo.img by running the command:
Code:
fastboot flash dtbo dtbo.img
Code:
fastboot reboot
Your phone while boot into LineageOS 18 and it will be awesomely lag free!
NOTES:
By doing this procedure you will have LOS18 system and vendor installed on both slots!
dtbo.img has to be flashed because when you flash a "new vendor" on both slots you need to flash dtbo as well. If you don't do this you will lose your WiFi and Bluetooth!!
Now you can install Magisk if you want root features (for the time being you must use Magisk 20422 Canary Version)
You can now also install a different Recovery if you like, for example, SHRP Recvoery. Simply go to TWRP and flash SHRP installer zip.
I've tested this procedure yesterday like 2 or 3 times. I've been up almost to 3 AM testing stuff. Right now I'm on LOS18 WITHOUT ANY BUG!
All files mentioned on this post can be found on the Telegram support group (including Magisk version)
Of course that you must store the TWRP img file on the same folder you have platform-tools and the TWRP zip file on your SDCard or phone internal memory....duh...
If you feel like this procedure sucks because it's too long, or if you think that this can be completely ignored and just flash the ROM like you've always done then DON'T ASK FOR ANY HELP!!! This will SOLVE any stupid problem your phone might have, so.... yeah, I won't give you credit if you don't want to spare 20 minutes (if so...) flashing things the correct way.
Cheers!
Click to expand...
Click to collapse
Thank you for this great how to do process.
Always most informative and helpful.
I have just one question.
I am now in the latest STOCK EU rom, which I flashed through RECOVERY rom and then used the magisk_patched boot method to root. No TWRP or any other recovery in it.
My question is this:
Can I skip fastboot flash the STOCK rom again AND go to step 2 , OR it is mandatory to start from step 1?
Again, thanks for all your help giving us all that knowledge
:good::good:

If you never had any other custom ROM installed on other slot, or did but have gone back to stock using fastboot, yes you can ignore step 1.
Cheers!

Typhus_ said:
If you never had any other custom ROM installed on other slot, or did but have gone back to stock using fastboot, yes you can ignore step 1.
Cheers!
Click to expand...
Click to collapse
so I have to go from step 1, as I have flashed EVERY custom rom available
Thanks man you are GREAT:good:

after executing commands
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
i am booting back in fastboot even holding Vol+ while booting what should i do? Thank you

If you have the phone locked with a pin, when you go into SHRP recovery, typing the same pin doesn't decrypt the phone.

pol00001 said:
after executing commands
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
i am booting back in fastboot even holding Vol+ while booting what should i do? Thank you
Click to expand...
Click to collapse
Have you flashed stock ROM with flash_all.bat? If not, try that.