I have flashed latest android 10 to my A3 and mistakenly uninstalled TWRP. Now i want to install twrp recovery. But everytime I flash it in partition b, it get stuck on fastboot screen.
If twrp doesn't support Android 10 then how come it supports other Android 10 based custom rom like Pixel Experience?
Because those custom ROMs use android 9 vendor, boot etc
Thanks for your helpful response
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Thank you for your helpful response. If i want to flash twrp permanently, which zip file i need to flash after booting it temporarily with your attached twrp.img?
Sapper Morton said:
You must always use TWRP Installer (there's no need in specific custom ROMs, since they provide built-in custom recovery), the image I attached can only be used to install temporarily in Android 10 firmware (other than 11.0.8.0 QFQMIXM). And remember, all of this could be avoided if Xiaomi had implemented the boot command into Mi A3 bootloader:
Code:
fastboot boot image_example.img
Click to expand...
Click to collapse
so i am guessing there is no way to add the boot command to fastboot
build v11.0.11.0
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Hi!
Thanks a lot, where I can find the file for the v11.0.11.0, or at least can you specify how I do this using stock boot?
Thanks! Hope to hear you back.
I booted with patched boot and finally was able to enter into TWRP recovery, but then I erased system/data/dalvik and tried to flash Pixel Experience but I am always getting error 1 when doing it. What can I do? It is something about the Android Q base? I'm now on build 11.0.11
Sapper Morton said:
You must always use TWRP Installer (there's no need in specific custom ROMs, since they provide built-in custom recovery), the image I attached can only be used to install temporarily in Android 10 firmware (other than 11.0.8.0 QFQMIXM). And remember, all of this could be avoided if Xiaomi had implemented the boot command into Mi A3 bootloader:
Code:
fastboot boot image_example.img
Click to expand...
Click to collapse
means that with this twrp it is used only to open the twrp periodically, once the custom rom is installed I install the twrp normally
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
What do you mean "patch the q boot image". What is that?
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Thanks you saved me. I could boot into recovery with your boot.img but the encryption failed. Nevertheless I could sideload the recovery.zip to the device and install on both slots.
Related
With this modded version of TWRP you can now install A1 roms into the 5X.
How to install A1 roms using this TWRP:
https://forum.xda-developers.com/mi-5x/how-to/guide-how-to-install-a1-rom-5x-t3777139
Oreo Modded TWRP 3.2.1-0 Download:
Google Drive
Nougat Modded TWRP 3.2.1-0 Download:
Google Drive
How to install:
- Unlock bootloader
- Enter in Fastboot Mode (Power Button + Vol Down)
- Flash using "fastboot flash recovery twrp.img"
- Enter in Recovery Mode (Power Button + Vol Up)
Which one should I download?
You should install the correspondent version according to your currently installed Android version. If your current system is Nougat, you should flash Nougat TWRP. Same for Oreo. It doesn't matter which version of Android are you going to install, but the one that you already have installed. If you are in Nougat and want to flash Oreo rom, after flashing it, be sure to flash Oreo TWRP. If you dont do it, recovery may not work.
How can I use the port feature?
First, download an A1 fastboot ROM. You can do so here. Then, flash system and boot partitions using fastboot.
After you flashed it, go to "Advanced" then tap on "Terminal". Write "a1to5x" and press Enter. Wait until it finishes. Make proper wipes and reboot.
Are there any other features?
I have enabled system.img and modem.img flashing, so people without a pc can flash A1 fastboot roms. But be careful, system.img can't be a sparse image (this are the images included on the a1 official fastboot rom), it should be a raw ext4 image. You can use simg2img to convert them. Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you. I know it is not a very easy process, but at least people without pc now have a chance to update their phones.
In what roms does it works?
I have only tested it with official Android One Oreo rom, however, it should work with Nougat Android One and with custom roms. Try it and let me know in what roms does it work.
How do you port A1 roms to the 5X?
I have been asked this question a lot of times. I can't give a step by step guide since I don't have enough spare time to make a decent guide. If you are interested on the porting process, take a look at /sbin/a1to5x (inside twrp ramdisk), it is the script which takes cares of the automatic porting process. Inside it you will find how the ports are made.
Where is the changelog?
You can check it here
Donations:
If you like my work and want to contribute, you can donate via paypal.me/aex12
Device Tree: https://github.com/Aex12/android_device_xiaomi_tiffany
Manifest used: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
XDA:DevDB Information
Modded TWRP 3.2.1, Tool/Utility for the Xiaomi Mi 5X
Contributors
Aex12
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Stable
Current Stable Version: 3.2.1
Created 2018-03-07
Last Updated 2018-03-08
Reserved
Love Man... You Are Love Brother
is it normal that the external memory is not shown?
@Aex12
Thanks for your great work. I have some question.
Should we install an whole A1 fastboot rom or only install system.img and boot.img like the old one?
vangame said:
@Aex12
Thanks for your great work. I have some question.
Should we install an whole A1 fastboot rom or only install system.img and boot.img like the old one?
Click to expand...
Click to collapse
Forgot to mention it on the thread. Thanks for reminding, I am updating it right now. You should only flash system and boot. Modem and other firmware partitions can be flashed too, but they are not mandatory.
And have someone test LineageOS 15.1 for Mi A1 with this recovery?
Awesome work @Aex12. Thanks a lot
Hello can I use it at tissot bootloader?
eurekaseven said:
is it normal that the external memory is not shown?
Click to expand...
Click to collapse
That was somthing I also have noticed.. without sd memory being shown I can't do a backup to SD Card.
Instead I'll have to do a local backup and connect to PC and copy files over, Early stages I guess we are lucky we can even see the Internal Memory right?
Alright so I was curious and thought I'd see what happens if I flash recovery Nougat Modded TWRP 3.2.1-0 ( While currently running Oreo )
I booted into recovery and instantly discovered that you no longer even have access to internal memory 0b shown.. Don't waste your time !
I flashed recovery Oreo Modded TWRP 3.2.1-0 using fast boot as you won't be able to flash a recovery rom using TWRP in this state..
https://www.xda-developers.com/how-to-install-twrp/
Shows an easy guide if you aren't sure howto do this
Can not get back to MIUI Nougat or even get old recovery to work
When i try to install back xiaomi.eu's miui rom after installing zip and do all the proper wipes, it reboot to system but says that encryption was interrupted and can't complete. So I tried to install back the nougat 3.2.1 recovery and try again, with the same result. again i tried to install the rom again with 3.1.1 recovery and same happens. With nougat recovery it can't mount any partition, so it can not opperate properly, only the oreo recovery works. the only rom that works and gets installed good is the oreo one that you submitted so what can i do to get back to my normal twrp recovery (no oreo) and to a miui rom? thanks
P.D: I also tried to flash with fastboot a a1 nougat rom and with the 3.1.1 twrp port it but no succes as it can no longer mount anything, only oreo twrp is working but still not get to work properly any other rom, via fastboot or via recovery. Bootloader is unlocked.
What phone and model is this 4? It states nothing
hi,
i tried to flash system.img from official MiA1 fastboot ROMs today but i got these message " target reported max download size of 536870912 bytes, is this a normal message? will the flash resume?
vangame said:
And have someone test LineageOS 15.1 for Mi A1 with this recovery?
Click to expand...
Click to collapse
I want to know this too!
Aex12 said:
Aex12, Brother Please Fix SD issue... Cant flash files from my SD Card.
Click to expand...
Click to collapse
Comparing fstab with stock recovery / sd supported recovery might fix this issue...
This recovery doesn't read my SD card. Only the internal storage.
>Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you
Yeah, anyone willing to do it for me?
udaan said:
>Modem.img can't neither be flashed directly from the downloaded fastboot rom. It should be a modem.img extracted with dd, you will need to ask some who flashed it with fastboot to extract it for you
Yeah, anyone willing to do it for me?
Click to expand...
Click to collapse
Make sure to make a backup of your current modem, just in case.
It's from v9.5.9.0: https://mega.nz/#!UAhwAQLY!-8np_yuZnJscEUFh9bJuCkkqDkPuZrr8Aa6o0kkBq5Q
My 5x does not go to recovery mode. My ROM is AOSPE. I am using OREO twrp. The device is not ROOTED
I can boot twrp using
Code:
fastboot boot twrp.img
but after using
Code:
fastboot flash recovery twrp.img
the phone does not go to recovery using Volume up + Power
tuhi009 said:
My 5x does not go to recovery mode. My ROM is AOSPE. I am using OREO twrp. The device is not ROOTED
I can boot twrp using
Code:
fastboot boot twrp.img
but after using
Code:
fastboot flash recovery twrp.img
the phone does not go to recovery using Volume up + Power
Click to expand...
Click to collapse
I think you need to fastboot flash boot image first, then go to twrp and flash it again from it.
---------- Post added at 08:14 AM ---------- Previous post was at 08:06 AM ----------
@Aex12 please update TWRP. I can't format /data /system etc from twrp made for MiA1(MohanCM's) but I cannot do it with yours. I have mi5x and it is ****ing stuck on boot. If I flash MiA1's fastboot rom I can get to fastboot and flash TWRP (since the bootloader is locked) but I can't do anything with your TWRP. But I can also flash MohanCM's twrp and I can do all that stuffs except for installing ROms and booting to it. im ****ing confused myself.
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Spocki990 said:
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Click to expand...
Click to collapse
You've got the kernel and recovery messed up on your device from the failed flash of twrp and magisk. I would start over by flashing the factory image using the flash all batch file with the -w edited out of it. Then try again booting twrp, not flashing it. Once you try to flash the twrp image file you pretty much have to start over with the stock boot image. When you boot into twrp you'll want to allow modifications. You also need to setup a pin or pattern security for your system so twrp will decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Spocki990 said:
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Click to expand...
Click to collapse
you are my hero. My phone was stuck in the situation you describe after installing active edge. I was thinking about wipe my pixel 3 until I saw your post. Thank you !:good:
Hi,this is my first time installing a custom rom and recovery and rooting and all.
I am on MIUI 10 8.11.22 beta on RN3 2gb.
And have unlocked bootloader using official method.
Currently following
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
Planning to
flash official twrp-3.3.1-0-kenzo
Install Havoc 9.0 OS https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
Install Magisk
but twrp site is showing
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
I think it is about boot.img but I do not have patched boot.img of my miui version and also (from above guide) to patch boot.img i need fastboot rom but linkhttps://en.miui.com/a-234.html only takes me to Chinese miui website.
Can any one share link to boot.img of fastboot rom for MIUI 10 8.11.22 beta?
And in Havoc OS post
https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
do I need custom kernel for 9.0?
In Magisk Post
Prerequisite
If you plan to install custom kernels, flash the zip AFTER installing Magisk
Make sure to remove any ‘boot image mods’ such as other root solutions. The easiest way is to restore the boot image from factory images, or reflash a non-prerooted custom ROM
Click to expand...
Click to collapse
does that mean i do not need to flash boot.img or do i need to flash it afterwards?
Qustions
1) Do I need boot.img file of my version or any will do?
2)Do I need custom kernel for havoc os 9.0?
3) how to proceed after flashing twrp(need help)?
here what i think i have to do after flasing twrp(correct me If i am wrong)
(do not flash boot .img as installing magisk) -> flash havoc os -> flash magisk->flash custom kernel(which one?)-> (flash boot.img) ->reboot
ARY-Pyran said:
Hi,this is my first time installing a custom rom and recovery and rooting and all.
I am on MIUI 10 8.11.22 beta on RN3 2gb.
And have unlocked bootloader using official method.
Currently following
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
Planning to
flash official twrp-3.3.1-0-kenzo
Install Havoc 9.0 OS https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
Install Magisk
but twrp site is showing
I think it is about boot.img but I do not have patched boot.img of my miui version and also (from above guide) to patch boot.img i need fastboot rom but linkhttps://en.miui.com/a-234.html only takes me to Chinese miui website.
Can any one share link to boot.img of fastboot rom for MIUI 10 8.11.22 beta?
And in Havoc OS post
https://forum.xda-developers.com/redmi-note-3/development/rom-havoc-os-t3845305
do I need custom kernel for 9.0?
In Magisk Post
does that mean i do not need to flash boot.img or do i need to flash it afterwards?
Qustions
1) Do I need boot.img file of my version or any will do?
2)Do I need custom kernel for havoc os 9.0?
3) how to proceed after flashing twrp(need help)?
here what i think i have to do after flasing twrp(correct me If i am wrong)
(do not flash boot .img as installing magisk) -> flash havoc os -> flash magisk->flash custom kernel(which one?)-> (flash boot.img) ->reboot
Click to expand...
Click to collapse
If u official unlocked using miunlock tool then u dont need any patched boot.img.
Flash latest twrp 3.3.1 kenzo
Download ur favourite rom and nano gapps zip to external sd card.
First go to wipe and do format data.
You must do it or rom wont boot.
So click Format data
Type Yes to format
This will decrypt and erase internal sd.
Then Swipe to "factory reset"
Then Go to install
Flash rom zip
Flash nano gapps.zip
Then Reboot and enjoy
Black_Stark said:
...
Click to expand...
Click to collapse
I know this is off topic but do you know something about "Red Light Blinking" and "init Storage:Fail" ?
Thanks for the tip. Currently on havoc os . Installation went smoothly
Was searching in preparation of my K30 arriving, and found an unofficial version of TWRP is now available.
https://www.google.com/amp/s/unofficialtwrp.com/unofficial-twrp-3-3-1-xiaomi-redmi-k30/amp/
Note: I've not tried it myself, as I don't have the phone yet.
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
please give instalation guide also
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
Thanks for the info @ddaggebi
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc (using e.g. `dd=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img`). Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Again, be sure to fastboot boot recovery and then dump your ROM's misc first if you plan on flashing the recovery using that batch script, since you might need to flash it back along with the ROM's recovery for OTAs to succeed.
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Hard_Rock83 said:
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Click to expand...
Click to collapse
Yes. But some features are limited for now.
btw I installed eu rom in case stock rom replaces TWRP to stock recovery.
osm0sis said:
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc. Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Also here is the latest Magisk Canary (20308) patched stock boot.img to simplify rooting for those just getting started on this device. Simply fastboot flash boot it..
Click to expand...
Click to collapse
Ok so the question is can we reboot to recovery normally or we need to manually type fastboot command to boot to recovery..
I am still searching for twrp , which can normally appears while rebooting to recovery
LR.Team twrp-3.4.0-0209 will be installed by default when you install Eu rom.
I can reboot into recovery as normal (by pressing "vol up" & "power" button). To install root, I can simply go to "Advanced" -> "Install Root" or by using boot.img method. One thing which I can't do is deleting (or changing file name) to system file to remove some of the unwanted app.
It works very well
https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914
Hi! Ive just installed los 17.1 from this guide : https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I have also installed twrp
But now Im confused on how to install magisk
Do I use the ramdisk from emui stock firmware and patch it and fastboot flash it?
Is there a way to get a ramdisk from the los image ?
Or is it possible to just flash the normal magisk zip in twrp ?
Any help would be appreciated thank you!
(Ane-lx1
Was running emui 9.0.0.133(c185))
DonnyRedZone1 said:
Hi! Ive just installed los 17.1 from this guide : https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I have also installed twrp
But now Im confused on how to install magisk
Do I use the ramdisk from emui stock firmware and patch it and fastboot flash it?
Is there a way to get a ramdisk from the los image ?
Or is it possible to just flash the normal magisk zip in twrp ?
Any help would be appreciated thank you!
(Ane-lx1
Was running emui 9.0.0.133(c185))
Click to expand...
Click to collapse
Simply download and flash patched recovery_ramdisk
-Alf- said:
and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
Click to expand...
Click to collapse
Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
-Alf- said:
Simply download and flash patched recovery_ramdisk
Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
Click to expand...
Click to collapse
Thank you so much for helping me over the past few days man ur a legend !
(realised i was being stupid nvm)