I have successfully recovered my dead/hard brick moto g4 plus mobile using below process.
To give you background, I have hard bricked my new moto g4 plus mobile. To do that, I have unlocked boot loader which void my warranty, then I have rooted yet and got root access. Till that it was working. After that I have installed custom rom cyanogenmod 14.1 . It was still working for some days. Now As I came from blackberry z10 to moto, I was missing blackberry hub features, so I downloaded BlackBerry android OS(Blackberry Priv) and tried to flash it. that's it, it stopped working. I know it was stupid things to do . I have given mobile to service center, other few famous mobile repairing shops, but no one was able to do anything.
My mobile was dead for almost 1 month, I tried lots of option, including MI flash tool, QPST(QFIL) etc. but didn't get it thought it. For current options also I was working for couple days, after that I got the solution.
Let start work now.....
------------------------------------------------------
There are two parts for this tutorial,
Part1 - make your device bootable/softbrick/start in recovery mode. This is difficult part and most of us stuck here only. We need to make device from hard brick to soft brick. Should work for all Qualcomm devices(except hardware failure).
Part2 - Flash ROM to your device. This is easy part and there are lots tutorial/information available to flashing ROM into device. It will be dependent on individual devices.
Part1:- -
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Download QualcommDrv.zip from here , extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver
now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” and the driver version 2.0.8.7 (please check it through Windows’ “Device Manager”). If its not detected, then you can keep mobile connecting to computer and press power button and volume down button.( This is for motorola g4 plus and can be different for your mobile. )
Now you have your mobile connected to computer, now follow the below steps.
Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat
It will start in command prompt and detect device on your computer port(eg. COM5, COM8 etc).
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile. Refer below Part2 for this.
If above didn't work and you are getting error like below..
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Or any other error, then its little tricky to solve this.
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.
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 2.059] ReadFile() failed, GetLastError()=0
[ 2.563] ...cpu.id = 2418 (0x972)
[ 2.563] ...cpu.sn = 28194769 (0x1ae37d1)
[ 2.563] Opening singleimage
[ 2.563] Loading package
[ 2.563] ...filename = singleimage.pkg.xml
[ 2.563] Loading programmer
[ 2.563] ...filename = programmer.mbn
[ 2.563] Sending programmer
[ 2.793] Handling things over to programmer
[ 2.793] Identifying CPU version
[ 2.793] Waiting for firehose to get ready
[ 5.800] ...MSM8952 1.1
[ 5.800] Determining target secure state
[ 5.800] ...secure = yes
[ 5.816] Flashing GPT...
[ 5.816] Flashing partition:0 with gpt_main0.bin
[ 5.816] Initializing storage
[ 5.816] Configuring device...
[ 5.832] ...blksz = 512
[ 6.331] Re-initializing storage...
[ 6.331] Initializing storage
[ 6.362] Flashing bootloader...
[ 6.362] Flashing aboot with emmc_appsboot.mbn
[ 6.721] Flashing rpm with rpm.mbn
[ 6.783] Flashing tz with tz.mbn
[ 7.033] Flashing hyp with hyp.mbn
[ 7.080] Flashing cmnlib with cmnlib.mbn
[ 7.158] Flashing keymaster with keymaster.mbn
[ 7.236] Flashing sbl1 with sbl1.mbn
[ 7.392] Rebooting to fastboot
[ 7.392] Total time: 7.392s
5. once this is complete then you mobile will boot in bootloader/recovery mode, or you can go to recovery mode using volume up/down button.
After this, your mobile would be detected using adb(android driver), and you can execute fastboot commands.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Step3 is the key for whole process. you may need to try multiple times while blank-flash.bat is running.
Once you reached here, Congratulations, your mobile is saved and back to life. next part flashing stock rom is very easy. I will try to find url for that.
you just need correct ROM for your mobile and steps to flash it.
Part 2 :
Below is url for motorola, you will get idea how to do it for your mobile by going through it.
Alternative, now you can give your mobile to service center or mobile repair shop to flash ROM.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
https://forum.xda-developers.com/showthread.php?t=2131284
https://www.xda-developers.com/how-to-install-custom-rom-android/
Let me know if you have any doubts/questions, I will try to update.
Also let me know if it helps you and you can also Donate (Optional).
Thanks for the help, it is good to know that there are people helping others but I already repaired it with the same method thanks for responding
Secure=no
vijayjadhav_143 said:
I have successfully recovered my dead/hard brick moto g4 plus mobile using below process.
To give you background, I have hard bricked my new moto g4 plus mobile. To do that, I have unlocked boot loader which void my warranty, then I have rooted yet and got root access. Till that it was working. After that I have installed custom rom cyanogenmod 14.1 . It was still working for some days. Now As I came from blackberry z10 to moto, I was missing blackberry hub features, so I downloaded BlackBerry android OS(Blackberry Priv) and tried to flash it. that's it, it stopped working. I know it was stupid things to do . I have given mobile to service center, other few famous mobile repairing shops, but no one was able to do anything.
My mobile was dead for almost 1 month, I tried lots of option, including MI flash tool, QPST(QFIL) etc. but didn't get it thought it. For current options also I was working for couple days, after that I got the solution.
Let start work now.....
------------------------------------------------------
There are two parts for this tutorial,
Part1 - make your device bootable/softbrick/start in recovery mode. This is difficult part and most of us stuck here only. We need to make device from hard brick to soft brick. Should work for all Qualcomm devices(except hardware failure).
Part2 - Flash ROM to your device. This is easy part and there are lots tutorial/information available to flashing ROM into device. It will be dependent on individual devices.
Part1:- -
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Download QualcommDrv.zip from here , extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver
now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” and the driver version 2.0.8.7 (please check it through Windows’ “Device Manager”). If its not detected, then you can keep mobile connecting to computer and press power button and volume down button.( This is for motorola g4 plus and can be different for your mobile. )
Now you have your mobile connected to computer, now follow the below steps.
Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat
It will start in command prompt and detect device on your computer port(eg. COM5, COM8 etc).
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile. Refer below Part2 for this.
If above didn't work and you are getting error like below..
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Or any other error, then its little tricky to solve this.
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.
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 2.059] ReadFile() failed, GetLastError()=0
[ 2.563] ...cpu.id = 2418 (0x972)
[ 2.563] ...cpu.sn = 28194769 (0x1ae37d1)
[ 2.563] Opening singleimage
[ 2.563] Loading package
[ 2.563] ...filename = singleimage.pkg.xml
[ 2.563] Loading programmer
[ 2.563] ...filename = programmer.mbn
[ 2.563] Sending programmer
[ 2.793] Handling things over to programmer
[ 2.793] Identifying CPU version
[ 2.793] Waiting for firehose to get ready
[ 5.800] ...MSM8952 1.1
[ 5.800] Determining target secure state
[ 5.800] ...secure = yes
[ 5.816] Flashing GPT...
[ 5.816] Flashing partition:0 with gpt_main0.bin
[ 5.816] Initializing storage
[ 5.816] Configuring device...
[ 5.832] ...blksz = 512
[ 6.331] Re-initializing storage...
[ 6.331] Initializing storage
[ 6.362] Flashing bootloader...
[ 6.362] Flashing aboot with emmc_appsboot.mbn
[ 6.721] Flashing rpm with rpm.mbn
[ 6.783] Flashing tz with tz.mbn
[ 7.033] Flashing hyp with hyp.mbn
[ 7.080] Flashing cmnlib with cmnlib.mbn
[ 7.158] Flashing keymaster with keymaster.mbn
[ 7.236] Flashing sbl1 with sbl1.mbn
[ 7.392] Rebooting to fastboot
[ 7.392] Total time: 7.392s
5. once this is complete then you mobile will boot in bootloader/recovery mode, or you can go to recovery mode using volume up/down button.
After this, your mobile would be detected using adb(android driver), and you can execute fastboot commands.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Step3 is the key for whole process. you may need to try multiple times while blank-flash.bat is running.
Once you reached here, Congratulations, your mobile is saved and back to life. next part flashing stock rom is very easy. I will try to find url for that.
you just need correct ROM for your mobile and steps to flash it.
Part 2 :
Below is url for motorola, you will get idea how to do it for your mobile by going through it.
Alternative, now you can give your mobile to service center or mobile repair shop to flash ROM.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
https://forum.xda-developers.com/showthread.php?t=2131284
https://www.xda-developers.com/how-to-install-custom-rom-android/
Let me know if you have any doubts/questions, I will try to update.
Also let me know if it helps you and you can also Donate (Optional).
Click to expand...
Click to collapse
For me it is showing secure=no and waiting for firehose to get ready is constantly popping out plz plz help me
Irvin16 said:
For me it is showing secure=no and waiting for firehose to get ready is constantly popping out plz plz help me
Click to expand...
Click to collapse
Could you please provide more details? on which steps you are getting error? error log/screenshot?
Its command prompt activity so not sure how you are getting pop up.
for moto g4 play
Colleague you have this file for moto g4 play
you can try above files, these are blankflash files meaning, after this your mobile will be reboot in recovery mode and will be available to connect it using adb/android driver and after that you can flash Moto g4 play stock ROM. you can search for moto g4 stock rom on internet.
fo moto g4 play
vijayjadhav_143 said:
you can try above files, these are blankflash files meaning, after this your mobile will be reboot in recovery mode and will be available to connect it using adb/android driver and after that you can flash Moto g4 play stock ROM. you can search for moto g4 stock rom on internet.
Click to expand...
Click to collapse
It's giving you this error.
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 1797 (0x705)
[ -0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.010] Failed identify board. Wrong package?
[ 0.010] ERROR: error loading package
[ 0.010] Check qboot_log.txt for more details
[ 0.010] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
try with other blankflash.
tecnologianet2 said:
It's giving you this error.
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 1797 (0x705)
[ -0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.010] Failed identify board. Wrong package?
[ 0.010] ERROR: error loading package
[ 0.010] Check qboot_log.txt for more details
[ 0.010] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
Click to expand...
Click to collapse
Did you tried with other blankflash*.zip, Please note below lines.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
for moto g4 play
vijayjadhav_143 said:
Did you tried with other blankflash*.zip, Please note below lines.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Click to expand...
Click to collapse
error logs
blankflash1
[ 0.000] Opening device: \\.\COM8
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 1797 (0x705)
[ 0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] Failed identify board. Wrong package?
[ 0.000] ERROR: error loading package
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
blankflash2
opening device: \\.\COM8
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
blankflash3
opening device: \\.\COM8
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
tecnologianet2 said:
error logs
blankflash1
[ 0.000] Opening device: \\.\COM8
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 1797 (0x705)
[ 0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] Failed identify board. Wrong package?
[ 0.000] ERROR: error loading package
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
blankflash2
opening device: \\.\COM8
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
blankflash3
opening device: \\.\COM8
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
Click to expand...
Click to collapse
please try below options to fix error (Unexpected packet: 4. Was expecting: 3)
1. Copy only singleimage.bin file from blankflash1 to blankfalsh 2 folder and run,
if not working then
2. revert above change, and only copy programmer.mbn in from blankflash1 to blankflash and run,
if not working then,
3. revert above changed and copy both programmer.mbn and singleimage.bin file from blankflash1 to blankflash2 and run.
please let me know the result.
for moto g4 play
vijayjadhav_143 said:
please try below options to fix error (Unexpected packet: 4. Was expecting: 3)
1. Copy only singleimage.bin file from blankflash1 to blankfalsh 2 folder and run,
if not working then
2. revert above change, and only copy programmer.mbn in from blankflash1 to blankflash and run,
if not working then,
3. revert above changed and copy both programmer.mbn and singleimage.bin file from blankflash1 to blankflash2 and run.
please let me know the result.
Click to expand...
Click to collapse
erro log
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
Ta giving same error i need singleimage file for moto g4 play
tecnologianet2 said:
erro log
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
Ta giving same error i need singleimage file for moto g4 play
Click to expand...
Click to collapse
you are really close of it because I was also getting error "Unexpected packet: 4. Was expecting: 3" then I tried few combinations of singleimage.bin and programmer.mbn files and it worked.
did you tried other combinations?
for moto g4 play
Yes many combinations
tecnologianet2 said:
Yes many combinations
Click to expand...
Click to collapse
Ok. Sorry, Actually I tried many days and many ways. I dont remember each and every things but these are the steps which helped me to get things done. there might be few difference due to different mobile you have. I will check my system and will check if I get some more details/scripts etc.
Don't give up.
fo moto g4 play
Poblema this in the singleimage.bin that is not for the model moto g4 play I need for this model
Blankflash files are device specific
siredux said:
Blankflash files are device specific
Click to expand...
Click to collapse
No, it's not because moto g4 play has another motherboard and moto g4 plus too.
Specifications for moto g4 play
Chipset
Qualcomm Snapdragon 410 MSM8916 Cortex-A53
tecnologianet2 said:
No, it's not because moto g4 play has another motherboard and moto g4 plus too.
Click to expand...
Click to collapse
OP says any Qualcomm device can be unbricked with this blankflash which is not true. This is only for G4/G4+. If you want to unbrick G4 Play you need that specific blankflash file, otherwise it will remain as a cute paperweight, duh
Will anyone from xda be able to create a blank image for this moto g4 play
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.
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!
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??