Database Develop

Hard Bricked, how can enter Emergency Download Mode?

I am using QFIL to try and revive my X4, but I have no idea how to get into EDL mode when I cannot do anything with the device. Computer recognizes it when I plug it in as Quectel QDLoader 9008 in Ports, but that's it.
Any suggestions would be appreciated. I don't want to have to pay MOTO to fix it if possible.
I've exhausted every resource I have.
Thank you anyone that can help or at least point me in the right direction.\
EDIT: When I was eMMC Software Download app, phone shows in COM3 Download mode, but I need an XML file to flash with that tool and don't know how to get that.

I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?

Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?

DustArma said:
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
Click to expand...
Click to collapse
No, my power went out in the middle of fastboot flashing and screwed up all the partitions. I am stuck without the blankflash.. Thank you for replying to try to help.

christopher68369 said:
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Click to expand...
Click to collapse
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.

johnjingle said:
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
Click to expand...
Click to collapse
you can not take it to the Moto warranty? you do not have to know how the phone went blank...

bookworth said:
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
Click to expand...
Click to collapse
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)

LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Bro! It's works! Thanks for blank-flash for my soft bricked moto x4.

O link não funciona
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Please guy, this link not work! Help me Please. Thanks

silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
It does, if you follow his instructions stated after the link.

Consegui agora!
jhedfors said:
It does, if you follow his instructions stated after the link.
Click to expand...
Click to collapse
Thanks Very much! work perfectly

Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error:
**** Log buffer [000001] 2018-07-26_14:55:02 ****
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 172 (0xac)
[ 0.004] ...cpu.sn = 2293722822 (0x88b76ec6)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.196] Handling things over to programmer
[ 0.197] Identifying CPU version
[ 0.197] Waiting for firehose to get ready
[ 3.212] ...SDM630 1.0
[ 3.213] Determining target secure state
[ 3.215] ...secure = yes
[ 3.238] Configuring device...
[ 3.243] Flashing GPT...
[ 3.243] Flashing partition with gpt.bin
[ 3.247] Initializing storage
[ 4.421] Target NAK!
[ 4.421] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.422] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.423] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.423] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.424] ...ERROR: Failed to get device info slot:0artition:0
[ 4.424] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.424] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.424] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.424] Check qboot_log.txt for more details
[ 4.425] Total time: 4.426s
[ 4.425]
[ 4.425] qboot version 3.86
[ 4.425]
[ 4.425] DEVICE {
[ 4.425] name = "\\.\COM6",
[ 4.425] flags = "0x144",
[ 4.425] addr = "0x62FD64",
[ 4.425] sahara.current_mode = "0",
[ 4.425] api.buffer = "0x2B15020",
[ 4.425] cpu.serial = "2293722822",
[ 4.425] cpu.id = "172",
[ 4.425] cpu.sv_sbl = "1",
[ 4.425] cpu.name = "SDM630",
[ 4.425] storage.type = "eMMC",
[ 4.425] sahara.programmer = "programmer.elf",
[ 4.425] module.firehose = "0x2A51630",
[ 4.425] api.firehose = "0xF2EF68",
[ 4.425] cpu.ver = "256",
[ 4.425] cpu.vername = "1.0",
[ 4.425] fh.max_packet_sz = "1048576",
[ 4.425] fh.storage_inited = "1",
[ 4.425] provisioning_may_hang = "true",
[ 4.425] }
[ 4.425]

silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
You mean you can't download ?

waltwittman1 said:
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error: (log text omitted)
Click to expand...
Click to collapse
I got a similar error when I tried the blank-flash on my bricked Moto X4. @waltwittman1 please let me know if you find a solution.

serial_write() Error
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error​

ttyUSB Permissions Linux
mistryous said:
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error​
Click to expand...
Click to collapse
While I was running as root on my Linux system, this was solved as an issue between the device showing up on /dev/ttyUSB0 initially. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].

Owner trashed the blankflash file. Can anyone hook me up please?

