Database Develop

For all of u who get error with update [[ root etc... ]]

So I get the same problem with update to ***170 [[got 132 ]] rooted and recovery.
For me update stopped at 14%
Solution
1. Make backup all ur photos etc
2.Download firmware from this topic http://forum.xda-developers.com/p8lite/general/huawei-p8-p8-lite-stock-rom-firmware-t3176374
3.Download Huawei Extractor http://forum.xda-developers.com/attachment.php?attachmentid=3262544&d=1429042973
4.Download http://forum.xda-developers.com/showthread.php?t=2317790
5.Open Command prompt and go to the directory where adb/fastboot is installed
6. Make sure that ur phone is full charged
7.Connect phone with USB debbuging on
8.Extract 'Huawei Extractor" to a folder and run the executable
9.Extract the firwmare archive (ex. ALE-L21V100R001C432B132_Europe_Dual) to a folder
10.Run Huawei Image Extractor
11.Browse (press [...]) and select the UPDATE.APP file inside the dload folder of the extracted firmware archive
12.Right click on the package files and do an Extract All to a folder (create one)
13.Copy the files: BOOT.img RECOVERY.img SYSTEM.img CUST.img to the directory where adb/fastboot is installed
14.Go to the opened command prompt and enter fastboot mode: 'adb reboot bootloader'
15.Flash the system partition: fastboot flash system SYSTEM.img (takes quite a bit)
16.Flash the custom partition: fastboot flash cust CUST.img
17.Flash the recovery partition: fastboot flash recovery RECOVERY.img
18.Flash the vendor partition: fastboot flash boot BOOT.img
19.Repeat all flashes if you get any error
20.Reboot phone: fastboot reboot
now go to settings and update ur phone, also again u can do root etc
oczywiscie pozdrawiam cala Polske

Problem installing not incremental ROM

Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.

I am on mac so cannot use Mi Flash

EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader

helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.

Only i dont understand: (recomend this others from this year locked boot loader) ?

EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.

Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:

EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.

Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...

EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.

When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.

EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)

Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?

EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/

every time I type:
fastboot oem edl
the screen of the smartphone goes off

Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?

EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?

No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.

Is Snapdragon SDK actually Qualcomm drivers?

helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?

Question Flashing TWRP doesn't work (Xiaomi Redmi 9t)

Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .

TWRP by brigudav- i flashed only twrp renamed to recovery.img and patched os via that stock recovery will not back.

Rename the file change nothing to me.
As information, when I try in try
Bash:
fastboot boot recovery.img
i get :
Bash:
FAILED (remote: unknown command)
in fastboot
and
Bash:
FAILED (remote: Unrecognized command boot)
in fastbootd
I've test lineage recovery and that's the same : impossible to boot on other recovery except the stock MI-Recovery 3.0 .

I get the exactly same errorwhile try booting twrp.img is there no custom recovery for lime that works?

GrandTouque said:
Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .
Click to expand...
Click to collapse
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image

ex-it said:
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image
Click to expand...
Click to collapse
You are right, I try to flash a unofficial TWRP that I found at this thread and now I've just a black screen when I boot on it but I can now boot on the OS with this "recovery".

Finally, I've found this one on this thread who works .

Question [SOLVED] Bricked device - can only access MIUI Recovery and Fastboot

I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?

zepolyerf said:
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
Click to expand...
Click to collapse
Drivers installed?

Hi! How can I check if drivers are installed? I'm on Linux, if that matters.

Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?

V0latyle said:
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
Click to expand...
Click to collapse
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?

zepolyerf said:
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
Click to expand...
Click to collapse
Your device might not have a recovery partition; in A/B partition layout devices, recovery lives in the boot image.
A bit of an explanation:
When you use fastboot boot <image> you're telling the device to load the image you're sending - so if you use fastboot boot twrp.img you're telling it to load the TWRP.img on your computer. This is what you should be using if you want to boot TWRP.
When you use fastboot flash <partition> <image> you're telling bootloader to flash the specified partition with the specified image. So, if you used fastboot flash boot twrp.img, bootloader will overwrite /boot with the TWRP image...meaning the device will only boot into TWRP.
As for why the device would only boot into stock recovery after you flashed the custom ROM, I suspect that it didn't flash the kernel, or otherwise may have corrupted the boot image. So, when the device tries to start the kernel, it failed and just boots into recovery instead.

What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?

zepolyerf said:
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
Click to expand...
Click to collapse
Reboot to bootloader. If you're currently in recovery mode, cancel the command (Ctrl+C) and use adb reboot bootloader. If you're currently in bootloader but it's not responding, just use the button combo to force a reset.
Remember, you can only use fastboot commands in bootloader mode. If you're in recovery, you can only use some ADB commands, but in this case, I don't think that will be much help.

This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.

