Cant open my moto g7 (XT 1962-4)using blank flash after dvhik wipe, phone shows up as Qualcomm HS USB QDLoader 9008 (COM3), tried 2 diferent blankflash both of them couldnt open my phone (windows 10 safemode)
now it says
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
it spit ou waiting for firehose before
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ -0.000] ERROR: device_open()->error opening device
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: -0.000s
FAILED: qb_flash_singleimage()->device_open()->error opening device
I ALSO GET THIS
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 186 (0xba)
[ -0.000] ...cpu.sn = 948261486 (0x3885526e)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ -0.000] ...filename = singleimage.pkg.xml
[ -0.000] Loading programmer
[ -0.000] ...filename = programmer.mbn
[ -0.000] Sending programmer
[ 0.306] Handling things over to programmer
[ 0.306] Identifying CPU version
[ 0.306] Waiting for firehose to get ready
moto g7 power gt1995-4
C:\Users\arturwrobel\Desktop\blankflash_ocean_PDOS29.114-134-2>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.000] Detecting device
[ 0.016] ...cpu.id = 186 (0xba)
[ 0.016] ...cpu.sn = 3127012053 (0xba626ad5)
[ 0.016] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.328] Handling things over to programmer
[ 0.328] Identifying CPU version
[ 0.344] Waiting for firehose to get ready
[ 61.591] Waiting for firehose to get ready
[1228.004] ...MSM8953 unknown
[1228.004] Determining target secure state
[1228.004] Waiting for firehose to get ready
[1288.743] ...secure = no
[1288.779] Initializing storage
[1288.783] Waiting for firehose to get ready
[1349.582] Configuring device...
[1349.582] Waiting for firehose to get ready
[1410.647] Waiting for firehose to get ready
[1471.582] Waiting for firehose to get ready
[1532.725] Waiting for firehose to get ready
[1593.409] Initializing storage
[1593.409] Waiting for firehose to get ready
[1654.192] Configuring device...
[1654.192] Waiting for firehose to get ready
[1715.070] Waiting for firehose to get ready
[1775.866] Waiting for firehose to get ready
[1836.707] Waiting for firehose to get ready
[1897.739] Waiting for firehose to get ready
Welcome to the club, i'm guessing you're on the Feb patch?
[SOLVED]
This is solved check for Feb Patch [SOLVED] thread!
Related
Hi, I post the updates of the contact with ARYKTECH https://web.telegram.org/#/[email protected]
I buy in http://www.aryk.tech/2017/11/moto-x-play-unbrick-solutions.html the blankflash file for bricked MXP when downgrade of Nougat Stable to MM and install the OTA of 2017/01.
2017/11/02:
I pay 10 USD with paypal and wait...
2017/11/03
I receive the files hours later in google drive:
https://forum.xda-developers.com/attachment.php?attachmentid=4323100&stc=1&d=1509823657
Information of the folders:
https://dl.xda-developers.com/4/3/2....png?key=lb74mdfB79Bje9bOnMbqjA&ts=1509823783
https://dl.xda-developers.com/4/3/2....png?key=gKWllZVzD1gzMKR5DoHOoA&ts=1509823783
The version send me is the same like the soaktest:
lux_retasia_ds_userdebug_7.1.1_NPD26.35_eng.praseed.170526.190746_intcfg_test-keys_retasiaall_03
When I execute the blank-flash.bat of the folders have a error.
C:\mxp blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.001s]
identifying device
...serial = 0x15C3716
...chip-id = 0x90B (MSM8939)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.004s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.004s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.001s]
sending programmer
FAILED (blank-flash:sahara-transfer-image:send-image:error reading packet)
C:\mxp blankflash\blankflash>pause
Presione una tecla para continuar . . .
----
C:\mxp blankflash\Err_blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x15C3716
...chip-id = 0x90B (MSM8939)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.004s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.003s]
switching to download mode
OKAY [ 0.000s]
greeting device for image downloading
OKAY [ 0.001s]
sending programmer
OKAY [ 0.047s]
flashing singleimage
...protocol = sdl
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
C:\mxp blankflash\Err_blankflash>pause
2017/11/04:
Right now i wait a new version.... who promised me to send.
As I guessed they began with bull****, assuming naive you have old security there )
I think they got nothing. Motorola leak strikes like a miracle, but not SO often.
Let us know if any of their methods work!
2017/11/05 send the version 3 of blankflash:
ERROR
**** Log buffer [000001] 2017-11-05_14:40:23 ****
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 2315 (0x90b)
[ -0.000] ...cpu.sn = 60355909 (0x398f545)
[ -0.000] Opening singleimage
[ -0.000] ERROR: error opening singleimage
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: 0.016s
[ -0.000]
[ -0.000] qboot version 3.40
[ -0.000]
[ -0.000] DEVICE {
[ -0.000] name = "\\.\COM8",
[ -0.000] flags = "0x64",
[ -0.000] addr = "0x22FE6C",
[ -0.000] sahara.current_mode = "3",
[ -0.000] api.buffer = "0x1A00020",
[ -0.000] cpu.serial = "60355909",
[ -0.000] cpu.id = "2315",
[ -0.000] cpu.sv_sbl = "0",
[ -0.000] api.bnr = "0x612FE8",
[ -0.000] }
[ -0.000]
[ -0.000]
[ -0.000] Backup & Restore {
[ -0.000] num_entries = 0,
[ -0.000] restoring = "false",
[ -0.000] backup_error = "not started",
[ -0.000] restore_error = "not started",
[ -0.000] }
[ -0.000]
Blankflash files I asks for version 3 instead of 4
soyguris said:
2017/11/05 send the version 3 of blankflash:
ERROR
**** Log buffer [000001] 2017-11-05_14:40:23 ****
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 2315 (0x90b)
[ -0.000] ...cpu.sn = 60355909 (0x398f545)
[ -0.000] Opening singleimage
[ -0.000] ERROR: error opening singleimage
[ -0.000] Check qboot_log.txt for more details
[ -0.000] Total time: 0.016s
[ -0.000]
[ -0.000] qboot version 3.40
[ -0.000]
[ -0.000] DEVICE {
[ -0.000] name = "\\.\COM8",
[ -0.000] flags = "0x64",
[ -0.000] addr = "0x22FE6C",
[ -0.000] sahara.current_mode = "3",
[ -0.000] api.buffer = "0x1A00020",
[ -0.000] cpu.serial = "60355909",
[ -0.000] cpu.id = "2315",
[ -0.000] cpu.sv_sbl = "0",
[ -0.000] api.bnr = "0x612FE8",
[ -0.000] }
[ -0.000]
[ -0.000]
[ -0.000] Backup & Restore {
[ -0.000] num_entries = 0,
[ -0.000] restoring = "false",
[ -0.000] backup_error = "not started",
[ -0.000] restore_error = "not started",
[ -0.000] }
[ -0.000]
Click to expand...
Click to collapse
I tried to flash blank flash files from Moto G4 Plus forum and it says, expected version 3 instead of 4 and it quit. I believe you have version 3 blank flash files. Waiting for you to successfully unbrick your Moto X Play, so that I can also get the same files and try to unbrik my MXP, fingers crossed!
2017/11/07: I escalated the case to Paypal and gave me back the money.
Only Motorola have the solution.
Can I test version 3 file on my MXP?
soyguris said:
2017/11/07: I escalated the case to Paypal and gave me back the money.
Only Motorola have the solution.
Click to expand...
Click to collapse
Could you please share the version 3 Blank Flash Files and let me test it on my MXP?
Lord of Hell said:
Could you please share the version 3 Blank Flash Files and let me test it on my MXP?
Click to expand...
Click to collapse
The files attached.
None of them works
done!
it works!??
I tested on my moto x play xt1563 and gave the same errors It did not work.
Sorry for english, i'm using google translate
Not working is a scam
Enviado desde mi XT1563 mediante Tapatalk
C:\Users\AKASH AK\Desktop\MOTO\Blankflash MG4P_3\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30324219 (0x1ceb5fb)
[ 0.003] Opening singleimage
[ 0.029] Loading package
[ 0.032] ...filename = singleimage.pkg.xml
[ 0.034] Loading programmer
[ 0.034] ...filename = programmer.mbn
[ 0.034] Sending programmer
[ 0.255] Handling things over to programmer
[ 0.255] Identifying CPU version
[ 0.257] Waiting for firehose to get ready
[ 60.755] Waiting for firehose to get ready
[121.209] ...MSM8952 unknown
[121.210] Determining target secure state
[121.213] Waiting for firehose to get ready
[181.424] ...secure = no
[181.435] Flashing GPT...
[181.435] Flashing partition:0 with gpt_main0.bin
[181.435] Initializing storage
[181.438] Waiting for firehose to get ready
[241.562] Configuring device...
[241.566] Waiting for firehose to get ready
[301.736] Waiting for firehose to get ready
[361.985] Waiting for firehose to get ready
[422.088] Waiting for firehose to get ready
[482.192] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[482.193] Check qboot_log.txt for more details
[482.193] Total time: 482.194s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
C:\Users\AKASH AK\Desktop\MOTO\Blankflash MG4P_3\blankflash>pause
Press any key to continue . . .
?? plzzzz help for this problem
this is latest bootloader
BL: B1.09 (sha-9a76df4, 2019-01-11 14:40:15) ?? thanks
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
I'd try the blankflash a few more times but it seems that blankflash does not work in rescuing devices updated to stock Oreo. Without access to a blankflash newer than 11/01/2019, we're stuck for options that don't require payment.
my wife plugged in her G5 plus into to plug last night and when she woke up it was turned off and doesn't respond to anything.. I tried using the volum - & power button to get it to recovery mode but it doesn't work. When I plug it in the white notification light blinks.. nothing has been tampered with (no custom flash or anything)
I browsed the forum and found some info at https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 but didn't get it to work since it was for a G4 plus:
- set pc to test mode
- installed Qualcomm drivers
- when phone is plugged into usb on PC I get a Qualcomm Device in COM3
- I tried using a blankflash batch file using Qboot 3.4 I found on other threads on the site but didn't work.. thread mentions a 3.85 for Oreo but can not find it
Code:
[ 0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 4.013] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.013] Check qboot_log.txt for more details
[ 4.014] Total time: 4.017s
[ 4.015]
[ 4.015] qboot version 3.40
[ 4.015]
[ 4.015] DEVICE {
[ 4.015] name = "\\.\COM3",
[ 4.015] flags = "0x64",
[ 4.015] addr = "0x61FE4C",
[ 4.015] api.bnr = "0x662F78",
[ 4.015] }
[ 4.015]
[ 4.015]
[ 4.015] Backup & Restore {
[ 4.015] num_entries = 0,
[ 4.015] restoring = "false",
[ 4.015] backup_error = "not started",
[ 4.015] restore_error = "not started",
[ 4.015] }
[ 4.015]
but when I keep running the batch (as stated in the thread, it can take some time to get a lock on the phone) I sometimes get something like this:
Code:
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 70 (0x46)
[ 0.004] ...cpu.sn = 2491206852 (0x947cccc4)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.009] ...filename = singleimage.pkg.xml
[ 0.012] Loading programmer
[ 0.012] ...filename = programmer.mbn
[ 0.012] Sending programmer
[ 0.227] Handling things over to programmer
[ 0.227] Identifying CPU version
[ 0.229] Waiting for firehose to get ready
[ 11.348] ReadFile() failed, GetLastError()=0
[ 11.350] ReadFile() failed, GetLastError()=0
[ 21.133] ReadFile() failed, GetLastError()=0
[ 21.136] ReadFile() failed, GetLastError()=0
[ 60.543] Waiting for firehose to get ready
[ 63.543] WriteFile() failed, GetLastError()=0
[ 68.482] ReadFile() failed, GetLastError()=0
[120.661] ...MSM8953 unknown
[120.661] Determining target secure state
[120.664] Waiting for firehose to get ready
[180.865] ...secure = no
[180.891] Waiting for firehose to get ready
[240.957] Configuring device...
[240.960] Waiting for firehose to get ready
[301.630] Waiting for firehose to get ready
[360.485] ReadFile() failed, GetLastError()=0
[360.489] ReadFile() failed, GetLastError()=0
[364.229] Waiting for firehose to get ready
[424.262] Waiting for firehose to get ready
[484.384] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->devic
e_read()->IO error
[484.384] Check qboot_log.txt for more details
[484.384] Total time: 484.385s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffe
r_read()->device_read()->IO error
Anybody who can point me in the direction of the correct files to get it to work?
Dieterweireldt said:
my wife plugged in her G5 plus into to plug last night and when she woke up it was turned off and doesn't respond to anything.. I tried using the volum - & power button to get it to recovery mode but it doesn't work. When I plug it in the white notification light blinks.. nothing has been tampered with (no custom flash or anything)
I browsed the forum and found some info at https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 but didn't get it to work since it was for a G4 plus:
- set pc to test mode
- installed Qualcomm drivers
- when phone is plugged into usb on PC I get a Qualcomm Device in COM3
- I tried using a blankflash batch file using Qboot 3.4 I found on other threads on the site but didn't work.. thread mentions a 3.85 for Oreo but can not find it
but when I keep running the batch (as stated in the thread, it can take some time to get a lock on the phone) I sometimes get something like this:
Anybody who can point me in the direction of the correct files to get it to work?
Click to expand...
Click to collapse
There is no blankflash file for the Moto G5+ , such a file has to be leaked by some Motorola employee but that didn't happen. There is one for the Moto Z2 play but that one was for Nougat and won't work on Oreo, it was risky on 7.0 too. You can search it here on XDA or Google if you want to give it a shot nevertheless but if you can't reach fastboot mode to flash a firmware you're most likely out of luck.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
There is no blankflash file for the Moto G5+ , such a file has to be leaked by some Motorola employee but that didn't happen. There is one for the Moto Z2 play but that one was for Nougat and won't work on Oreo, it was risky on 7.0 too. You can search it here on XDA or Google if you want to give it a shot nevertheless but if you can't reach fastboot mode to flash a firmware you're most likely out of luck.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Ok thank you for the reply.. ordered the G8 plus for her now
Dieterweireldt said:
Ok thank you for the reply.. ordered the G8 plus for her now
Click to expand...
Click to collapse
Good choice.
Sent from my Moto G5 Plus using XDA Labs
try flashing lineage os 17 but my device was hard brick ed in the February patch update try to use an existing blankflash but it doesn't work I need a newer one and don't exit, someone has it or I have to wait
C:\Users\Windows\Desktop\blankflash (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM9
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 186 (0xba)
[ 0.000] ...cpu.sn = 431154525 (0x19b2e55d)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.322] Handling things over to programmer
[ 0.322] Identifying CPU version
[ 0.322] Waiting for firehose to get ready
[ 63.848] Waiting for firehose to get ready
[124.207] ...MSM8953 unknown
[125.269] Determining target secure state
[125.698] Waiting for firehose to get ready
[186.411] ...secure = no
[190.829] Initializing storage
[201.027] Waiting for firehose to get ready
[266.599] Configuring device...
[266.605] Waiting for firehose to get ready
[328.286] Waiting for firehose to get ready
[388.635] Waiting for firehose to get ready
[448.965] Waiting for firehose to get ready
[509.214] Initializing storage
[510.903] Waiting for firehose to get ready
I have the exact same problem, just on the G7 Power.
florosus said:
I have the exact same problem, just on the G7 Power.
Click to expand...
Click to collapse
Found this on another thread but now it asks for firehose to recover fastboot, need a firehose file so i can boot my phone xt1962-4 RIVER
https://mirrors.lolinet.com/firmware/moto/river/
https://forum.xda-developers.com/mo...ck-moto-g7-t3938342/post81971781#post81971781
lolcos said:
Found this on another thread but now it asks for firehose to recover fastboot, need a firehose file so i can boot my phone xt1962-4 RIVER
https://mirrors.lolinet.com/firmware/moto/river/
https://forum.xda-developers.com/mo...ck-moto-g7-t3938342/post81971781#post81971781
Click to expand...
Click to collapse
currently a developer is creating the file for river, already testie but sends error I hope soon is good
Ivan.coe said:
currently a developer is creating the file for river, already testie but sends error I hope soon is good
Click to expand...
Click to collapse
where did you find that info? Can you share the info you got, have you got any file that i could run on QFIL
lolcos said:
where did you find that info? Can you share the info you got, have you got any file that i could run on QFIL
Click to expand...
Click to collapse
https://t.me/MotoG7RiverDiscussion
I also bricked my G7 River February Patch - XT1962-4 PPOS29.114-134-10, need a new blankflash the provided one is not working...
Ivan.coe said:
try flashing lineage os 17 but my device was hard brick ed in the February patch update try to use an existing blankflash but it doesn't work I need a newer one and don't exit, someone has it or I have to wait
Click to expand...
Click to collapse
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM5
[ 0.008] Detecting device
[ 0.011] ...cpu.id = 186 (0xba)
[ 0.011] ...cpu.sn = 467405420 (0x1bdc0a6c)
[ 0.011] Opening singleimage
[ 0.012] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.014] Loading programmer
[ 0.014] ...filename = programmer.mbn
[ 0.014] Sending programmer
[ 0.298] Handling things over to programmer
[ 0.298] Identifying CPU version
[ 0.299] Waiting for firehose to get ready
[ 61.000] Waiting for firehose to get ready
[121.321] ...MSM8953 unknown
[121.321] Determining target secure state
[121.322] Waiting for firehose to get ready
[181.677] ...secure = no
[181.693] Initializing storage
Click to expand...
Click to collapse
BradXY said:
I also bricked my G7 River February Patch, need a new blankflash the provided one is not working...
Click to expand...
Click to collapse
still nothing, maybe they'll take it out until android 10 arrives
Please someone make the blankflash of the February patch, I have a Moto G7 paperweight
Seems we are completely SOL and totally FUBAR
[SOLVED]
This is solved check for Feb Patch [SOLVED] thread!
I recently got a new Moto G7 (XT1962-5) and almost instantly bricked it while trying to install LineageOS (forgot the copy_partitions step :-/)
Now I no longer get into fastboot, but I still see the phone as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" with "lsusb" (I'm on Linux).
Reading the forum I had some hope to revive it via a blankflash, but the error message I get includes
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.003] ...cpu.id = 186 (0xba)
[ 0.003] ...cpu.sn = 675895826 (0x28495a12)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.mbn
[ 0.009] Sending programmer
[ 0.291] Handling things over to programmer
[ 0.291] Identifying CPU version
[ 0.294] Waiting for firehose to get ready
[ 3.300] Target NAK!
[ 3.300] ...This version of programmer has been revoked!
[ 3.300] ...Rebooting to blank flash mode in 30 seconds...
So it seems that the blankflash image I'm using (https://mirrors.lolinet.com/firmware/moto/river/blankflash/blankflash_from_QPUS30.52-16-2-5.zip) is too old.
Does anyone know whether there is a more recent one available? Any other hints are also greatly appreciated!
I have no idea why, but using the blankflash from https://drive.google.com/open?id=1ShVC_VUJXIKkexunWpt1qtCRB29N0BlZ worked (found in https://forum.xda-developers.com/t/blankflash-moto-g7-xt1962-5-river-reteu-9-0-ppo29-80-66.4020263/), although it is supposed to be for a different model. Now back to installing!
Larabiata said:
I have no idea why, but using the blankflash from https://drive.google.com/open?id=1ShVC_VUJXIKkexunWpt1qtCRB29N0BlZ worked (found in https://forum.xda-developers.com/t/blankflash-moto-g7-xt1962-5-river-reteu-9-0-ppo29-80-66.4020263/), although it is supposed to be for a different model. Now back to installing!
Click to expand...
Click to collapse
Do you have the blankflash still with you to share. please??