Develop Bugs

XT1789-01 HS-USB QLoader 9008?

Just got a XT1789-01 from a friend whos daughters phone just abruptly stopped working. No signs of life, except when plugged in to a computer I see the QLoader 9008 driver load. I tried some blank flash that says to bring the booloader back but it did nothing but say Generic Error. The tool does seem to detect the phone though.
Any ideas? The girl that uses this phone is like 10 so I know its not been tampered with software wise to cause this.
Motorola devices are not my cup of tea when it comes to flashing.
Thanks!

https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
At the bottom of the post is a link for qualcomm diag drivers, signed for windows.
Attached is the unbrick.zip, use the drivers mentioned above though. Basically unplug your phone and install the drivers, reboot pc and plug in, wait for the drivers to recognize and settle, then blankflash. Afterwards you'll be in a clean bootloader. Flash the latest firmware for your variant. This thread has instructions and links for flashing firmwares, just make sure it's for your variant. You can also try using the lmsa tool mentioned in post #275 to flash the firmware needed.

41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
At the bottom of the post is a link for qualcomm diag drivers, signed for windows.
Attached is the unbrick.zip, use the drivers mentioned above though. Basically unplug your phone and install the drivers, reboot pc and plug in, wait for the drivers to recognize and settle, then blankflash. Afterwards you'll be in a clean bootloader. Flash the latest firmware for your variant. This thread has instructions and links for flashing firmwares, just make sure it's for your variant. You can also try using the lmsa tool mentioned in post #275 to flash the firmware needed.
Click to expand...
Click to collapse
Thanks. But I still get "FAILED General error" on the blank flash.
C:\1>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 3695693525 (0xdc47ced5)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.016] ReadFile() failed, GetLastError()=0
[ 0.342] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.344] ERROR: sahara_download()->general error
[ 0.344] Check qboot_log.txt for more details
[ 0.345] Total time: 0.346s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\1>pause
Press any key to continue . . .

hyelton said:
Thanks. But I still get "FAILED General error" on the blank flash.
C:\1>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 3695693525 (0xdc47ced5)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.007] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.016] ReadFile() failed, GetLastError()=0
[ 0.342] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.344] ERROR: sahara_download()->general error
[ 0.344] Check qboot_log.txt for more details
[ 0.345] Total time: 0.346s
FAILED: qb_flash_singleimage()->sahara_download()->general error
C:\1>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Try holding pwr+vol down, then execute the bat file

Same exact error

hyelton said:
Same exact error
Click to expand...
Click to collapse
I've only had to use that once and I didn't run into problems. Double check that the right driver is installed in your device manager, make sure you're running admin prompt (best from the folder so the path is all set). Try executing the command then plug in your phone. Make sure you're using a 2.0 usb port off the mobo and not a hub or 3+ port. Outside of those suggestions I can't help, I don't know the error correlation. I know some had issues getting to to go, but ultimately it was "things just clicked and worked this time" scenario.
The post where you got the drivers has links to unbricking guides, check those if needed.

41rw4lk said:
I've only had to use that once and I didn't run into problems. Double check that the right driver is installed in your device manager, make sure you're running admin prompt (best from the folder so the path is all set). Try executing the command then plug in your phone. Make sure you're using a 2.0 usb port off the mobo and not a hub or 3+ port. Outside of those suggestions I can't help, I don't know the error correlation. I know some had issues getting to to go, but ultimately it was "things just clicked and worked this time" scenario.
The post where you got the drivers has links to unbricking guides, check those if needed.
Click to expand...
Click to collapse
Yeah drivers are correct, laptop and desktop both usb 2.0 and 3.0 has been tried. Different usb cables, I’m assuming something has went wrong with this phone. As it’s never been tampered with. So I’ll give it a few more goes before giving up on it.
Sent from my iPhone using Tapatalk

which blank flash did you try N or O?

