Related
* I'm 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 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 could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Needed tools : Backup your phone before following any steps
1. Minimal adb and fastboot
2. official TWRP 3.3 for jasmine_sprout Download img file from twrp website
3. latest magisk manager 19.2 zip file from magisk manager website
First step : Boot loader unlock
1) Tap on build number more than 7 times and unlock developer option in about phone.
2) turn on OEM Unlocking and USB debugging
Now open command windows in adb shell folder and connect your device to computer.
type : 1) adb devies (this should show your device after giving permission in your phone : conformation that your device is
connected)
2) adb reboot bootloader
3) fastboot devices ( conformation that your phone is coonected in fastboot mode)
4) fastboot oem unlock
( after that you need to follow according steps in your phone and grant to unlock phone)
keep in mind this will reset your phone. Afteer reboot again turn on developer options and usb debugging
5) fastboot flashing unlock_critical
( the warning and steps you need to follow again in your phone like in step 4)
this will again reset your phone.Afteer reboot again turn on developer options and usb debugging
Congratulations your bootloader is Unlocked now.
STEP 2. Flashing TWRP and Magisk Install
before that keep in mind As Mi A2 follows A/B boot partition system so DONT DIRECT FLASH TWRP FROM
FASTBOOT.
" Dont forget to turn on developer options and usb debugging "
open command window in adb shell folder and boot your phone in bootloader mode as told earlier and connect to computer.
Copy twrp-3.3.0-0-jasmine_sprout.img to minimal adb and fastboot folder. you can rename it to your convenient name
type : 1) fastboot boot twrp-3.3.0-0-jasmine_sprout.img
or if you renamed it
fastboot boot YourRenameName.img
this will temporarily boot twrp in your Device. As twrp is booted you will be able to see your phone connected in computer
(file transfer mode)
Copy and paste both magiskmanager.zip (current latest stable is 19.2 ) into phone
Flash your downloaded version of Magiskmanager.zip
Reboot your Phone.
Congratulations If nothing goes sideways Your phone is Magisk Rooted.
If you want to flash something using TWRP now is the time Otherwise as Mi A2 has A/B slot form and no Recovery Partition You Cannot flash TWRP permanently.
But You can always boot TWRP from adb and use it.
ROM flashing help
Can't flash ROM after using this method
Torque422 said:
Can't flash ROM after using this method
Click to expand...
Click to collapse
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Failed
No such a directory problem, please help
Please elaborate more about the problem ? @shahidrok
shahidrok said:
No such a directory problem, please help
Click to expand...
Click to collapse
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
TYPHOON9055 said:
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks ?, i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now?
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Hve done everything but when i try to reboot to twrp it gets stuck on twrp logo,dont know what im doing wrong.
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
I get error 1 during flashing
Amnvlad said:
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
Click to expand...
Click to collapse
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Alucard said:
I get error 1 during flashing
Click to expand...
Click to collapse
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic ?
Torque422 said:
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic
Click to expand...
Click to collapse
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
Available custom roms are for Oreo versions if you have updated ur device to pie , it won't work.
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
I was on stock pie + may update (10.0.9)
Follow this way , unlock the bootloader via fastboot oem unlock, fastboot flashing unlock it will reboot here, goto developer settings Enable usb debugging
Then do this fastboot flashing unlock_critical It will again reboot
Now, install the magisk app And download the patched boot image from internet Whatever your build no is, mine was 10.0.9 so i downloaded version 10.0.9_boot.img
Open the magisk app, click on install , select and patch a file, Then choose this downloaded patched image, it will flash it successfully, if it don't Then you have mistaken something..
After this there will be a patched.img in download folder Which is just created by magisk, copy this img to pc, Through fastboot Flash it "fastboot boot patched.img"
Now, flash TwrpImage3.3.img through fastboot
When you boot in , Copy and paste your rom, gapps
Now flash twrpVersion3.2.img via fastboot
Clear system,data,caches, Flash the rom in slot B
Now flash the twrp3.2.zip through installed twrp, click on recovery And it will boot to twrp
Now Flash the gapps in slot a (i used nano)
Now flash magisk.zip through twrp
Reboot , That's it!
(Twrp 3.2 is stable for flashing rom and gapps , Just for first time When we coming from stock
Twrp 3.3 latest Gives us MTP transfer, The difference is this in using both of these)
Installation of magisk is the last process, it is part of rom, First installed ur desired rom and then magisk
You said, You installed twrp, as i mentioned above You forgot to do some steps as about patched boot + installation of magisk through patched file etc..
Though you can try to search on google for your next step
patched supported magisk Version x.x.x for mi a2
If you got the file, You are lucky.. otherwise flash the stock rom with mi flash tool
And Start from unlocking bootloader
Magisk Module available.
Torque422 said:
Please elaborate more about the problem ? @shahidrok
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
Thanks , i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Click to expand...
Click to collapse
There is a magisk module available for installing kali nethunter in this device. i never tried installing it but it should work fine. Read proper descriptions before installing it though.
Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
the adb recognized my phone but fastboot do not, help me out please
Andrew.kathy said:
the adb recognized my phone but fastboot do not, help me out please
Click to expand...
Click to collapse
Probably a problem with drivers, check and reinstall drivers
Can i use this method to flash magisk on Mi 9T pro?
I can't boot into twrp
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Topper8118 said:
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Click to expand...
Click to collapse
Checklist:
- there is file of <compatible TWRP recovery> in ADB/Fastboot directory with the name you are typing in fastboot command
- ADB drivers installed correctly (both "adb devices -l" and "fastboot devices" return valid results in corresponding phone states)
- only one phone (namely MiA2) is connected to PC
- phone fully unlocked (OEM debugging enabled and PC was previously approved for ADB in phone)
- USB port on MB of PC is USB-2.x or USB-3.x-compatible-with-Mi-A2<which is not true in general>
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
HTCDevil said:
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
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???
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"
}
Redwolf fork
Code:
/*
* Your warranty is now void.
*
* We're 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 recovery
* 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.
*
*/
OrangeFox is FREE SOFTWARE
Supports Treble, Miui, Custom Roms
Download:
Stable Builds
OrangeFox Recovery R10.0_2.1 [Latest]
INSTALLATION:
1- How to install OrangeFox Recovery ?
Method-1=
1. Download the OrangeFox zip file and copy it to your device (internal or external storage)
2. Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
3. 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 recovery.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)
4. When OrangeFox recovery boots, if you have the 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)
5. Install the OrangeFox zip (always install the latest build available)
6. 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)
7. Reboot to System
8. Enjoy!
Method-2=
0. Backup your ROM and all your files
1. Download the OrangeFox zip file to your device
2. Reboot to your custom TWRP-based Recovery
3. Install the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
2 -How to flash rom(s) using OrangeFox Recovery:
1. Format data (TIPPING YES).
2. Flash rom zip (PE, BEAST, ATOM
ETC...)
3. Flash OrangeFox-Recovery.zip again. ( INSTALLER, THE PHONE WILL REBOOT TO ORANGE RECOVERY (IF YOU DONT FLASH THIS AGAIN, RECOVERY WILL DISAPPEAR)
4. Flash Magisk v20.
5. Flash Gapps (optional).
6. Flash Patch_no_fde.
Frequently Asked Questions, MIUI OTA, Troubleshooting, and Sundry Information:
* See https://forum.xda-developers.com/showpost.php?p=76885728&postcount=3
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* ATG and Dadi11 - for Redwolf
* Kirillmaster4 - for graphics
* z31s1g - for TWRP theme
* @mauronofrio - for the decryption on Mi A3
* All our helpers and testers ( @prakaship78 , @nelinthon_Kekis , @Dvyhrs , @ihsaneDZ and the others ) - for your patience and help
FEATURES:
* Supports Treble and non-Treble ROMs
* Up-to-date Oreo kernel, built from sources
* Increased compatibility with TWRP
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM [only for some devices]
* Password
* Support for Miui and Custom ROMs
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Screenshots - see below
Visit to https://orangefox.tech/
Finally,now we can see some roms for this device
Thanx alot to all creators and supporters
Any rom there for orange fox or still only fastboot Roms?
And big thx for the recovery works like a charm
But i don't flash any rom for now
dennis46419 said:
Any rom there for orange fox or still only fastboot Roms?
And big thx for the recovery works like a charm
But i don't flash any rom for now
Click to expand...
Click to collapse
Pixel experience now has a recovery flashable zip
trkzmn said:
...bla bla bla...
INSTALLATION:
Method-1=
1. Download the OrangeFox zip file, copy to your computer and your device.
2. Unpack the zip and input recovery.img to your pc desktop.
3. Open cmd and give this command "fastboot flash boot recovery.img"
4. Reboot to recovery.
5. When boot orangefox recovery install > OrangeFox-R10.0_2-laurel_sprout.zip [Download Latest Build] .
6. Enjoy
...bla bla bla...
Click to expand...
Click to collapse
Hello!
Thanks for your work, truly appreciate it.
Could you update the OP with the install method that I'm going to describe next? It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for Noob users.
Download the OrangeFox zip file and copy it to your device (internal or external storage)
Extract the recovery.img from the zip 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 recovery.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 OrangeFox recovery boots, if you have the 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 OrangeFox 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
Enjoy
Why do I suggest this? Well, please read the hidden content:
By doing this method (which seems more complicated but I've tried my best to explain it as if I were explaining it to a 4 years old kid...) we will flash the recovery.img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When OrangeFox 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 recovery.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 the 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 recovery.img and boot.img).
Cheers!
---------- Post added at 12:04 ---------- Previous post was at 11:16 ----------
Hello....again...
I've just tested the install method that I've explained but, unfortunately, it's not working.
OrangeFox recovery only boots if the installer zip is run through TWRP...don't really know why since I've tested a lot of times doing this exact same method with TWRP recovery, and it's working. It should be working here as well.
Anyway the OF recovery boots but I think that it does not decrypt data. It doesn't gets frozen on the welcome screen (like before) but it doesn't decrypt (I see all the files with the "weird" names). This, of course, is only bad for those who want to remain on stock ROM. For anyone who wants to move on to custom ROMs, just format user data and your set to go.
Cheers!
OrangeFox Recovery R10.0_2.1 Changes
* Fix stuck in fastboot mode after flashing OrangeFox with fastboot
Post Changes
1. OrangeFox recovery installation made easier with explanations (Thanks to @Typhus_)
2. Custom rom install method added (Thanks to @nelinthon)
Hi all, can we do a backup of all data (system, boot...) And restore with orangefox?
I'm afraid to test any rom and not to be able to return to the original configuration... I have the 5 october update
Shineali said:
Hi all, can we do a backup of all data (system, boot...) And restore with orangefox?
Click to expand...
Click to collapse
Yes you can.
Shineali said:
I'm afraid to test any rom and not to be able to return to the original configuration... I have the 5 october update
Click to expand...
Click to collapse
Follow the install custom rom steps. If you still have problem with it take recovery.log and send me
trkzmn said:
Yes you can.
Follow the install custom rom steps. If you still have problem with it take recovery.log and send me
Click to expand...
Click to collapse
Ok thanks!!!
Anyone fix this error
There is recovery.img
I already changed name to .img and then try..but nothing happened
RJ- said:
Anyone fix this error
Click to expand...
Click to collapse
RJ- said:
There is recovery.img
I already changed name to .img and then try..but nothing happened
Click to expand...
Click to collapse
On the first image your running commands on "C:\Program Files\Minimal ADB and Fastboot" folder.
On the second image your showing the files on "C:\adb" folder.
You must run the commands on the folder where you have the img file stored! Rename the file!!? WTF!?
Besides, you didn't read the instructions carefully, not only your running the command to change slot wrong but, also, you've tried to flash recovery.img into currently active slot before trying to change slot (based on your command history on first image).
PLEASE!
If you're not comfortable doing these simple steps, or if you don't have patience to read all instructions carefully, then just DON'T DO ANYTHING!!
People with this kind of behavior are the main reason why most devs often just drop development. How will you be able to successfully flash a ROM and/or report true bugs, if you're not able to just execute simple commands that have been explained step by step? Maybe my instructions weren't clear enough....perhaps I should have start the steps with:
"Turn on your computer";
"Put your hands on your keyboard and mouse";
"Login to your account";
etc....
ALSO, the recovery on the OP has been updated. Even if you did everything correctly you would end up on fastboot since your trying to flash the wrong OF version!
Please, search, please read, please...USE YOUR BRAIN!
Thanks
Hi I tried to install but i get an error during orangefox first boot there's no option to install orangefox....zip ot seems like the files were encrypted. They have a strange names...
It could be that didn't give permission to write? O do the steps again bit didn't ask me for permission.
Thanks in advance.
Shineali said:
Hi I tried to install but i get an error during orangefox first boot there's no option to install orangefox....zip ot seems like the files were encrypted. They have a strange names...
It could be that didn't give permission to write? O do the steps again bit didn't ask me for permission.
Thanks in advance.
Click to expand...
Click to collapse
Seems files are encrypted.
- Format data
- Flash OrangeFox.zip
RJ- said:
Anyone fix this error
Click to expand...
Click to collapse
Don't use minimal adb, try to use platform tools for windows.
Can Orangefox recovery support for OTA updates in MiA3???
ricky9779 said:
Can Orangefox recovery support for OTA updates in MiA3???
Click to expand...
Click to collapse
No rom for this device has ota support yet anyway. And if you mean ota for stock rom then definitely not as you need stock boot.img for stock ota or it won't work
Website and download link down at the moment or it is just for me?
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.
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.
*/
Lineage OS 17.1
Properties
Selinux mode : Enforcing
Build type : user
Gapps : not included
LOS recovery : included
Known issues
FM radio
You have to wake up the phone to use the FOD
No charging icon when off
Maybe others you tell me
Installation
I'm not sure about that but you can try :
1 - Download latest stock android 10 ROM from here
2 - Install OrangeFox from here
3 - Set A as active slot, flash stock rom, orangefox installer zip, reboot recovery
4 - Set B as active slot, flash stock rom, orangefox installer zip, reboot recovery again (now you have A10 vendor blobs in both A/B slots)
5 - Flash custom ROM zip
5,5- Maybe factory reset on los recovery
6 - Flash OrangeFox installer
7 - Reboot recovery
8 - Flash Gapps / Magisk(optional)
9 - fastboot format:f2fs userdata
Troubleshoot
If wifi/bluetooth is not working, flash stock dtbo.img with fastboot flash dtbo.img
If ROM keeps rebooting to recovery, format userdata (wipes internal storage!) with fastboot format:f2fs userdata
Downloads
Download 28/03/2020
Checksum : 05a147341c33bf1e04b16bad721d2961
Download 21/03/2020
Checksum : e2fbec3542e8d9c164854103cceb38cf
Telegarm Group
Sources
ROM
Device tree
Kernel
Vendor
Credits
Big thank's to @Golbinex !
LineageOS team - ROM
@Harukey
@prakaship78
@charliespencerchaplin
XDAevDB Information
[ROM][10][UNOFFICIAL] Lineage OS 17.1, ROM for the Xiaomi Mi A3
Contributors
dantir
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: Lineage OS 17.1
Created 2020-03-21
Last Updated 2020-03-28
Changelog
28/03/2020 : FOD fix
23/03/2020 : DO NOT USE THIS BUILD IT DOESN'T BOOT
21/03/2020 : first relase
Nice, will check it out once I get TWRP working again
Plans for official?
amnher said:
Plans for official?
Click to expand...
Click to collapse
I would love to but it's my first rom, I have a lot to learn.
Also I think to be official it must be perfect like no dtbo.img to flash.
fm radio
would there be a way to get fm radio working?
thank you
how to do this (If ROM keeps rebooting to recovery, format userdata (wipes internal storage!) with fastboot format:f2fs userdata)
I just cannot get it to boot, it always leads to a bootloop. I have followed the guide here and here and also installed latest Android 10 fastboot zip to both slots and flashed the twrp-patched boot image to boot to recovery (flashing regular images included in recovery threads will always boot to bootloader) to flash this, it just doesn't boot... Anyone had any luck?
Any way we could have this rom as permissive ?
In order to have gravitybox working we just need permissive selinux ?
vaykossil said:
Any way we could have this rom as permissive ?
In order to have gravitybox working we just need permissive selinux ?
Click to expand...
Click to collapse
Change it, if you use Gravitybox you should know how to root your phone.
Then is easy to change SELinux status, temporaly in a terminal
Code:
setenforce 0
If you want it to stick is better to have a script running at boot with Magisk instead of editing system config files.
The point is if you want permissive mode do it your self, the default state should be Enforced for everyone is a matter of security.
Makishima said:
I just cannot get it to boot, it always leads to a bootloop. I have followed the guide here and here and also installed latest Android 10 fastboot zip to both slots and flashed the twrp-patched boot image to boot to recovery (flashing regular images included in recovery threads will always boot to bootloader) to flash this, it just doesn't boot... Anyone had any luck?
Click to expand...
Click to collapse
me too, I tried different recoverys, different steps but no luck, I just can't get it to boot.
Many thanks for the ROM!
I followed the current installation instructions on the start page (but i did NOT "5,5- Maybe factory reset on los recovery") and the rom seems to work very well (Fingerprint sensor, Bluetooth music box, ...).
After I booted to Lineage OS the first time the android logo appeared two times but then Lineage OS started correctly. I didn't need to flash the dtbo.img.
Initially I also did the step "5,5- Maybe factory reset on los recovery", but when I tried to boot to OrangeFox recovery from fastboot again the bootloader/fastboot screen was launched.
I found one minor issue: When you disable the screen lock then the background image is shifted a little bit for a short time. I also successfully tested data decryption in the provided OrangeFox recovery.
I would be glad if "Signature Spoofing" would be enabled so you can use microG with this rom.
I own the global version of the Mi A3.
facundonak said:
me too, I tried different recoverys, different steps but no luck, I just can't get it to boot.
Click to expand...
Click to collapse
I think you installed 23/03 build. Try the last one : 28/03 It should be better.
FOD works in general, but does it much slower than on stock ROM, and you have to wake up phone first...
Hey dantir,
Thanks for your efforts on this ROM. Been on lineageOS on multiple phones till date. Rooting for you to get this to a more stable state. Kindly request you to not abandon this ROM.
Thanks a lot.
Do magisk modules work well? call recording, busybox, etc ...?
hello
i have bootloop error
before to install lineageos my data partition was encrypted, so i formated it, in order to send via adb the lineageos zip
then i installed lineageos
this command has error :
fastboot format:f2fs userdata
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
can you confirm we must flash lineageos in orangefox
after installing lineageos must i reboot in fastboot to execute this command : fastboot format:f2fs userdata
hello i installed the rom
how do you create this rom, can you post the instructions
i would like to create a custom rom with my app included as a system app
thnaks
noogpout said:
hello
i have bootloop error
before to install lineageos my data partition was encrypted, so i formated it, in order to send via adb the lineageos zip
then i installed lineageos
this command has error :
fastboot format:f2fs userdata
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
can you confirm we must flash lineageos in orangefox
after installing lineageos must i reboot in fastboot to execute this command : fastboot format:f2fs userdata
Click to expand...
Click to collapse
Hey! Just use official TWRP (link), works fine with! Did not have to do anything special.
Also, this rom seems stable, gonna start using it as daily driver this weekend I guess. Thanks @dantir, will you keep this updated? You use it as a daily driver too? Any bugs found in the 28th version?