Here you go.
luvcustom said:
Owner trashed the blankflash file. Can anyone hook me up please?
Click to expand...
Click to collapse
This is the one I use. This is my first post to the XDA forums so they prevented me from linking to my dropbox. So, replace the [dot] with a . and you should be good.
.dropbox [dot] com/s/3xi85sy207x3vs6/blankflash.zip?dl=0[/url]

Win 10 waiting for device message and nothing more.
and no 9008 port

moved

How to unbrick Montana xt179x bricked(HS-USB QDloader 9008)

Method tested and used with succes by @kalyansundhar on xt1795
Thanks for his detailed tutorial for unbrick the phones!
https://forum.xda-developers.com/showpost.php?p=76747247&postcount=258
Also please read the post's after that before posting your question
can be already answered to it
Tutorial for using Windows 7(language Brasilian & English, Thanks to @caikehenrique)
becouse flashing process can be done on Windows too
Thanks to @Thi_os
i made a video presentation to help the users wich dont
know how to do it
video for users with windows OS
video for extracting the.tar.gz archive in windows
sorry for my english
Oreo 8.1 mmcblk0.img thanks to @meltbanana
Nougat 7.1 mmncblk0.img xt1794(102-49-8) with md5-code by @hanshu43
Nougat 7.1 mmncblk0.img xt1795 with md5-code and tool to verify it
Thanks to @echo92 for providing md5-code of a working file
Tips & tricks!
The BEST method to flash the sdcard with mmcbk0.img file is to use LINUX!
Windows user have no need to install Linux in pc, you can run Linux from a bootable usb-stik or pendrive by 8Gb at least
0)put the moto g5s in wall charger till finish flashing sdcard to be charged on boot test!
1) run linux, preferable cinnamon or mate versions of linux Mint or Ubuntu(for ubuntu dont use LTS version)
2)insert the sdcard in pc or card reader and opend "Disks" apk
3)in "Disks"apk select sdcard and you will see the sdcard partitions
4) press "-" to delete the partition(delete al partitions if are more than one)
5)press "+" to create a new one and name it mmcblk0, set FAT(FAT32) file format and press "CREATE"
6)press "Play"button to mount the sdcard, look to see what path sdcard have(/dev/sd??) the and close the "Disks"apk
7)go to Desktop, opend "Computer" and navigate to the location when the img file is extracted(mmcblk0.img)
8)opend the window where img file is with root(right click on window and select "opend as root")
9)in root window opend the Terminal(right click on window and select "opend terminal")
no need to type "su" in terminal, it have already root
10)type in terminal the comand writed below and dont forget to eliminate that "1" from the sdcard path,
that "1"can make the differnce betwen phone boot or not!!!!!
Terminal comands
- if your sdcard is seen like " /dev/sdb1"
in terminal aply that comand:
dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
-if your sdcard is seen like " /dev/mmcblk0p1"
in terminal aply that comand:
dd bs=4M if=mmcblk0.img of=/dev/mmcblk0 status=progress oflag=sync
and flashing process should start
when it finish, test the sdcard in phone and it should boot!
IF you get an size error of the sdcard in terminal you have to change the sdcard and try again!
This is the last edit of sdcard flashing tutorial, i cant make better than that!!
Thankyou!

thanks bro! i have my device hard bricked,but device manager detects it as "quectel QDLoader 9008" but not Qulacomm dloader husb 9008 now what to do ?

pardhav said:
thanks bro! i have my device hard bricked,but device manager detects it as "quectel QDLoader 9008" but not Qulacomm dloader husb 9008 now what to do ?
Click to expand...
Click to collapse
i resume you flashed a wrong image files.
did you try to use blankflash with montana image files?

:/
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error

Marceloaps said:
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Click to expand...
Click to collapse
Thankyou very much for your report!
can you provide the qboot_log.txt saved to chech it?
also can you try the singleimage.bin atached?
rename it from singleimage.bin.txt to singleimage.bin(delete .txt from name)
Thankyou!

