**** Log buffer [000001] 2018-04-29_23:09:21 ****
[ 0.000] Opening device: \\.\COM9
[ 0.063] Detecting device
[ 0.078] ...cpu.id = 94 (0x5e)
[ 0.125] ...cpu.sn = 4273788185 (0xfebcd519)
[ 0.125] Opening singleimage
[ 0.531] Loading package
[ 0.609] ...filename = pkg.xml
[ 0.688] Loading programmer
[ 0.938] ...filename = programmer.elf
[ 0.938] Sending programmer
[ 1.142] ReadFile() failed, GetLastError()=0
[ 1.510] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 1.551] ERROR: sahara_download()->general error
[ 1.554] Check qboot_log.txt for more details
[ 1.593] Total time: 1.609s
[ 1.611]
[ 1.611] qboot version 3.85
[ 1.611]
[ 1.611] DEVICE {
[ 1.611] name = "\\.\COM9",
[ 1.611] flags = "0x64",
[ 1.611] addr = "0x62FD64",
[ 1.611] sahara.current_mode = "0",
[ 1.611] api.buffer = "0x28B6020",
[ 1.611] cpu.serial = "4273788185",
[ 1.611] cpu.id = "94",
[ 1.611] cpu.sv_sbl = "0",
[ 1.611] cpu.name = "MSM8998",
[ 1.611] storage.type = "UFS",
[ 1.611] sahara.programmer = "programmer.elf",
[ 1.611] api.bnr = "0x27F3E10",
[ 1.611] }
[ 1.611]
[ 1.611]
[ 1.611] Backup & Restore {
[ 1.611] num_entries = 0,
[ 1.611] restoring = "false",
[ 1.611] backup_error = "not started",
[ 1.611] restore_error = "not started",
[ 1.611] }
[ 1.611]
--------------
this is blank flash error log. I don't know this error. any solutions?
**** Log buffer [000001] 2018-05-27_19:15:58 ****
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 79 (0x4f)
[ 0.002] ...cpu.sn = 3414389940 (0xcb8374b4)
[ 0.002] Opening singleimage
[ 0.339] Loading package
[ 0.343] ...filename = singleimage.pkg.xml
[ 0.345] Loading programmer
[ 0.347] ...filename = programmer.mbn
[ 0.347] Sending programmer
[ 1.378] ERROR: sahara_download()->IO error
[ 1.378] Check qboot_log.txt for more details
[ 1.378] Total time: 1.378s
[ 1.378]
[ 1.378] qboot version 3.40
[ 1.378]
[ 1.378] DEVICE {
[ 1.378] name = "/dev/ttyUSB0",
[ 1.378] flags = "0x60",
[ 1.378] addr = "0x41C63D78",
[ 1.378] serial_nix.device_pathname = "/sys/bus/usb/devices/2-1.3/2-1.3:1.0/ttyUSB0",
[ 1.378] sahara.current_mode = "0",
[ 1.378] api.buffer = "0x7FE2D204C010",
[ 1.378] cpu.serial = "3414389940",
[ 1.378] cpu.id = "79",
[ 1.378] cpu.sv_sbl = "1",
[ 1.378] cpu.name = "MSM8937",
[ 1.378] storage.type = "eMMC",
[ 1.378] sahara.programmer = "programmer.mbn",
[ 1.378] api.bnr = "0xC5B7F0",
[ 1.378] }
[ 1.378]
[ 1.378]
[ 1.378] Backup & Restore {
[ 1.378] num_entries = 0,
[ 1.378] restoring = "false",
[ 1.378] backup_error = "not started",
[ 1.378] restore_error = "not started",
[ 1.378] }
[ 1.378]
Might have a paperweight now. I have tried using the blankflash utility here (https://mirrors.lolinet.com/firmware/motorola/smith/blankflash/) but get an error about Sahara not expecting a 1. Can get the specifics if it would help. But apparently the blankflash files are really specific to what version the device was last using. Mine was T-Mobile still on an older 10 build.
Here's the log:
Code:
**** Log buffer [000001] 2021-06-26_12:10:15 ****
[ -0.000] Opening device: \\.\COM3
[ -0.000] Detecting device
[ 0.245] ReadFile() failed, GetLastError()=0
[ 1.486] ...cpu.id = 286 (0x11e)
[ 1.486] ...cpu.sn = 3255226195 (0xc206cf53)
[ 1.486] Opening singleimage
[ 1.486] Loading package
[ 1.486] ...filename = pkg.xml
[ 1.486] Loading programmer
[ 1.486] ...filename = programmer.elf
[ 1.486] Sending programmer
[ 3.937] ReadFile() failed, GetLastError()=0
[ 4.193] Unexpected command, expecting 3 or 18 or 4, got 1 instead.
[ 4.193] ERROR: sahara_download()->general error
[ 4.193] Check qboot_log.txt for more details
[ 4.193] Total time: 4.197s
[ 4.193]
[ 4.193] qboot version 3.86
[ 4.193]
[ 4.193] DEVICE {
[ 4.193] name = "\\.\COM3",
[ 4.193] flags = "0x64",
[ 4.193] addr = "0x62FD54",
[ 4.193] sahara.current_mode = "0",
[ 4.193] api.buffer = "0x2B20020",
[ 4.193] cpu.serial = "3255226195",
[ 4.193] cpu.id = "286",
[ 4.193] cpu.sv_sbl = "0",
[ 4.193] cpu.name = "SM_SAIPAN",
[ 4.193] storage.type = "UFS",
[ 4.193] sahara.programmer = "programmer.elf",
[ 4.193] api.bnr = "0x7D4F30",
[ 4.193] }
[ 4.193]
[ 4.193]
[ 4.193] Backup & Restore {
[ 4.193] num_entries = 0,
[ 4.193] restoring = "false",
[ 4.193] backup_error = "not started",
[ 4.193] restore_error = "not started",
[ 4.193] }
Seems like some of the Qualcomm flashing tools could help if I could get the specific Firehose files. Though I think I'm way in over my head and could be badly misunderstanding this all.
If you can boot into fastboot then flash all.
But if you can't then try this:
Download MSM tool.
Download Qualcomm driver.
Download your device stock ROM.
Boot into EDL mode, then connect your device.
Finally flash it through msm tool and you're done.
XDHx86 said:
If you can boot into fastboot then flash all.
But if you can't then try this:
Download MSM tool.
Download Qualcomm driver.
Download your device stock ROM.
Boot into EDL mode, then connect your device.
Finally flash it through msm tool and you're done.
Click to expand...
Click to collapse
Thanks but that tool seems to very specifically be for Oppo/OnePlus devices and very much not Motorola. Won't recognize it.
I updated the OP with more details
gorei23 said:
Thanks but that tool seems to very specifically be for Oppo/OnePlus devices and very much not Motorola. Won't recognize it.
I updated the OP with more details
Click to expand...
Click to collapse
If you can't get firehose files, then there is a different method for you to try.
Although I only tried it once on a different Moto device, but it still worked.
Try flashing your device specific blank flash file, then you should be able to boot to bootloader.
After successfully booting to bootloader use RSD tool to flash your device specific ROM.
It won't matter if you have locked bootloader or not, since you'd be flashing stock ROM or latest ROM.
RSD tool only works with bootloader, so don't bother using it with your bricked phone.
edit
XDHx86 said:
If you can't get firehose files, then there is a different method for you to try.
Although I only tried it once on a different Moto device, but it still worked.
Try flashing your device specific blank flash file, then you should be able to boot to bootloader.
After successfully booting to bootloader use RSD tool to flash your device specific ROM.
It won't matter if you have locked bootloader or not, since you'd be flashing stock ROM or latest ROM.
RSD tool only works with bootloader, so don't bother using it with your bricked phone.
Click to expand...
Click to collapse
As per the logs in the OP I can't seem to get the blank flash to work. My hypothesis is it's either a version mismatch (research into similar threads seems to show these files need to match the specific version you're running. This file is the only available afaik) or it's the result of me having switched to slot B when it's trying to flash A. But yes if I could get the bootloader up then I'd be good. It's unlocked.
Haven't had any luck finding firehose files for it either :/
My last ditch approach would be to send to Moto. I would hope that they either couldn't boot it far enough to tell it has been tampered with and not seeing any other damage they replace it. Or they flash a bootloader, realize it's been messed with and send it back (with working bootloader). Worst that happens is they send it back unchanged right?
gorei23 said:
As per the logs in the OP I can't seem to get the blank flash to work. My hypothesis is it's either a version mismatch (research into similar threads seems to show these files need to match the specific version you're running. This file is the only available afaik) or it's the result of me having switched to slot B when it's trying to flash A. But yes if I could get the bootloader up then I'd be good. It's unlocked.
Haven't had any luck finding firehose files for it either :/
My last ditch approach would be to send to Moto. I would hope that they either couldn't boot it far enough to tell it has been tampered with and not seeing any other damage they replace it. Or they flash a bootloader, realize it's been messed with and send it back (with working bootloader). Worst that happens is they send it back unchanged right?
Click to expand...
Click to collapse
Are you sure you can't find firehose files in the ROM? There is no programmer.xml or patch0.xml or anything similar in the extracted ROM?
XDHx86 said:
Are you sure you can't find firehose files in the ROM? There is no programmer.xml or patch0.xml or anything similar in the extracted ROM?
Click to expand...
Click to collapse
I can't seem to - I think programmer.elf in the blankflash file is the programmer, obviously. Still lost on the other needed files.
Tried on linux and also enabled debug options. Didn't get anwhere but more info got spit out.
Code:
sudo ./qboot --debug=1 blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Opening serial device: /dev/ttyUSB1
[ 0.000] serial_open():228: opening /dev/ttyUSB1
[ 0.000] Detecting device
[ 0.000] Switching to command mode
[ 0.000] Receiving HELLO packet
[ 0.000] ...protocol version: 2
[ 0.000] ...compatible with: 1
[ 0.000] ...max. packet size: 1024
[ 0.000] ...current mode: Image transfer pending
[ 0.000] Sending HELLO_RESP packet
[ 0.000] Receiving COMMAND_READY packet
[ 0.000] Identifying device
[ 0.000] Reading CPU serial number
[ 0.000] Sending CMD_EXEC packet, cmd=CMD_READ_SN
[ 0.000] Receiving CMD_EXEC_RESP packet
[ 0.000] ...payload: 4 byte(s)
[ 0.000] Receiving payload
[ 0.000] Reading CPU id
[ 0.000] Sending CMD_EXEC packet, cmd=CMD_READ_HWID
[ 0.000] Receiving CMD_EXEC_RESP packet
[ 0.001] ...payload: 24 byte(s)
[ 0.001] Receiving payload
[ 0.001] Reading SBL SV
[ 0.001] Sending CMD_EXEC packet, cmd=CMD_READ_SV_SBL
[ 0.001] Receiving CMD_EXEC_RESP packet
[ 0.001] ...payload: 4 byte(s)
[ 0.001] Receiving payload
[ 0.001] Reading debug data
[ 0.001] Sending CMD_EXEC packet, cmd=CMD_READ_DEBUG_DATA
[ 0.001] Receiving CMD_EXEC_RESP packet
[ 0.001] ...payload: 520 byte(s)
[ 0.001] Receiving payload
[ 0.001] Debug data dump follows
[ 0.001] 00000000 02 00 00 00 02 00 00 00 0b 00 0a ef 00 00 00 00 |................|
[ 0.001] 00000010 00 00 00 00 00 00 00 00 bf 9e e7 46 00 00 10 54 |...........F...T|
[ 0.001] 00000020 03 00 00 00 00 00 00 00 18 fa 32 00 00 00 00 00 |..........2.....|
[ 0.001] 00000030 d0 00 00 00 59 00 00 ef 02 02 01 ef 00 00 00 00 |....Y...........|
[ 0.001] 00000040 04 00 00 00 00 00 00 00 a6 f1 a1 49 00 00 10 54 |...........I...T|
[ 0.001] 00000050 03 00 00 00 00 00 00 00 38 f7 32 00 00 00 00 00 |........8.2.....|
[ 0.001] 00000060 31 04 00 00 5a 00 00 ef 00 00 00 00 00 00 00 00 |1...Z...........|
[ 0.001] 00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
[ 0.001] *
[ 0.001] 00000200 00 00 00 00 00 00 00 00 |........ |
[ 0.001] ...cpu.id = 286 (0x11e)
[ 0.001] ...cpu.sn = 3255226195 (0xc206cf53)
[ 0.001] Opening singleimage
[ 0.001] Loading package
[ 0.003] ...filename = pkg.xml
[ 0.004] Loading programmer
[ 0.004] ...filename = programmer.elf
[ 0.004] Sending programmer
[ 0.005] Switching to image download mode
[ 0.005] Sending CMD_SWITCH_MODE packet
[ 0.005] Receiving HELLO packet
[ 0.005] ...protocol version: 2
[ 0.005] ...compatible with: 1
[ 0.005] ...max. packet size: 1024
[ 0.005] ...current mode: Image transfer pending
[ 0.005] Sending HELLO_RESP packet
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.005] Sending 64 bytes
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.005] Sending 1064 bytes
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.005] Sending 4096 bytes
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.109] Sending 3384 bytes
[ 0.109] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 1.112] ERROR: sahara_download()->IO error
[ 1.112] Check qboot_log.txt for more details
[ 1.112] Total time: 1.112s
FAILED: qb_flash_singleimage()->sahara_download()->IO error
And the log file is the same except this at the end:
Code:
[ 1.112] Total time: 1.112s
[ 1.112]
[ 1.112] qboot version 3.86
[ 1.112]
[ 1.112] DEVICE {
[ 1.112] name = "/dev/ttyUSB1",
[ 1.112] flags = "0x61",
[ 1.112] addr = "0xE1EEC160",
[ 1.112] serial_nix.device_pathname = "/sys/bus/usb/devices/1-1/1-1:1.0/ttyUSB1",
[ 1.112] sahara.current_mode = "0",
[ 1.112] api.buffer = "0x7F36B1733010",
[ 1.112] cpu.serial = "3255226195",
[ 1.112] cpu.id = "286",
[ 1.112] cpu.sv_sbl = "0",
[ 1.112] cpu.name = "SM_SAIPAN",
[ 1.112] storage.type = "UFS",
[ 1.112] sahara.programmer = "programmer.elf",
[ 1.112] api.bnr = "0x9AD8A0",
[ 1.112] }
[ 1.112]
[ 1.112]
[ 1.112] Backup & Restore {
[ 1.112] num_entries = 0,
[ 1.112] restoring = "false",
[ 1.112] backup_error = "not started",
[ 1.112] restore_error = "not started",
[ 1.112] }
gorei23 said:
Tried on linux and also enabled debug options. Didn't get anwhere but more info got spit out.
Code:
sudo ./qboot --debug=1 blank-flash
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Opening serial device: /dev/ttyUSB1
[ 0.000] serial_open():228: opening /dev/ttyUSB1
[ 0.000] Detecting device
[ 0.000] Switching to command mode
[ 0.000] Receiving HELLO packet
[ 0.000] ...protocol version: 2
[ 0.000] ...compatible with: 1
[ 0.000] ...max. packet size: 1024
[ 0.000] ...current mode: Image transfer pending
[ 0.000] Sending HELLO_RESP packet
[ 0.000] Receiving COMMAND_READY packet
[ 0.000] Identifying device
[ 0.000] Reading CPU serial number
[ 0.000] Sending CMD_EXEC packet, cmd=CMD_READ_SN
[ 0.000] Receiving CMD_EXEC_RESP packet
[ 0.000] ...payload: 4 byte(s)
[ 0.000] Receiving payload
[ 0.000] Reading CPU id
[ 0.000] Sending CMD_EXEC packet, cmd=CMD_READ_HWID
[ 0.000] Receiving CMD_EXEC_RESP packet
[ 0.001] ...payload: 24 byte(s)
[ 0.001] Receiving payload
[ 0.001] Reading SBL SV
[ 0.001] Sending CMD_EXEC packet, cmd=CMD_READ_SV_SBL
[ 0.001] Receiving CMD_EXEC_RESP packet
[ 0.001] ...payload: 4 byte(s)
[ 0.001] Receiving payload
[ 0.001] Reading debug data
[ 0.001] Sending CMD_EXEC packet, cmd=CMD_READ_DEBUG_DATA
[ 0.001] Receiving CMD_EXEC_RESP packet
[ 0.001] ...payload: 520 byte(s)
[ 0.001] Receiving payload
[ 0.001] Debug data dump follows
[ 0.001] 00000000 02 00 00 00 02 00 00 00 0b 00 0a ef 00 00 00 00 |................|
[ 0.001] 00000010 00 00 00 00 00 00 00 00 bf 9e e7 46 00 00 10 54 |...........F...T|
[ 0.001] 00000020 03 00 00 00 00 00 00 00 18 fa 32 00 00 00 00 00 |..........2.....|
[ 0.001] 00000030 d0 00 00 00 59 00 00 ef 02 02 01 ef 00 00 00 00 |....Y...........|
[ 0.001] 00000040 04 00 00 00 00 00 00 00 a6 f1 a1 49 00 00 10 54 |...........I...T|
[ 0.001] 00000050 03 00 00 00 00 00 00 00 38 f7 32 00 00 00 00 00 |........8.2.....|
[ 0.001] 00000060 31 04 00 00 5a 00 00 ef 00 00 00 00 00 00 00 00 |1...Z...........|
[ 0.001] 00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
[ 0.001] *
[ 0.001] 00000200 00 00 00 00 00 00 00 00 |........ |
[ 0.001] ...cpu.id = 286 (0x11e)
[ 0.001] ...cpu.sn = 3255226195 (0xc206cf53)
[ 0.001] Opening singleimage
[ 0.001] Loading package
[ 0.003] ...filename = pkg.xml
[ 0.004] Loading programmer
[ 0.004] ...filename = programmer.elf
[ 0.004] Sending programmer
[ 0.005] Switching to image download mode
[ 0.005] Sending CMD_SWITCH_MODE packet
[ 0.005] Receiving HELLO packet
[ 0.005] ...protocol version: 2
[ 0.005] ...compatible with: 1
[ 0.005] ...max. packet size: 1024
[ 0.005] ...current mode: Image transfer pending
[ 0.005] Sending HELLO_RESP packet
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.005] Sending 64 bytes
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.005] Sending 1064 bytes
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.005] Sending 4096 bytes
[ 0.005] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 0.109] Sending 3384 bytes
[ 0.109] Receiving READ_DATA, READ_DATA_64, or END_IMAGE_TX packet
[ 1.112] ERROR: sahara_download()->IO error
[ 1.112] Check qboot_log.txt for more details
[ 1.112] Total time: 1.112s
FAILED: qb_flash_singleimage()->sahara_download()->IO error
And the log file is the same except this at the end:
Code:
[ 1.112] Total time: 1.112s
[ 1.112]
[ 1.112] qboot version 3.86
[ 1.112]
[ 1.112] DEVICE {
[ 1.112] name = "/dev/ttyUSB1",
[ 1.112] flags = "0x61",
[ 1.112] addr = "0xE1EEC160",
[ 1.112] serial_nix.device_pathname = "/sys/bus/usb/devices/1-1/1-1:1.0/ttyUSB1",
[ 1.112] sahara.current_mode = "0",
[ 1.112] api.buffer = "0x7F36B1733010",
[ 1.112] cpu.serial = "3255226195",
[ 1.112] cpu.id = "286",
[ 1.112] cpu.sv_sbl = "0",
[ 1.112] cpu.name = "SM_SAIPAN",
[ 1.112] storage.type = "UFS",
[ 1.112] sahara.programmer = "programmer.elf",
[ 1.112] api.bnr = "0x9AD8A0",
[ 1.112] }
[ 1.112]
[ 1.112]
[ 1.112] Backup & Restore {
[ 1.112] num_entries = 0,
[ 1.112] restoring = "false",
[ 1.112] backup_error = "not started",
[ 1.112] restore_error = "not started",
[ 1.112] }
Click to expand...
Click to collapse
If you can't find your device programmer nor can you find a blank flash file. Maybe a recovery tool can do the trick for you.
There is this tool "Motorola Rescue & Smart Assistant" that motorola has, idk if it works but try it out. Maybe there's a different tool out there.
Or maybe this programmer.elf is the file you need, try opening it in an editor. If it looks like this then it is the one, then it's probably the one you're looking for.
Goodluck.
Same problem, could you correct It?
eddykc said:
Same problem, could you correct It?
Click to expand...
Click to collapse
No, never got any farther. The device should still be in warranty period. I sent it to Motorola and (after a few weeks, ugh) they said they couldn't fix it and are sending me a (like) new one.
Send it to Motorola, it's free
Not recommend doing that, you're lucky they allowed it, technically by unlocking the bootloader you were supposed to have voided the warranty, the TMobile Razr seems to have flown under the radar in the unlock program, and you might affect the future ability of people together obtain unlock tokens for the TMobile units. At least IMHO.
XDHx86 said:
If you can't get firehose files, then there is a different method for you to try.
Although I only tried it once on a different Moto device, but it still worked.
Try flashing your device specific blank flash file, then you should be able to boot to bootloader.
After successfully booting to bootloader use RSD tool to flash your device specific ROM.
It won't matter if you have locked bootloader or not, since you'd be flashing stock ROM or latest ROM.
RSD tool only works with bootloader, so don't bother using it with your bricked phone.
Click to expand...
Click to collapse
Can’t flash last firmware with locked bootloader i got permission denied!!
Hello, after almost having a heart attack with my Razer 2 showing the qusb_bulk message, I decided to fix my moto z2 with the same message. Did what almost all good threads say but while running the blankfast (blankflash_from_NDX26.183-15_17) it keeps showing the same error, I made sure I don't have moto drivers installed, and uninstalled the qualcomm drivers once. And it keeps showing.
If anyone had the same error, and can help, I'll be pretty grateful.
**** Log buffer [000001] 2022-12-21_16:42:26 ****
[ 0.000] Opening device: \\.\COM6
[ 0.000] ERROR: device_open()->error opening device
[ 0.001] Check qboot_log.txt for more details
[ 0.001] Total time: 0.002s
[ 0.001]
[ 0.001] qboot version 3.85
[ 0.001]
[ 0.001] DEVICE {
[ 0.001] name = "\\.\COM6",
[ 0.001] flags = "0x60",
[ 0.001] addr = "0x62FD54",
[ 0.001] api.bnr = "0xE22FE8",
[ 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]
Did anyone manage to generate a SingleImage htc file for flashing via blankflash program (for motorola )? To my strangeness, I downloaded the BlankFlash program for Motorola with the same processor as the HTC M9 model, installed the drivers (Qalcomm Emergency 9008 Download Model for qhusb_bulk Device) and communicates with the computer . Any idea how to fix the bootlader for this model?
**** Log buffer [000001] 2023-02-06_15:00:07 ****
[ -0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.005] ...cpu.id = 2368 (0x940)
[ 0.005] ...cpu.sn = 17772425 (0x10f2f89)
[ 0.005] Opening singleimage
[ 0.006] ERROR: error opening singleimage
[ 0.006] Check qboot_log.txt for more details
[ 0.007] Total time: 0.008s
[ 0.008]
[ 0.008] qboot version 3.86
[ 0.008]
[ 0.008] DEVICE {
[ 0.008] name = "\\.\COM3",
[ 0.008] flags = "0x64",
[ 0.008] addr = "0x62FD54",
[ 0.008] sahara.current_mode = "3",
[ 0.008] api.buffer = "0x2AF0020",
[ 0.008] cpu.serial = "17772425",
[ 0.008] cpu.id = "2368",
[ 0.008] cpu.sv_sbl = "0",
[ 0.008] api.bnr = "0x1092D88",
[ 0.008] }
[ 0.008]
[ 0.008]
[ 0.008] Backup & Restore {
[ 0.008] num_entries = 0,
[ 0.008] restoring = "false",
[ 0.008] backup_error = "not started",
[ 0.008] restore_error = "not started",
[ 0.008] }
[ 0.008]
blankflash.zip | by erfanoabdi for Moto G6 Plus
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
please delete singleimage,img before run
Or anyone have mmcblk0.img file from htc m9 ?
Maybe this : https://www.hovatek.com/forum/thread-19721.html