Same here, I think we need an updated blankflash
**** Log buffer [000001] 2019-03-14_20:10:40 ****
[ 0.000] Opening device: \\.\COM3
[ 0.004] Detecting device
[ 0.008] ...cpu.id = 94 (0x5e)
[ 0.008] ...cpu.sn = 4062057235 (0xf21e1313)
[ 0.009] Opening singleimage
[ 0.015] Loading package
[ 0.027] ...filename = pkg.xml
[ 0.037] Loading programmer
[ 0.040] ...filename = programmer.elf
[ 0.040] Sending programmer
[ 0.100] ReadFile() failed, GetLastError()=0
[ 0.370] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.454] ERROR: sahara_download()->general error
[ 0.457] Check qboot_log.txt for more details
[ 0.475] Total time: 0.489s
[ 0.485]
[ 0.485] qboot version 3.85
[ 0.485]
[ 0.485] DEVICE {
[ 0.485] name = "\\.\COM3",
[ 0.485] flags = "0x64",
[ 0.485] addr = "0x28FD64",
[ 0.485] sahara.current_mode = "0",
[ 0.485] api.buffer = "0x2525020",
[ 0.485] cpu.serial = "4062057235",
[ 0.485] cpu.id = "94",
[ 0.485] cpu.sv_sbl = "15",
[ 0.485] cpu.name = "MSM8998",
[ 0.485] storage.type = "UFS",
[ 0.485] sahara.programmer = "programmer.elf",
[ 0.485] api.bnr = "0x475FF8",
[ 0.485] }
[ 0.485]
[ 0.485]
[ 0.485] Backup & Restore {
[ 0.485] num_entries = 0,
[ 0.485] restoring = "false",
[ 0.485] backup_error = "not started",
[ 0.485] restore_error = "not started",
[ 0.485] }
[ 0.485]

Same problem here!
I think that I need some updated blankflash files. I have tried to found in 4PDA, but the link was removed, the file name was "blankflash_SPRINT_8.0.0_OCXS27.109-48-6.zip" or " blankflash_VZW_8.0.0_ODXS27.109-34-12_12.zip". I have a xt1789-05, dual sim, but I think these files can save me! Anyone have these files? Thanks.

i have this error, can you help me?
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM5",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0x1D2D70",
[ 0.001] }
[ 0.001]
[ 0.001]
[ 0.001] Backup & Restore {
[ 0.001] num_entries = 0,
[ 0.001] restoring = "false",
[ 0.001] backup_error = "not started",
[ 0.001] restore_error = "not started",
[ 0.001] }
[ 0.001]

XxeAgLeAnGeLxX said:
i have this error, can you help me?
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM5",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0x1D2D70",
[ 0.001] }
[ 0.001]
[ 0.001]
[ 0.001] Backup & Restore {
[ 0.001] num_entries = 0,
[ 0.001] restoring = "false",
[ 0.001] backup_error = "not started",
[ 0.001] restore_error = "not started",
[ 0.001] }
[ 0.001]
Click to expand...
Click to collapse
I was experiencing this exact same issue when running the blankflash. I ran it several times only to receive the same error over and over.
Did you put your device into EDL Mode or did it happen after a bad flash?
Do you know if your bootloader is still intact? Do you know how to exit EDL Mode to get back to the bootloader?
Here is what you do...
Since you are in EDL Mode trying to run the blankflash, get everything set up like you are about to run the blankflash again. Connect your device and verify it is connected in the Device Manager. Press and Hold Volume Down + Power and double-click the file to run the blankflash. Continue holding the Volume Down + Power while attempting to run the blankflash and if your bootloader is still intact this will take you back into the bootloader. It may take a few attempts to get back. Just keep holding the Volume Down + Power and double clicking the blankflash file until it takes you back to the bootloader.
Now, this is assuming that your bootloader is still intact. If it is and you can get back to the bootloader then you can run a flash-all for your device that matches the software you were running and get your device back to an operational state. Good luck.

pekenolucas said:
I think that I need some updated blankflash files. I have tried to found in 4PDA, but the link was removed, the file name was "blankflash_SPRINT_8.0.0_OCXS27.109-48-6.zip" or " blankflash_VZW_8.0.0_ODXS27.109-34-12_12.zip". I have a xt1789-05, dual sim, but I think these files can save me! Anyone have these files? Thanks.
Click to expand...
Click to collapse
Follow this guide it has worked for many. Make sure you read it all first, and make sure your phone is in edl mode. Your phone will have a blank screen but you'll see HS-USB QLoader 9008 in your device manager when connected to your pc.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

