Database Info

Redmi Note 7 Pro - Bricked (Current Device Anti Rollback is greater than this Pkg.)

I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.

TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs

hackermssharma said:
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thank you for taking time to reply to my query. I did what you suggested and got into EDL mode. Xiaomi Mi Flash picked up the device as COM10 but when I tried to flash it shows "sahara read end error with status:40" and nothing happens.
Any further idea?

TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
I suggest you use the older variant of the MiFlash tool.
How did you flash Peter's? Did you use "fastboot flash recovery recovery.img"? That's the only right command.
Also are you sure you have the Indian variant of the phone? Another way to bypass anti roll back would be to clear all partitions, and then flash the required ROM.
Sorry if I'm not able to help you, I'll try having a look later on.

Thank you for your support. I had to go to the service center as no solution could be found.

Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.

dnyaneshmoh said:
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
Click to expand...
Click to collapse
Thank you for your feedback but the phone bootloader remained unlocked as when the phone starts there is "unlocked" written in bottom.
I got the phone back from Service Center. It's working fine but strangely still the bootloader is shown as unlocked in the start animation.

Unable to install TWRP - Stuck fastboot mode

Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,

C666PO said:
Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.0.3 GM21BA
Anndroid Version: 10
Model: GM1913
Hi all,
I received yesterday my Oneplus 7 Pro. My objective is to install nethunter fully rooted.
After looking the requirements in the offensive security website i noticed i need 3 things
TWRP
Magisk
DM-Verify
I started with TWRP watching different tutorials and comparing them but they are similar.
- Installed sdk platform tools and Minimal adb/fastboot ( tried both ways )
-unlocked the bootloader and enabled usb debug mode.
- Once i do " fastboot boot twrp.img " everything seems " okay " in the terminal, but the phone becomes stuck in fastboot mode logo image, it never actually boots into the twrp.
In a different tutorial, i replaced the "fastboot boot twrp.img" with " fastboot flash boot twrp.img ". This broke my phone i couldn't start the android or go the recovery mode, i couldn't leave fastboot mode unless to restart or to turn off the phone. I fixed this by " fastboot flash boot boot.img " that i had available in the platform tools folder.
I tried different twrp images:
TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
TWRP 3.3.1-70 Unified Unofficial Pie by mauronofrio
twrp-3.3.1-4-guacamole.img
Nothing seems to work, i don't know what else to try or what am i doing wrong.
I've been 8 hours around this so any help would be deeply appreciated.
Kind regards,
Click to expand...
Click to collapse
I have an almost identical problem to you.
except: my device is GM1910, I had a stock hydrogen OS, which has been converted to oxygen OS.
so far, I have tried twrp-3.3.1-0, 3.3.1-2, 3.3.1-3, 3.3.1-4, on oxygen OS version 10.0.2.GM21AA, 10.0.3.GM21AA, and 10.3.0.GM21AA, all would stuck at the fastboot mode logo screen
Rolling back to a lower version of oxygen OS, including version 9.5.1 and 9.5.7 causes my OP7P in bootloader mode no longer recognized by "fastboot devices", or even by "dmseg" as a usb device.
I received a suggestion of trying the latest TWRP 3.3.1-74 build, which I intend to try later tonight, but got not so optimistic about, seeing that you've experimented with TWRP 3.3.1-74 Unified Unofficial Pie by mauronofrio
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?

OblixioN said:
One observation I do like to make, is that android 9 is considered as Pie while android 10 was developed from android Q.
since your device is already android 10 at version 10.0.3, should you still use the Pie TWRP build?
Click to expand...
Click to collapse
Hi OblixioN,
I tried the image with the Q at the end: TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio and it worked. I had no idea what the Q or Pie meant so your information just solved my problem. I assume it will work for you.
Huge thanks!

Thanks - worked for me as well!
Unfortunately I formated before getting to this solution, so rather unnecessary for me, but what I did was getting the unofficial twrp for guacamole here:
h-t-t-p-s://androidfilehost.com/?fid=4349826312261707787
(from this post: https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322)
Then I booted to fastboot at ran
Code:
fastboot set_active a
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
fastboot set_active b
fastboot boot .\twrp-3.3.1-75-guacamole-unified-Q-mauronofrio.img
Now I could boot into twrp, it found all the internal data storage, and I could sideload
Code:
adb sideload .\twrp-installer-3.3.1-4-guacamole.zip
adb sideload .\Magisk-v20.3.zip

C666PO said:
I had no idea what the Q or Pie meant so your information just solved my problem.
Click to expand...
Click to collapse
It means if you are on Android Q, you need to use the TWRP version that supports Android Q.

Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?

OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
hey there.
So, first of, You restart it by pressing and holding volume up, down and power at the same time for 10+ seconds.
And second, try updating Oxygen OS to its latest version. It works for me now, just unpacked a new OnePlus 7 Pro, didn't work on Android 9, works on Android 10 latest update.

OrionGiant said:
Hey, I seem to have the same problem but how do u get it unstuck from the Fastboot Mode so I can try another version of TWRP?
Click to expand...
Click to collapse
While in fastboot , " fastboot boot twrp.img

Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?