here
**** Log buffer [000001] 2018-03-19_14:40:38 ****
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ 4.032] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.032] Check qboot_log.txt for more details
[ 4.032] Total time: 4.032s
[ 4.032]
[ 4.032] qboot version 3.40
[ 4.032]
[ 4.032] DEVICE {
[ 4.032] name = "\\.\COM3",
[ 4.032] flags = "0x64",
[ 4.032] addr = "0x22FE6C",
[ 4.032] api.bnr = "0x3A2FE8",
[ 4.032] }
[ 4.032]
[ 4.032]
[ 4.032] Backup & Restore {
[ 4.032] num_entries = 0,
[ 4.032] restoring = "false",
[ 4.032] backup_error = "not started",
[ 4.032] restore_error = "not started",
[ 4.032] }
[ 4.032]
**** Log buffer [000001] 2018-03-19_14:41:06 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.049] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.049] Check qboot_log.txt for more details
[ 4.049] Total time: 4.049s
[ 4.049]
[ 4.049] qboot version 3.40
[ 4.049]
[ 4.049] DEVICE {
[ 4.049] name = "\\.\COM3",
[ 4.049] flags = "0x64",
[ 4.049] addr = "0x22FE6C",
[ 4.049] api.bnr = "0x372FE8",
[ 4.049] }
[ 4.049]
[ 4.049]
[ 4.049] Backup & Restore {
[ 4.049] num_entries = 0,
[ 4.049] restoring = "false",
[ 4.049] backup_error = "not started",
[ 4.049] restore_error = "not started",
[ 4.049] }
[ 4.049]
**** Log buffer [000001] 2018-03-19_14:51:30 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.047s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM3",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x22FE6C",
[ 4.047] api.bnr = "0x7D2FE8",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
**** Log buffer [000001] 2018-03-19_15:11:44 ****
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.007] Total time: 4.008s
[ 4.051]
[ 4.051] qboot version 3.40
[ 4.051]
[ 4.051] DEVICE {
[ 4.051] name = "\\.\COM3",
[ 4.051] flags = "0x64",
[ 4.051] addr = "0x22FE6C",
[ 4.051] api.bnr = "0x582FE8",
[ 4.051] }
[ 4.051]
[ 4.051]
[ 4.051] Backup & Restore {
[ 4.051] num_entries = 0,
[ 4.051] restoring = "false",
[ 4.051] backup_error = "not started",
[ 4.051] restore_error = "not started",
[ 4.051] }
[ 4.051]

Marceloaps said:
**** Log buffer [000001] 2018-03-19_14:40:38 ****
[ 4.051] }
[ 4.051]
Click to expand...
Click to collapse
Thankyou, is not very clear!
did you test the singleimage.bin posted above?

help me
Unable to download file
call me on facebook and pass qboot.log
https://www.facebook.com/
---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------
help me :/ :crying:

sorry for all!
the file dont work
i will keep looking for a working file
Thankyou!
also thanks to @Marceloaps for patience to test and test and test.......