Blank flash after reomal of battery works
hyelton said:
Just got a XT1789-01 from a friend whos daughters phone just abruptly stopped working. No signs of life, except when plugged in to a computer I see the QLoader 9008 driver load. I tried some blank flash that says to bring the booloader back but it did nothing but say Generic Error. The tool does seem to detect the phone though.
Any ideas? The girl that uses this phone is like 10 so I know its not been tampered with software wise to cause this.
Motorola devices are not my cup of tea when it comes to flashing.
Thanks!
Click to expand...
Click to collapse
Dear remove battery and then blank flash it will work

XT1789-05 Need blankflash to unbrick

Hi. Sorry my english)
I bought a phone on Ali. I tried to install LOS16, but after flashing the phone became a black screen and QUSB_BULK.
The phone was Android 8.0.0 retcn.
When I try to restore blankflash_oreo, I get the following errors:
Code:
**** Log buffer [000001] 2019-05-01_23:10:10 ****
[ 0.000] Opening device: \\.\COM7
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 94 (0x5e)
[ 0.005] ...cpu.sn = 2549234984 (0x97f23d28)
[ 0.005] Opening singleimage
[ 0.006] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.012] ...filename = programmer.elf
[ 0.012] Sending programmer
[ 0.084] ReadFile() failed, GetLastError()=0
[ 0.390] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 0.390] ERROR: sahara_download()->general error
[ 0.391] Check qboot_log.txt for more details
[ 0.391] Total time: 0.391s
[ 0.391]
[ 0.391] qboot version 3.85
[ 0.391]
[ 0.391] DEVICE {
[ 0.391] name = "\\.\COM7",
[ 0.391] flags = "0x64",
[ 0.391] addr = "0x28FD64",
[ 0.391] sahara.current_mode = "0",
[ 0.391] api.buffer = "0x2145020",
[ 0.391] cpu.serial = "2549234984",
[ 0.391] cpu.id = "94",
[ 0.391] cpu.sv_sbl = "0",
[ 0.391] cpu.name = "MSM8998",
[ 0.391] storage.type = "UFS",
[ 0.391] sahara.programmer = "programmer.elf",
[ 0.391] api.bnr = "0x2085FF8",
[ 0.391] }
[ 0.391]
[ 0.391]
[ 0.391] Backup & Restore {
[ 0.391] num_entries = 0,
[ 0.391] restoring = "false",
[ 0.391] backup_error = "not started",
[ 0.391] restore_error = "not started",
[ 0.391] }
[ 0.391]
Please share blankflash on 1789-05 for 8.0.0

https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

Thanks, but not work
Code:
F:\1789-05\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 94 (0x5e)
[ 0.004] ...cpu.sn = 2549234984 (0x97f23d28)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.008] ...filename = pkg.xml
[ 0.010] Loading programmer
[ 0.011] ...filename = programmer.elf
[ 0.011] Sending programmer
[ 0.164] Handling things over to programmer
[ 0.164] Identifying CPU version
[ 0.166] Waiting for firehose to get ready
[ 29.142] ReadFile() failed, GetLastError()=0
[ 45.246] ReadFile() failed, GetLastError()=0
[141.851] ReadFile() failed, GetLastError()=0
[156.494] Waiting for firehose to get ready
[174.054] ReadFile() failed, GetLastError()=0
[190.155] ReadFile() failed, GetLastError()=0
[206.257] ReadFile() failed, GetLastError()=0
[217.966] ...MSM8998 unknown
[217.966] Determining target secure state
[217.968] Waiting for firehose to get ready
[222.356] ReadFile() failed, GetLastError()=0

Make sure you have the drivers installed, use a 2.0 usb port off the mobo. It can be finicky, so check your cable, check your drivers, use another port. It'll work. Some have had luck by unplugging the phone, starting the script, holding vol dwn, and replugging the phone. It can be finicky, just try it again.

