Develop Bugs

Stuck on MIUI pie latest beta!

Actually I flashed MIUI 10 pie beta yesterday and now because of battery drain issues and bugs I want to go to another ROM which is masik 3.3 which is based on Oreo.
I am not sure what to do.
Should I directly install masik 3.3 by doing clean flash over Miui Pie beta or should I first go to Developer/Stable Oreo based MIUI 10 ROM and then clean flash Masik 3.3?
What abour ARB/firmware?Thanks!

First oreo latest stabil miflash to flash. After install twrp and masik 3.3 clean flash

Second option (I did it already). Flash via Mi Flash latest stable.
The first option will soft brick your device.

Letrix said:
Second option (I did it already). Flash via Mi Flash latest stable.
The first option will soft brick your device.
Click to expand...
Click to collapse
I tried using mi flash but device id not showing.
To confirm I type adb devices in command prompt. List of devices attached is showing empty. After that i tried installing new updates drivers but nothing helped. I am on windows 10. ADB drivers are also installed. Platform tools too. I did all but list of devices is showing empty in fastboot mode. Though I can see adb devices when in recovery or in system. I don't know what to do. can you help please?

Vivi_31 said:
I tried using mi flash but device id not showing.
To confirm I type adb devices in command prompt. List of devices attached is showing empty. After that i tried installing new updates drivers but nothing helped. I am on windows 10. ADB drivers are also installed. Platform tools too. I did all but list of devices is showing empty in fastboot mode. Though I can see adb devices when in recovery or in system. I don't know what to do. can you help please?
Click to expand...
Click to collapse
You have installed pie rom u cant go back to masik 3.3 cause its oreo based rom. I sent you a meassage just check.

Vivi_31 said:
I tried using mi flash but device id not showing.
To confirm I type adb devices in command prompt. List of devices attached is showing empty. After that i tried installing new updates drivers but nothing helped. I am on windows 10. ADB drivers are also installed. Platform tools too. I did all but list of devices is showing empty in fastboot mode. Though I can see adb devices when in recovery or in system. I don't know what to do. can you help please?
Click to expand...
Click to collapse
Install Pie and MIUI Pie Recovery. Then, from recovery, boot to bootloader and check in PC if it's listed.

thewhitewolf89 said:
You have installed pie rom u cant go back to masik 3.3 cause its oreo based rom. I sent you a meassage just check.
Click to expand...
Click to collapse
Yes that's why

Letrix said:
Install Pie and MIUI Pie Recovery. Then, from recovery, boot to bootloader and check in PC if it's listed.
Click to expand...
Click to collapse
Well I tried it but didn't work.
Instead now I am flashing Pixel Experience and then after going to pixel experience, I will go to latest MIUI stable ROM available on Xiaomi website and then never go to Miui beta Pie update unless stable version comes. Too much headache. lol
But thank you all who responded

Is it possible to return to Oreo 10.2.2.0 from Pie beta 9.3.28?
I have unlocked bootloader and orangefox recovery for pie.

umair42 said:
Is it possible to return to Oreo 10.2.2.0 from Pie beta 9.3.28?
I have unlocked bootloader and orangefox recovery for pie.
Click to expand...
Click to collapse
I returned to Oreo from Xiaomi.eu Pie Beta. It's described above

Vivi_31 said:
Actually I flashed MIUI 10 pie beta yesterday and now because of battery drain issues and bugs I want to go to another ROM which is masik 3.3 which is based on Oreo.
I am not sure what to do.
Should I directly install masik 3.3 by doing clean flash over Miui Pie beta or should I first go to Developer/Stable Oreo based MIUI 10 ROM and then clean flash Masik 3.3?
What abour ARB/firmware?Thanks!
Click to expand...
Click to collapse
I recovered my phone by flashing Stock ROM "miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip" via TWRP. It will overwrite TWRP with Stock Recovery, You have to reflash TWRP via fastboot.
After that you will be able to flash any Custom ROM successfully.

