[recovery] [modded] twrp 3.2.1-0 [oreo support] - Xiaomi Mi 5X ROMs, Kernels, Recoveries, & Other De

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.

Related

Bootloop after flashing rr nougat

Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Apcoolboy said:
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Click to expand...
Click to collapse
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
There is flashable zip file which is extracted from miui rom only. So both way will be good as flash latest stable miui rom and then twrp > rom zip > gapps. Or twr0 > firmware zip (search in any custom rom thread you will get one) > custom rom zip > gapps.
Only benefit of flashing firmware zip is less time consuming and less file size (around 50mb) compare to full miui rom.
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
unlock your bootloader again it will run without problem..

[TWRP][montana] Squid TWRP for Moto G5S

This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.

Problem with flashing root (or anything else) after installing LineageOS

Dear XDA Experts!
As I was flashing on my Redmi Note 4 Snapdragon Global (mido) LineageOS 15.1 step by step using instructions from LineageOS site I came up with a problem. Suddenly the the fastboot command didn’t “see” my phone. Before that when I was typing in the command prompt (as administrator) “adb devices” it said it found my phone. When I typed “fastboot devices” it turned out it didn’t “see” my phone so I couldn’t do the “fastboot flash recovery twrp-x.x.x-x-mido.img” command. However before fastboot stopped detecting my device I was able to do this command “adb reboot bootloader”. It turned out later that adb still was detecting my device but fastboot still was NOT detecting it.
So to flash TWRP on my phone I used a XiaomiFlashTool in which I could among other options choose to flash TWRP.
I selected this option, the XiaomiFlashTool that in order to even start and work needs access to the Internet it download the latest file twrp-x.x.x-x-mido.img with TWRP for my device and flashed it.
Now, having the TWRP installed I flashed in TWRP the file containing the LinageOS and afterwards I flashed Gapps instantly with no reboot as it was written in the guide. Then I rebooted the device to normal system mode.
The LineageOS started for the first time, I configured it and Gapps were present.
Later I’ve chosen to root the phone so I booted to TWRP and selected Install to install Magisk17.2.zip but it didn’t work cause an error occurred “couldn’t mount /data”. It was all red.
When I try to do the same thing with superSu the same problem occurred.
Could You tell me what I did wrong?
And which drivers/install programs to use to repair or uninstall and install fastboot again so It can work cause there are so many of them and the LineageOS guide doesn’t cover that thing in 100% ?
androidbadboy said:
Dear XDA Experts!
As I was flashing on my Redmi Note 4 Snapdragon Global (mido) LineageOS 15.1 step by step using instructions from LineageOS site I came up with a problem. Suddenly the the fastboot command didn’t “see” my phone. Before that when I was typing in the command prompt (as administrator) “adb devices” it said it found my phone. When I typed “fastboot devices” it turned out it didn’t “see” my phone so I couldn’t do the “fastboot flash recovery twrp-x.x.x-x-mido.img” command. However before fastboot stopped detecting my device I was able to do this command “adb reboot bootloader”. It turned out later that adb still was detecting my device but fastboot still was NOT detecting it.
So to flash TWRP on my phone I used a XiaomiFlashTool in which I could among other options choose to flash TWRP.
I selected this option, the XiaomiFlashTool that in order to even start and work needs access to the Internet it download the latest file twrp-x.x.x-x-mido.img with TWRP for my device and flashed it.
Now, having the TWRP installed I flashed in TWRP the file containing the LinageOS and afterwards I flashed Gapps instantly with no reboot as it was written in the guide. Then I rebooted the device to normal system mode.
The LineageOS started for the first time, I configured it and Gapps were present.
Later I’ve chosen to root the phone so I booted to TWRP and selected Install to install Magisk17.2.zip but it didn’t work cause an error occurred “couldn’t mount /data”. It was all red.
When I try to do the same thing with superSu the same problem occurred.
Could You tell me what I did wrong?
And which drivers/install programs to use to repair or uninstall and install fastboot again so It can work cause there are so many of them and the LineageOS guide doesn’t cover that thing in 100% ?
Click to expand...
Click to collapse
Use a Treble compatible TWRP like OrangeFox R8 and then flash Magisk
Noter2017 said:
Use a Treble compatible TWRP like OrangeFox R8 and then flash Magisk
Click to expand...
Click to collapse
I used the latest TWRP for mid (I saw when the XiaomiFlashTool was downloading the latest TWRP for mido).
May I ask why shall I use a Treble compatible since my Redmi Note 4 was manufactured in 2017 and came with not Oreo but with Nougat so it is not compatible with Project Treble from the start.
BTW Can You please direct me to that Treble compatible TWRP please?
BTW#2 The Xiaomi tool only flashes the latest TWRP .img for mido by downloading it from the internet (I can't change which TWRP will it flash).
BTW#3 The only thing I can think off to flash other TWRP is by fastboot but can You help me which or where to find it so I can uninstall current fastboot and install again or repair by installing again?
androidbadboy said:
I used the latest TWRP for mid (I saw when the XiaomiFlashTool was downloading the latest TWRP for mido).
May I ask why shall I use a Treble compatible since my Redmi Note 4 was manufactured in 2017 and came with not Oreo but with Nougat so it is not compatible with Project Treble from the start.
BTW Can You please direct me to that Treble compatible TWRP please?
BTW#2 The Xiaomi tool only flashes the latest TWRP .img for mido by downloading it from the internet (I can't change which TWRP will it flash).
BTW#3 The only thing I can think off to flash other TWRP is by fastboot but can You help me which or where to find it so I can uninstall current fastboot and install again or repair by installing again?
Click to expand...
Click to collapse
You will find OrangeFox TWRP here:
https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933
Simply boot into your existing recovery and flash OrangeFox from there.
LineageOS 15.1 on our phone uses Treble, so you need a compatible recovery. After flashing OrangeFox, you can flash Magisk
Noter2017 said:
You will find OrangeFox TWRP here:
https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933
Simply boot into your existing recovery and flash OrangeFox from there.
LineageOS 15.1 on our phone uses Treble, so you need a compatible recovery. After flashing OrangeFox, you can flash Magisk
Click to expand...
Click to collapse
But how to flash that rom since fastboot doesnt detect my phone?
androidbadboy said:
But how to flash that rom since fastboot doesnt detect my phone?
Click to expand...
Click to collapse
Can you boot into recovery?
Noter2017 said:
Can you boot into recovery?
Click to expand...
Click to collapse
I can boot into latest TWRP for mido from LineageOS site (turns out the same file is downloaded from XiaomiFlashTool)
I wanted to say Yes, I can boot to TWRP
androidbadboy said:
I can boot into latest TWRP for mido from LineageOS site (turns out the same file is downloaded from XiaomiFlashTool)
I wanted to say Yes, I can boot to TWRP
Click to expand...
Click to collapse
Great. Then all you have to do is to download OrangeFox, save it to your SD card and flash it.
After that reboot to recovery and it will start OrangeFox.
Flash Magisk and all will work
Noter2017 said:
Great. Then all you have to do is to download OrangeFox, save it to your SD card and flash it.
After that reboot to recovery and it will start OrangeFox.
Flash Magisk and all will work
Click to expand...
Click to collapse
But how am I suppose to flash it when fastboot doesnt work, adb works
Which driver/installler shall I use to repair or instal or install or uninstall and install fastboot again to use it to flash that OrangeFox
androidbadboy said:
But how am I suppose to flash it when fastboot doesnt work, adb works
Which driver/installler shall I use to repair or instal or install or uninstall and install fastboot again to use it to flash that OrangeFox
Click to expand...
Click to collapse
Its simple
save the orange fox twrp to your phone
Boot into your twrp recovery
Flash orange fox recovery
Your recovery will automatically reboot into orange fox.
kavin36 said:
Its simple
save the orange fox twrp to your phone
Boot into your twrp recovery
Flash orange fox recovery
Your recovery will automatically reboot into orange fox.
Click to expand...
Click to collapse
so is it possible to flash a TWRP by a different TWRP and it will replace it?
androidbadboy said:
so is it possible to flash a TWRP by a different TWRP and it will replace it?
Click to expand...
Click to collapse
You're right.
kavin36 said:
You're right.
Click to expand...
Click to collapse
That's a great idea but sadly I can't flash TWRP anymore. I don't know what happened. The Xiaomi program I was using to do this suddenly stopped flashing it telling me that there's something wrong with drivers
When I do "fastboot flash recovery TWRPforMido.img" it "flashes" the file in less then a second and when I enter recovery I see the old Xiaomi 3.0 stock recovery.
I have the device unlocked, developer options with USB debugging are ON.
I'm compleatly idealess.
Can You tell me what other ways to flash TWRPmido.img?
androidbadboy said:
That's a great idea but sadly I can't flash TWRP anymore. I don't know what happened. The Xiaomi program I was using to do this suddenly stopped flashing it telling me that there's something wrong with drivers
When I do "fastboot flash recovery TWRPforMido.img" it "flashes" the file in less then a second and when I enter recovery I see the old Xiaomi 3.0 stock recovery.
I have the device unlocked, developer options with USB debugging are ON.
I'm compleatly idealess.
Can You tell me what other ways to flash TWRPmido.img?
Click to expand...
Click to collapse
not sure bout this situation
But try doing the same but download orange fox recovery from xda forums and use the same method to flash.
That's
Fastboot mode in phone
Command from cmd
Flash recovery
Reboot recovery
kavin36 said:
not sure bout this situation
But try doing the same but download orange fox recovery from xda forums and use the same method to flash.
That's
Fastboot mode in phone
Command from cmd
Flash recovery
Reboot recovery
Click to expand...
Click to collapse
I already done this a thousand times. Nothing.
androidbadboy said:
I already done this a thousand times. Nothing.
Click to expand...
Click to collapse
do us have root access
If us have try flashify app from play store
Select recovery
Browse the orange fox recovery on it phone
Flash
Only if ur rooted
kavin36 said:
do us have root access
If us have try flashify app from play store
Select recovery
Browse the orange fox recovery on it phone
Flash
Only if ur rooted
Click to expand...
Click to collapse
Nope I don't.
But I finally flashed stock, TWRP for mido (not Orange) and Magisk for root and I'm so tierd now
Just tell me what shall I do next to install 1. Lin Os (their guide is not accurate in 100%) 2. Some custom romwith project treble and Android Pie, some popular good stuff
server error - a double post
androidbadboy said:
Nope I don't.
But I finally flashed stock, TWRP for mido (not Orange) and Magisk for root and I'm so tierd now
Just tell me what shall I do next to install 1. Lin Os (their guide is not accurate in 100%) 2. Some custom romwith project treble and Android Pie, some popular good stuff
Click to expand...
Click to collapse
I've heard that Crdroid official
And Siberia os unofficial are the most stable pie ROMs
Make sure it twrp is treble supported becuz someone told that official twrp has no treble support that's the reason I use orange fox
If it ain't treble supported just flash orange fox from the same twrp
Do advanced wipe
Install from and gapps
---------- Post added at 07:27 PM ---------- Previous post was at 07:27 PM ----------
kavin36 said:
I've heard that Crdroid official
And Siberia os unofficial are the most stable pie ROMs
Make sure it twrp is treble supported becuz someone told that official twrp has no treble support that's the reason I use orange fox
If it ain't treble supported just flash orange fox from the same twrp
Do advanced wipe
Install from and gapps
Click to expand...
Click to collapse
Also Ive seen that Serbia unofficial is a bit more stable than crdroid official. Its your preferences
kavin36 said:
I've heard that Crdroid official
And Siberia os unofficial are the most stable pie ROMs
Make sure it twrp is treble supported becuz someone told that official twrp has no treble support that's the reason I use orange fox
If it ain't treble supported just flash orange fox from the same twrp
Do advanced wipe
Install from and gapps
---------- Post added at 07:27 PM ---------- Previous post was at 07:27 PM ----------
Also Ive seen that Serbia unofficial is a bit more stable than crdroid official. Its your preferences
Click to expand...
Click to collapse
Could You do step by step 1., 2. what I shall do (at the example of Linage OS). And what about that advanced wipe thing. People that told me steps just like You didn't mention Advanced wipe

Unofficial TWRP now available

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

When will TWRP get support to Android 10?

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.

Categories

Resources