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

Moto Z3 Play Hard Bricked

Tryng to root my device (XT1929-6), I bricked the phone. After installing the motorola device manager, i tried to blankflash the phone, but thats the log
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 204 (0xcc)
[ 0.000] ...cpu.sn = 3748563624 (0xdf6e8aa8)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.016] Failed identify board. Wrong package?
[ 0.016] ERROR: error loading package
[ 0.016] Check qboot_log.txt for more details
[ 0.016] Total time: 0.031s
FAILED: qb_flash_singleimage()->error loading package
Please help! I am not 100% certain where this thread must to be, if I am wrong tell me.

And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..

Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.

Teto Balsámico said:
I tried to use SuperSU zip file to root. I wasn't able to install TWRP, for installing supersu I used "fastboot boot TWRP.img" beacause the phone doesn't have a recovery partition. When i tried to install supersu, it returned "Unable to mount /vendor (busy)" (not full message beacause i don't have acces to the logs), then y tried to fix "vendor using the repair tool of twrp, and after the restart it was full bricked. Actually windows sometimes detects the device if you press power button and vol down, but it can't recognise the type of device.
Click to expand...
Click to collapse
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.

Willy33 said:
And how did you try to get the root? More details can be? In general, for our device, there is no right blankflash, unfortunately ((
.......And yes, you already I understand the third person with a brick ..
Click to expand...
Click to collapse
Willy33 said:
I don’t understand why it was to invent with su when a working method for getting root rights using magisk and even without twrp was already described here, but this is not the point ... you need to install the necessary drivers for blankflash and the phone is defined as Qualcomm 9008 , and after that start blankflash. But as I said earlier, there is no blankflash file yet, just for our phone.
Click to expand...
Click to collapse
And how do i get those drivers? And where i can see how the computer recognises the mobile as Qualcomm 9008? just for the time being.

Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.

Willy33 said:
Internet spaces help very well))) it is enough to drive in Qualcomm 9008 and that's it. And to look naturally in the windows device manager.
and on YouTube you can even find instructions on how to properly install these drivers.
Click to expand...
Click to collapse
Thanks for your help!

I have the same problem. Could you fix the error?

Do I have to do something else for linux to detect my moto z3? Windows detects it without problem, but it always shows an error when reading the storage

Help..
E:\Descargas\qualkom dri>.\qboot.exe blank-flash
Motorola qboot utility version 3.86
[ 0.002] Opening device: \\.\COM4
[ 0.238] Detecting device
[ 0.248] ...cpu.id = 204 (0xcc)
[ 0.248] ...cpu.sn = 2761611797 (0xa49ada15)
[ 0.249] Opening singleimage
[ 0.594] Loading package
[ 0.603] ...filename = pkg.xml
[ 0.606] Loading programmer
[ 0.637] ...filename = programmer.elf
[ 0.638] Sending programmer
[ 0.832] Handling things over to programmer
[ 0.833] Identifying CPU version
[ 0.833] Waiting for firehose to get ready
[ 4.132] ...SDM636 1.0
[ 4.134] Determining target secure state
[ 4.137] ...secure = yes
[ 4.200] Configuring device...
[ 4.211] Flashing GPT...
[ 4.212] Flashing partition with gpt.bin
[ 4.221] Initializing storage
[ 4.300] ...blksz = 512
[ 4.521] Target NAK!
[ 4.521] ...ERROR: SDCC Error 29 (3)
[ 4.521] ...ERROR: Write Failed sector 0, size 48
[ 4.522] ...ERROR: Failed to write 1 slot 0, partition 0, start_sector 48 num_sectors 0, error 3
[ 4.522] ...Finished programming start_sector 48 and TotalSectorsToProgram 48
[ 4.522] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK
[ 4.523] Check qboot_log.txt for more details
[ 4.524] Total time: 4.538s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->lun_write()->storage_write()->firehose_do_fmt()->do_recipe()->NAK

Brand new Moto X4 bricked with Lineage 16.0 payton