yawarniazi said:
I recovered my phone by flashing Stock ROM "miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip" via TWRP. It will overwrite TWRP with Stock Recovery, You have to reflash TWRP via fastboot.
After that you will be able to flash any Custom ROM successfully.
Click to expand...
Click to collapse
Does it softbrick ur whyred? The safety way is flash thru mi flasher

yawarniazi said:
I recovered my phone by flashing Stock ROM "miui_HMNote5HMNote5ProGlobal_V10.2.1.0.OEIMIXM_5191f339c3_8.1.zip" via TWRP. It will overwrite TWRP with Stock Recovery, You have to reflash TWRP via fastboot.
After that you will be able to flash any Custom ROM successfully.
Click to expand...
Click to collapse
Won't it brick(ARB) phone if I go back to stable?
Are you sure about ROM you flash? because on xiaomi official website its saying latest stable is V10.2.20 and not V10.2.1.0.
Can you confirm it plz? Thanks!

Kuato said:
Does it softbrick ur whyred? The safety way is flash thru mi flasher
Click to expand...
Click to collapse
Do you know anyother way which doesnt require pc? Actually my device is not getting recognized in adb devicess...I tried all but nothing helped.

Vivi_31 said:
Do you know anyother way which doesnt require pc? Actually my device is not getting recognized in adb devicess...I tried all but nothing helped.
Click to expand...
Click to collapse
I was tried to direct flash with TWRP and softbrick my whyred, but I figured out when I was done flash miui 8.1, I should flash Redwolf recovery which is capable to flash persist partition to fix some of bugs acquired from downgrade. Its work for me, first I tried direct flash to miui 10.2.2.0 and its boot fine, but when I reboot, It doesnt boot up and on my pc detected as 9008 (softbrick?). Then I flash pie twrp thru fastboot and booting to twrp, flash miui beta pie and let it booting,
Second try. Now im on miui pie again LOL. then I flash miui 10.2.2.0 thru TWRP, and flash redwolf recovery, then reboot to redwolf, then flash persist.img. then boot up fine and no bug.

Kuato said:
I was tried to direct flash with TWRP and softbrick my whyred, but I figured out when I was done flash miui 8.1, I should flash Redwolf recovery which is capable to flash persist partition to fix some of bugs acquired from downgrade. Its work for me, first I tried direct flash to miui 10.2.2.0 and its boot fine, but when I reboot, It doesnt boot up and on my pc detected as 9008 (softbrick?). Then I flash pie twrp thru fastboot and booting to twrp, flash miui beta pie and let it booting,
Second try. Now im on miui pie again LOL. then I flash miui 10.2.2.0 thru TWRP, and flash redwolf recovery, then reboot to redwolf, then flash persist.img. then boot up fine and no bug.
Click to expand...
Click to collapse
I flashed latest stable rom on miui pie beta through twrp. Now i cannot boot into recovery mode at all (softbrick?)
When I boot into miui, we have to setup things but when we are adding account google services stops and i see black screen , I cannot go ahead, i think zip file was not good. I dont know what to do now. I cant go to twrp neither to system and cannot flash through fastboot becuz it doent recognize adb devices

Vivi_31 said:
I flashed latest stable rom on miui pie beta through twrp. Now i cannot boot into recovery mode at all (softbrick?)
When I boot into miui, we have to setup things but when we are adding account google services stops and i see black screen , I cannot go ahead, i think zip file was not good. I dont know what to do now. I cant go to twrp neither to system and cannot flash through fastboot becuz it doent recognize adb devices
Click to expand...
Click to collapse
Does fastboot recognized?? If its recognized. U can fix it easily.
I was on same problem as you, but I can flash thru mi flasher. At my second try (to make my phone in same condition as before I fix it), I flash oreo recovery without reboot the device after flashing miui oreo. And then flash the persist img thru advance-terminal and its work and no softbrick anymore.