I went into fastboot mode by pressing Vol Down + Power buttons.
Plugged the phone in to my Linux machine. Have VirtualBox recognize my device.
Opened MiFlash tool. Selected the flash rom from Xiaomi's site. Got an Antirollback error. Here's the logs:
Code:
[4:41:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:25 AM]:GetScriptDevices
[4:41:28 AM]:add device f8b471a6 index 0
[4:41:48 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:48 AM]:GetScriptDevices
[4:41:51 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:41:51 AM]:add device f8b471a6 index 0
[4:41:51 AM]:Thread start,thread id 11,thread name f8b471a6
[4:41:51 AM]:start process id 4212 name cmd
[4:49:16 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:16 AM]:GetScriptDevices
[4:49:16 AM]:add device f8b471a6 index 1
[4:49:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:24 AM]:GetScriptDevices
[4:49:24 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:49:24 AM]:add device f8b471a6 index 1
[4:49:24 AM]:Thread start,thread id 12,thread name f8b471a6
[4:49:24 AM]:start process id 1704 name cmd
[4:49:25 AM]:Thread stopped, thread id 12, thread name f8b471a6
[4:51:22 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:51:23 AM]:GetScriptDevices
[4:51:23 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:51:23 AM]:add device f8b471a6 index 1
[4:51:23 AM]:Thread start,thread id 19,thread name f8b471a6
[4:51:23 AM]:start process id 3400 name cmd
[4:52:26 AM]:GetUserInfo
[4:52:39 AM]:authentication edl error:Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[4:56:31 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:56:31 AM]:GetScriptDevices
[6:00:17 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:18 AM]:driver oem5.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\Windows\INF\oem5.inf,result True,GetLastWin32Error
[6:00:19 AM]:set RegistryKey value:android_winusb.inf--oem5.inf
[6:00:19 AM]:mkdir "C:\Users\IEUser\.android"
[6:00:19 AM]:output:A subdirectory or file C:\Users\IEUser\.android already exists.
[6:00:19 AM]: echo 0x2717 >>"C:\Users\IEUser\.android\adb_usb.ini"
[6:00:19 AM]:output:
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:20 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:20 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:21 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:driver oem6.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:22 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\Windows\INF\oem6.inf,result True,GetLastWin32Error
[6:00:22 AM]:set RegistryKey value:qcser.inf--oem6.inf
[6:01:33 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:34 AM]:GetScriptDevices
[6:01:34 AM]:add device f8b471a6 index 1
[6:01:55 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:55 AM]:GetScriptDevices
[6:01:55 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[6:01:55 AM]:add device f8b471a6 index 1
[6:01:55 AM]:Thread start,thread id 12,thread name f8b471a6
[6:01:55 AM]:start process id 6280 name cmd
[6:01:56 AM]:Thread stopped, thread id 12, thread name f8b471a6
Any idea on what to do next?

BigChungus321 said:
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
Click to expand...
Click to collapse
It might as well be a brick haha. I must be dumb (very likely) or there's just not a lot of clear and comprehensive resources out there to fix this kind of thing.

Ahh anti roll back error is pretty simple to fix, you just have to remove the check from the .bat files, there are tutorials on YT that can help, after that reflash stock rom in MiFlash.
If you're worried about anti roll back, don't worry, ARB value for the device has been 3 so far so it's safe to downgrade. Goodluck

Seeing a ton of Bricked Notes on here this last week, Y`all making me nervous about doing anything with mine lol

I faced this problem in linux got around it with usb 2.0 interface doesn't worked with usb 3.0 and above but my device was different when I got this recovery flash waiting problem. Also try to updated the platform tools.

So the solution was to entirely ditch Linux and use Windows to play with fastboot and adb commands via the terminal.
I don't understand why it worked when I did it on Windows when I was using the same platform tools on Linux. Oh well.

[Complete Tutorial] Root your Moto G9 Power with TWRP and Magisk:

mistersmee have made a post about how to root your device with Magisk, however this post is about how to root your device using a Magisk .Zip file and TWRP (You should know it as TeamWin Recovery Project..), this is an easier way to root your Moto G9 Power. But if you want you can also try the other method! ​How to root your Moto G9 Power (cebu)​Step 1 - Download needed files:
TWRP - Download TWRP for cebu;
Magisk .Apk file - Download only from Github;
ADB and FastBoot - I use ADB and FastBoot Minimal;
(Extremely recommended! But optional..) Device original rom - In case of bootloop.
Step 2 - Make a backup:
The following step will perform a factory data reset!
Step 3 - Unlock BootLoader:
Open ADB Window and type
Code:
fastboot oem get_unlock_data
(And hit enter)
You should get a code like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Open Notepad and remove anything but the code, the result should be like this
Code:
INFO0A40040192024205#4C4D3556313230INFO30373731363031303332323239#BD00INFO8A672BA4746C2CE02328A2AC0C39F95INFO1A3E5#1F53280002000000000000000INFO0000000
Proceed with login on Moto Care;
Go to Motorola Unlock page and paste the code;
Pick the unlock code provided by Motorola (Normally it should be emailed to you) and run
Code:
fastboot oem unlock {put the key here}
on ADB;
After this you phone should reset.
Step 4 - Flash TWRP:
Pick TWRP .Img file and put it in ADB folder;
Run the following commands:
Code:
fastboot flash recovery twrp.img
fastboot reboot
If you get any error try
Code:
fastboot boot twrp.img
;
Boot into TWRP.
Step 5 - Flash Magisk:
Change Magisk .Apk extension to .Zip;
On TWRP ignore any password screen, copy Magisk .Zip to phone;
Go to install and find the .Zip, flash it, and clean Dalvik Cache.
Done​