Download the essential dummy image to bypass Anti-rollback Protection (ARB) by reactivating Fastboot connection from your PC to a Xiaomi device. This ARB Bypasser is a flash-able image that you can make use of before installing TWRP custom recovery on ARB-enabled devices such as Redmi Note 5, Mi 6X, Redmi S2, or Mi 8. You need this or your device will brick and broken.
What is ARB? It is a new security mechanism introduced by Google since Android Oreo. Xiaomi has managed to adopt the security measure on the latest MIUI updates for some devices. This protection will prevent users from downgrading their devices to older MIUI versions.
However, there is another side effect of the protection. Fans of custom recoveries, custom ROMs, and Magisk root, cannot easily flash any custom binaries to their phone through the ADB-fastboot connection. This dummy image acts as the fastboot unlocker.
Necessary reading:
Download Fastboot Unlocker to bypass ARB
Grab the file from the direct link below. The file is very small in size. Download it to your computer and use programs like Winzip or Winrar to decompress the file. You may also use the built-in unzipper feature on Windows 8/8.1/10.
What does this ARB bypasser do?
- It checks for the value of ARB index.
- If the ARB index is smaller than 4, then it flashes normally.
- If the ARB index is 4, it flashes dummy to the anti-rollback pass, then proceeds to flash a ROM, after flashing is done you will have the same ARB 4.
- If the ARB index is bigger than 4, like 5 or something else, the script will abort and tell you to get a ROM with ARB 4.
Recommended reading:
How to use?
fastboot flash antirbpass dummy.img
You have to flash dummy ARB bypasser or the fastboot unlocker every time you reboot your ARB-enabled device into the bootloader/fastboot mode. Otherwise, the planted ARB protection will block any fastboot commands.
Credits: AL_IRAQI.
Why do I get the message “System has been destroyed” when I flash dummy file?
I had a locked bootloader and try this command.
Got this message and to my luck phone boot it normal, just because bootloader was locked I guess…
I’m really afraid to get root at this point because of that. My Redmi Note 5 Global is now unlocked and waiting the next step to get root…
You need an unlocked bootloader. Otherwise, your device may return error when flashing the dummy image.
So, are you telling me that, now, with bootloader unlocked, rooting process will go without errors? I mean I should go ahead and root my phone without any fears of brick? Could be so easy?
Can this be used with k20 pro?
I can’t apply any recovery on my mi 6X (converted from mi A2).
Whenever I give fastboot command it crashes and no longer accepts any fastboot command. Only after rebooting.
Example:
C: \ adb> getvar anti fastboot
anti: 4
finished. total time: 0.001s
—————————————————————–
C: \ adb> fastboot flash recovery twrp-3.3.1-0-wayne.img
target reported max download size of 536870912 bytes
sending ‘recovery’ (37620 KB) …
FAILED (data transfer failure (Too many links))
finished. total time: 0.144s
With dummy.img:
C: \ adb> fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending ‘antirbpass’ (8 KB) …
OKAY [0.005s]
writing ‘antirbpass’ …
OKAY [0.005s]
finished. total time: 0.014s
C: \ adb> fastboot flash recovery twrp-3.3.1-0-wayne.img
target reported max download size of 536870912 bytes
sending ‘recovery’ (37620 KB) …
FAILED (data transfer failure (Too many links))
finished. total time: 0.055s
I can’t update MIUI.eu 11 because it updates by recovery, nor does it apply magisk.
Have a solution to my problem?
how to unlock bootloader of hardbricked redmi note 5 pro
Basicaly you can’t. Bring it to the nearest Mi authorized service center
target reported max download size of 805306368 bytes
sending ‘antirbpass’ (8 KB)…
OKAY [ 0.016s]
writing ‘antirbpass’…
FAILED (remote: (antirbpass) No such partition)
finished. total time: 0.016s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending ‘recovery’ (38924 KB)…
OKAY [ 0.839s]
writing ‘recovery’…
FAILED (remote: Error flashing partition : Write Protected)
finished. total time: 0.955s
what is next