Two days ago I purchased a new Moto X4 XT1900-1 and eagerly installed lineage-16.0-20190311-nightly-payton-signed.zip, only to brick my phone. It no longer turns on, but it does appear in syslog:
Code:
Mar 14 07:59:59 mint kernel: [ 2846.234567] usb 3-3: new high-speed USB device number 11 using xhci_hcd
Mar 14 07:59:59 mint kernel: [ 2846.389413] usb 3-3: New USB device found, idVendor=05c6, idProduct=9008
Mar 14 07:59:59 mint kernel: [ 2846.389415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 14 07:59:59 mint kernel: [ 2846.389416] usb 3-3: Product: QUSB__BULK
Mar 14 07:59:59 mint kernel: [ 2846.389417] usb 3-3: Manufacturer: Qualcomm CDMA Technologies MSM
Mar 14 07:59:59 mint kernel: [ 2846.390291] qcserial 3-3:1.0: Qualcomm USB modem converter detected
Mar 14 07:59:59 mint kernel: [ 2846.390354] usb 3-3: Qualcomm USB modem converter now attached to ttyUSB0
Mar 14 07:59:59 mint mtp-probe: checking bus 3, device 11: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-3"
Mar 14 07:59:59 mint mtp-probe: bus: 3, device: 11 was not an MTP device
Mar 14 07:59:59 mint upowerd[1768]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0
Mar 14 07:59:59 mint upowerd[1768]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-3
I found this thread: reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319, where @erfanoabdi indicated it was a known issue and recoverable.
I downloaded the blankflash from drive.google.com/file/d/1XWPW7qEYhWqi6lL-1308GgmFht98BiV5/view and followed the steps as described at reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319/eicp5sy/
The output of blank-flash.sh is
Code:
[email protected]:~/Downloads/blankflash$ ./blank-flash.sh
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
FAILED: qb_flash_singleimage()->device_open()->error opening device
The output of qboot_log.txt is
Code:
[email protected]:~/Downloads/blankflash$ cat qboot_log.txt
**** Log buffer [000001] 2019-03-14_08:18:31 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
[ 0.000]
[ 0.000] qboot version 3.86
[ 0.000]
[ 0.000] DEVICE {
[ 0.000] name = "/dev/ttyUSB0",
[ 0.000] flags = "0x60",
[ 0.000] addr = "0xA3CCC830",
[ 0.000] serial_nix.device_pathname = "/sys/bus/usb/devices/3-3/3-3:1.0/ttyUSB0",
[ 0.000] api.bnr = "0x1B535F0",
[ 0.000] }
[ 0.000]
[ 0.000]
[ 0.000] Backup & Restore {
[ 0.000] num_entries = 0,
[ 0.000] restoring = "false",
[ 0.000] backup_error = "not started",
[ 0.000] restore_error = "not started",
[ 0.000] }
[ 0.000]
I have tried running blank-flash.sh while holding down the Power Button + Vol Down Button, but the results are always the same.
HALP PLZ!!!!

dougfir said:
Two days ago I purchased a new Moto X4 XT1900-1 and eagerly installed lineage-16.0-20190311-nightly-payton-signed.zip, only to brick my phone. It no longer turns on, but it does appear in syslog:
I found this thread: reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319, where @erfanoabdi indicated it was a known issue and recoverable.
I downloaded the blankflash from drive.google.com/file/d/1XWPW7qEYhWqi6lL-1308GgmFht98BiV5/view and followed the steps as described at reddit.com/r/LineageOS/comments/b06uoi/moto_x4_payton_bricked_after_update_to_110319/eicp5sy/
The output of blank-flash.sh is
The output of qboot_log.txt is
I have tried running blank-flash.sh while holding down the Power Button + Vol Down Button, but the results are always the same.
HALP PLZ!!!!
Click to expand...
Click to collapse
Run it as root.
The power vol down combo is more an art than science.

serial_write Error Help
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​

Are you running as root?

ttyUSB Permissions Linux
gee one said:
Are you running as root?
Click to expand...
Click to collapse
Yes as root. Solved as an issue between the device showing up on /dev/ttyUSB0 initially on Linux. 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].

