Please help, i think i have September security patch and tried to install via otg and my moto g4 plus is bricked.
[ -0.000] Opening device: \\.\COM4
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2418 (0x972)
[ 0.007] ...cpu.sn = 29673406 (0x1c4c7be)
[ 0.007] Opening singleimage
[ 0.007] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.243] Handling things over to programmer
[ 0.245] Identifying CPU version
[ 0.250] Waiting for firehose to get ready
[ 60.639] Waiting for firehose to get ready
[120.793] ...MSM8952 unknown
[120.794] Determining target secure state
[120.804] Waiting for firehose to get ready
[180.968] ...secure = no
[181.001] Flashing GPT...
[181.002] Flashing partition:0 with gpt_main0.bin
[181.002] Initializing storage
[181.008] Waiting for firehose to get ready
[241.159] Configuring device...
[241.167] Waiting for firehose to get ready
[301.312] Waiting for firehose to get ready
[361.460] Waiting for firehose to get ready
[421.619] Waiting for firehose to get ready
[481.766] 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
[481.770] Check qboot_log.txt for more details
[481.774] Total time: 481.780s
[481.776]
[481.776] qboot version 3.40
[481.776]
[481.776] DEVICE {
[481.776] name = "\\.\COM4",
[481.776] flags = "0x64",
[481.776] addr = "0x61FE5C",
[481.776] sahara.current_mode = "0",
[481.776] api.buffer = "0x2EF2020",
[481.776] cpu.serial = "29673406",
[481.776] cpu.id = "2418",
[481.776] cpu.sv_sbl = "0",
[481.776] cpu.name = "MSM8952",
[481.776] storage.type = "eMMC",
[481.776] sahara.programmer = "programmer.mbn",
[481.776] module.firehose = "0x30ED0C0",
[481.776] cpu.ver = "0",
[481.776] cpu.vername = "unknown",
[481.776] api.bnr = "0x26F55C0",
[481.776] }
[481.776]
[481.776]
[481.776] Backup & Restore {
[481.776] num_entries = 0,
[481.776] restoring = "false",
[481.776] backup_error = "not started",
[481.776] restore_error = "not started",
[481.776] }
[481.776]
did u tried this ?
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
veejay97 said:
Please help, i think i have September security patch and tried to install via otg and my moto g4 plus is bricked.
[ -0.000] Opening device: \\.\COM4
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 2418 (0x972)
[ 0.007] ...cpu.sn = 29673406 (0x1c4c7be)
[ 0.007] Opening singleimage
[ 0.007] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.017] Loading programmer
[ 0.018] ...filename = programmer.mbn
[ 0.018] Sending programmer
[ 0.243] Handling things over to programmer
[ 0.245] Identifying CPU version
[ 0.250] Waiting for firehose to get ready
[ 60.639] Waiting for firehose to get ready
[120.793] ...MSM8952 unknown
[120.794] Determining target secure state
[120.804] Waiting for firehose to get ready
[180.968] ...secure = no
[181.001] Flashing GPT...
[181.002] Flashing partition:0 with gpt_main0.bin
[181.002] Initializing storage
[181.008] Waiting for firehose to get ready
[241.159] Configuring device...
[241.167] Waiting for firehose to get ready
[301.312] Waiting for firehose to get ready
[361.460] Waiting for firehose to get ready
[421.619] Waiting for firehose to get ready
[481.766] 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
[481.770] Check qboot_log.txt for more details
[481.774] Total time: 481.780s
[481.776]
[481.776] qboot version 3.40
[481.776]
[481.776] DEVICE {
[481.776] name = "\\.\COM4",
[481.776] flags = "0x64",
[481.776] addr = "0x61FE5C",
[481.776] sahara.current_mode = "0",
[481.776] api.buffer = "0x2EF2020",
[481.776] cpu.serial = "29673406",
[481.776] cpu.id = "2418",
[481.776] cpu.sv_sbl = "0",
[481.776] cpu.name = "MSM8952",
[481.776] storage.type = "eMMC",
[481.776] sahara.programmer = "programmer.mbn",
[481.776] module.firehose = "0x30ED0C0",
[481.776] cpu.ver = "0",
[481.776] cpu.vername = "unknown",
[481.776] api.bnr = "0x26F55C0",
[481.776] }
[481.776]
[481.776]
[481.776] Backup & Restore {
[481.776] num_entries = 0,
[481.776] restoring = "false",
[481.776] backup_error = "not started",
[481.776] restore_error = "not started",
[481.776] }
[481.776]
Click to expand...
Click to collapse
I am getting exactly the same message when executing the blankflash file from August the 21st on a Motorola G4 Plus that had been bricked a week ago during an update.
siddhesh9146 said:
did u tried this ?
https://forum.xda-developers.com/mot...guide-t3657761
Click to expand...
Click to collapse
I have tried the quoted link and also the following one without success:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Do I need a newer blankflash file?
Thanks in advance
Amberdawn said:
I have tried the quoted link and also the following one without success:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Thanks in advance
Click to expand...
Click to collapse
this link that you gave is trash, those are very old files which won't work at all
first delete all the files you have downloaded, all zips and all extracted files too
make sure nothing is there, clean your downloaded folder or IDM if you use it
then download fresh blankflash from here : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
trust me, it will work, you are mixing the older and newer blankflash files
and then report me back!
siddhesh9146 said:
this link that you gave is trash, those are very old files which won't work at all
first delete all the files you have downloaded, all zips and all extracted files too
make sure nothing is there, clean your downloaded folder or IDM if you use it
then download fresh blankflash from here : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
trust me, it will work, you are mixing the older and newer blankflash files
and then report me back!
Click to expand...
Click to collapse
I was mixing newer and older files in a folder but I have tried deleting all the files, downloading and using fresh blankflash files from the link you quoted with no success.
I have cleaned the download folder and I have left only the fresh blankflash folder.
I am obtaining the following:
Code:
[ 0.001] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30778144 (0x1d5a320)
[ 0.003] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.008] Sending programmer
[ 0.227] Handling things over to programmer
[ 0.228] Identifying CPU version
[ 0.230] Waiting for firehose to get ready
[ 60.472] Waiting for firehose to get ready
[123.536] ...MSM8952 unknown
[123.536] Determining target secure state
[123.541] Waiting for firehose to get ready
[184.100] ...secure = no
[184.133] Flashing GPT...
[184.134] Flashing partition:0 with gpt_main0.bin
[184.135] Initializing storage
[184.145] Waiting for firehose to get ready
[245.666] Configuring device...
[245.670] Waiting for firehose to get ready
[307.737] Waiting for firehose to get ready
[370.305] Waiting for firehose to get ready
[430.370] Waiting for firehose to get ready
[491.434] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[491.434] Check qboot_log.txt for more details
[491.437] Total time: 491.438s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
Any advice?
Amberdawn said:
I was mixing newer and older files in a folder but I have tried deleting all the files, downloading and using fresh blankflash files from the link you quoted with no success.
I have cleaned the download folder and I have left only the fresh blankflash folder.
I am obtaining the following:
Code:
[ 0.001] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30778144 (0x1d5a320)
[ 0.003] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.008] Sending programmer
[ 0.227] Handling things over to programmer
[ 0.228] Identifying CPU version
[ 0.230] Waiting for firehose to get ready
[ 60.472] Waiting for firehose to get ready
[123.536] ...MSM8952 unknown
[123.536] Determining target secure state
[123.541] Waiting for firehose to get ready
[184.100] ...secure = no
[184.133] Flashing GPT...
[184.134] Flashing partition:0 with gpt_main0.bin
[184.135] Initializing storage
[184.145] Waiting for firehose to get ready
[245.666] Configuring device...
[245.670] Waiting for firehose to get ready
[307.737] Waiting for firehose to get ready
[370.305] Waiting for firehose to get ready
[430.370] Waiting for firehose to get ready
[491.434] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[491.434] Check qboot_log.txt for more details
[491.437] Total time: 491.438s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
Any advice?
Click to expand...
Click to collapse
can you tell me when your device was bricked? I mean on which update? and also tell me the android version and security patch before bricking your phone
siddhesh9146 said:
can you tell me when your device was bricked? I mean on which update? and also tell me the android version and security patch before bricking your phone
Click to expand...
Click to collapse
First of all, it's not my device so I don't have all the answers...
The device was bricked a week ago. First, it got stuck in the booting process, exactly when Motorola logo appears. It remained for hours so a reboot into fastboot mode was performed. Then, the database had been wiped. After that, the phone started rebooting normally, it started updating and it got stuck again for 2h. As a result of this, the mobile was switched off and as a consecuence was bricked.
The device had stock Android 7 but I don't know the exact version as the owner doesn't know. I can confirm that it definitively had the security patch from September.
Hope you find this information useful
Amberdawn said:
First of all, it's not my device so I don't have all the answers...
The device was bricked a week ago. First, it got stuck in the booting process, exactly when Motorola logo appears. It remained for hours so a reboot into fastboot mode was performed. Then, the database had been wiped. After that, the phone started rebooting normally, it started updating and it got stuck again for 2h. As a result of this, the mobile was switched off and as a consecuence was bricked.
The device had stock Android 7 but I don't know the exact version as the owner doesn't know. I can confirm that it definitively had the security patch from September.
Hope you find this information useful
Click to expand...
Click to collapse
Any suggestion? Any idea of what is happening with the device?
Regards
Amberdawn said:
Any suggestion? Any idea of what is happening with the device?
Regards
Click to expand...
Click to collapse
Did you tried flashing stock rom again?
strongst said:
Did you tried flashing stock rom again?
Click to expand...
Click to collapse
No I didn't. As I was looking for a solution for the blankflash issue I haven't tried to go any further step yet.
Hi,
Still having problems while executing the blankflash file, can't figure out what could be the problem. Any idea/suggestion?
Thanks in advance.
Amberdawn said:
Hi,
Still having problems while executing the blankflash file, can't figure out what could be the problem. Any idea/suggestion?
Thanks in advance.
Click to expand...
Click to collapse
What problems are you having with the blankflash, are they the same as previously or different?
Can you confirm with the owner they are using the latest blankflash still (as provided here): https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
You may wish to also confirm they've tried the tips below: (from https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
Click to expand...
Click to collapse
If this doesn't work, then we might have to start considering a service repair - does the owner know if their device is still under warranty?
echo92 said:
What problems are you having with the blankflash, are they the same as previously or different?
Can you confirm with the owner they are using the latest blankflash still (as provided here): https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
The problems I am having are the same as previously. I can confirm that I am using the blankflash still as provided in the link you quoted.
I'm going to post again what I'm obtaining after executing the blankflash
Code:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30778144 (0x1d5a320)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.005] ...filename = singleimage.pkg.xml
[ 0.006] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.230] Handling things over to programmer
[ 0.231] Identifying CPU version
[ 0.237] Waiting for firehose to get ready
[ 63.482] Waiting for firehose to get ready
[127.045] ...MSM8952 unknown
[127.046] Determining target secure state
[127.052] Waiting for firehose to get ready
[188.612] ...secure = no
[188.624] Flashing GPT...
[188.625] Flashing partition:0 with gpt_main0.bin
[188.625] Initializing storage
[188.629] Waiting for firehose to get ready
[252.178] Configuring device...
[252.184] Waiting for firehose to get ready
[312.752] Waiting for firehose to get ready
[373.317] Waiting for firehose to get ready
[436.386] Waiting for firehose to get ready
[497.451] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[497.452] Check qboot_log.txt for more details
[497.455] Total time: 497.457s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
Log from qboot_log.txt file:
Code:
[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30778144 (0x1d5a320)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.005] ...filename = singleimage.pkg.xml
[ 0.006] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.230] Handling things over to programmer
[ 0.231] Identifying CPU version
[ 0.237] Waiting for firehose to get ready
[ 63.482] Waiting for firehose to get ready
[127.045] ...MSM8952 unknown
[127.046] Determining target secure state
[127.052] Waiting for firehose to get ready
[188.612] ...secure = no
[188.624] Flashing GPT...
[188.625] Flashing partition:0 with gpt_main0.bin
[188.625] Initializing storage
[188.629] Waiting for firehose to get ready
[252.178] Configuring device...
[252.184] Waiting for firehose to get ready
[312.752] Waiting for firehose to get ready
[373.317] Waiting for firehose to get ready
[436.386] Waiting for firehose to get ready
[497.451] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[497.452] Check qboot_log.txt for more details
[497.455] Total time: 497.457s
[497.456]
[497.456] qboot version 3.40
[497.456]
[497.456] DEVICE {
[497.456] name = "\\.\COM3",
[497.456] flags = "0x64",
[497.456] addr = "0x61FE5C",
[497.456] sahara.current_mode = "0",
[497.456] api.buffer = "0x2F01020",
[497.456] cpu.serial = "30778144",
[497.456] cpu.id = "2418",
[497.456] cpu.sv_sbl = "0",
[497.456] cpu.name = "MSM8952",
[497.456] storage.type = "eMMC",
[497.456] sahara.programmer = "programmer.mbn",
[497.457] module.firehose = "0x3088C78",
[497.457] cpu.ver = "0",
[497.457] cpu.vername = "unknown",
[497.457] api.bnr = "0x2746888",
[497.457] }
[497.457]
[497.457]
[497.457] Backup & Restore {
[497.457] num_entries = 0,
[497.457] restoring = "false",
[497.457] backup_error = "not started",
[497.457] restore_error = "not started",
[497.457] }
[497.457]
echo92 said:
You may wish to also confirm they've tried the tips below: (from https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 )
If this doesn't work, then we might have to start considering a service repair - does the owner know if their device is still under warranty?
Click to expand...
Click to collapse
I can also confirm that I have tried following the steps from that post. It's true that sometimes I need to follow these tips in order for blankflash to start executing.
However, the blankflash process doesn't work properly.
I think that the device is still under warranty. I have realised that more and more people are reporting the same problem.
I guess someone from motorola need to leak another blankflash...
siddhesh9146 said:
did u tried this ?
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
thank you so much..:good:
Bro... 1st of all.. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
This is the one u need to follow! But, DO NOT USE THE BOOTLOADER AND GPT OF THE ROM WITH BUILD NUMBER 14-8...YOU SHOULD DOWNLOAD LATEST ROM.. i.e., ending with build number 14-10...extract it and then use the bootloader and GPT files from this..
The only reason you are stuck on this is because you have not updated your usb moto drivers... Uninstall what you have, download them again.. Remember, download them again and then install and then use blankflash.. I have used it twice.. Once to unbrick my phone and another to make a youtube video!
Just in case you need to see what and how to do my video link is https://youtu.be/m2NqpY6X-X4
Hope this helps! Good luck!
abhi212b said:
Bro... 1st of all.. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
This is the one u need to follow! But, DO NOT USE THE BOOTLOADER AND GPT OF THE ROM WITH BUILD NUMBER 14-8...YOU SHOULD DOWNLOAD LATEST ROM.. i.e., ending with build number 14-10...extract it and then use the bootloader and GPT files from this..
The only reason you are stuck on this is because you have not updated your usb moto drivers... Uninstall what you have, download them again.. Remember, download them again and then install and then use blankflash.. I have used it twice.. Once to unbrick my phone and another to make a youtube video!
Just in case you need to see what and how to do my video link is https://youtu.be/m2NqpY6X-X4
Hope this helps! Good luck!
Click to expand...
Click to collapse
Hi abhi212b! I have tried following your video but again, I got stuck in the "waiting for firehose to get ready" step.
siddhesh9146 said:
I guess someone from motorola need to leak another blankflash...
Click to expand...
Click to collapse
Are you sure? I'm starting to think the same but then I see people who have succeeded unbricking their devices...
Is the device's hardware damaged?
Your help is much appreciated
Amberdawn said:
Hi abhi212b! I have tried following your video but again, I got stuck in the "waiting for firehose to get ready" step.
Are you sure? I'm starting to think the same but then I see people who have succeeded unbricking their devices...
Is the device's hardware damaged?
Your help is much appreciated
Click to expand...
Click to collapse
Did you update the drivers?? it should work.. i was stuck on waiting for firehose for like 2 hours, and after i updated the drivers, the procedure got through in 1st attempt..
abhi212b said:
Did you update the drivers?? it should work.. i was stuck on waiting for firehose for like 2 hours, and after i updated the drivers, the procedure got through in 1st attempt..
Click to expand...
Click to collapse
Yes, I did! I uninstalled the Motorola Drivers and then reinstalled the ones linked in your video. I also reinstalled the Qualcomm drivers
Moto g4 plus
I have a moto g4 plus .......i m update with oreo today.....after update net work is note working ....imei is fine....but network problem.....after i m downgrade with nougate 7.0 ......imei nomber is null.....after i m update 40mb in nougate system update....mobile restart for installing but now in dead mode......
I m trying blank flash but "waiting for firehose get ready" stunk at this moment.....
Plz help me some body.......
This is another question on how to unbrick a hard-bricked G4.
What I did so far:
1) Windows runs on test mode.
2) QualcommDrv installed --> Device is shown as "Qualcomm HS-USB QDLoader 9008 (COM5)"
3) Downloaded "blankflash-MotoG4" package and ran the blank-flash.bat file --> ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
4) Pressed POWER BUTTON + VOL DOWN while running the bat file: same error
5) out of curiosity I took a blankflas package for G4+ and this took me to " Waiting for firehose to get ready"
but nothing more happened after this message.
Any advice? Thank you!
The same problem is happening with my moto g4.
The same problem is happening with my moto g4, I tried many blank flash, but did not work.
markusk11 said:
This is another question on how to unbrick a hard-bricked G4.
What I did so far:
1) Windows runs on test mode.
2) QualcommDrv installed --> Device is shown as "Qualcomm HS-USB QDLoader 9008 (COM5)"
3) Downloaded "blankflash-MotoG4" package and ran the blank-flash.bat file --> ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
4) Pressed POWER BUTTON + VOL DOWN while running the bat file: same error
5) out of curiosity I took a blankflas package for G4+ and this took me to " Waiting for firehose to get ready"
but nothing more happened after this message.
Any advice? Thank you!
Click to expand...
Click to collapse
Can you check the qboot log and see if there's any more info there that might explain what the problem is? An IO error normally indicates that your device can't be detected or there's an issue with the file system
qboot_log.txt
[ -0.000] Opening device: \\.\COM5
[ 0.010] Detecting device
[ 0.012] ...cpu.id = 2418 (0x972)
[ 0.012] ...cpu.sn = 39153073 (0x2556db1)
[ 0.012] Opening singleimage
[ 0.012] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.018] Loading programmer
[ 0.019] ...filename = programmer.mbn
[ 0.019] Sending programmer
[ 0.236] Handling things over to programmer
[ 0.237] Identifying CPU version
[ 0.239] Waiting for firehose to get ready
[ 9.753] ReadFile() failed, GetLastError()=0
[ 9.803] ReadFile() failed, GetLastError()=0
[ 62.253] Waiting for firehose to get ready
[122.562] ...MSM8952 unknown
[122.562] Determining target secure state
[122.564] Waiting for firehose to get ready
[182.873] ...secure = no
[182.883] Flashing GPT...
[182.884] Flashing partition:0 with gpt_main0.bin
[182.884] Initializing storage
[182.887] Waiting for firehose to get ready
[243.195] Configuring device...
[243.197] Waiting for firehose to get ready
[303.506] Waiting for firehose to get ready
[363.814] Waiting for firehose to get ready
[424.126] Waiting for firehose to get ready
[484.430] 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
[484.430] Check qboot_log.txt for more details
[484.431] Total time: 484.431s
[484.432]
[484.432] qboot version 3.40
[484.432]
[484.432] DEVICE {
[484.432] name = "\\.\COM5",
[484.432] flags = "0x64",
[484.432] addr = "0x28FE6C",
[484.432] sahara.current_mode = "0",
[484.432] api.buffer = "0x2600020",
[484.432] cpu.serial = "39153073",
[484.432] cpu.id = "2418",
[484.432] cpu.sv_sbl = "0",
[484.432] cpu.name = "MSM8952",
[484.432] storage.type = "eMMC",
[484.432] sahara.programmer = "programmer.mbn",
[484.432] module.firehose = "0x25616A0",
[484.432] cpu.ver = "0",
[484.432] cpu.vername = "unknown",
[484.432] api.bnr = "0x2567DA8",
[484.432] }
[484.432]
[484.432]
[484.432] Backup & Restore {
[484.432] num_entries = 0,
[484.432] restoring = "false",
[484.432] backup_error = "not started",
[484.432] restore_error = "not started",
[484.432] }
[484.432]
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
If you has bricked your Moto g7 you must join this group https://t.me/MotoG7RiverDiscussion There you will find a new blankflash file, that's working with last motorola's february update.
Enjoy it, wash your hands and take care of yourself!
I need Help
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ 0.001] Detecting device
[ 4.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.008] Check qboot_log.txt for more details
[ 4.010] Total time: 4.013s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
**** Log buffer [000001] 2020-04-02_12:00:32 ****
[ -0.000] Opening device: \\.\COM5
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.007] Total time: 4.009s
[ 4.007]
[ 4.007] qboot version 3.40
[ 4.007]
[ 4.007] DEVICE {
[ 4.007] name = "\\.\COM5",
[ 4.007] flags = "0x64",
[ 4.007] addr = "0x61FE4C",
[ 4.007] api.bnr = "0x8B2D20",
[ 4.007] }
[ 4.007]
[ 4.007]
[ 4.007] Backup & Restore {
[ 4.007] num_entries = 0,
[ 4.007] restoring = "false",
[ 4.007] backup_error = "not started",
[ 4.007] restore_error = "not started",
[ 4.007] }
[ 4.007]
I already tried having one hand pressing less volume and power
I blankflashed my device and it worked, right now I don't know what else to do after that
Korax94 said:
I blankflashed my device and it worked, right now I don't know what else to do after that
Click to expand...
Click to collapse
You must install stock rom using fastboot mode. Chek instructions in this thread - https://forum.xda-developers.com/moto-g7/how-to/manually-update-g7-using-fastboot-t3917381
Could someone kindly describe how to unbrick Moto G7 XT1962-1 RETUS Factory unlocked model
Korax94 said:
I blankflashed my device and it worked, right now I don't know what else to do after that
Click to expand...
Click to collapse
Could you upload the blankflash you used?