Pls help me ;(
Can u upload new singleimage.bin to any filehost? or help me differently please.
**** Log buffer [000001] 2018-03-19_22:15:26 ****
[ -0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.053] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.053] Check qboot_log.txt for more details
[ 4.053] Total time: 4.055s
[ 4.053]
[ 4.053] qboot version 3.40
[ 4.053]
[ 4.053] DEVICE {
[ 4.053] name = "\\.\COM10",
[ 4.053] flags = "0x64",
[ 4.053] addr = "0x61FE5C",
[ 4.053] api.bnr = "0x2F92E28",
[ 4.053] }
[ 4.053]
[ 4.053]
[ 4.053] Backup & Restore {
[ 4.053] num_entries = 0,
[ 4.053] restoring = "false",
[ 4.053] backup_error = "not started",
[ 4.053] restore_error = "not started",
[ 4.053] }
[ 4.053]
**** Log buffer [000001] 2018-03-19_22:28:48 ****
[ 0.000] Opening device: \\.\COM10
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.016] ...cpu.sn = 868549579 (0x33c503cb)
[ 0.016] Opening singleimage
[ 0.187] ERROR: error opening singleimage
[ 0.187] Check qboot_log.txt for more details
[ 0.187] Total time: 0.266s
[ 0.187]
[ 0.187] qboot version 3.40
[ 0.187]
[ 0.187] DEVICE {
[ 0.187] name = "\\.\COM10",
[ 0.187] flags = "0x64",
[ 0.187] addr = "0x61FE5C",
[ 0.187] sahara.current_mode = "3",
[ 0.187] api.buffer = "0x3245020",
[ 0.187] cpu.serial = "868549579",
[ 0.187] cpu.id = "79",
[ 0.187] cpu.sv_sbl = "1",
[ 0.187] api.bnr = "0x2EF2FE8",
[ 0.187] }
[ 0.187]
[ 0.187]
[ 0.187] Backup & Restore {
[ 0.187] num_entries = 0,
[ 0.187] restoring = "false",
[ 0.187] backup_error = "not started",
[ 0.187] restore_error = "not started",
[ 0.187] }
[ 0.187]
**** Log buffer [000001] 2018-03-19_22:29:02 ****
[ 0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.049s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM10",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x61FE5C",
[ 4.047] api.bnr = "0x2F02EE0",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
I'm counting on you.

It was nothing, so we improved more and we moved slowly, I need to be here.

anyone, has a OTAupdate saved?
to share it here please!
Thankyou!

vaserbanix said:
After many searching's, i think i managed to create a singleimage.bin for montana
it is made on xt1793 modell and it (maybe) can work on all montana version's
i cant test it! sorry, my phone is not bricked and hope to do not brick it in near future
so the singleimage.bin file is not tested
you will do test on your own risk
please think twice or more many times before act
Download the "Blankflash" zip, (link removed)
extract it in your pc(Windows or Linux)
in Windows opend the blankflash folder and do double-click on blank-flash.bat
a cmd window will opend and it will wait for your device to be conected
connect the phone and the process should start
in Linux opend the blankflash folder, opend terminal and tipe:./blank-flash.sh and hit enter
after you will see "<waiting for device>" line, connetct the phone and the process should start
hope singleimage.bin to be good for all versions of montana and to work helping you to restore the phone
What is a Forum without users?
Thankyou!
in case of ERRors please post along your coment a screenshot with cmd or terminal
or copy-paste all lines from it here
Thankyou again!
Click to expand...
Click to collapse
Where is the files why linked removed haven't tried yet. Is there any other file.

ASHDCBZ said:
Where is the files why linked removed haven't tried yet. Is there any other file.
Click to expand...
Click to collapse
i removed the link becouse the file is corupted or not valid, blankflash cant open it!
i have to get other method to get singleimage.bin for montana
Thankyou!
Sent from my Moto G5s using Tapatalk

vaserbanix said:
i removed the link becouse the file is corupted or not valid, blankflash cant open it!
i have to get other method to get singleimage.bin for montana
Thankyou!
Sent from my Moto G5s using Tapatalk
Click to expand...
Click to collapse
ok thank you for trying pls. find any other way as service center not helping and not doing anything about it.

ASHDCBZ said:
ok thank you for trying pls. find any other way as service center not helping and not doing anything about it.
Click to expand...
Click to collapse
I'm working on that.
Thankyou!
Sent from my Moto G5s using Tapatalk

Good work and thanks. My device I left for maintenance in a specialized store. Unfortunately they called me saying it could not be fixed. So as soon as I search I will participate in the forum and help develop it to help others. Leave your work as soon as I will part of it.

hey... plz help me i m alo facing this problem my device moto g5s got hard brickes
xdanielmonster said:
Can u upload new singleimage.bin to any filehost? or help me differently please.
**** Log buffer [000001] 2018-03-19_22:15:26 ****
[ -0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.053] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.053] Check qboot_log.txt for more details
[ 4.053] Total time: 4.055s
[ 4.053]
[ 4.053] qboot version 3.40
[ 4.053]
[ 4.053] DEVICE {
[ 4.053] name = "\\.\COM10",
[ 4.053] flags = "0x64",
[ 4.053] addr = "0x61FE5C",
[ 4.053] api.bnr = "0x2F92E28",
[ 4.053] }
[ 4.053]
[ 4.053]
[ 4.053] Backup & Restore {
[ 4.053] num_entries = 0,
[ 4.053] restoring = "false",
[ 4.053] backup_error = "not started",
[ 4.053] restore_error = "not started",
[ 4.053] }
[ 4.053]
**** Log buffer [000001] 2018-03-19_22:28:48 ****
[ 0.000] Opening device: \\.\COM10
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 79 (0x4f)
[ 0.016] ...cpu.sn = 868549579 (0x33c503cb)
[ 0.016] Opening singleimage
[ 0.187] ERROR: error opening singleimage
[ 0.187] Check qboot_log.txt for more details
[ 0.187] Total time: 0.266s
[ 0.187]
[ 0.187] qboot version 3.40
[ 0.187]
[ 0.187] DEVICE {
[ 0.187] name = "\\.\COM10",
[ 0.187] flags = "0x64",
[ 0.187] addr = "0x61FE5C",
[ 0.187] sahara.current_mode = "3",
[ 0.187] api.buffer = "0x3245020",
[ 0.187] cpu.serial = "868549579",
[ 0.187] cpu.id = "79",
[ 0.187] cpu.sv_sbl = "1",
[ 0.187] api.bnr = "0x2EF2FE8",
[ 0.187] }
[ 0.187]
[ 0.187]
[ 0.187] Backup & Restore {
[ 0.187] num_entries = 0,
[ 0.187] restoring = "false",
[ 0.187] backup_error = "not started",
[ 0.187] restore_error = "not started",
[ 0.187] }
[ 0.187]
**** Log buffer [000001] 2018-03-19_22:29:02 ****
[ 0.000] Opening device: \\.\COM10
[ 0.002] Detecting device
[ 4.047] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.047] Check qboot_log.txt for more details
[ 4.047] Total time: 4.049s
[ 4.047]
[ 4.047] qboot version 3.40
[ 4.047]
[ 4.047] DEVICE {
[ 4.047] name = "\\.\COM10",
[ 4.047] flags = "0x64",
[ 4.047] addr = "0x61FE5C",
[ 4.047] api.bnr = "0x2F02EE0",
[ 4.047] }
[ 4.047]
[ 4.047]
[ 4.047] Backup & Restore {
[ 4.047] num_entries = 0,
[ 4.047] restoring = "false",
[ 4.047] backup_error = "not started",
[ 4.047] restore_error = "not started",
[ 4.047] }
[ 4.047]
I'm counting on you.
Click to expand...
Click to collapse
plz reply me please its too urgent I lost my device I mean device hard bricked I need a working blank flash file for my montana sory for my bad English but I m very worried about my device plz someone help me anyway.....plz reply me on [email protected] its been too long there is no solution I found on internet ....plz help mee guys to get my device backon track...its hard bricked and only a notification light is blinking ...I can nor go to fastboot mode as well.....plz help and rplyyy..than you

