Which .bat file?what are the commands in .bat ? I need to do this but on a linux machine. I cannot run a .bat file.
Which .bat file?what are the commands in .bat ? I need to do this but on a linux machine. I cannot run a .bat file.
Have a look at the readme.txt:
Okay thank you for the reply, I believe I was confusing this post with another on the forum.Have a look at the readme.txt:
"it will restore only bootloader on a hard bricked motorla device, you have to Reflash fastboot firmware for compelete unbrick"
There's no .bat file inside. This tool here will only restore your bootloader to be able to start fastboot mode on your device. That's it.
Run
fastboot getvar all
and post your output here.how to enter Moto g52 XT2221 to Edl ?Hello guys presenting all New Motorola unbrick tool which can restore bootloader on any hard bricked Motorola Phone through EDL Mod..
How to use:
Download:
- Install qcom or mtk driver according your device
- run tool, select model, click unbrick button
- Now connect phone in EDL or BROM mod according your device
- wait until success, once done your phone rebooted in fastboot mod, just download and flash fastboot firmware by running flash_all.bat
Current version: V1.0 beta
Credit: Me for compiling it, Motorola Inc for Providing firmware & loader
Source Code: Github
Disclaimer:
Donate: use button inside support section in tool
- use at own risk
- adviced for Retail devices, however you can try on branded too bcz your phone already in dead condition
Supported model:
*Edge 2021 SD778
*Edge 20 Lite
*Edge 20 Pro XT2153-1
*Edge 20
*Edge 30
*Edge 30 Pro
*Edge 30 Plus
*Edge Plus
*Edge X30
*Edge
*G50 XT2137-2
*G9 Power 2021
*Defy 2021
*G Pure
*E 2020
*Moto E5 Plus
*E5 SD425
*Moto E6
*Moto E7 Plus
*Moto G 5G
*Moto G Play 2021
*Moto G Power 2022)
*G Power 2021
*G Stylus VZW
*G Stylus 5G
*Moto G6 Play
*Moto G6 Plus
*Moto G6
*G7 Play
*G7 Plus
*G7 Power
*Moto G7
*G8 Play
*G8 Plus
*G8 Power XT2041-7
*Moto G8
*G9 Play
*G9 Plus
*G9 Power
*Moto G10
*Moto G30
*Moto G31
*Moto G41
*Moto G50 5G
*Moto G50
*G52 XT2221-1
*G52 XT2221-2
*Moto G60
*Moto G71 5G
*Moto G82
*Moto G100
*Moto G200 5G
*One Power
*One Zoom
*Z3 Play
*Moto Z4
*One 5G ACE
*One Action
*One Fusion Plus
*One Fusion
*One Hyper
*One Macro
*One Vision
*Motorola One
*P30 Note
*P30 Play
*Razr 5G XT2071-5
*Motorola Razr 2019
View attachment 5709087
test point
How's your device shown up in the Windows' device manager when plugged in?Heres my problem
I had a pin on my device when i did a factory reset
when in recovery mode it ask for a password and i didn't input anything i just pressed reboot and it gave an error of some sort and i pressed reboot again and the screen turned black...now when i plug it into the computer it gives a small ambient sound. Holding power for 2 minutes does nothing and holding the vol down and power does nothing either. i need help...
the error i got when using the unbrick tool is
[ -0.000] Opening device: \\.\COM5
Detecting device
[ 30.492] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
ok i installed the drivers from this site https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/How's your device shown up in the Windows' device manager when plugged in?
Windows 11 update should load a newer version. Have a look there.
im on windows 11 but i also followed the github site that you posted nothing happened when i tried the unbrick too againWindows 11 update should load a newer version. Have a look there.
Try this tool:
![]()
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)github.com
The tool here in this thread uses Moto's blankflash files and they have often problems.
You should have a look on Windows update for a new version of your QC HS-USB driver.im on windows 11 but i also followed the github site that you posted nothing happened when i tried the unbrick too again
I followed all the steps you providedYou should have a look on Windows update for a new version of your QC HS-USB driver.
How did u try to unbrick? We need every step of it to be able to help you. All I know is that you did something. So my help for you is: You did something wrong.
it says the best drivers for the device is already installedYou should have a look on Windows update for a new version of your QC HS-USB driver.
How did u try to unbrick? We need every step of it to be able to help you. All I know is that you did something. So my help for you is: You did something wrong.
1.bin SM_KAMORTA_H eMMC
2.bin SM_KODIAK UFS
3.bin SM8250 UFS
4.bin SM_KODIAK UFS
5.bin SM_KODIAK UFS
6.bin SM_WAIPIO UFS
7.bin SM8250 UFS
8.bin SM_WAIPIO UFS
9.bin SM_KODIAK UFS
10.bin MSM8953 eMMC
11.bin MSM8937 eMMC
MSM8940 eMMC
12.bin MSM8917 eMMC
13.bin MSM8937 eMMC
MSM8940 eMMC
14.bin SM_KAMORTA eMMC
15.bin SM_BITRA UFS
SM_BITRA_H UFS
16.bin SM_KAMORTA eMMC
17.bin SM_KAMORTA_H eMMC
18.bin SM_NICOBAR eMMC
19.bin SM_MANNAR UFS
20.bin MSM8937 eMMC
MSM8940 eMMC
21.bin SDM630 eMMC
22.bin MSM8953 eMMC
23.bin MSM8953 eMMC
24.bin SDM636 eMMC
SDM660 eMMC
25.bin MSM8953 eMMC
26.bin MSM8953 eMMC
27.bin SM_NICOBAR eMMC
28.bin SM_NICOBAR eMMC
29.bin SM_NICOBAR eMMC
30.bin SM_KAMORTA_H eMMC
31.bin SM7150 UFS
32.bin SM_KAMORTA_H eMMC
33.bin SM_KAMORTA eMMC
34.bin SM_KAMORTA_H eMMC
35.bin SM_MANNAR UFS
36.bin SM_DIVAR UFS
39.bin SM_DIVAR UFS
40.bin SM7150 UFS
41.bin SM_STRAIT UFS
42.bin SM_STRAIT UFS
43.bin SM8250 UFS
44.bin SM_LAHAINA UFS
45.bin SDM636 eMMC
46.bin SM6150 UFS
47.bin SDM636 eMMC
SDM660 eMMC
48.bin SM6150 UFS
49.bin SM_BITRA UFS
SM_BITRA_H UFS
50.bin SM7150 UFS
51.bin SDM710 eMMC
52.bin SM6150 UFS
53.bin SDM636 eMMC
54.bin MSM8953 eMMC
55.bin SM_SAIPAN UFS
56.bin SDM710 UFS
SDM670 UFS
a.bin SM_MANNAR UFS
b.bin SM_KAMORTA_H eMMC
redmi5asingle.bin
MSM8917 eMMC
Every .bin file contains a "index.xml" where the board is listed. You can also use a hex viewer or termux with hexeditwas trying to find the correlation between SoC or model and the <number> files.
i have all Motorola firehose but i really don't want to leak them in bulk, if you need it for testing purpose, feel free to contact me, i attach some for older modelThank you, @mark332 for this treasure trove.
I'm not particularly interested in "do-it-all GUI tools", but I do like the actual Firehose loaders.
I've managed to extract 57 Firehose loaders from all the moto/<number>.bin files.
I was trying to find the correlation between SoC or model and the <number> files.
There are SoC numbers like SM8250 in there but I've yet to find a real index.
the flashtool.qch is an SQLite database, but I haven't dived too deep yet.
There is some duplication of the Firehose loaders.
I've been using a loader for my Moto G Power (2021) from a random source.
I find that that exact (MD5) loader is found in 17.bin and 34.bin
In any case, it looks like the "range restricted" problem is still there.
Code:1.bin SM_KAMORTA_H eMMC 2.bin SM_KODIAK UFS 3.bin SM8250 UFS 4.bin SM_KODIAK UFS 5.bin SM_KODIAK UFS 6.bin SM_WAIPIO UFS 7.bin SM8250 UFS 8.bin SM_WAIPIO UFS 9.bin SM_KODIAK UFS 10.bin MSM8953 eMMC 11.bin MSM8937 eMMC MSM8940 eMMC 12.bin MSM8917 eMMC 13.bin MSM8937 eMMC MSM8940 eMMC 14.bin SM_KAMORTA eMMC 15.bin SM_BITRA UFS SM_BITRA_H UFS 16.bin SM_KAMORTA eMMC 17.bin SM_KAMORTA_H eMMC 18.bin SM_NICOBAR eMMC 19.bin SM_MANNAR UFS 20.bin MSM8937 eMMC MSM8940 eMMC 21.bin SDM630 eMMC 22.bin MSM8953 eMMC 23.bin MSM8953 eMMC 24.bin SDM636 eMMC SDM660 eMMC 25.bin MSM8953 eMMC 26.bin MSM8953 eMMC 27.bin SM_NICOBAR eMMC 28.bin SM_NICOBAR eMMC 29.bin SM_NICOBAR eMMC 30.bin SM_KAMORTA_H eMMC 31.bin SM7150 UFS 32.bin SM_KAMORTA_H eMMC 33.bin SM_KAMORTA eMMC 34.bin SM_KAMORTA_H eMMC 35.bin SM_MANNAR UFS 36.bin SM_DIVAR UFS 39.bin SM_DIVAR UFS 40.bin SM7150 UFS 41.bin SM_STRAIT UFS 42.bin SM_STRAIT UFS 43.bin SM8250 UFS 44.bin SM_LAHAINA UFS 45.bin SDM636 eMMC 46.bin SM6150 UFS 47.bin SDM636 eMMC SDM660 eMMC 48.bin SM6150 UFS 49.bin SM_BITRA UFS SM_BITRA_H UFS 50.bin SM7150 UFS 51.bin SDM710 eMMC 52.bin SM6150 UFS 53.bin SDM636 eMMC 54.bin MSM8953 eMMC 55.bin SM_SAIPAN UFS 56.bin SDM710 UFS SDM670 UFS a.bin SM_MANNAR UFS b.bin SM_KAMORTA_H eMMC redmi5asingle.bin MSM8917 eMMC
Yes, I summarized that all in the "spoiler" list.Every .bin file contains a "index.xml" where the board is listed. You can also use a hex viewer or termux with hexedit
The main thing I need from EDL functionality is not to write 70-odd partitions (as it seems the goal for most people who use GUI tools), but to pull copies of boot and recovery. I use them to root either directly or with Magisk.
That would be much appreciated.If you like to I could build a *.bin file for your device. Later you just need to move it into the moto folder where it'll replace one of the other device files. Of course I'll tell you which one.