I had experienced below :
- Try to flash MI5 (with unlocked bootloader) with MiFlash (latest version) (Power battery at ~28%)
- It is hang at "system.img" over 20 mins, and unplug, become "bricked" (this bricked is just start up at mi logo, able to boot into recovery & fastboot mode)
- After installing "minimal adb & fastboot tools", some command, make it into "OEM EDL" mode and flash again using MiFlash (another version from some tutorial)
- Suddenly, fastboot mode screen is off, the power is out (I guess)
- Only see "qualcomm hs-usb qdloader 9008 (COM10)" in device manager (before running into "EDL" mode, it is shown as something Android Phone Interface, not named "MI interface", but it is Phone interface, not COM PORT
- At the stage, it is another "bricked", unable to boot into recovery and fastboot mode, no response on all button combination, plug device with USB to PC, only can see "qualcomm hs-usb qdloader 9008 (COM10)" is detected
- In MiFlash, it can detect also (Device as "COM10"), by all type of flashing ("Flash all" , "Flash all except storage"...), status always shown as "Missed hello packets, try to recover", but the time is still counting, whatever I tried many method
- It has been over 6 hours for this (~28% power), finally the window give detected device and undetected device in 3-5 sec back and fore.
- I give up to flash, try to charge the MI5 with to power pack (~4-5 hours)
- I wake up, and try to flash, it is success
By Conclusion, some points figure out
- Turn device into EDL mode will turn device detected as "COM" device, it means EDL mode is "COM" device while FASTBOOT mode is "Interface" device
- With tried many MiFlash version, some version detect device when it is "COM" device, some detect it when it is "ADB" or USB driver device
(Finally, it is succeed using "COM" device)
- "Bricked" device, it is not actual bricked, but just situation, my situation look like "bricked" are summaried as 3 :
1. keep start up at "MI" logo on boot (caused by flash failure), OS corrupted : this can be solved by correctly flashing rom
2. all has no response (when in EDL mode) : this is just an status of EDL mode, no need to solve, just continue your action
3. Out of Power : this cause nothing to do, just plug your USB to power to charge
Summaried Actual Step to Flash
(I had success 2 rom on CHINA DEV ROM & GLOBAL ROM) :
Preparation
1. Download OS Rom for fastboot from http://en.miui.com/a-234.html
2. Install Mi Flash (e.g. version "Miflash_tool_gemini_20160401.exe")
Download from https://www.androidfilehost.com/?fid=24521665358595574
* this version need switch device into OEM EDL mode
3. Install minimal adb & fastboot tools (minimal_adb_fastboot_v1.4_setup)
Download from https://www.androidfilehost.com/?fid=24521665358595410
4. Unlock Device
a. Submit request from Xiaomi (en.miui.com/unlock)
b. Recevie SMS notification unlock permission is ready
c. Go to en.miui.com/unlock to download the "unlock" tools
c. Login MI account on device (check if the device is on this list of MI account OR check i.mi.com)
e. Run downloaded "unlock" tools (MiFlashUnlock.exe), follow the instruction
Flashing
1. Boot device into fastboot mode (press "voulmn -" + "power" button), and connect device with USB cable
2. Open command console, go to installed minimal adb & fastboot tools folder (e.g. "C:\Program Files (x86)\Minimal ADB and Fastboot)
3. Check if device connected in fastboot ready by command "fastboot devices"
4. Switch fastboot mode to OEM emergency download mode (EDL) by command "fastboot oem edl"
5. Open MiFlash,
a. browse the downloaded rom
b. click "Refresh" button to load connected mobile device
c. select "Flash all"
d. click "Flash" to start flashing rom
6. Waiting to complete (~150s my experience from both China dev ROM & Global ROM)
7. Reboot
----------------------------------------------------------
Finally, I had questioned are:
1. why some tutorial mentioned (not to mention) change to EDL is need, they can flash success
2. why the latest MiFlash on (http://en.miui.com/a-234.html) is not work, it cannot detect device (whatever it is COM(EDL mode) or Interface(fastboot mode))
3. Look like there are 2 version of MiFlash,
a. one type, its installation is packed with "Google ADB and driver, Qualcomm USB serial driver, Xiaomi MiFlash program..."
Folder named "MiPhone" in "Program Files" folder
b. one type, its only contains MiFlash program, folder named "XiaoMi", and its interface language is S.Chinese for me
4. Is it an must to flash in EDL mode?
If anyone had idea of above, please advise
This is the only unbrick method that worked for me - This one should be added to the index thread. The two listed there did not work.
I have the same issue, the method above doesn't help, adb can't see the phone. That's a problem. A computer, device manager doesn,t see the phone, a plug charger as well. I've tried many many times to switch on, after 1000 times it is started
Than I flashed a leastest rom, and ina new rom touch screen doesn't work. So I - stupid - flashed one before. That looked fine, but after work xposed installed it happened again
It happened me with
miui_MI5Global_V8.0.5.0.MAAMIDG_026a414948_6.0.zip (touch screen)
and
miui_MI5Global_V8.1.2.0.MAAMIDI_9fbec19bb6_6.0.zip (bricked)
In both roms I instaled xposed-v85-sdk23-arm64-MIUI-edition-by-SolarWarez-20160609.zip
I've got a feeleing the leastest roms are not comaptible with xposed v.85
work for me too
it s really work for me too but i flashed rom after my phone is not opening.
if i try to charge charging led is working but i can not start phone.
can you help me
I can get into fastboot, but I can't boot directly to custom recovery unless I connect to my laptop and run toolkit. Any ideas?
Quick boot from the play store is working fine on my Nexus 6.
DON'T.
USE.
TOOLKITS!
Download and install Minimal ADB and Fastboot. Downloaded latest TWRP for Nexus 6 (twrp-3.0.3-0-shamu.img at this time of writing). Enabled adb debugging if you haven't already on your Nexus 6 developer options. Put the twrp you downloaded in the same folder as your minimal adb and fastboot. Go to that folder and open cmd-here (this opens a command prompt window in that directory). Type adb devices to verify it sees your phone connected. Type adb reboot-bootloader to reboot into bootloader mode. Type fastboot flash recovery twrp-3.0.3-0-shamu.img . Now try to boot into recovery and it should work.
Hi,
I ask for help
After attempting to install xpose on the miuI 10 mi5 and restart, the initial logo was rotating and could not go any further.
After various crashes and tortures, I blew him all with a wipe from TRWP.
Now the situation is as follows:
- Mi PC sUIT does not see it (ask for connect your device via USB)
- PC does not see mi5, in Android Divace - Android ADB Interface (yellow triangle)yesterday everything worked, I did not touch anything on the PC.
I think that xiaomi_usb_driver are ok
- vol+,power = can run TWRP 3.2.3.0, so I wipe it all
- Vol-,power = fastboot mode chrash after 10-20 seconds and switch to the logo where it remains in the loop
- mi5 do not react on commands from PC side:fastboot devices,adb devices, fastboot flash recovery twrp.img, fastboot boot twrp.img, adb sideload miui10, etc
It was root with help TRWP,lazyflasherand MagiskManager
is there any idea how to install again miui 10?
thanks in advance
that is thit
In TWRP: Mount, Enable MTP (data, chache) conect with PC and copy/paste ROM
This version of TWRP works on the Lenovo TB-X606FA, TB-X606F and TB-X606X.
Warning: this TWRP will not work for any of the Tab M10 variants with Qualcomm SOCs. For the TB-X505F, see this thread. For the TB-X605F/L, see this thread.
Code:
#include <std_disclaimer.h>
/*
* We are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Encryption
This device was released with Android 9 using full disk encryption (FDE). But we now have Android 13 GSIs for this tablet - and Android 13 does not support FDE. Android 13 only supports file-based encryption (FBE).
If you are using a ROM/GSI that uses FBE, you must use the twrp with -fbe in the name. If you use the wrong one, twrp will not be able to decrypt the data partition.
If you don't know if you're using FBE or FDE, then run this command while Android is running: adb shell getprop ro.crypto.type. If it returns "block", then your device is FDE. If it returns "file", it's FBE.
Installation
With a stock ROM, it is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
If Windows 10/11 does not recognise your tablet in fastboot mode, then see post #2.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download the latest magisk.apk to your SDcard or OTG device. Change the filetype from "apk" to "zip".
get a copy of the vbmeta.img file from the stock ROM. It should be located in one of the subdirectories of LMSA's c:\ProgramData\LMSA\Download\RomFiles directory (after you download it using the LMSA rescue (power-off mode). This is only required the first time you flash TWRP, or the first time after you re-flash the whole stock ROM.
if your bootloader is already unlocked, go to step 5. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot flashing unlock
follow the instructions on the tablet, then reboot to Android.
note: if fastboot reports <waiting for device>, then you need to install the Mediatek USB drivers. Go to developer.android.com/studio/run/oem-usb, then find the link to Mediatek (MTK) and follow the installation instructions.
note: after unlocking, tablet will take a while to come back up - because it has to do a factory reset and encrypt data again.
flash the TWRP image:
Code:
adb reboot bootloader
fastboot flash recovery twrp_X606FA_11.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
backup the stock boot, system and vendor partitions in TWRP, if you don't have backups already
load Magisk:
In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
2023-03-27 - add TWRP 3.7.0 for FBE ROMs/GSIs (Android 13+) only
2022-02-06 - added separate download for TB-X606F
2021-12-16 - TWRP 3.6.0 updates
- support for Android 12 decryption (keymaster)
2021-07-05 - TWRP 3.5.2 updates
- corrected display of Cyrillic (and other non-ASCII characters) in file names on external drives (utf8)
2021-03-10 - TWRP 3.5.1 updates
- cherrypicked update 1995 to force splash screen to display on boot
- orientation is now landscape (for tablets)
- updated install instructions to reflect new Magisk apk (v22).
2021-02-02 - fix blank screen on boot - don't need to press power button anymore to wake screen up
2021-01-24 - TWRP 3.5.0_10-0: initial release
Downloads (FDE)
This will work with stock ROMs and most pre-A13 ROMs/GSIs.
TWRP 3.6.0_11-0 for X606FA: twrp-X606FA_11.img
TWRP 3.6.0_11-0 for X606F: twrp-X606F_11.img
Downloads (FBE)
This will not work with stock ROMs or most pre-A13 ROMs/GSIs. This is for ROMs/GSIs that use FBE to encrypt. Android 13+ only supports FBE.
TWRP 3.7.0_12-1 for X606FA with FBE encryption: twrp-X606F_12.1.fbe.img
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-12.1
https://github.com/Yahoo-Mike/recovery_device_lenovo_X606FA/tree/android-12.1-fbe
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Created 2021-01-24
Last Updated 2023-03-27 (FBE support)
Windows 10/11 does not recognise tablet in fastboot mode
If your tablet is recognised by ADB but not by fastboot in Windows, you might need to get the latest versions of fastboot and the Mediatek usb drivers.
1. use the latest fastboot version
Make sure you are using the latest version of fastboot. There were major changes to fastboot for Android 10.
If you are using PowerShell, make sure it's picking up the fastboot you expect: fastboot --version. If not, use ./fastboot from the directory with the executable.
2. update device drivers
Try the latest Mediatek (MTK) drivers from Install OEM USB drivers. When they are loaded, they appear in Device Manager as "Kedacom USB Device/Android ADB Interface".
If Windows complains that the drivers are unsigned and refuses to load them, then do this as Administrator in Windows:
bcdedit /set testsigning on
reboot Windows
install the drivers
bcdedit /set testsigning off
In Windows 11, you might also need to turn off Secure Boot in your PC's BIOS to get the bcdedit command to work.
So I have the ZA5W0097US, would you suggest this wouldn't work?
ldeveraux said:
So I have the ZA5W0097US, would you suggest this wouldn't work?
Click to expand...
Click to collapse
That looks like a TB_X606F. This TWRP might work. We won't know for sure until someone tries.
Remember, the screen will be blank when TWRP boots up. You'll just have to click the power button twice to wake it up. I'll try and fix that over the next few days.
If you decide to try this TWRP and it doesn't work, please let me know what happens. And when you're booted into Android, can you tell me what the results of these ADB commands are?
Code:
adb shell getprop ro.hardware
adb shell getprop ro.boot.hardware
New version is now available in the first post.
The blank screen issue is mostly fixed...mostly. The screen is still blank on boot when decrypting data, but then it wakes up. No need to press the power button anymore.
I just got my TB-X606F (it's actually finishing setup right now) and I'm going to try flashing this TWRP onto it. I *think* the only difference between the "F" and "FA" version is that the "FA" comes with some sort of Alexa capability.
Both adb commands output "mt8768".
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
sirp0p0 said:
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
Click to expand...
Click to collapse
Cool. I'll update the OP.
Maybe check you have the latest version of fastboot on your main machine. There were some major changes for Android 10.
Good call. My adb and fastboot were both way out of date.
I also have the TB-X606F and was able to get this working 100%. I thought it was going to wipe my system so I backed everything up beforehand, but no wipe. Just replaced recovery with TWRP and here I am. Thanks a ton, great to have another TWRP recovery device!
ldeveraux said:
... I thought it was going to wipe my system so I backed everything up beforehand, but no wipe.
Click to expand...
Click to collapse
It will only wipe if you are unlocking the bootloader for the first time.
Thanks for the feedback.
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
snickle said:
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Rebooteed to bootloader flashed twrp and vbmenta. REbooted to recovery and twrp came up. Installed magisk zip and rebooted. No root and stock recovery comes up instaead of TWRP.
THoughts?
Also still no fastboot commands available when tablet booted, just from bootloader.
Tried completely reflashing stock image, still no change.
snickle said:
...rebooted to twrp, but could not find magisk on sdcard for some reason.
Click to expand...
Click to collapse
You have to download Magisk-v21.4.zip and push it to /external_sd/.
If you did that, can you see your other files in /external_sd/ ?
snickle said:
...tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Make sure you have the latest adb and fastboot from Google. There were some major changes to fastboot for Android 10.
Also make sure you have the latest USB drivers from Lenovo.
I have the latest adb and drivers. fastboot commands used to work.
I rebooted to bootloader and flashed thre patched boot image made with the canary version of magisk and got root.
I then reflashed twrp and vbmeta and things seem to be working. Except for fastboot commands whlle booted.
snickle said:
I have the latest adb and drivers. fastboot commands used to work.
Click to expand...
Click to collapse
For Windows, the latest fastboot --version is 31.0.0-7110759
snickle said:
...things seem to be working. Except for fastboot commands whlle booted.
Click to expand...
Click to collapse
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Yahoo Mike said:
For Windows, the latest fastboot --version is 31.0.0-7110759
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Click to expand...
Click to collapse
Latest ADB and drivers loaded.
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
snickle said:
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
Click to expand...
Click to collapse
That's ok. That's how it's supposed to work.
ADB only works when your device is in recovery or system. It won't work when you're in fastboot or EDL mode.
Fastboot only works when your device is in fastboot mode. It won't work when you're in EDL, recovery or system.
The fastboot utility is an interface to the Android bootloader. When your device is in fastboot mode, you can use this utility to configure (some of) the bootloader and partition images. That's about it. I'm oversimplifying again, but...once the bootloader has passed on execution to EDL or a kernel (recovery or system), the fastboot utility can't work because the bootloader process is no longer running.
Unhelpfully fastboot just displays the "waiting for device" message, rather than something like "waiting for device to enter fastboot mode".
I hope that helps explain what's going on.
Twrp is working as expected no issues I have found, except for the need to press the power button s few times after booting into recovery to get twrp screen.
Hello! I need a bit of help... I have a TB-606F, 4GB/64GB version
I'm stuck on step 5. I've unlocked the bootloader, flashing TWRP and vbmeta seems successful, but then I cannot reboot into recovery. Using the fastboot reboot command I get "fastboot: usage: unknown reboot target recovery". If I try to reboot using volume up + volume down + power it eventually boots to Android.
Any thoughts are much appreciated!
Decryption works
Otg work
Flash
Mtp/adb
F2FS support
Fastbootd
Adb sideload
Changelog:
Fixed boot on MiUi when encrypted with pin (Tested on MiUi CN nightly 21.7.27 ) it means Tested on MiUi 12.5.3 )
Flashing instructions:
( Linux users )
boot to fastboot
navigate to downloaded file folder
open terminal and type: "fastboot flash recovery twrp-3.5.2.0-yarpiin-umi-A11.img"
reboot and enjoy
( Windows users )
You will need the platform-tools from the Android SDK on your computer. Download the platform-tools as per your operating system.
Windows users will need proper drivers installed on their computer. You can try the simple FWUL adb/fastboot ISO or the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct recovery file and copy the file into the same folder as your platform-tools. Rename the image to twrp.img and type:
fastboot flash recovery twrp-3.5.2.0-yarpiin-umi-A11_v2.img
fastboot reboot
Link:--
GitHub - yarpiin/twrp_device_xiaomi_umi: TWRP Source for Xiaomi Mi10
TWRP Source for Xiaomi Mi10 . Contribute to yarpiin/twrp_device_xiaomi_umi development by creating an account on GitHub.
github.com
Thank you very much, finally I've got full backup over OTG (ExFAT formatted)!
Slán!
works for me
hello can you please set the download link
bavaria Jo said:
hello can you please set the download link
Click to expand...
Click to collapse
https://github.com/yarpiin/twrp_device_xiaomi_umi/releases/download/v002/twrp-3.5.2.0-yarpiin-umi-A11_v2.img
works perfectly
Thanks for sharing
Any news about Twrp for A12?