Kuato said:
Does fastboot recognized?? If its recognized. U can fix it easily.
I was on same problem as you, but I can flash thru mi flasher. At my second try (to make my phone in same condition as before I fix it), I flash oreo recovery without reboot the device after flashing miui oreo. And then flash the persist img thru advance-terminal and its work and no softbrick anymore.
Click to expand...
Click to collapse
Well I went to service centre and they flashed it. I am on Stable ROM now. I couldn't through my computer because it's not recognising adb devices but recognising fastboot devices. I can't boot into any recovery other then stock even through fastboot devices. You know why? I can't find any reasons for that.

Vivi_31 said:
Well I went to service centre and they flashed it. I am on Stable ROM now. I couldn't through my computer because it's not recognising adb devices but recognising fastboot devices. I can't boot into any recovery other then stock even through fastboot devices. You know why? I can't find any reasons for that.
Click to expand...
Click to collapse
Have u flash antirbpass before flashing ?

Kuato said:
Have u flash antirbpass before flashing ?
Click to expand...
Click to collapse
Idk much ab it but what I do is :
fastboot devices
fastboot flash antirbpass dummy.img
fastboot flash recovery recovery.img
after that it says error : Can't target recovery.
and stuck on mi logo if i boot into any other recovery

Recovery mode is not starting

I had Orangefox recovery installed on my Redmi note 5 Pro with Android 8.1,
After the release of Orangefox recovery for PIE,
I flashed the zip of Orangefox recovery,
& Waited to boot into Recovery, but it is not booting into recovery,
Only the logo is showing whenever I try to boot into Recovery
I've tried to install the recovery also through Adb commands, then also it is not booting into Recovery
Is it means I will unable to use recovery on my phone ever, because there is no any solution for this issue on internet.
Please help me guys.

Pritam Mohriya said:
I had Orangefox recovery installed on my Redmi note 5 Pro with Android 8.1,
After the release of Orangefox recovery for PIE,
I flashed the zip of Orangefox recovery,
& Waited to boot into Recovery, but it is not booting into recovery,
Only the logo is showing whenever I try to boot into Recovery
I've tried to install the recovery also through Adb commands, then also it is not booting into Recovery
Is it means I will unable to use recovery on my phone ever, because there is no any solution for this issue on internet.
Please help me guys.
Click to expand...
Click to collapse
What's rom and fw are you using?

Masik 4.0 Android 8.1 Oreo

Pritam Mohriya said:
Masik 4.0 Android 8.1 Oreo
Click to expand...
Click to collapse
maybe fix it with fastboot rom and miflash this wll install stock miui recovery, then youll need to install twrp

raptorddd said:
maybe fix it with fastboot rom and miflash this wll install stock miui recovery, then youll need to install twrp
Click to expand...
Click to collapse
Yeah may be.
But Can we use mi flash tool without having stock recovery installed?

Pritam Mohriya said:
Yeah may be.
But Can we use mi flash tool without having stock recovery installed?
Click to expand...
Click to collapse
Yes you can, miflash work in fastboot mode not in recovery, it will also restore your recovery to stock.

sushuguru said:
Yes you can, miflash work in fastboot mode not in recovery, it will also restore your recovery to stock.
Click to expand...
Click to collapse
Okay. I'll do it, and tell you if get fixed.
Thankyou so much for helping me.

Can NOT boot into custom recovery after MIUI Pie 10.3.1 Global Stable update

My bootloader is unlocked.
After installing PIE update to MIUI Global 10.3.1.0 Stable, when I try to boot OrangeFox recovery ver. R9.0-2 for Whyred using fastboot command "fastboot boot recovery.img" in CMD ( the result is shown below), the phone does NOT boot in OrangeFox recovery. It just remain stuck on MI logo after booting ...
C:\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.951s]
booting OKAY [ 0.157s]
Finished. Total time: 1.158s
Kindly advise on how to resolve the issue

