Struggling to recover Moto G6 - Moto G6 Questions & Answers

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

Related

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 G6 HardBricked after update! Help me please! :(

Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
davigiolo said:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
Click to expand...
Click to collapse
I believe you can enter download mode, or fastboot mode by doing the following:
1. First of all, turn off your phone – press power button and then select “power off”.
2. The USB cord must be near you, as a connection between your device and your computer must be established at some point.
3. Press and hold the volume down button on your Moto G.
4. While pressing the mentioned key also press Power button.
5. Now connect your Moto G with your computer by plugging in the USB cable.
6. Download mode / bootloader mode should now be installed – some drivers might be installed automatically.
From here you can reflash the stock rom. As long as your bootloader is unlocked, its ALMOST impossible to hardbrick your phone.
davigiolo said:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
Click to expand...
Click to collapse
Sahara is the g7....
What the heck are talking g6 stuff for? Wrong phone, firmware, forum, everything.
madbat99 said:
Sahara is the g7....
What the heck are talking g6 stuff for? Wrong phone, firmware, forum, everything.
Click to expand...
Click to collapse
What the heck... ??
1. G7 is called "river"
2. There isn't any Moto device which is called "sahara"
3. Sahara is a GUI tool for working with devices in Qualcomm DLOAD mode (bricked devices)!! So the "sahara_downloader" doesn't stand in any relationship to the Moto G7!!!
WoKoschekk said:
What the heck... ??
1. G7 is called "river"
2. There isn't any Moto device which is called "sahara"
3. Sahara is a GUI tool for working with devices in Qualcomm DLOAD mode (bricked devices)!! So the "sahara_downloader" doesn't stand in any relationship to the Moto G7!!!
Click to expand...
Click to collapse
Yep, I misread "Sahara"
There are some g7's called "lake(plus) and River"
My mistake.
Same problem
davigiolo said:
Hello guys, I bought a motorola g6 some time ago. It was rooted. I went back to rom stock to remove root and installed it normally, but the phone updated, and after didn't turn on anymore, even pressing the power and volume buttons. It only turns on a led light when plugged into the computer.. I already followed the steps from the topic below, but my phone is G6, not G6 Plus
https://forum.xda-developers.com/g6-plus/how-to/ultimate-guide-how-to-unbrick-moto-g6-t3862927
This is the blankflash error
*** Log buffer [000001] 2019-08-17_19:01:29 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 154 (0x9a)
[ 0.005] ...cpu.sn = 2421618069 (0x9056f595)
[ 0.005] Opening singleimage
[ 0.052] Loading package
[ 0.056] ...filename = singleimage.pkg.xml
[ 0.058] Loading programmer
[ 0.058] ...filename = programmer.mbn
[ 0.059] Sending programmer
[ 1.063] ERROR: sahara_download()->IO error
[ 1.063] Check qboot_log.txt for more details
[ 1.063] Total time: 1.063s
[ 1.064]
[ 1.064] qboot version 3.40
[ 1.064]
[ 1.064] DEVICE {
[ 1.064] name = "\\.\COM5",
[ 1.064] flags = "0x64",
[ 1.064] addr = "0x61FE4C",
[ 1.064] sahara.current_mode = "0",
[ 1.064] api.buffer = "0x1400020",
[ 1.064] cpu.serial = "2421618069",
[ 1.064] cpu.id = "154",
[ 1.064] cpu.sv_sbl = "0",
[ 1.064] cpu.name = "MSM8953",
[ 1.064] storage.type = "eMMC",
[ 1.064] sahara.programmer = "programmer.mbn",
[ 1.064] api.bnr = "0x1345FF8",
[ 1.064] }
[ 1.064]
[ 1.064]
[ 1.064] Backup & Restore {
[ 1.064] num_entries = 0,
[ 1.064] restoring = "false",
[ 1.064] backup_error = "not started",
[ 1.064] restore_error = "not started",
[ 1.064] }
[ 1.064]
I don't know if an upgrade could damage the motherboard.
I really hope you can help me, I'm realy sad, new phone
Click to expand...
Click to collapse
I have de same problem, only blinking led when you plug it to usb, nothing else.
Did you figure out how to solve it?
nibx said:
I have de same problem, only blinking led when you plug it to usb, nothing else.
Did you figure out how to solve it?
Click to expand...
Click to collapse
Hello dear happy owners of Moto G6 bricks.
Please, would you be so kind as to accept me into your team of elite owners of useless nutcrackers based on the Motorola Moto G6.
My XT1925-5 device was also hardbricked, after upgrading to Android 9.0 Pie and installing the latest security updates.
Also, when trying to flash the blankflash_PPS29.26 utility.bat receive
error: Sahara Download IO Error.
Email me if there are any positive results when getting a smartphone memory dump and creating a new blankflash for the latest OTA.
This is my contact email ([email protected]) if there are people willing to collaborate to write a new Blank Flash together.
ZulC_Silence said:
Hello dear happy owners of Moto G6 bricks.
Please, would you be so kind as to accept me into your team of elite owners of useless nutcrackers based on the Motorola Moto G6.
My XT1925-5 device was also hardbricked, after upgrading to Android 9.0 Pie and installing the latest security updates.
Also, when trying to flash the blankflash_PPS29.26 utility.bat receive
error: Sahara Download IO Error.
Email me if there are any positive results when getting a smartphone memory dump and creating a new blankflash for the latest OTA.
This is my contact email ([email protected]) if there are people willing to collaborate to write a new Blank Flash together.
Click to expand...
Click to collapse
Flash the latest RETAIL (PPSS29.55...) from here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ with RSD Lite 6.2.4, this happened to me days ago with a XT1925-2 RETLA and this was the way to recover it.
pdloud said:
Flash the latest RETAIL (PPSS29.55...) from here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ with RSD Lite 6.2.4, this happened to me days ago with a XT1925-2 RETLA and this was the way to recover it.
Click to expand...
Click to collapse
I do not understand, please tell me the algorithm of actions?
I have the official firmware for XT1925-5 for Android 9 Pie ,you can get SBL1 from it.bin, SingleImage.Bin.
And redo BlankFlash_from_29. 26 for my firmware version?
ZulC_Silence said:
I do not understand, please tell me the algorithm of actions?
I have the official firmware for XT1925-5 for Android 9 Pie ,you can get SBL1 from it.bin, SingleImage.Bin.
And redo BlankFlash_from_29. 26 for my firmware version?
Click to expand...
Click to collapse
I have an XT1295-2 RETLA and there is no official Pie firmware for this model, so what happened to me was that I've received an update and the OTA bricked my device, what I did was:
1.- Downloaded de latest RETAIL Pie firmware from the link I've posted before.
2.- Flashed this firmware with RSDLite (I've tried to flash it manually but no luck).
3.- Nothing else, the device booted without problems.
pdloud said:
I have an XT1295-2 RETLA and there is no official Pie firmware for this model, so what happened to me was that I've received an update and the OTA bricked my device, what I did was:
1.- Downloaded de latest RETAIL Pie firmware from the link I've posted before.
2.- Flashed this firmware with RSDLite (I've tried to flash it manually but no luck).
3.- Nothing else, the device booted without problems.
Click to expand...
Click to collapse
thank you for your answer.
ZulC_Silence said:
I do not understand, please tell me the algorithm of actions?
I have the official firmware for XT1925-5 for Android 9 Pie ,you can get SBL1 from it.bin, SingleImage.Bin.
And redo BlankFlash_from_29. 26 for my firmware version?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ali/official/RETRU/
XT1925-5_ALI_RETRU_9.0_PPSS29.55-37-7-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Thats the image you want to flash. As long as you can still boot into fastboot mode you can recover.
theseeker2654 said:
https://mirrors.lolinet.com/firmware/moto/ali/official/RETRU/
XT1925-5_ALI_RETRU_9.0_PPSS29.55-37-7-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Thats the image you want to flash. As long as you can still boot into fastboot mode you can recover.
Click to expand...
Click to collapse
I can 't boot in any way at all.
Fastboot doesn 't see the device.
It is only defined as Qualcomm HS-USB QDloader 9008.
Neither fastboot nor Qfill.exe does not see the device.
Here you need a working blank flash.bin, specifically for my version of the SOFTWARE (PPSS29.55-37-4-3), which will be kindly merged with Motorola's technical servers .
Otherwise, there is no way to restore the loader Chains.

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

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?

Categories

Resources