mistryous said:
Yes as root. Solved as an issue between the device showing up on /dev/ttyUSB0 initially on Linux. 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].
Click to expand...
Click to collapse
doing it as root but getting
Code:
serial_write(), line 280: Input/output error
please help!!!!

Struggling to recover Moto G6

I had my moto G6 in storage as I had upgraded and no longer needed it till today. I pulled it out and noticed it wouldn't turn on. I figured it was dead and plugged it in when I was promptly greeted with a fastboot menu and logs complaining the hab image couldn't be verified. Tried rebooting a couple times hoping for a fluke and alas, my luck is not good.
So I followed the recommendation on the screen and got the lovely Lenovo Rescue and Smart Assistant to reprogram my phone. It tried the first time and my phone ended up with a black screen and white LED blinking at 1Hz. After a time the Lenovo tool gave up and errored out. I held the power button for a minute and I was able to get back to the fastboot screen and figured I would just try again.
I tried a second time and it progressed further into the process before it did the same thing again. I am now with a phone that does little more than blink the white LED. But I do see that the CPU is in a EDL mode and enumerates as a COM port. I found this thread for the G6 Plus and was able to get some luck but the blankflash errored out (not surprised as it was for the plus and not the 'regular' G6).
[ULTIMATE GUIDE] How To Unbrick your Moto G6 Plus
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY AND IT'S NOT 100% GUARANTEED TO WORK. WORKED ON MY G6 PLUS (XT1926-7) AND SOME OTHER USERS ON WINDOWS. THINGS YOU WILL NEED: Motorola and Qualcomm Drivers; BlankFlash file; Stock ROM; STEPS: PART...
forum.xda-developers.com
I spent some time online and found this link:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I downloaded the PDS29.118-15-11-14 and gave that a try. I produced some results but ultimately ended in an error.
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 154 (0x9a)
[ 0.004] ...cpu.sn = 1862624572 (0x6f05653c)
[ 0.004] Opening singleimage
[ 0.012] Loading package
[ 0.015] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.265] Handling things over to programmer
[ 0.266] Identifying CPU version
[ 0.268] Waiting for firehose to get ready
[ 60.504] Waiting for firehose to get ready
[121.584] ...MSM8953 unknown
[121.584] Determining target secure state
[121.586] Waiting for firehose to get ready
[184.162] ...secure = no
[184.177] Waiting for firehose to get ready
[244.227] Configuring device...
[244.229] Waiting for firehose to get ready
[306.781] Waiting for firehose to get ready
[370.379] Waiting for firehose to get ready
[431.463] Waiting for firehose to get ready
[494.029] ERROR: do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[494.029] Check qboot_log.txt for more details
[494.029] Total time: 494.032s
[494.029]
[494.029] qboot version 3.40
[494.029]
[494.029] DEVICE {
[494.029] name = "\\.\COM3",
[494.029] flags = "0x64",
[494.029] addr = "0x61FE4C",
[494.029] sahara.current_mode = "0",
[494.029] api.buffer = "0x802020",
[494.029] cpu.serial = "1862624572",
[494.029] cpu.id = "154",
[494.029] cpu.sv_sbl = "0",
[494.029] cpu.name = "MSM8953",
[494.029] storage.type = "eMMC",
[494.029] sahara.programmer = "programmer.mbn",
[494.029] module.firehose = "0x6A1D30",
[494.029] cpu.ver = "0",
[494.029] cpu.vername = "unknown",
[494.029] api.bnr = "0x6AAAA8",
[494.029] }
[494.029]
[494.030]
[494.030] Backup & Restore {
[494.030] num_entries = 0,
[494.030] restoring = "false",
[494.030] backup_error = "not started",
[494.030] restore_error = "not started",
[494.030] }
[494.030]
I think the exact blankflash I am looking for might be called: PPS29.118_15_11_16_cid18
The reason I suspect this is because the image that the Lenovo tool was trying to download and install to the phone has a full name of:
ALI_AMZ_PPS29.118_15_11_16_cid18_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
Does anyone happen to have any suggestions? Would be cool to get this phone back from the dead, no matter what ROM ends up on it.
Thanks in advance