I try more and more, but still not work.
I try: win vista x32, win 8.1 x64, win 10 x 64,
two cables, stock and other,
drivers qualcomm x32 and x64,
desktop and notebook, other port.
I try:
blankflash_from_NDX26.183-15_17
blankflash_oreo
blankflash_SPRINT_8.0.0_OCXS27.109-48-6
I don't know what to try yet.

MarkNsk87 said:
I try more and more, but still not work.
I try: win vista x32, win 8.1 x64, win 10 x 64,
two cables, stock and other,
drivers qualcomm x32 and x64,
desktop and notebook, other port.
I try:
blankflash_from_NDX26.183-15_17
blankflash_oreo
blankflash_SPRINT_8.0.0_OCXS27.109-48-6
I don't know what to try yet.
Click to expand...
Click to collapse
Idk if anyone has been successful using the oreo blankflash, the one I linked to has been used successfully many times, so use that one. Verify that the proper driver is assigned to the phone in your device manager, and make sure you're using an administrator cmd prompt. Might try uninstalling the drivers, reboot pc, reinstall drivers, reboot pc, plug in the phone and let everything recognize and settle, verify drivers in device manager, open admin prompt and go for it with the ndx (nougat) blankflash.

I reinstalled the driver, rebooted and tried to execute the command under the administrator, the log changed a little, but still unsuccessfully
Code:
**** Log buffer [000001] 2019-05-02_13:23:28 ****
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 12.844] ReadFile() failed, GetLastError()=0
[ 13.372] ...cpu.id = 94 (0x5e)
[ 13.372] ...cpu.sn = 2549234984 (0x97f23d28)
[ 13.372] Opening singleimage
[B][ 13.372] ERROR: error opening singleimage[/B]
[ 13.388] Check qboot_log.txt for more details
[ 13.388] Total time: 13.388s
[ 13.388]
[ 13.388] qboot version 3.85
[ 13.388]
[ 13.388] DEVICE {
[ 13.388] name = "\\.\COM3",
[ 13.388] flags = "0x64",
[ 13.388] addr = "0x28FD64",
[ 13.388] sahara.current_mode = "3",
[ 13.388] api.buffer = "0x25DB020",
[ 13.388] cpu.serial = "2549234984",
[ 13.388] cpu.id = "94",
[ 13.388] cpu.sv_sbl = "0",
[ 13.388] api.bnr = "0x5D2F78",
[ 13.388] }
[ 13.388]
[ 13.388]
[ 13.388] Backup & Restore {
[ 13.388] num_entries = 0,
[ 13.388] restoring = "false",
[ 13.388] backup_error = "not started",
[ 13.388] restore_error = "not started",
[ 13.388] }
[ 13.388]

Blankflash did not work because of the Motorola_Mobile_Drivers_v6.4.0 drivers, I don’t know how they interfere, but because of them there were errors reading the device and the blankflash did not work.
I worked on my body with blankflash_from_NDX26.183-15_17 - and this is a Verizon bout campaign, judging by the information in the bootloader.
Important all have brick: uninstall Motorola_Mobile_Drivers, before you start blankflash!

Don't wory Mark. I think I have the same gold retcn version of 1789-05. I tried flash some versions of LOS 15 and 16, always ends with Qualcomm mode. For me works blankflash from nougat, but only when battery is less than 10%. When my phone is fully charged, when I try blankflash the phone reconnect to pc. Take me a few evenings to figure it out. Works with Motorola drivers and Qualcomm certificate driver installed in the same time.
Now I have stock EU 8.0 and radio from retcn.
Works everything except Smart lock.
Good luck.
Wysłane z mojego Moto Z (2) przy użyciu Tapatalka