SABMAN said:
Hi!
I'm on the latest official OxygenOS 11 and am having the exact same issue you hade above.
Tried everything mentioned above and the phone is still boot looping :'(
Any more tips?
Click to expand...
Click to collapse
I tried installing a new kernal and after that mine would go directly to bootloader, no matter what I did it went directly to bootload, thankfully fastboot was still active but using boot cmd into anything would fail,, ,I started my msm tool, and rebooted into edl and as soon as a com port became active on the MSM panel I hit start, and it took off running and did it's thing,

I think my issue had two reasons!
1. The boot.img file i used was from the earlier Oxygen update not the version i had just installed.
2. The phone encryption (but i doubt this!)
Anyway since nothing helped i erased the phone and restored it Now it's working again!

[GUIDE] Install GSI on Xiaomi Mi 10

This is how it works for me.
If someone knows a better way let me know.
What you need
Xiaomi Mi 10 (UMI) with unlocked bootloader and latest Xiaomi.eu ROM installed
A/B GSI
PC with ADB & Fastboot installed
USB Cable
Mi 10 stock recovery installed or img for installation
TWRP.img for Mi 10 (If you want to install anything else like Magisk or something)
Boot to fastboot
(Skip this part if you're using stock recovery)
Power off your phone
Hold Volume down + Power until you see fastboot screen
Flash stock recovery found in latest firmware
Code:
fastboot flash recovery recovery.img
Boot to recovery
Power off your phone
Hold Volume up + Power until you see recovery screen
Wipe data
Select option Connect with MiAssistant
Reboot into fastbootd (Fastboot User Space)
Code:
adb reboot fastboot
Erase system partition
Code:
fastboot erase system
Flash your GSI
Code:
fastboot flash system system.img
If you're done here and doesn't want to install anything else
Just reboot and enjoy!
Code:
fastboot reboot
If you want to install anything else
Reboot to fastboot
Code:
fastboot reboot bootloader
Boot TWRP
Code:
fastboot boot TWRP.img
Use MTP to transfer your zip files to internal storage
Install them
Reboot
Enjoy!
Working Images (Need to be A/B)
Quack Phh-Treble
AOSP Q Mod //CAOS
Maybe any image with phhusson treble_experimentations included
At this time (Patch v222) there are some issues (Nothing compared to MIUI's bugs )
Audio issues (Most of them can be fixed by disabling audio effetcs in phh's Settings)
BT audio doesn't work
Fingerprint doesn't work
90 Hz Display doesn't work (Limited to 60 Hz)
Tell me if you found any other working GSI (Please provide forum link)

Which vendor and firmware did you used? Latest one 20.9.4 or specific one?
https://xiaomifirmwareupdater.com/vendor/umi/
https://xiaomifirmwareupdater.com/firmware/umi/

sceryavuz said:
Which vendor and firmware did you used? Latest one 20.9.4 or specific one?
https://xiaomifirmwareupdater.com/vendor/umi/
https://xiaomifirmwareupdater.com/firmware/umi/
Click to expand...
Click to collapse
My Mi 10 was on latest xiaomi.eu stable.

you can write what system images you managed to run on mi10

Kabanoska said:
you can write what system images you managed to run on mi10
Click to expand...
Click to collapse
Sorry I dont understand
Edit: Now I got it...

Is it same guide for Mi 10 Pro?

henkka22 said:
Is it same guide for Mi 10 Pro?
Click to expand...
Click to collapse
I think it'll be the same. As long as you can go to fastbootd with this guide it should be fine.

Basecatcherz said:
I think it'll be the same. As long as you can go to fastbootd with this guide it should be fine.
Click to expand...
Click to collapse
I can confirm that this tutorial works for cmi too. Phhs treble is running but same bugs. Andy yans lineage didn't work If you want this tutorial could be copied to mi 10 pro forums too since there is no roms for it

henkka22 said:
I can confirm that this tutorial works for cmi too. Phhs treble is running but same bugs. Andy yans lineage didn't work If you want this tutorial could be copied to mi 10 pro forums too since there is no roms for it
Click to expand...
Click to collapse
There is something weird here...
I tried some other GSI and ended up soft bricked. Flashed latest stock (boots up) and then flashed CAOS GSI again.
It goes to boot splash and restarts all the time.
Are you on xiaomi.eu?

Basecatcherz said:
There is something weird here...
I tried some other GSI and ended up soft bricked. Flashed latest stock (boots up) and then flashed CAOS GSI again.
It goes to boot splash and restarts all the time.
Are you on xiaomi.eu?
Click to expand...
Click to collapse
I flashed latest stable xiaomi.eu (was on weekly) and then flashed phhs treble. Can't flash over weekly android 11. Didn't try caos

henkka22 said:
I flashed latest stable xiaomi.eu (was on weekly) and then flashed phhs treble. Can't flash over weekly android 11. Didn't try caos
Click to expand...
Click to collapse
Alright. I flashed latest stable xiaomi.eu ROM and now CAOS boots up. Looks like they made some relevant changes.

And btw you don't need stock recovery. I have twrp which have userspace fastboot aka fastbootd so I can leave it installed

henkka22 said:
And btw you don't need stock recovery. I have twrp which have userspace fastboot aka fastbootd so I can leave it installed
Click to expand...
Click to collapse
I tried that, too (LR Team). But Windows was unable to find the right driver and I was unable to use it. Even on Ubuntu it wasn't working.

Basecatcherz said:
I tried that, too (LR Team). But Windows was unable to find the right driver and I was unable to use it. Even on Ubuntu it wasn't working.
Click to expand...
Click to collapse
I just used newest platform tools directly from google site on ubuntu

henkka22 said:
I just used newest platform tools directly from google site on ubuntu
Click to expand...
Click to collapse
On ubuntu I used them, too. In the windows package there are no drivers included.
I tried many drivers flying around in the www...

Does caos gsi pass safetynet for you?

henkka22 said:
Does caos gsi pass safetynet for you?
Click to expand...
Click to collapse
The non-rooted variant with magisk, yes.
Phh's got the problem thats it's pre-rooted.

Basecatcherz said:
On ubuntu I used them, too. In the windows package there are no drivers included.
I tried many drivers flying around in the www...
Click to expand...
Click to collapse
I used Windows originally, you'll have to manually install the Xiaomi drivers from Xiaomi cn website through computer mangement, on this link: https://www.xiaomi.cn/post/18464849. Since these are not signed, you will have to disable signature enforcement on Windows 10! Here is an article on doing that, method 1 works: https://windowsloop.com/disable-driver-signature-enforcement-on-windows/.
Or you can try Mi Flash Tool and look for the install driver option, I haven't tried that method. Let us know how it goes .

xda-jimjongs said:
I used Windows originally, you'll have to manually install the Xiaomi drivers from Xiaomi cn website through computer mangement, on this link: https://www.xiaomi.cn/post/18464849. Since these are not signed, you will have to disable signature enforcement on Windows 10! Here is an article on doing that, method 1 works: https://windowsloop.com/disable-driver-signature-enforcement-on-windows/.
Or you can try Mi Flash Tool and look for the install driver option, I haven't tried that method. Let us know how it goes .
Click to expand...
Click to collapse
I will try that. Maybe tomorrow
Unsigned drivers are not the way I like...

I have MIUI 11 Xiaomi.eu Android 10 stable, can I flash this ROM and Gapps, and maybe some progress to remove in existing issues?

Question ONEPLUS 9 china unbrick

ONEPLUS 9 china unbrick what i must to do to bypass model id and flash device

What are you stuck on, give me exact details. I have same device and have done it every which way. PM if needed. Plus there are other threads with exactly what you need.

illusiveairforce said:
What are you stuck on, give me exact details. I have same device and have done it every which way. PM if needed. Plus there are other threads with exactly what you need.
Click to expand...
Click to collapse
i got china version i flash this :
How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA​now device edl mode only

mhammadleo said:
i got china version i flash this :
How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA​now device edl mode only
Click to expand...
Click to collapse
Hello I think this should help you. You just have to make sure that your device is recognized by the adb and fastboot tools with the command "fastboot devices" and then run the file "flash-all_slotb.bat" as administrator.
I want to clarify that this is a supposed compilation for the oneplus 9 to which I replaced the files that it flashes with those of the official rom of the normal oneplus 9 that is on the official page of oneplus.
Fastboot OOS_11.2.7.7.LE25BA.rar
drive.google.com

Same .. Can someone please provide us with the chinese MSMTool

Extract Files - TeraBox
Please enter the password to extract your files.
www.terabox.com
Password: cn1d

MSM Tool for OnePlus 9 2110 Chinese variant.
Hi, my phone is currently bricked and in a bootloop. My MSM tools have no problems recognizing op9, but all of them give me a "device not match image" error, I'm using Lite Firehose option, because I can't stop my phone from constantly rebooting...
forum.xda-developers.com

The System Has Been Destroyed

So I tried to install TWRP from this website
Download And Install TWRP on Xiaomi Poco X3 NFC - FlashXiaomi
Download And Install TWRP on Xiaomi Poco X3 NFC allows facilitates the use of custom software, including the latest custom ROMs, kernels...
flashxiaomi.com
& stupidly me replaced the twrp file with "twrp-3.4.0-15-surya-mauronofrio" then finished the following instruction( I think the twrp won't match with vbmeta.img stuff like that) after that my phone stuck on logo and try to turn off & on it say Destroyed like the title. pls Help me

Hello. When trying to boot, try to catch fastboot, it should come in. I also had one and I could do it fastboot + miflash.

rambo1155 said:
Hello. When trying to boot, try to catch fastboot, it should come in. I also had one and I could do it fastboot + miflash.
Click to expand...
Click to collapse
yeah I'm to confident using CMD, that more safe & likely work with Mi Tool. ty anyway

I had similiar situation and all I did was I flashed different version of TWRP and it worked.