Related
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???
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.
*/
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.
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?
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
edwaine said:
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
Click to expand...
Click to collapse
The title says Android 11; will this work with Android 10? I tried on LineageOS 17.1 (Android 10) and TWRP said the image was too large but I already had Magisk 22 installed.
Perhaps: 1) Install LineageOS 17.1 weekly update with Options/Update/Updater
2) Boot into Lineage recovery to change slots
3) Reboot into bootloader
4) fastboot boot twrp-3.5.1_9-0-marlin.img
5) As OP said, "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk"
6) Reboot into recovery (may not be needed?)
7) Flash Magisk-v22.0.apk (renamed to Magisk-v22.0.zip)
8) Reboot system & violin!
I've been trying to get TWRP and Magisk installed without having to use another computer to go into fastboot and flash the image. There may be a way to use the Magisk TWRP A/B retention script. This at least tells me why using TWRP 3.5.2_9-0-marlin.img to install the TWRP zip file would never reboot into recovery. Thanks.
lichan said:
The title says Android 11; will this work with Android 10? I tried on LineageOS 17.1 (Android 10) and TWRP said the image was too large but I already had Magisk 22 installed.
Perhaps: 1) Install LineageOS 17.1 weekly update with Options/Update/Updater
2) Boot into Lineage recovery to change slots
3) Reboot into bootloader
4) fastboot boot twrp-3.5.1_9-0-marlin.img
5) As OP said, "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk"
6) Reboot into recovery (may not be needed?)
7) Flash Magisk-v22.0.apk (renamed to Magisk-v22.0.zip)
8) Reboot system & violin!
I've been trying to get TWRP and Magisk installed without having to use another computer to go into fastboot and flash the image. There may be a way to use the Magisk TWRP A/B retention script. This at least tells me why using TWRP 3.5.2_9-0-marlin.img to install the TWRP zip file would never reboot into recovery. Thanks.
Click to expand...
Click to collapse
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
edwaine said:
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
Click to expand...
Click to collapse
Thanks, I'll check into the repartitioning.
edwaine said:
Youre free to try the steps. I only confirmed it on Android 11 because I'm already using Pixel Experience 11 Plus. You really need to repartition before TWRP can fit to your Phone.
Click to expand...
Click to collapse
What's the difference between PE and stock pixel rom? aren't they the same?
X4c3 said:
What's the difference between PE and stock pixel rom? aren't they the same?
Click to expand...
Click to collapse
Same. But with added features on Pixel Experience 11 Plus
edwaine said:
Same. But with added features on Pixel Experience 11 Plus
Click to expand...
Click to collapse
You own Cherry Mobile G1(seed/crackling), are you from Philippines? where did you buy your Pixel XL with unlocked boot loader?
edwaine said:
This works both ways on Sailfish & Marlin
TWRP 3.5.1_9-0 as Recovery Ramdisk can now co-exist with Magisk! Yey!
The twrp-installer-3.5.1_9-0-marlin.zip is still unable to boot back to recovery after flashing. But as long as you flash twrp-3.5.1_9-0-marlin.img as Recovery Ramdisk, then you're okay.
Note: Download first twrp-3.5.1_9-0-marlin.img from twrp.me and save it to your preferred download location.
You need to boot TWRP from bootloader by typing "fastboot boot twrp.img". After TWRP loads up, go to "Advanced>Install TWRP Image as Recovery Ramdisk>Find twrp-3.5.1_9-0-marlin.img location>Install Recovery Ramdisk".
After that reboot back to recovery then flash Magisk-v22.0.apk & viola!
Click to expand...
Click to collapse
I can confirm that this works on the Pixel 2 XL (taimen). I just tested it with twrp-3.5.2_9-0-taimen.img and Magisk-v23.0 with Havoc-OS v4.6 (Android 11).
No go for me. Not sure why my pixel xl gen 1 refusing to boot to any twrp when flashed but 3.3.0.0. I can command line boot fastboot to the latest fine though.