Moto G5s Plus (XT1805) in Hardbrick, need help please

Hi everybody
I'm new to this Forum and now after 3 days of researching this site (and nearly the whole internet ) for solving this issue
i have to post this, hoping someone can help me.
What it is about?
Next to me lies the Motorola Moto G5s Plus (XT1805) EU Model from my mother.​And as i now can say it is Hardbricked, because it will no longer turn on, no fastboot mode, no Recovery mode ...nothing.​Just a black screen and no response to any button pushes.​All what it is doing: when i plug the USB cable in, whether Power socket or Laptop, the LED in the top left corner​is continuous flashing.​Also the laptop shows "Qualcomm HS-USB QDLoader 9008" in the "Ports"-Section of the device manager.​
What i did so far?
First, as i read, i left the phone untouched and unplugged for 24 hrs. Hoping it will charge when i plug it back in and let it for a hour or so.
After that i tried to switch it on with the powercord plugged in and pushing the power button ->nothing
Then i tried the VOL- + Power Button combo for Fastboot Mode ->nothing
The same two steps with unplugged powercord ->nothing
Then i did further research and after a long time i've finally found a specific Blankflash for this mobile phone ->HERE​I downloaded it, connected the phone to the Laptop and started the "blank-flash.bat".​​Well, it aborted. This is what the Log-File has written:​​
Spoiler
**** Log buffer [000001] 2023-01-08_21:30:15 ****
[ -0.000] Opening device: \\.\COM4
[ 0.006] Detecting device
[ 0.015] ...cpu.id = 70 (0x46)
[ 0.015] ...cpu.sn = 1802228975 (0x6b6bd4ef)
[ 0.016] Opening singleimage
[ 0.018] Loading package
[ 0.022] ...filename = singleimage.pkg.xml
[ 0.026] Loading programmer
[ 0.028] ...filename = programmer.mbn
[ 0.030] Sending programmer
[ 0.281] Handling things over to programmer
[ 0.281] Identifying CPU version
[ 0.281] Waiting for firehose to get ready
[ 60.626] Waiting for firehose to get ready
[122.241] ...MSM8953 unknown
[122.241] Determining target secure state
[122.241] Waiting for firehose to get ready
[183.829] ...secure = no
[183.844] Waiting for firehose to get ready
[245.913] Configuring device...
[245.915] Waiting for firehose to get ready
[305.971] Waiting for firehose to get ready
[366.032] Waiting for firehose to get ready
[428.615] Waiting for firehose to get ready
[489.666] ERROR: do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[489.666] Check qboot_log.txt for more details
[489.666] Total time: 489.669s
[489.666]
[489.666] qboot version 3.40
[489.666]
[489.666] DEVICE {
[489.666] name = "\\.\COM4",
[489.666] flags = "0x64",
[489.666] addr = "0x61FE4C",
[489.666] sahara.current_mode = "0",
[489.666] api.buffer = "0x133D020",
[489.666] cpu.serial = "1802228975",
[489.666] cpu.id = "70",
[489.666] cpu.sv_sbl = "0",
[489.666] cpu.name = "MSM8953",
[489.666] storage.type = "eMMC",
[489.666] sahara.programmer = "programmer.mbn",
[489.666] module.firehose = "0xFEE7A8",
[489.666] cpu.ver = "0",
[489.666] cpu.vername = "unknown",
[489.666] api.bnr = "0xE689F8",
[489.666] }
[489.666]
[489.666]
[489.666] Backup & Restore {
[489.666] num_entries = 0,
[489.666] restoring = "false",
[489.666] backup_error = "not started",
[489.666] restore_error = "not started",
[489.666] }
[489.666]
​
​In prepare for when the Blankflash works i already downloaded an official Firmware for the XT1805 model from ->HERE
Now I'm stuck and don't know what to do next; or as we say in germany: "Ich bin mit meinem Latein am Ende"
I would really appreciate it if someone could help me
thanks in advance

Nobody?