I get this error, can someone help me?
[ 0.000] Opening device: \\.\COM7
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 94 (0x5e)
[ 0.007] ...cpu.sn = 2357123697 (0x8c7eda71)
[ 0.007] Opening singleimage
[ 0.008] Loading package
[ 0.013] ...filename = pkg.xml
[ 0.015] Loading programmer
[ 0.017] ...filename = programmer.elf
[ 0.017] Sending programmer
[ 0.181] Handling things over to programmer
[ 0.182] Identifying CPU version
[ 0.185] Waiting for firehose to get ready
[ 3.642] ...MSM8998 2.1
[ 3.804] Determining target secure state
[ 3.987] ...secure = yes
[ 4.334] Configuring device...
[ 4.361] Skipping UFS provsioning as target is secure
[ 4.362] Configuring device...
[ 5.938] Target NAK!
[ 5.939] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 1
[ 5.939] ...ERROR: Failed to open the device 3 slot 0 partition 1
[ 5.940] ...INFO: Device type 3, slot 0, partition 1, error 0
[ 5.940] ...WARN: Set bootable failed to open 3 slot 0, partition 1, error 0
[ 5.940] ERROR: do_package()->do_recipe()->NAK
[ 5.942] Check qboot_log.txt for more details
[ 5.943] Total time: 5.946s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->NAK
Thank you

41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
thanks this method heleped me

you need a blank flash updated for your bootloader, theres at least 5 updates on oreo (OTA UPDATES), then you will need the latest blankflash compatible, maybe the Oreo blank flash that you found here is older than your bricked bootloader. (Sorry for my bad english)

iurd2007 said:
you need a blank flash updated for your bootloader, theres at least 5 updates on oreo (OTA UPDATES), then you will need the latest blankflash compatible, maybe the Oreo blank flash that you found here is older than your bricked bootloader. (Sorry for my bad english)
Click to expand...
Click to collapse
This is a bit of an old post, and I assume those issues are resolved, not sure who you're addressing. As far as oreo blankflash, there is one but as far as I know no one has had success with it. The one that I post frequently uses nougat believe it or not, but it has worked many many times even on oreo and there is no reason to mess with what works. Especially when it comes to blankflashing, it's usually your last chance to resolve the problem.

41rw4lk said:
This is a bit of an old post, and I assume those issues are resolved, not sure who you're addressing. As far as oreo blankflash, there is one but as far as I know no one has had success with it. The one that I post frequently uses nougat believe it or not, but it has worked many many times even on oreo and there is no reason to mess with what works. Especially when it comes to blankflashing, it's usually your last chance to resolve the problem.
Click to expand...
Click to collapse
To blankflash Oreo , you need oreo blankflash, but the last version. There is a oreo (soak test) but not the official stock. But recently someone post the final blankflash for the latest OTA.

iurd2007 said:
To blankflash Oreo , you need oreo blankflash, but the last version. There is a oreo (soak test) but not the official stock. But recently someone post the final blankflash for the latest OTA.
Click to expand...
Click to collapse
You're mistaken. I won't argue the point, by all means do what you will.

41rw4lk said:
You're mistaken. I won't argue the point, by all means do what you will.
Click to expand...
Click to collapse
Ok...

[Help]blank-flash failed (XT1789-3 unlocked) ERROR: sahara_greet_device,IO error