Did you temporarily deactivate the Anti-Rollback-Feature with
>fastboot flash antirbpass dummy.img
where you will find the dummy.img in the official download of the Xiaomi firmware before trying to boot into recovery?
This needs to be done in the same fastboot-session that you want to boot into recovery.

NOTE 5 PRO Soft Bricked recovery bootLoop after MIUI Pie 10.3.1 Global Stable update
One more!! Hello i have a note 5 pro, yesterday it received automatic OTA update of miui 10.3.1.0.PEIMIXM with android 9.0, after install it soft bricked saying this miui version cant be installed on this device.
it lets me wipe data, which didnt help, also i connect with mi assistant using my pc suite nothing works, pc suite wont even recognize the phone on windows 10,.
PLEASE HELP! !
Kindly advise on how to resolve the issue[/QUOTE]

JosephusQuint said:
Did you temporarily deactivate the Anti-Rollback-Feature with
>fastboot flash antirbpass dummy.img
where you will find the dummy.img in the official download of the Xiaomi firmware before trying to boot into recovery?
This needs to be done in the same fastboot-session that you want to boot into recovery.
Click to expand...
Click to collapse
Many thanks for the advice. Worked like a charm. :good:
No, I did NOT deactivate the Anti-Rollback-Feature which was causing the problem.
In the past, whenever I installed custom recovery on my device including the first time, I did NOT have to flash dummy.img as my device booted into custom recovery without flashing dummy.img.
P.S.: I used dummy.img from this thread:
Everything About Anti Roll-back [Whyred]

ExoticPoint said:
One more!! Hello i have a note 5 pro, yesterday it received automatic OTA update of miui 10.3.1.0.PEIMIXM with android 9.0, after install it soft bricked saying this miui version cant be installed on this device.
it lets me wipe data, which didnt help, also i connect with mi assistant using my pc suite nothing works, pc suite wont even recognize the phone on windows 10,.
PLEASE HELP! !
Kindly advise on how to resolve the issue
Click to expand...
Click to collapse
ONLY IF you have Unlocked-Bootloader, then you can use this MIUI Flashing Guide- Method 2: Fastboot Update to unbrick your device.
Please carefully chose the firmware version (Global / India) to download the fastboot stock ROM for your device.

Lahoria said:
Many thanks for the advice. Worked like a charm. :good:
No, I did NOT deactivate the Anti-Rollback-Feature which was causing the problem.
In the past, whenever I installed custom recovery on my device including the first time, I did NOT have to flash dummy.img as my device booted into custom recovery without flashing dummy.img.
P.S.: I used dummy.img from this thread:
Everything About Anti Roll-back [Whyred]
Click to expand...
Click to collapse
Great that it solved your problem!
As addendum: The Anti-Rollback (afaik) has to be disabled every single time the recovery is changed/updated. This caught me off guard as I wanted to update TWRP from within the offical TWRP app. This failed and made my recovery unusable (Although I could still normally boot into system).
So let this be a cautionary tale to people.

I can't boot to my custom recovery in my redmi note 5. it is booting to the original recovery. I tried TWRP and REDWOLF recoveries . It will boot in the first time, then I reboot my phone after that when I reboot, it is booting to the original recovery. Same happened when I tried RED WOLf recovery. Pls help me.

Ayyappadas said:
I can't boot to my custom recovery in my redmi note 5. it is booting to the original recovery. I tried TWRP and REDWOLF recoveries . It will boot in the first time, then I reboot my phone after that when I reboot, it is booting to the original recovery. Same happened when I tried RED WOLf recovery. Pls help me.
Click to expand...
Click to collapse
After flash twrp, just flash magisk zip through twrp recovery...

TWRP Recovery Not Opening