For few days i have to fix some my heathy problems, my possibilities right now are limited(i have only the phone with me).
When I'll go back home, I'll continue to try to get a working singleimage.bin for unbrick the phones(or others method if exist)
Sorry and thanks for understanding!
Also please dont add other post's under this for now so everyboby can see it!
Thankyou again!

XT1792
> Unlocked bootloader + twrp + root
> accidentally removed stock rom by twrp
> installing new stock rom by adb fastboot
> BRICKED
> only selfie flash light blinkin when I put on charger or USB
> I installed qualcom drivers and worked, tried others blankflash
but I'm stucked and can't revive G5S by those blankflash
> Please, help me

Can you enter eMMC download mode (9006/DLOAD) from EDL mode on Moto G5s Plus?

Hello,
After installing
various versions of QPST (2.7.437, 2.7.460)
HDDRawCopy 1.10
Qualcomm_Diag_QD_Loader_2016_driver
I can successfully boot the phone in emergency download mode (COM port in device manager) aka mode 9008
What I would like is access to the raw eMMC (mode 9006) to further nand backup it. So, I tried to switch to DLOAD in eMMC Software Download.
It either doesn't work (unending progress bar), or gives an error 0x80004005.
What I also tried is entering EDL again and sending firehose commands using CLI:
Code:
qboot -p COM5 blank-flash programmer.mbn prog_emmc_firehose_8953_ddr_lenovo.mbn --debug=1
I think I downloaded qboot.exe and the .mbn's on some github repos, MSM8953 is the codename for SD 625
It's not really better, but gives more verbose messages:
Code:
**** Log buffer [000001] 2018-09-22_17:04:40 ****
[ 0.001] Opening device: \\.\COM5
[ 0.001] Opening serial device: \\.\COM5
[ 0.003] Detecting device
[ 0.003] Switching to command mode
[ 0.003] Receiving HELLO packet
[ 0.003] ...protocol version: 2
[ 0.004] ...compatible with: 1
[ 0.004] ...max. packet size: 1024
[ 0.004] ...current mode: Image transfer pending
[ 0.004] Sending HELLO_RESP packet
[ 0.005] Receiving COMMAND_READY packet
[ 0.005] Identifying device
[ 0.005] Reading CPU serial number
[ 0.005] Sending CMD_EXEC packet, cmd=CMD_READ_SN
[ 0.006] Receiving CMD_EXEC_RESP packet
[ 0.006] ...payload: 4 byte(s)
[ 0.006] Receiving payload
[ 0.007] Reading CPU id
[ 0.007] Sending CMD_EXEC packet, cmd=CMD_READ_HWID
[ 0.007] Receiving CMD_EXEC_RESP packet
[ 0.011] ...payload: 24 byte(s)
[ 0.011] Receiving payload
[ 0.012] Reading SBL SV
[ 0.012] Sending CMD_EXEC packet, cmd=CMD_READ_SV_SBL
[ 0.012] Receiving CMD_EXEC_RESP packet
[ 0.012] ...payload: 4 byte(s)
[ 0.013] Receiving payload
[ 0.013] Reading debug data
[ 0.013] Sending CMD_EXEC packet, cmd=CMD_READ_DEBUG_DATA
[ 0.013] Receiving CMD_EXEC_RESP packet
[ 0.014] ...payload: 256 byte(s)
[ 0.014] Receiving payload
[ 0.015] Debug data dump follows
[ 0.015] 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
[ 0.015] *
[ 0.015] ...cpu.id = 70 (0x46)
[ 0.016] ...cpu.sn = 1066281865 (0x3f8e2b89)
[ 0.016] Opening singleimage
[ 0.018] ERROR: error opening singleimage
[ 0.018] Check qboot_log.txt for more details
[ 0.018] Total time: 0.018s
[ 0.018]
[ 0.018] qboot version 3.40
[ 0.018]
[ 0.018] DEVICE {
[ 0.018] name = "\\.\COM5",
[ 0.018] flags = "0x65",
[ 0.018] addr = "0x61FE5C",
[ 0.018] sahara.current_mode = "3",
[ 0.018] api.buffer = "0x31F6020",
[ 0.018] cpu.serial = "1066281865",
[ 0.018] cpu.id = "70",
[ 0.018] cpu.sv_sbl = "0",
[ 0.018] api.bnr = "0x2872FE8",
[ 0.018] }
[ 0.018]
[ 0.018]
[ 0.018] Backup & Restore {
[ 0.018] num_entries = 0,
[ 0.018] restoring = "false",
[ 0.018] backup_error = "not started",
[ 0.018] restore_error = "not started",
[ 0.018] }
[ 0.018]
So it complains about singleimage, but all I want is just the emmc block mode. Has anyone managed to make it work?
My OS is Windows 10 Pro x64 1709, if that matters.

