Database Develop

Mi FastBoot Unbrick Tool 2.0

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tool
* before flashing/using it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is this tool?
After getting so many errors while using MiFlash Tool, I decided to find a simple but an effective way for flashing the rom without any errors.After many attempt i was able to finad a perfect solution for it.
**********************************************************************
The main cause of getting bootloop is relocking of the bootloader
**********************************************************************
This tool was created as a result of it. Hope this will help all others who are facing this issue..
Features of this Tool
Small in size nearly 3 mb
No need of edl,Works with fastboot mode
Chance of failure is 1% or below
Downloads
Requirements
Java Installed In PC. Get java form here
ADB drivers installed..Get it from here
Pda Net (optional)..Get it from here
Bootloader Unlocked
Get Fastboot rom from here
What are the problems ocuured whenusing MiFlashTool??
The main errors i faced with Mi FlashTool Are:-
Unspecified error(0x80004005
Not enough Memory
Error while receiving halo Packet
And many other errors i havent noticed or didnt cared
What/How this tool works?
-So after bricking my phone many time (nor even able to enter Recovery Mode) and many unsuccessfull flash using MiFlashTool i looked into the Fastboot rom files and Got an idea about how the Flashing process works.
-All you need is fastboot to unbrick the phone. No edl or no other things to flash the rom.
- For almost every Mi Phone , unbricking will be same as mentioned in Manual Method(This tool is designed for RN3).If i get testers will think about doing for other models also.
- I used the RN3 rom from here
***************************************************************
(only use if you replace the Unlocked Bootloader file)
***************************************************************
-First Things first
Run cmd ad administrator and run the following command one by one
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
3. Reboot your system.
-Download the file from the attachment and extract it in the images folder of the fastboot rom.The folder will have many files like boot,cache,cust etc..
-Once extracted the software copy and paste the unlocked bootloader file in the images folder and overwrite any existing file.
-Now run the software and follow the instructions (its very noob friendly,I think there will be no more need for detailed tutorial):good:
- Once the flashing Process is completed your phone will be good to go
Not Working ?? Try Manually
- Go to Images Folder of the fastboot rom and holding shift key right click to Open Command Window Here. :good:
- Once you entered the cmd and execute the command individually as shown below.
Code:
fastboot flash tz tz.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash tzbak tz.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hypbak hyp.mbn
fastboot erase boot
fastboot flash modem NON-HLOS.bin
fastboot –S 512M flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash sec sec.dat
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase DDR
fastboot flash cust cust.img
Once thats done your phone will be ready to go.
If you replaced the unlocked bootloader file you may get continuous reboot. If you face something like that simply type the following command(After doing above process only)
Code:
fastboot oem unlock-go
Your Phone will reboot. If it Didnt Reboot Type this code to reboot
Code:
fastboot reboot
Once the above steps are done your phone will be back in action :good:
It will reboot system, and wait for your device to boot accordingly, no worries it will listen to your prayers to unbrick. :silly:
Enjoy
DISCLAIMER: DO ON YOUR OWN RISK. Flashing can potentially bricked or bootloop your device.
F.A.Q
1.Developer it dosent worked for me!!
Ans:- Use manual method
2.Software not opening?
Ans:- Install Java from above link.
3.I have a suggestion
Ans:- Use Contact me Option in the Software. Will reply as soon as possible
4.Iam willing to be a tester
Ans:- PM me
5. How can i help further?
A. Consider donation and pm me if interested.
Payapl:- here
Paytm:- here
XDA:DevDB Information
Mi FastBoot Unbrick Tool, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
adithyan25, pknow
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2017-01-15
Created 2017-01-15
Last Updated 2017-01-15

Reserved

screenshot? this can unlock bootloader? and where is the link download??

zilan said:
screenshot? this can unlock bootloader? and where is the link download??
Click to expand...
Click to collapse
So fast final edit going on

reserved

I have a question, How can you use fastboot mode when the device's bootloader is locked? Because fastboot will work only if the bootloader is unlocked, so if it's locked then you will get a message showing "remote device locked".

Raaj52 said:
I have a question, How can you use fastboot mode when the device's bootloader is locked? Because fastboot will work only if the bootloader is unlocked, so if it's locked then you will get a message showing "remote device locked".
Click to expand...
Click to collapse
In my knoledge it gets locked while messing with unknown things.
Read Op i mentioned we need unlocked bootloader.

Two questions-
1-does it matter if bootloader is unofficially unlocked.
2- does this work only for rn3 Kenzo? Would it work for other mi models?
Edit: other rn3 models not mi as incorrectly written. OP mentions it is for rn3 only

adithyan25 said:
In my knoledge it gets locked while messing with unknown things.
Read Op i mentioned we need unlocked bootloader.
Click to expand...
Click to collapse
I read that, what I am asking is when a device gets bricked and bootloader gets relocked how can you say this tool can unbrick that device? So this tool is not meant for unbricking devices in which bootloader is locked.
Please don't think I am discouraging you! I am giving you a more clear picture.

Raaj52 said:
I read that, what I am asking is when a device gets bricked and bootloader gets relocked how can you say this tool can unbrick that device? So this tool is not meant for unbricking devices in which bootloader is locked.
Please don't think I am discouraging you! I am giving you a more clear picture.
Click to expand...
Click to collapse
Yeah...I got it..I wrote another thread on unbricking the tool if boot loader is locked... This thread is for whom those who are stuck at bootloop or mi logo after they try messing up with unknown things...including me...
Peace

anshude1 said:
Two questions-
1-does it matter if bootloader is unofficially unlocked.
2- does this work only for rn3 Kenzo? Would it work for other mi models?
Edit: other rn3 models not mi as incorrectly written. OP mentions it is for rn3 only
Click to expand...
Click to collapse
Nope mine unofficially unlocked worked charm...
And I'm using kenzo..and this tool only designed for kenzo...but manual method is same for all devices

adithyan25 said:
Yeah...I got it..I wrote another thread on unbricking the tool if boot loader is locked... This thread is for whom those who are stuck at bootloop or mi logo after they try messing up with unknown things...including me...
Peace
Click to expand...
Click to collapse
Hey bro, I am trying to help you! Check your PM

Raaj52 said:
Hey bro, I am trying to help you! Check your PM
Click to expand...
Click to collapse
Peace ...
(Y) replied

HELP ME
I want to contact you can you give your mail
i m using redmi note 2 2014818 model
every rom cause bootloop even mi rom too
help me pls its mine dad phone
help

THEPAINCOMES said:
I want to contact you can you give your mail
i m using redmi note 2 2014818 model
every rom cause bootloop even mi rom too
help me pls its mine dad phone
help
Click to expand...
Click to collapse
Wrong section to ask... Download your phones stock ROM from miui website.delete bootloadet file and flash it using miflash tool.
Phone will be back to life again...pm me if u have any doubts

I was using this method for my old redmi 3 and its work well to unbrick in any condition (except hardware failure) and now its available for redmi note 3 pro! The different is I was using CMD manually LOL
Sent from my kenzo using XDA Labs

Please need help! I used regional ROM with TWRP at unlocked divece. After rom update i get NVram fail and "no sim" note. I try to recovery nvram from TWRP but it give me fail notification. Then I restore IMEI and MAC with MauiMeta utilites, flash oficial china rom (and lock preloader) - it's not fixed, same "no sim" . There is life device, IMEI, MAC, modem version - all here, but still "no sim". If i make emergency call - it's works. What can i do more?

maxnah said:
Please need help! I used regional ROM with TWRP at unlocked divece. After rom update i get NVram fail and "no sim" note. I try to recovery nvram from TWRP but it give me fail notification. Then I restore IMEI and MAC with MauiMeta utilites, flash oficial china rom (and lock preloader) - it's not fixed, same "no sim" . There is life device, IMEI, MAC, modem version - all here, but still "no sim". If i make emergency call - it's works. What can i do more?
Click to expand...
Click to collapse
Double Check first which device u have . kenzo or kate ?
Dont flash kenzo rom on kate or vice versa.
Kenzo is redmi note 3 pro . size is 15 cm
Kate is redmi note 3 special edition. Size is 15.2 cm.

You can flash kenzo rom on kate (and kate on kenzo). It's same. You cannot flash kenzo firmware on kate (and cannot flash kate firmware on kenzo) !!!
Odoslané z Redmi Note 3 pomocou Tapatalku

Black_Stark said:
Double Check first which device u have . kenzo or kate ?
Dont flash kenzo rom on kate or vice versa.
Kenzo is redmi note 3 pro . size is 15 cm
Kate is redmi note 3 special edition. Size is 15.2 cm.
Click to expand...
Click to collapse
sorry, wrong post - hennesy (MTK)

Brick my MI A2

After much thinking, I decided to root my new phone, but things did not go well. I unlocked the bootloader and everything went well, but at the time of installing twrp everything went to hell. Now I try to install the official ROM via miFlash and via Fastboot but I always get errors.
In myFlash tool I get: error: FAILED (remote: GetVar Variable not Found)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fastboot I get: sending system_a
FAILED
"Flash system_a error".
I have bootloop and I can not turn off the device. Can somebody help me?

https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188

minnuss said:
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
Click to expand...
Click to collapse
Hi, I followed the steps but I can't flash system. I got the same error: "Flash system_a error" in "a" and in "b" FAILED (remote: GetVar Variable not Found)

Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Yes something strange with the latest fastboot rom. I could flash it but tried a LOT.

use ./fastboot flashing unlock_critical

Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.

djmitza222 said:
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
Click to expand...
Click to collapse
I tried, flash some images well, but in boot.img just shows flashing but doesn´t continue. I had waiting long time.

Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.

djmitza222 said:
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
Click to expand...
Click to collapse
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Doesn't work! :/ i got the same error in slot a and b. I tried flash handly, but the problem continues just in system.img. other images flashed well.

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.

meltbanana said:
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
Click to expand...
Click to collapse
:crying: Seriously? your warranty was avoid?

Antolinetz said:
:crying: Seriously? your warranty was avoid?
Click to expand...
Click to collapse
after 2 hours playing with that faulty phone I clearly decided not to open it and sent it back. I suspect there's hardware (RAM?) issues with some Mi A2 devices. as I wrote I wasn't even able to load a kernel. it did weird things and gave me strange fastboot feedback. atm I'll stick with tissot but I'm unsure about xiaomi's latest smartphones .

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
same occured with me. Try this:
./fastboot flash system_a system.img
./fastboot flash system_b system.img

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
download the 1.0.2 version, it has an unbrick option that takes care of most softbricks
YOU MUST RUN the unlock oem unlock, flashing, and unlock flashing_critical options (options 1 2 and 3) before trying the unbrick option. If the unbrick option does not work, try the revert to stock option.
For any others getting in a bootloop from TWRP, download the 1.0.1 version and run the Launch TWRP option it will overwrite the boot.img to a usable one. TWRP is really buggy right now so FOLLOW THE INSTRUCTIONS.
And for those who have a bootloop because they tried to install xposed, run the revert to stock option. Unfortunately ATM there is no way to keep your data unless you put the https://magiskroot.net/uninstall-magisk-module-twrp/ zip on your device.

Hi guys, finally whith EDL mode, after hours and hours flashed well!
fastboot oem edl
or
fastboot-edl-v2
I have reviewed each .img file and I also found that apparently the system.img file was not decompressed correctly. Then I went to the always reliable Total commander and was decompressed fine.
Thank you all!

people try:
1- Another usb port
2- Another usb cable
3- Another PC

I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs

woofwoof75 said:
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
but how?

[SOLVED] Mi 9 stuck on Bootloop, no recovery

So I'm pretty much a noob when it comes to flashing custom ROM's and such stuff, and always follow written tutorials where available.
Yesterday I managed to flash Revolution OS to my Mi 9 (with unlocked Bootloader) and using Twrp it worked perfectly.
Now today I tried to reset the device due to some Issues, and I must've accidentally deleted the ROM itself somehow, because now the phone just Bootloops all the time.
Recovery is not accessible, or I'm unsure if there is even a recovery still on it, but I can access fastboot.
I tried different commands like flashing ROM to the device via Fastboot or Mi Flash tool, but it either fails with unknown error or it doesn't progress the command.
So I wanted to ask, if there is any hope for my Mi 9 or if I just made a expensive mistake.
Any answers, tips and possible solutions are appreciated, thank you!

Goatfreak99 said:
So I'm pretty much a noob when it comes to flashing custom ROM's and such stuff, and always follow written tutorials where available.
Yesterday I managed to flash Revolution OS to my Mi 9 (with unlocked Bootloader) and using Twrp it worked perfectly.
Now today I tried to reset the device due to some Issues, and I must've accidentally deleted the ROM itself somehow, because now the phone just Bootloops all the time.
Recovery is not accessible, or I'm unsure if there is even a recovery still on it, but I can access fastboot.
I tried different commands like flashing ROM to the device via Fastboot or Mi Flash tool, but it either fails with unknown error or it doesn't progress the command.
So I wanted to ask, if there is any hope for my Mi 9 or if I just made a expensive mistake.
Any answers, tips and possible solutions are appreciated, thank you!
Click to expand...
Click to collapse
Did you've tried to flash system (download an unzip your first miui rom e.g. Global, eu...) and twrp via adb?
For me it was fine in a same situation.

You can download the fastboot ROM from xiaomi side, extract following from tgz file
-boot
-recovery
-vendor
-system
And flash it manually via fastboot. Welcome back to Miui world....

Laptapper said:
Did you've tried to flash system (download an unzip your first miui rom e.g. Global, eu...) and twrp via adb?
For me it was fine in a same situation.
Click to expand...
Click to collapse
Hey thank you very much for your reply.
I was able to flash TWRP via Fastboot but when entering the command fastboot boot recovery.img it still bootlooped again and I still couldn't acess Recovery through button combination.
Is there anything I might be doing wrong or so?

The only option you have now is to flash the full rom via fastboot

gogoffm said:
You can download the fastboot ROM from xiaomi side, extract following from tgz file
-boot
-recovery
-vendor
-system
And flash it manually via fastboot. Welcome back to Miui world....
Click to expand...
Click to collapse
Just spend the last couple hours following your advice, but I still get abootloop and no recovery option on the phone itself.
Flashing all the parts worked but it seems like it's not really applying them?
I used the stock cepherus ROM

Puhh, then I am really don't know. This method always worked for me. Can you make a sc of the fastboot commands you are using to flash the files ?

Goatfreak99 said:
Just spend the last couple hours following your advice, but I still get abootloop and no recovery option on the phone itself.
Flashing all the parts worked but it seems like it's not really applying them?
I used the stock cepherus ROM
Click to expand...
Click to collapse
And which twrp?

- Download XiaomiADBFastbootTools.
- Connect through Fastboot
- Download a stable official rom via the program
- Flash the Rom via the program
- Voila, you're back on stock

Laptapper said:
And which twrp?
Click to expand...
Click to collapse
for TWRP I use Twrp_3.3.0_Cepheus.

KaiseRRUby said:
- Download XiaomiADBFastbootTools.
- Connect through Fastboot
- Download a stable official rom via the program
- Flash the Rom via the program
- Voila, you're back on stock
Click to expand...
Click to collapse
Thank you for the reply, I've downloaded that program and aam currently tring to flash the official global developer ROM with it.
Last log however is :
C:\Users\\xaft_tmp>fastboot getvar product 2>&1 | findstr /r /c:"^product: *cepheus" || echo Missmatching image and device
Is that supposed to be like that, or do I need a different ROM?
I have the Mi 9 Global Version if that's of use

C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>set CURRENT_ANTI_VER=1
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>(set version=1 )
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>if [1] EQU [] set version=0
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>set anticheck="antirollback check pass"
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot getvar product 2>&1 | findstr /r /c:"^product: *cepheus" || echo Missmatching image and device
Missmatching image and device
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot getvar product 2>&1 | findstr /r /c:"^product: *cepheus" || exit /B 1
product: cepheus
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot erase boot ||
Erasing 'boot' OKAY [ 0.008s]
Finished. Total time: 0.040s
C:\Users\Win8Pro.GAMINGPC.000\xaft_tmp>fastboot flash crclist C:\Users\Win8Pro.GAMINGPC.000\Documents\cepheus_global_images_9.5.30_20190530.0000.00_9.0_global\images\crclist.txt ||
Sending 'crclist' (0 KB) OKAY [ 0.012s]
Writing 'crclist' FAILED (remote: 'update crc list failed')
fastboot: error: Command failed
"Flash crclist error"
Done!
this was the last log after it failed

Try using MiFlashPro tool. You can download the rom directly from the app. I had this issue before and that is the only way I fixed it. Make sure you download the rom that is labeled as fastboot.

Goatfreak99 said:
for TWRP I use Twrp_3.3.0_Cepheus.
Click to expand...
Click to collapse
For me this one
https://forum.xda-developers.com/Mi-9/how-to/recovery-unofficial-twrp-recovery-3-2-3-t3912118
Was working with the system flash to start twrp.
Also I've found in this twrp more usefull options and also more partitions of the phone could be backup.
I'm now on v17 but I've didn't got the link right now.
But don't reboot after flashing twrp and system with adb command, use instead the hardware keys to boot in twrp.
If you've got a backup then you can restore it, may be you've got to flash then also magisk again.
This was the way which was working for me.

Laptapper said:
For me this one
https://forum.xda-developers.com/Mi-9/how-to/recovery-unofficial-twrp-recovery-3-2-3-t3912118
Was working with the system flash to start twrp.
Also I've found in this twrp more usefull options and also more partitions of the phone could be backup.
I'm now on v17 but I've didn't got the link right now.
But don't reboot after flashing twrp and system with adb command, use instead the hardware keys to boot in twrp.
If you've got a backup then you can restore it, may be you've got to flash then also magisk again.
This was the way which was working for me.
Click to expand...
Click to collapse
You Sir,are a true legend.
I was immediatly able to flash that TWRP onto my Mi 9 and from there I could flash the stock ROm.
Thank you very, very much!
I already was afraid of bricking my 450 $ purchase but thanks to you it is back up and running again ^^

Goatfreak99 said:
You Sir,are a true legend.
I was immediatly able to flash that TWRP onto my Mi 9 and from there I could flash the stock ROm.
Thank you very, very much!
I already was afraid of bricking my 450 $ purchase but thanks to you it is back up and running again ^^
Click to expand...
Click to collapse
Well done bro, you've flashed it and it's your work.
I don't know why the others mostly don't use this twrp.

Goatfreak99 said:
You Sir,are a true legend.
I was immediatly able to flash that TWRP onto my Mi 9 and from there I could flash the stock ROm.
Thank you very, very much!
I already was afraid of bricking my 450 $ purchase but thanks to you it is back up and running again ^^
Click to expand...
Click to collapse
I tried flashing that TWRP. But once I boot to recovery, it still goes back to fastboot.

RebornCheiko said:
I tried flashing that TWRP. But once I boot to recovery, it still goes back to fastboot.
Click to expand...
Click to collapse
when you flashed TWRP using fastboot, dont using reboot recovery command but use key combo, volume up/power.
in that way recovery sticks

marcel112 said:
when you flashed TWRP using fastboot, dont using reboot recovery command but use key combo, volume up/power.
in that way recovery sticks
Click to expand...
Click to collapse
It still doesn't work.
I have no choice but to flash the stock ROM using MiFlash Tool, thankfully it worked.

Bricked Mi 9 Lite
Hello. I know this may not be the right topic for which I am sorry. I need your help!
At night my mother's phone caught a bootloop (MI 9 Lite) This is a factory phone used for a month. I was looking for ways to solve the problem. The phone sticks to the MI logo and restart. MI flash sees the phone but there is an error during flash. The program sees the device but does not want flash. I have no idea how to solve the problem. Please help.
Regards
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ps.
If you have links to programs / drivers that can be useful for phone repair. I will be very grateful.

Unlocked but TWRP not possilbe Mi 9T Pro

I unlocke my Mi9T Pro (global) and tried to flash twrp, but for whatever reason I never managed to boot it
Now i can just get into fastboot
everything else no longer possible,
any ideas how I can get boot android again

I tried different twrp
with
fastboot flash recovery twrpXY
also
fastboot boot twrpXY
doesn't work
and yes it's a Raphael

You need to fastboot flash your stock ROM using Mi Flash tool.
Then you should be able to boot into system again.

P12AV33N said:
You need to fastboot flash your stock ROM using Mi Flash tool.
Click to expand...
Click to collapse
Flash not successful, doesn't really start to flash
stops at this line:
info:$for /F "tokens=2 delims=: " %i in ('fastboot -s XXXXXXXX getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )

dna99 said:
Flash not successful, doesn't really start
stops at this line:
info:$for /F "tokens=2 delims=: " %i in ('fastboot -s XXXXXXXX getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
Click to expand...
Click to collapse
Try flashing the latest global stable ROM
Seems like an issue related with Anti Roll Back feature implemented by Xiaomi.
The ROM you are flashing has lower ARB version i.e. 1
while the ROM you currently have installed has version 2
(Reboot device into fasboot mode, connect to pc, open command prompt and type "fastboot getvar anti" (without quotes) and check the ARB version)
Then download the ROM which has higher or same ARB version as your device.
Now the Question is, how will you find a ROM with same or higher ARB version?
and the answer is, I don't know.
btw if you tried flashing this ROM via twrp recovery, you would've ended up hard bricking your device.
It's good that Mi Flash gave you this error.
Edit : I'm assuming all this based on what's written in the error.
you have to make sure yourself by checking the ARB version using CMD in your PC.

P12AV33N said:
Try flashing the latest global stable ROM
(Reboot device into fasboot mode, connect to pc, open command prompt and type "fastboot getvar anti" (without quotes) and check the ARB version)
Then download the ROM which has higher or same ARB version as your device.
Click to expand...
Click to collapse
mhhh:
fastboot getvar anti
anti: 1
finished. total time: 0.003s
----
as I failed installing twrp, i tried to install the stable rom again and try it again.

dna99 said:
mhhh:
fastboot getvar anti
anti: 1
finished. total time: 0.003s
----
as I failed installing twrp, i tried to install the stable rom again and try it again.
Click to expand...
Click to collapse
type "fastboot oem device-info" in cmd and let me know.

i just happen to notice that ther is no stable version of raphael..... for fastboot...

fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
finished. total time: 0.012s

dna99 said:
i just happen to notice that ther is no stable version of raphael..... for fastboot...
Click to expand...
Click to collapse
http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
flash this.

does it also work for global, as this is the indian version

is there a step by step how to for installing twrp on the mi9t pro

I just read this, is this still a problem:
https://forum.xda-developers.com/showpost.php?p=77560732&postcount=22
as I also have a Ryzen
-----
although unlocking the bootloader worked

err:target reported max download size of 805306368 bytes
err:sending 'modem' (164428 KB)...
err:FAILED (data transfer failure (Unknown error))
err:finished. total time: 5.407s
info:"Flash modem error"
error:FAILED (data transfer failure (Unknown error))
process exit.
flashSuccess False
isFactory False CheckCPUID False
before:flashSuccess is False set IsUpdate:True set IsDone True
after:flashSuccess is False set IsUpdate:false set IsDone true

But at least it finally started

dna99 said:
But at least it finally started
Click to expand...
Click to collapse
Flashing started?
---------- Post added at 11:48 AM ---------- Previous post was at 11:48 AM ----------
dna99 said:
I just read this, is this still a problem:
https://forum.xda-developers.com/showpost.php?p=77560732&postcount=22
as I also have a Ryzen
-----
although unlocking the bootloader worked
Click to expand...
Click to collapse
Nah, I have ryzen as well but everything works fine.

P12AV33N said:
Flashing started?
Click to expand...
Click to collapse
I mean, at least it got way further in the procedure
it didn't start flashing the system

dna99 said:
I mean, at least it got way further in the procedure
it didn't start
Click to expand...
Click to collapse
Do let me know when you get the device working again.

I could just enter TWRP again
@ P12av33N
Any Ideas how i can make it stay fixed in recovery?

dna99 said:
I could just enter TWRP again
@ P12av33N
Any Ideas how i can make it stay fixed in recovery?
Click to expand...
Click to collapse
Flash magisk

⋆ [DISCONTINUED][ROOT]-Realme_6_[UPDATED][B61][LATEST] ⋆

TRY ALL At Your Risk
[To root Realme 6 you need to unlock bootloader first. After unlock bootloader just follow the method.
I am not responsible for any kind of stuck or bootloop issue or hard brick.. This file was tested in my own device Realme 6 RMX2001
###############
svetiusFirst Enable OEM UNLOCKING and USB DEBUGGING on Developer Options)
##HIT THANKS BUTTON##
### WARNING###
*DON'T UPDATE THE SOFTWARE OF YOUR DEVICE IN ROOT *
[Realme 6 - Root]
0. For unlocking bootloader type
? fastboot flashing unlock
1. Download realme6_root.zip
2. Enter fastboot mode using deeptesting_apk
3. Type ? fastboot flashing unlock in ADB
4. Select yes on your device to unlock bootloader
5. Type ? fastboot reboot
6. In your device turn on usb debugging
7. Type ? adb reboot bootloader
8. Recovery would boot into fastboot mode ( i.e you would boot into fastboot mode with recovery mode UI)
9. Type ? fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Type ? fastboot flash boot boot.img
##################
? Note:
Download Link- https://drive.google.com/file/d/1--U0QfVZpNmOI9v7mA6ZsSghw42NBykv/view?usp=drivesdk
-(NEW UPDATED) Deep Test- Apk- https://drive.google.com/file/d/10Uy34zbKhic89zGRhgJwAfGCeXTCMR4C/view?usp=drivesdk
#########################
# WARNING. #
########################
*Don't Use Old Boot IMG and Vbmeta IMG In ( Update)
Here Is New Boot.img And New Vbmeta Img (B61)
Boot- HERE- https://drive.google.com/file/d/11X4n0E1dI0XspumNmELMs7Nxt1WiE4ZX/view?usp=drivesdk
Vbmata- https://drive.google.com/file/d/18AUHwdBRrUL6L6NeHnWENXWGhoyYzzgZ/view?usp=drivesdk
▫ Do it your own risk, We are not responsible if anything goes wrong
▫ Unlock bootloader will erase all your internal storage, So take backup as well
~Credits: arvaaz
NEW APK WORKING
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hit Thanks Button For More Updates

Someone Sent Me This SS Try And Feedback

arvaaz said:
TRY ALL At Your Risk
[Realme 6 - Root]
0. For unlocking bootloader type
? fastboot flashing unlock
1. Download realme6_root.zip
2. Enter fastboot mode using deeptesting_apk
3. Type ? fastboot flashing unlock in ADB
4. Select yes on your device to unlock bootloader
5. Type ? fastboot reboot
6. In your device turn on usb debugging
7. Type ? adb reboot bootloader
8. Recovery would boot into fastboot mode ( i.e you would boot into fastboot mode with recovery mode UI)
9. Type ? fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Type ? fastboot flash boot boot.img
? Note:
Do it your own risk, We are not responsible if anything goes wrong
Unlock bootloader will erase all your internal storage, So take backup as well
~Credits: mekarmur
Click to expand...
Click to collapse
Where is the file? 404 not found.

RantiHasan said:
Where is the file? 404 not found.
Click to expand...
Click to collapse
Here

arvaaz said:
Here
Click to expand...
Click to collapse
The file is removed or deleted.. Try upload a new link

RantiHasan said:
The file is removed or deleted.. Try upload a new link
Click to expand...
Click to collapse
https://drive.google.com/file/d/1--U0QfVZpNmOI9v7mA6ZsSghw42NBykv/view?usp=drivesdk

arvaaz said:
https://drive.google.com/file/d/1--U0QfVZpNmOI9v7mA6ZsSghw42NBykv/view?usp=drivesdk
Click to expand...
Click to collapse
Just flash it.. Using adb and fastboot cmd.
But now what? Its not booting into any custom recover or any superSu or magisk hasn’t install..
Whats the next step

"Failed to submit application
This phone model does not support in-depth test" writing.
Could it be wrong model app?

RantiHasan said:
Just flash it.. Using adb and fastboot cmd.
But now what? Its not booting into any custom recover or any superSu or magisk hasn’t install..
Whats the next step
Click to expand...
Click to collapse
Flash stock Rom

arvaaz said:
Flash stock Rom
Click to expand...
Click to collapse
I dont know wht r u talking about... Your title is to root realme 6. What should i do after flashing boot.img to root rm6

arvaaz said:
TRY ALL At Your Risk
[Realme 6 - Root]
Bro its work.. Thanks.. But I rewrite the step and please add a litte line with magisk install.
To root Realme 6 you need to unlock bootloader first. After unlock bootloader just follow the method.
I am not responsible for any kind of stuck or bootloop issue or hard brick.. This file was tested in my own device Realme 6 RMX2001
1. Download the flash.zip file below. Extract it and open cmd from the extracted folder
2. In your device turn on usb debugging
3. Type 'adb reboot bootloader'
4. Recovery would boot into fastboot mode
5 Type 'fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img'
6. Type 'fastboot flash boot boot.img'
7. Now reboot your device and install magisk_manager from the link below..
8. Now open magisk and a zip file was promote to install. Accept it. Your device will reboot and you are done.
9. You can check root via root checker app
10. Enjoy
Click to expand...
Click to collapse

My phone doesn't go into bootloader mode. Fastboot_unlock_verify fail writing and exiting mode. What should I do?

RantiHasan said:
arvaaz said:
TRY ALL At Your Risk
[Realme 6 - Root]
Bro its work.. Thanks.. But I rewrite the step and please add a litte line with magisk install.
To root Realme 6 you need to unlock bootloader first. After unlock bootloader just follow the method.
I am not responsible for any kind of stuck or bootloop issue or hard brick.. This file was tested in my own device Realme 6 RMX2001
1. Download the flash.zip file below. Extract it and open cmd from the extracted folder
2. In your device turn on usb debugging
3. Type 'adb reboot bootloader'
4. Recovery would boot into fastboot mode
5 Type 'fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img'
6. Type 'fastboot flash boot boot.img'
7. Now reboot your device and install magisk_manager from the link below..
8. Now open magisk and a zip file was promote to install. Accept it. Your device will reboot and you are done.
9. You can check root via root checker app
10. Enjoy
Click to expand...
Click to collapse
Thanks
Click to expand...
Click to collapse

mercan01 said:
My phone doesn't go into bootloader mode. Fastboot_unlock_verify fail writing and exiting mode. What should I do?
Click to expand...
Click to collapse
Use fastboot cmd

@arvazzz
Is your phone indian or else?

arvaaz said:
Use fastboot cmd
Click to expand...
Click to collapse
In what mode?

abudabi said:
@arvazzz
Is your phone indian or else?
Click to expand...
Click to collapse
Indian

mercan01 said:
In what mode?
Click to expand...
Click to collapse
Read instructions carefully

Read instructions carefully
Click to expand...
Click to collapse
I read the instruction many times
---------- Post added at 11:32 AM ---------- Previous post was at 11:21 AM ----------
First Enabled OEM UNLOCKING and USB DEBUGGING on Developer Options (usb debugging allowed)
second fastboot flashing unlock
<waiting for any device>???