I am using Pixel Experience as custom ROM, when update arrived I tried to install it but it freeze at starting screen of TWRP, recovery not really started, and now I am stuck in kinda bootloop, please help !!
Device : Xiaomi Redmi Note 5 Pro
Code Name : whyred
TWRP version : latest (3.6.2_9-0)

standingalone said:
I am using Pixel Experience as custom ROM, when update arrived I tried to install it but it freeze at starting screen of TWRP, recovery not really started, and now I am stuck in kinda bootloop, please help !!
Device : Xiaomi Redmi Note 5 Pro
Code Name : whyred
TWRP version : latest (3.6.2_9-0)
Click to expand...
Click to collapse
try to enter in fastboot mode and flash Orangefox which is newer than the twrp.

NOSS8 said:
try to enter in fastboot mode and flash Orangefox which is newer than the twrp.
Click to expand...
Click to collapse
Really, newer than official TWRP 3.6.2_9-0?

drnightshadow said:
Really, newer than official TWRP 3.6.2_9-0?
Click to expand...
Click to collapse
no, that's a mistake on my part.

same problem with me
after hardbrick i have installed twrp then my phone got freezed and then i somehow installed pitchblack using commands like
getvar anti
anitbrpass something
then pitchblack was installed but twrp and and ofox are not installling
device whyred

SurajCr said:
same problem with me
after hardbrick i have installed twrp then my phone got freezed and then i somehow installed pitchblack using commands like
getvar anti
anitbrpass something
then pitchblack was installed but twrp and and ofox are not installling
device whyred
Click to expand...
Click to collapse
Antibrpass dummy.IMG BTW..
Wow that's weird 2nd report that twrp is not working ... Khmm ..that's what I do the 1st thing after unlocking bootloader... Idk something is missing or there is new ABR .. Really weird need new whyred to test...

Enter fastboot mode, on your PC use the command "fastboot reboot", your phone should reboot, it will try to re-enter TWRP, do not allow that, try to re-enter fastboot mode, use the command "fastboot continue" and it should boot normally.

How To Guide OrangeFox Recovery | UNOFFICIAL for Xiaomi 11T

1. Boot into fastboot mode. To do this, restart your device, then press the volume down key until the fastboot screen appears.
2. Connect your device to PC/laptop.
3. Now to install the recovery, enter "fastboot flash boot boot.img" or you can drag the image to cmd "fastboot flash boot (drag file)"
It is important to have your own boot.img, it does not load on all firmwares. To boot, you need to flash it in OrangeFoxboot to the boot section.

Does this work on android 12 (MIUI 13.0.5 global) ?

mangi. k said:
It is important to have your own boot.img, it does not load on all firmwares. To boot, you need to flash it in OrangeFoxboot to the boot section.
Click to expand...
Click to collapse
Hi guy,
I don't really understand what you mean ?? are you succeed in flashing Orange Recovery ?
What is OFRP-agate-boot-1.img ? Is it necessary to rename this file to "boot.img" and then flashing it via fastboot ?
To sum up, to install orange recovery, do I have to flash the file in the link via fastboot ?

Greetings, I wanted to know if someone has been able to install this Recovery on Xiaomi mi 11T Amber

felixpaz1992 said:
Greetings, I wanted to know if someone has been able to install this Recovery on Xiaomi mi 11T Amber
Click to expand...
Click to collapse
Man could you try flashing this on a11

Stephanizgo said:
Man could you try flashing this on a11
Click to expand...
Click to collapse
I tried it like TWRP, but it only remains in the fox logo, not whether I'm skipping something or it's the IMG 1ue that doesn't work

felixpaz1992 said:
I tried it like TWRP, but it only remains in the fox logo, not whether I'm skipping something or it's the IMG 1ue that doesn't work
Click to expand...
Click to collapse
I booted on MIUI 14 but could not boot system
Please show me your kernel version if it's also 4.14.186 I want to know if this phone was EOL from the day it shipped