TwoPointZero said:
Hello,
After installing
various versions of QPST (2.7.437, 2.7.460)
HDDRawCopy 1.10
Qualcomm_Diag_QD_Loader_2016_driver
I can successfully boot the phone in emergency download mode (COM port in device manager) aka mode 9008
What I would like is access to the raw eMMC (mode 9006) to further nand backup it. So, I tried to switch to DLOAD in eMMC Software Download.
It either doesn't work (unending progress bar), or gives an error 0x80004005.
What I also tried is entering EDL again and sending firehose commands using CLI:
I think I downloaded qboot.exe and the .mbn's on some github repos, MSM8953 is the codename for SD 625
It's not really better, but gives more verbose messages:
So it complains about singleimage, but all I want is just the emmc block mode. Has anyone managed to make it work?
My OS is Windows 10 Pro x64 1709, if that matters.
Click to expand...
Click to collapse
i have the same problem as you

Moto X4 XT1900-2 Hard Bricked Error

Hello Everyone. Please help me un bricking moto X4.
1) First, I'm new to this field.
2) My Moto X4 is totally dead and no sign of life. No fastboot, no recovery and none of the key works.
One thing I want to say that my device is totally intact. I have never try to root or unlock this. The device is in stock condition with the last latest update. Day before I was just using its hotspot to access internet on my PC. I don't know when it get switched off. And till then no sign of life on my moto x4. Can't even see whether it is charging or not? I tried to flash firmware but stuck with errors. I have read blankflash can be helpful but didn't find a blankflash for moto X4 XT1900-2. I also tried a blankflash file but stuck at a problem with error.
**** Log buffer [000001] 2020-09-30_13:20:41 ****
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 34.445] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.445] Check qboot_log.txt for more details
[ 34.445] Total time: 34.446s
[ 34.445]
[ 34.445] qboot version 3.86
[ 34.445]
[ 34.445] DEVICE {
[ 34.445] name = "\\.\COM3",
[ 34.445] flags = "0x64",
[ 34.445] addr = "0x62FD54",
[ 34.445] api.bnr = "0x1102BE0",
[ 34.445] }
[ 34.445]
[ 34.445]
[ 34.445] Backup & Restore {
[ 34.445] num_entries = 0,
[ 34.445] restoring = "false",
[ 34.445] backup_error = "not started",
[ 34.445] restore_error = "not started",
[ 34.445] }
Please anyone can provide me blankflash file for Motorola X4 XT1900-2. And suggest any other solution so that I can reboot my device, unbrick, . I'm on Android 9 with last latest update. please help me.

