So a while ago i got myself a new phone and the Moto went into "storage", the thing was on and working when i put it on the shelf, in a few days time the battery went dead because i didnt charge so naturally it shut itself off, 7 months later (today), i plugged it in and the thing wont power on, id only get the LED blinking thing and thats all the life i see from it.
What have i tried?
Entering bootloader (that didnt work) and im still on a black screen (turned off not just blank) with LED flashing, i installed the whole load of drivers: Qualcomm drivers, ADB fastboot, moto drivers from their site all the fun stuff. Then i found a thread on here suggesting the blank-flash thing (finally a glimpse of hope), i got it downloaded, started the bat file, crossed my fingers and as i expected..absolutely nothing happened or rather ERROR happened.... "ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error". Riiiiight....google it you might say and google it i did (and since i got to the point where i had to search on Bing its clear that nothing i found worked)
So why am i here, why do i care about a phone i dont use anymore (quite simple i wanna have a backup JIC Xiaomi decides to nope on me anytime soon)
And since i have been spending all the time from 8 am to now on this matter, here i am
I tried a different pc (with even a diff version of windows 10 installed on it)
I tried the thing with the windows testing mode on and off
I tried the motorola suggested recovery tool which basically did nothing but remind me my phone is long gone
I tried Ubuntu (to be fair i barely knew what the hell i was doing there but i still gave ADB and fastboot a try just so i can say i did as much as i can)
Here i am, clueless, i googled as much i could, youtubed it to moon and back, and i finally thrown in the towel and decided to ask for help here.
i dont expect to even get an answer but if you got any idea just send it
Moto G4 XT1622 (last time i used it i think it was on RessurectionRemix or LineageOS one of the newer versions however i cant remember if it were 8 or 9 though)
oh and this
Code:
**** Log buffer [000001] 2020-11-20_10:35:57 ****
[ 0.000] Opening device: \\.\COM3
[ 0.006] Detecting device
[ 4.077] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.077] Check qboot_log.txt for more details
[ 4.077] Total time: 4.079s
[ 4.077]
[ 4.077] qboot version 3.40
[ 4.077]
[ 4.077] DEVICE {
[ 4.077] name = "\\.\COM3",
[ 4.077] flags = "0x64",
[ 4.077] addr = "0x61FE4C",
[ 4.077] api.bnr = "0x1D2E80",
[ 4.077] }
[ 4.077]
[ 4.077]
[ 4.077] Backup & Restore {
[ 4.077] num_entries = 0,
[ 4.077] restoring = "false",
[ 4.077] backup_error = "not started",
[ 4.077] restore_error = "not started",
[ 4.077] }
[ 4.077]
Skellytone said:
So a while ago i got myself a new phone and the Moto went into "storage", the thing was on and working when i put it on the shelf, in a few days time the battery went dead because i didnt charge so naturally it shut itself off, 7 months later (today), i plugged it in and the thing wont power on, id only get the LED blinking thing and thats all the life i see from it.
What have i tried?
Entering bootloader (that didnt work) and im still on a black screen (turned off not just blank) with LED flashing, i installed the whole load of drivers: Qualcomm drivers, ADB fastboot, moto drivers from their site all the fun stuff. Then i found a thread on here suggesting the blank-flash thing (finally a glimpse of hope), i got it downloaded, started the bat file, crossed my fingers and as i expected..absolutely nothing happened or rather ERROR happened.... "ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error". Riiiiight....google it you might say and google it i did (and since i got to the point where i had to search on Bing its clear that nothing i found worked)
So why am i here, why do i care about a phone i dont use anymore (quite simple i wanna have a backup JIC Xiaomi decides to nope on me anytime soon)
And since i have been spending all the time from 8 am to now on this matter, here i am
I tried a different pc (with even a diff version of windows 10 installed on it)
I tried the thing with the windows testing mode on and off
I tried the motorola suggested recovery tool which basically did nothing but remind me my phone is long gone
I tried Ubuntu (to be fair i barely knew what the hell i was doing there but i still gave ADB and fastboot a try just so i can say i did as much as i can)
Here i am, clueless, i googled as much i could, youtubed it to moon and back, and i finally thrown in the towel and decided to ask for help here.
i dont expect to even get an answer but if you got any idea just send it
Moto G4 XT1622 (last time i used it i think it was on RessurectionRemix or LineageOS one of the newer versions however i cant remember if it were 8 or 9 though)
oh and this
Code:
**** Log buffer [000001] 2020-11-20_10:35:57 ****
[ 0.000] Opening device: \\.\COM3
[ 0.006] Detecting device
[ 4.077] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.077] Check qboot_log.txt for more details
[ 4.077] Total time: 4.079s
[ 4.077]
[ 4.077] qboot version 3.40
[ 4.077]
[ 4.077] DEVICE {
[ 4.077] name = "\\.\COM3",
[ 4.077] flags = "0x64",
[ 4.077] addr = "0x61FE4C",
[ 4.077] api.bnr = "0x1D2E80",
[ 4.077] }
[ 4.077]
[ 4.077]
[ 4.077] Backup & Restore {
[ 4.077] num_entries = 0,
[ 4.077] restoring = "false",
[ 4.077] backup_error = "not started",
[ 4.077] restore_error = "not started",
[ 4.077] }
[ 4.077]
Click to expand...
Click to collapse
5how is it listed in device manager?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
5how is it listed in device manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
It shows up as some Qualcomm DL9008, im quite sure thats a good sign cause it is recognised as a qualcomm device
Skellytone said:
It shows up as some Qualcomm DL9008, im quite sure thats a good sign cause it is recognised as a qualcomm device
Click to expand...
Click to collapse
That means it's in EDL mode only a blankflash or mmcblk0.img will work.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
That means it's in EDL mode only a blankflash or mmcblk0.img will work.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
ive been trynig the blank flash fopr 5 hours now, no result
can you tell me more about mmcblk0.img though or send me to a post ?
Skellytone said:
ive been trynig the blank flash fopr 5 hours now, no result
can you tell me more about mmcblk0.img though or send me to a post ?
Click to expand...
Click to collapse
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my Moto E (4) using Tapatalk
Related
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
I had unlocked my bootloader and was trying to lock it by flashing NPJ25.93-14 after the NPJ25.93-14-8 update it didn't lock my bootloader and it booted up but with bootloader unlocked warning.After keeping it for OTA update i noticed my phone is not
turning on but led light flashes after every one second .It is not evening going to fastboot mode after flashing blankflash.bat file .
At a service center they said they would replace the board for Rs 6000. I am running low on budget please help me!
I had repaired my Moto g using ur tutorial which was in the same state so i think u can help me.:crying::crying::crying:
these are the errors i get while running blankflash.bat
**** Log buffer [000001] 2017-07-24_17:59:43 ****
[ 0.000] Opening device: \\.\COM7
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2418 (0x972)
[ 0.000] ...cpu.sn = 15734574 (0xf0172e)
[ 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.218] Handling things over to programmer
[ 0.218] Identifying CPU version
[ 0.218] Waiting for firehose to get ready
[ 9.688] ReadFile() failed, GetLastError()=0
[ 9.741] ReadFile() failed, GetLastError()=0
[ 9.791] ReadFile() failed, GetLastError()=0
[ 9.841] ReadFile() failed, GetLastError()=0
[ 24.003] ReadFile() failed, GetLastError()=0
[ 28.417] ReadFile() failed, GetLastError()=0
[ 62.338] Waiting for firehose to get ready
[122.866] ...MSM8952 unknown
[122.866] Determining target secure state
[122.867] Waiting for firehose to get ready
[183.284] ...secure = no
[183.292] Flashing GPT...
[183.292] Flashing partition:0 with gpt_main0.bin
[183.293] Initializing storage
[183.295] Waiting for firehose to get ready
[243.596] Configuring device...
[243.597] Waiting for firehose to get ready
[303.901] Waiting for firehose to get ready
[364.211] Waiting for firehose to get ready
[424.574] Waiting for firehose to get ready
[485.180] 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
[485.180] Check qboot_log.txt for more details
[485.180] Total time: 485.180s
[485.180]
[485.180] qboot version 3.40
[485.180]
[485.180] DEVICE {
[485.180] name = "\\.\COM7",
[485.180] flags = "0x64",
[485.180] addr = "0x22FE6C",
[485.180] sahara.current_mode = "0",
[485.180] api.buffer = "0x1770020",
[485.180] cpu.serial = "15734574",
[485.180] cpu.id = "2418",
[485.180] cpu.sv_sbl = "0",
[485.180] cpu.name = "MSM8952",
[485.180] storage.type = "eMMC",
[485.180] sahara.programmer = "programmer.mbn",
[485.180] module.firehose = "0x33F2B8",
[485.180] cpu.ver = "0",
[485.180] cpu.vername = "unknown",
[485.180] api.bnr = "0x16DA760",
[485.180] }
[485.180]
[485.180]
[485.180] Backup & Restore {
[485.180] num_entries = 0,
[485.180] restoring = "false",
[485.180] backup_error = "not started",
[485.180] restore_error = "not started",
[485.180] }
[485.180]
**** Log buffer [000001] 2017-07-31_13:01:06 ****
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ 4.058] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.058] Check qboot_log.txt for more details
[ 4.058] Total time: 4.058s
[ 4.058]
[ 4.058] qboot version 3.40
[ 4.058]
[ 4.058] DEVICE {
[ 4.058] name = "\\.\COM8",
[ 4.058] flags = "0x64",
[ 4.058] addr = "0x22FE6C",
[ 4.058] api.bnr = "0x782F40",
[ 4.058] }
[ 4.058]
[ 4.058]
[ 4.058] Backup & Restore {
[ 4.058] num_entries = 0,
[ 4.058] restoring = "false",
[ 4.058] backup_error = "not started",
[ 4.058] restore_error = "not started",
[ 4.058] }
[ 4.058]
JOEL JOE PIOUS said:
I had unlocked my bootloader and was trying to lock it by flashing NPJ25.93-14 after the NPJ25.93-14-8 update it didn't lock my bootloader and it booted up but with bootloader unlocked warning.After keeping it for OTA update i noticed my phone is not
turning on but led light flashes after every one second .It is not evening going to fastboot mode after flashing blankflash.bat file .
At a service center they said they would replace the board for Rs 6000. I am running low on budget please help me!
I had repaired my Moto g using ur tutorial which was in the same state so i think u can help me.:crying::crying::crying:
Click to expand...
Click to collapse
Bro, it's really sad. i m also going through the same condition. The only solution for this issue is flashing blankflash. But no one have updated blankflash . So we only have to wait for updated blankflash.
ADITYA_KUMAR said:
Bro, it's really sad. i m also going through the same condition. The only solution for this issue is flashing blankflash. But no one have updated blankflash . So we only have to wait for updated blankflash.
Click to expand...
Click to collapse
:crying::crying:
ADITYA_KUMAR said:
Bro, it's really sad. i m also going through the same condition. The only solution for this issue is flashing blankflash. But no one have updated blankflash . So we only have to wait for updated blankflash.
Click to expand...
Click to collapse
If anything helps in getting ur phone alive plz report to me too
JOEL JOE PIOUS said:
If anything helps in getting ur phone alive plz report to me too
Click to expand...
Click to collapse
same for u2. plzz inform me 2. :crying::crying:
Damn, your brick was avoidable even, since flashing the NPJS25.93-14-8 fastboot firmware would likely have locked your device and kept it going.
Unfortunately, we'll have to see if Motorola even makes a new blankflash for our devices, a slight chance may be if Android O comes out for our device, if they still make our device by then...
I tried locking with np25.93-14-8 but was unsuccessful
:crying::crying:
echo92 said:
damn, your brick was avoidable even, since flashing the npjs25.93-14-8 fastboot firmware would likely have locked your device and kept it going.
unfortunately, we'll have to see if motorola even makes a new blankflash for our devices, a slight chance may be if android o comes out for our device, if they still make our device by then...
Click to expand...
Click to collapse
thanks anyways
JOEL JOE PIOUS said:
:crying::crying:
Click to expand...
Click to collapse
Yeah, unfortunately by downgrading from the June update it's a hard brick - and the blankflash we have, as you've mentioned, doesn't recover devices
Only resolutions at the moment is to save up to get the motherboard replaced or save up for a new device (whatever that might be)
there is nothing like newer blankflash. our devices are bricked now and they will bricked forever. get the motherboard replaced or save up for a new device
I can't afford to replace the motherboard now . waiting for blankflash or doing repair whenever i can afford:crying:
echo92 said:
Yeah, unfortunately by downgrading from the June update it's a hard brick - and the blankflash we have, as you've mentioned, doesn't recover devices
Only resolutions at the moment is to save up to get the motherboard replaced or save up for a new device (whatever that might be)
Click to expand...
Click to collapse
but moto g xt1033 came back to life with the blankflash file:crying:
siddhesh9146 said:
there is nothing like newer blankflash. our devices are bricked now and they will bricked forever. get the motherboard replaced or save up for a new device
Click to expand...
Click to collapse
u changed ur board ? how much ?
ADITYA_KUMAR said:
Bro, it's really sad. i m also going through the same condition. The only solution for this issue is flashing blankflash. But no one have updated blankflash . So we only have to wait for updated blankflash.
Click to expand...
Click to collapse
Same problem with me...m also going through same condition...can I get ur no plzz...
can someone plz upload file name
sdm_hdr.mbn and
pitfile.pit
adb commands for.
sdm_hdr.mbn
dd if=/dev/block/mmcblk0p1 of=/sdcard/Desktop/
sdm_hdr.mbn
pitfile.pit
dd if=/dev/block/mmcblk0p9 of=/sdcard/Desktop/
pitfile.pit
and copy this file frome desktop and uploade on mega.
tawanda01 said:
can someone plz upload file name
sdm_hdr.mbn and
pitfile.pit
adb commands for.
sdm_hdr.mbn
dd if=/dev/block/mmcblk0p1 of=/sdcard/Desktop/
sdm_hdr.mbn
pitfile.pit
dd if=/dev/block/mmcblk0p9 of=/sdcard/Desktop/
pitfile.pit
and copy this file frome desktop and uploade on mega.
Click to expand...
Click to collapse
Hey m having G4 plus XT1643
My phone was hard bricked can u plzz tell me what can I do ???? Plzz help me.....
deepakgadhave61 said:
Hey m having G4 plus XT1643
My phone was hard bricked can u plzz tell me what can I do ???? Plzz help me.....
Click to expand...
Click to collapse
Please read a bit as I told you. All users here waiting for blank flash...
I have successfully booted to bootloader but im unable to run fastboot command..
Error
C:\mfastboot>mfastboot flash partition gpt.bin
< waiting for device >
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.093s
Plzz help
can u plz iexplain how could u boot into bootloader as i have hardbricked my phone
deepakgadhave61 said:
I have successfully booted to bootloader but im unable to run fastboot command..
Error
C:\mfastboot>mfastboot flash partition gpt.bin
< waiting for device >
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.093s
Plzz help
Click to expand...
Click to collapse
what was the version of update u have in ur phone, then flash latest firmware
Someone can measure a help my phone received a December update of Android 7.0 when the phone renicio it does not care anymore when it connects the charger it just flashes I already tried to use blank-flash more without success of the error at the end of the process I'm going to show The log below I hope someone can help me
**** Log buffer [000001] 2019-03-26_12:16:19 ****
[ 0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 0.005] ...cpu.id = 2418 (0x972)
[ 0.005] ...cpu.sn = 42510165 (0x288a755)
[ 0.005] Opening singleimage
[ 0.105] Loading package
[ 0.108] ...filename = singleimage.pkg.xml
[ 0.111] Loading programmer
[ 0.111] ...filename = programmer.mbn
[ 0.112] Sending programmer
[ 0.333] Handling things over to programmer
[ 0.334] Identifying CPU version
[ 0.337] Waiting for firehose to get ready
[ 60.457] Waiting for firehose to get ready
[120.553] ...MSM8952 unknown
[120.553] Determining target secure state
[120.555] Waiting for firehose to get ready
[180.676] ...secure = no
[180.690] Flashing GPT...
[180.695] Flashing partition:0 with gpt_main0.bin
[180.709] Initializing storage
[180.713] Waiting for firehose to get ready
[240.827] Configuring device...
[240.829] Waiting for firehose to get ready
[300.937] Waiting for firehose to get ready
[361.039] Waiting for firehose to get ready
[421.180] Waiting for firehose to get ready
[481.279] 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.280] Check qboot_log.txt for more details
[481.281] Total time: 481.283s
Click to expand...
Click to collapse
Which blankflash did you try, have you tried this one https://forum.xda-developers.com/showpost.php?p=79013024&postcount=523 ?
Looks like the blankflash has trouble communicating, maybe try a few more times?
What firmware were you previously on, was it the stock Oreo firmware?
android 7.0
I already did everything and I can not resuscitate the cell phone.
jabezinho said:
I already did everything and I can not resuscitate the cell phone.
Click to expand...
Click to collapse
Which blankflashes have you tried? Try using a computer with a USB 2.0 port and try some of the tips in https://forum.xda-developers.com/showpost.php?p=73434849&postcount=2 and https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Okay, were you always on Android 7? Or did you downgrade your device from a later stock firmware? Also, which December update did you get, was it the NPJ25.93-14 December 2016 update or the NPJS25.93-14-13 December 2027 update?
it was in 8.1 but it was bugged the sound was getting down by itself and lost important connections by calsa of that I went back to android 7.0 appeared an update botei to install after that the phone does not call anymore only it stays flashing the led in the loaded or when it connects to the pc
jabezinho said:
it was in 8.1 but it was bugged the sound was getting down by itself and lost important connections by calsa of that I went back to android 7.0 appeared an update botei to install after that the phone does not call anymore only it stays flashing the led in the loaded or when it connects to the pc
Click to expand...
Click to collapse
Having been on stock 8.1 previously, that's the main problem - downgrading and flashing your device with an old OTA has corrupted your bootloader (your bootloader likely did not get downgraded for security reasons). Currently we do not have a working method to resolve this - there have been methods tested/currently being tested, which have not borne any good results.
If you cannot wait, you will likely have to pay for a repair or purchase a new device, there's no other method available to save your device right now. This is partly why we advise not downgrading stock firmware unless you do not use OTA updates (and even then, be careful).
when it arrives in that part it type that restarts it makes noise of connected and disconnected and stays long in that part then then it carries until the error
[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.004] ...cpu.sn = 42510165 (0x288a755)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.007] ...filename = singleimage.pkg.xml
[ 0.009] Loading programmer
[ 0.010] ...filename = programmer.mbn
[ 0.010] Sending programmer
[ 0.236] Handling things over to programmer
[ 0.237] Identifying CPU version
[ 0.239] Waiting for firehose to get ready
Click to expand...
Click to collapse
jabezinho said:
when it arrives in that part it type that restarts it makes noise of connected and disconnected and stays long in that part then then it carries until the error
Click to expand...
Click to collapse
You could keep trying, see if your device connects with the blankflash (though the same error keeps appearing with members that have tried it - no firehose connection, so the blankflash is unable to flash a working bootloader to your device. Sometimes a bad connection, sometimes the blankflash is too old to repair your device). Else, you'd have to wait for a blankflash created after 11/01/2019, which is not very likely and would have to be leaked from Motorola.
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
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??