this phone is XT1789-3, its unlocked ,and im replaced it the 6GB RAM chip.Then it can only boot to bootloader,and can not refresh new Bootloader.so i need to flash a new GPT and bootloader .
i successed puted into EDL 9008 Model.but blank-flash faild.its said that:
[ -0.000] Opening device: \\.\COM10
[ 0.001] Detecting device
[ 34.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.008] Check qboot_log.txt for more details
[ 34.009] Total time: 34.011s
[ 34.009] qboot version 3.85
[ 34.009] DEVICE {
[ 34.009] name = "\\.\COM10",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x5B2898",
anyone know how to do it?
which 9008 should i need ?

did you reslove this? im having the same issue

Help with Hard Brick Z2 Force (XT1789-04 AT&T) Is Internal Memory Fried?

Hi, looking for a kind soul who can provide me with some insight or direction.
My Phone:
Moto Z2 Force XT1789-04 AT&T
Carrier unlocked with unlock code from AT&T to use T-Mobile SIM
Updated to either Build number: OCXS27.109-47-20 or Build number: OCXS27.109-47-23 using LMSA (not OTA)
Official build, never tried to root it
My Circumstance:
I was using fingerprint unlock and my login attempts were failing.
In a brief moment of frustration, and stupidity, I repeatedly retried FP unlock (probably 10+ times)
Display went dim and phone became unresponsive, and ultimately turned into a brick with no way to power on; nothing displayed when plugged in to charge.
My Attempts to Fix:
After trying various button reset options with no success, I plugged my phone into my PC and saw QUSB_BULK
Further searching led me to https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5 (thanks 41rw4lk)
I installed the Qualcomm driver and got Qualcomm HS-USB QDLoader 9008 to show up in Device Manager.
I tried blank-flash.bat using blankflash_from_NDX26.183-15_17 (again, thanks, 41rw4lk)
Here is the output from the batch command:
Code:
c:\Downloads\MOTOZ2FORCE\blankflash_from_NDX26.183-15_17>blank-flash.bat
c:\Downloads\MOTOZ2FORCE\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ -0.000] Opening device: \\.\COM4
[ -0.000] Detecting device
[ 0.016] ...cpu.id = 94 (0x5e)
[ 0.016] ...cpu.sn = 1009594148 (0x3c2d2f24)
[ 0.016] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.elf
[ 0.016] Sending programmer
[ 0.176] Handling things over to programmer
[ 0.176] Identifying CPU version
[ 0.176] Waiting for firehose to get ready
[ 3.200] ...MSM8998 2.1
[ 3.200] Determining target secure state
[ 3.200] ...secure = yes
[ 3.247] Configuring device...
[ 3.263] Skipping UFS provsioning as target is secure
[ 3.263] Configuring device...
[ 4.824] Target NAK!
[ 4.824] ...ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 1
[ 4.824] ...ERROR: Failed to open the device 3 slot 0 partition 1
[ 4.824] ...INFO: Device type 3, slot 0, partition 1, error 0
[ 4.824] ...WARN: Set bootable failed to open 3 slot 0, partition 1, error 0
[ 4.824] ERROR: do_package()->do_recipe()->NAK
[ 4.824] Check qboot_log.txt for more details
[ 4.824] Total time: 4.824s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->NAK
Here is the device info from the log:
Code:
[ 4.824] qboot version 3.85
[ 4.824]
[ 4.824] DEVICE {
[ 4.824] name = "\\.\COM4",
[ 4.824] flags = "0x144",
[ 4.824] addr = "0x62FD54",
[ 4.824] sahara.current_mode = "0",
[ 4.824] api.buffer = "0x29C4020",
[ 4.824] cpu.serial = "1009594148",
[ 4.824] cpu.id = "94",
[ 4.824] cpu.sv_sbl = "0",
[ 4.824] cpu.name = "MSM8998",
[ 4.824] storage.type = "UFS",
[ 4.824] sahara.programmer = "programmer.elf",
[ 4.824] module.firehose = "0x6D91C8",
[ 4.824] api.firehose = "0x721F50",
[ 4.824] cpu.ver = "513",
[ 4.824] cpu.vername = "2.1",
[ 4.824] fh.max_packet_sz = "1048576",
[ 4.824] fh.storage_inited = "1",
[ 4.824] }
So, best as I can decipher, the blank-flash is failing because it cannot create a filesystem on the internal memory.
I read something about A/B slots, but I'm starting to lose my way.
Am I done for?
Thanks for looking. Truly appreciate the folks in this community.

Wait! Am I using a Nougat blank-flash? Do I need an Oreo blank-flash? Is there one available for the XT1789-04?

lobbybee said:
Wait! Am I using a Nougat blank-flash? Do I need an Oreo blank-flash? Is there one available for the XT1789-04?
Click to expand...
Click to collapse
See if there is one on
https://mirrors.lolinet.com/firmware/moto
Sent from my Moto E (4) using Tapatalk