siddh315 said:
Hello Everyone. Please help me un bricking moto X4.
1) First, I'm new to this field.
2) My Moto X4 is totally dead and no sign of life. No fastboot, no recovery and none of the key works.
One thing I want to say that my device is totally intact. I have never try to root or unlock this. The device is in stock condition with the last latest update. Day before I was just using its hotspot to access internet on my PC. I don't know when it get switched off. And till then no sign of life on my moto x4. Can't even see whether it is charging or not? I tried to flash firmware but stuck with errors. I have read blankflash can be helpful but didn't find a blankflash for moto X4 XT1900-2. I also tried a blankflash file but stuck at a problem with error.
**** Log buffer [000001] 2020-09-30_13:20:41 ****
[ 0.000] Opening device: \.\COM3
[ 0.002] Detecting device
[ 34.445] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.445] Check qboot_log.txt for more details
[ 34.445] Total time: 34.446s
[ 34.445]
[ 34.445] qboot version 3.86
[ 34.445]
[ 34.445] DEVICE {
[ 34.445] name = "\.\COM3",
[ 34.445] flags = "0x64",
[ 34.445] addr = "0x62FD54",
[ 34.445] api.bnr = "0x1102BE0",
[ 34.445] }
[ 34.445]
[ 34.445]
[ 34.445] Backup & Restore {
[ 34.445] num_entries = 0,
[ 34.445] restoring = "false",
[ 34.445] backup_error = "not started",
[ 34.445] restore_error = "not started",
[ 34.445] }
Please anyone can provide me blankflash file for Motorola X4 XT1900-2. And suggest any other solution so that I can reboot my device, unbrick, . I'm on Android 9 with last latest update. please help me.
Click to expand...
Click to collapse
Window 10?
Sent from my ocean using XDA Labs

sd_shadow said:
Window 10?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Yeah, WIndows 10, 64 bit with 20H1 update.

siddh315 said:
Yeah, WIndows 10, 64 bit with 20H1 update.
Click to expand...
Click to collapse
It shows in Device Manager as ?
Qualcomm HS-USB QDLoader 9008 or
Qualcomm QHSUSB_Bulk

sd_shadow said:
It shows in Device Manager as ?
Qualcomm HS-USB QDLoader 9008 or
Qualcomm QHSUSB_Bulk
Click to expand...
Click to collapse
it is Qualcomm HS-USB QDLoader 9008

Anyone who have qcn file for Moto x4

Moto G6 XT1925-6 "bricked" from normal use--blankflash not working

Hi all,
My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white light blinks every second or so, and the phone shows up as the following USB device (port):
Qualcomm HS-USB QDLoader 9008 (COM4)
I have tried 3-4 different blankflash files numerous times (including the two from https://mirrors.lolinet.com/firmware/moto/ali/blankflash/) and always get an IO error. The phone would have been fully updated as of 11/1, it was being used on Cricket Wireless if that matters. Lenovo Moto Smart Assistant was no help unfortunately since the phone cannot boot into fastboot.
I tried again today since one 'fix' seemed to be to let the battery discharge. It was unplugged for ~5 days and no change.
Any other tips/tricks or am I SOL? She was somewhat due for an upgrade anyways, but thought I'd try one last time to look for other solutions.
Thanks!

timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!

armrbackthrsday said:
timing is absolutely critical in EDL mode - i.e., you don't have long to start the flashing once you plug the USB cable in. sounds like you have the correct drivers, given that the phone shows up properly in device manager. try the following in quick succession:
0. plug the USB cable into the computer (not the phone, yet)
1. start the blankflash script from lolinet
2. depress and hold the power and volume_down buttons
3. connect the USB cable
4. script will do its magic (release the buttons) and reboot the phone to the bootloader
hope this helps!
Click to expand...
Click to collapse
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

Heat84 said:
Exactly when are you supposed to release the buttons? No matter when I do, I get:
ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?

armrbackthrsday said:
hmm, sounds like the blankflash script is not recognizing the correct COM port. does the device show up as "Qualcomm HS-USB QDLoader 9008" in device manager?
Click to expand...
Click to collapse

I fixed that problem by rebooting the phone while qflash was running. Now I have a different error that you see below at 3. 485.
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
I don't actually have to worry about this any more because I was tired of playing around and took the phone(a Motorola Edge plain 2020) back to Best Buy where I got it, and they couldn't fix it, but they did offer to exchange it for a new one. I chose an "open box" one that probably was returned the day after it was bought by the first owner for some stupid reason. I also got a $74 refund to even the exchange(I would've had to wait a week for a new one or choose a different make and/or model phone available in store otherwise). But don't let that stop you from offering a translation to this error message if you have one. I'm curious and you may help someone else.
Why would the developer of Qboot not have any documentation of what the error messages mean? What's the point of writing error messages if you don't tell anybody what they mean? Was that done out of arrogance or stupidity? Also, when it says to check qboot log for details, that BS. Everything you see during the flash attempt on screen is all you see in the log. Nothing more.
By the way if you're interested, I started a thread about my problem before I found this one: https://forum.xda-developers.com/t/...hard-hard-bricked-edge.4341829/#post-85717539
By the way 2: It seems to be a weird coincidence that you resurrected this thread almost a year after the last (and only) post at the SAME TIME I was having the same issue they were. Even though you didn't help me and I don't need the help anymore, you gotta admit that that's a little creepy. lol