The Nougat blankflash is fine. The phone shipped with a Nougat pbl and the way I understand it is that can't be modified or upgraded, it can be reflashed with the same, but that's it. Don't quote me on that though. As for an Oreo blankflash, there is one, but I've never heard any success stories from it and Nougat has always done the trick.
I've seen that error before, it is speculated that maybe the storage is failing, but I don't know if anyone has ever been able to say 'yes, your storage is no good and that's why you get this error' etc. It maybe very well be the case and I'm not sure if those who have faced that error have been able to recover.
What version of windows are you running? Have you tried running as an admin, using different ports?
If you are on Win10 have you tried going old school and disabling integrity checks and turning test signing on? Win10 isn't very friendly when it comes to our phone, we recommend Win7 and command prompt, not powershell. So if you're using Win10 and haven't done the above, it's worth a shot.

41rw4lk said:
What version of windows are you running? Have you tried running as an admin, using different ports?
Click to expand...
Click to collapse
Previously on Win10 as Admin from CMD window.
Also just tried on Win7, per suggestion, with the same results.
I used 3 different USB2 ports on the PC, iterated through 3 different USB-C cables.
I found the --debug=2 flag for qboot.exe and started digging through the output. Now it's got me wondering:
1) Why is it specifying UFS instead of eMMC? Phonemore.com specs says it's UFS 2.1
2) It appears to be skipping storage initialization because "target is secure." Is blankflash failing b/c my bootloader was not unlocked before it bricked?
3) Should I look into using QFIL to manually configure the reinitialization of the file system, whether UFS or eMMC?

lobbybee said:
Previously on Win10 as Admin from CMD window.
Also just tried on Win7, per suggestion, with the same results.
I used 3 different USB2 ports on the PC, iterated through 3 different USB-C cables.
I found the --debug=2 flag for qboot.exe and started digging through the output. Now it's got me wondering:
1) Why is it specifying UFS instead of eMMC? Phonemore.com specs says it's UFS 2.1
2) It appears to be skipping storage initialization because "target is secure." Is blankflash failing b/c my bootloader was not unlocked before it bricked?
3) Should I look into using QFIL to manually configure the reinitialization of the file system, whether UFS or eMMC?
Click to expand...
Click to collapse
I believe the pbl is loaded before bootloader lock is detected, hence the reason it was able to exploit and unlock booloaders. Obviously we all can agree that something is failing when it comes to initializing the UFS storage it needs to write to. Whether it is corrupted, dead, or something else... I'm not knowledgeable enough to answer that. You might explore around with QFIL since it has an option in settings to select storage type, emmc or ufs. What you do from here on out is all you. I'd make sure you have your drivers installed and do only what is necessary to get back to a bootloader where you can flash a clean stock firmware. Keep us posted with your results and good luck.

Question I need help with the G10 XT2127-1 blankflash. I tried 3 blankflash and when trying to install this error.

I need help with the G10 XT2127-1 blankflash. I tried 3 blankflash and when trying to install this error.
[ 0.000] Opening device: \\.\COM30
[ 0.000] Detecting device
[ 3,659] ReadFile() failed, GetLastError()=0
[ 6,619] ...cpu.id = 310 (0x136)
[ 6,619] ...cpu.sn = 3251673319 (0xc1d098e7)
[ 6,619] Opening singleimage
[ 6,619] Loading package
[ 6,635] ...filename = pkg.xml
[ 6,635] Loading programmer
[ 6,635] ...filename = programmer.elf
[ 6,635] Sending programmer
[ 6.741] Handling things over to programmer
[ 6.741] Identifying CPU version
[ 6.741] Waiting for firehose to get ready
[ 9,820] ...SM_KAMORTA 1.0
[ 9,820] Determining target secure state
[ 9,820] ...secure = yes
[ 9.851] Configuring device...
[ 9,851] Flashing GPT...
[ 9,851] Flashing partition with gpt.bin
[ 9,867] Initializing storage
[11,040] Target NAK!
[ 11.040] ...INFO: handler getStorageInfo allowed
[ 11.040] ...INFO: Calling handler for getStorageInfo
[ 11.040] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 11.040] ...ERROR: Failed to open the device:1 slot:0 partition:0 error:0
[ 11.040] ...ERROR: OPEN handle NULL and no error, weird 203917508
[ 11.040] ...ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3
[ 11.040] 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
[ 11.040] Check qboot_log.txt for more details
[ 11,040] Total time: 11,040s
FAILED: qb_flash_singleimage()->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