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.
Related
C:\Users\AKASH AK\Desktop\MOTO\Blankflash MG4P_3\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.003] ...cpu.id = 2418 (0x972)
[ 0.003] ...cpu.sn = 30324219 (0x1ceb5fb)
[ 0.003] Opening singleimage
[ 0.029] Loading package
[ 0.032] ...filename = singleimage.pkg.xml
[ 0.034] Loading programmer
[ 0.034] ...filename = programmer.mbn
[ 0.034] Sending programmer
[ 0.255] Handling things over to programmer
[ 0.255] Identifying CPU version
[ 0.257] Waiting for firehose to get ready
[ 60.755] Waiting for firehose to get ready
[121.209] ...MSM8952 unknown
[121.210] Determining target secure state
[121.213] Waiting for firehose to get ready
[181.424] ...secure = no
[181.435] Flashing GPT...
[181.435] Flashing partition:0 with gpt_main0.bin
[181.435] Initializing storage
[181.438] Waiting for firehose to get ready
[241.562] Configuring device...
[241.566] Waiting for firehose to get ready
[301.736] Waiting for firehose to get ready
[361.985] Waiting for firehose to get ready
[422.088] Waiting for firehose to get ready
[482.192] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[482.193] Check qboot_log.txt for more details
[482.193] Total time: 482.194s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
C:\Users\AKASH AK\Desktop\MOTO\Blankflash MG4P_3\blankflash>pause
Press any key to continue . . .
?? plzzzz help for this problem
this is latest bootloader
BL: B1.09 (sha-9a76df4, 2019-01-11 14:40:15) ?? thanks
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
I'd try the blankflash a few more times but it seems that blankflash does not work in rescuing devices updated to stock Oreo. Without access to a blankflash newer than 11/01/2019, we're stuck for options that don't require payment.
my wife plugged in her G5 plus into to plug last night and when she woke up it was turned off and doesn't respond to anything.. I tried using the volum - & power button to get it to recovery mode but it doesn't work. When I plug it in the white notification light blinks.. nothing has been tampered with (no custom flash or anything)
I browsed the forum and found some info at https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 but didn't get it to work since it was for a G4 plus:
- set pc to test mode
- installed Qualcomm drivers
- when phone is plugged into usb on PC I get a Qualcomm Device in COM3
- I tried using a blankflash batch file using Qboot 3.4 I found on other threads on the site but didn't work.. thread mentions a 3.85 for Oreo but can not find it
Code:
[ 0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 4.013] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.013] Check qboot_log.txt for more details
[ 4.014] Total time: 4.017s
[ 4.015]
[ 4.015] qboot version 3.40
[ 4.015]
[ 4.015] DEVICE {
[ 4.015] name = "\\.\COM3",
[ 4.015] flags = "0x64",
[ 4.015] addr = "0x61FE4C",
[ 4.015] api.bnr = "0x662F78",
[ 4.015] }
[ 4.015]
[ 4.015]
[ 4.015] Backup & Restore {
[ 4.015] num_entries = 0,
[ 4.015] restoring = "false",
[ 4.015] backup_error = "not started",
[ 4.015] restore_error = "not started",
[ 4.015] }
[ 4.015]
but when I keep running the batch (as stated in the thread, it can take some time to get a lock on the phone) I sometimes get something like this:
Code:
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 70 (0x46)
[ 0.004] ...cpu.sn = 2491206852 (0x947cccc4)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.009] ...filename = singleimage.pkg.xml
[ 0.012] Loading programmer
[ 0.012] ...filename = programmer.mbn
[ 0.012] Sending programmer
[ 0.227] Handling things over to programmer
[ 0.227] Identifying CPU version
[ 0.229] Waiting for firehose to get ready
[ 11.348] ReadFile() failed, GetLastError()=0
[ 11.350] ReadFile() failed, GetLastError()=0
[ 21.133] ReadFile() failed, GetLastError()=0
[ 21.136] ReadFile() failed, GetLastError()=0
[ 60.543] Waiting for firehose to get ready
[ 63.543] WriteFile() failed, GetLastError()=0
[ 68.482] ReadFile() failed, GetLastError()=0
[120.661] ...MSM8953 unknown
[120.661] Determining target secure state
[120.664] Waiting for firehose to get ready
[180.865] ...secure = no
[180.891] Waiting for firehose to get ready
[240.957] Configuring device...
[240.960] Waiting for firehose to get ready
[301.630] Waiting for firehose to get ready
[360.485] ReadFile() failed, GetLastError()=0
[360.489] ReadFile() failed, GetLastError()=0
[364.229] Waiting for firehose to get ready
[424.262] Waiting for firehose to get ready
[484.384] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->devic
e_read()->IO error
[484.384] Check qboot_log.txt for more details
[484.384] Total time: 484.385s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffe
r_read()->device_read()->IO error
Anybody who can point me in the direction of the correct files to get it to work?
Dieterweireldt said:
my wife plugged in her G5 plus into to plug last night and when she woke up it was turned off and doesn't respond to anything.. I tried using the volum - & power button to get it to recovery mode but it doesn't work. When I plug it in the white notification light blinks.. nothing has been tampered with (no custom flash or anything)
I browsed the forum and found some info at https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 but didn't get it to work since it was for a G4 plus:
- set pc to test mode
- installed Qualcomm drivers
- when phone is plugged into usb on PC I get a Qualcomm Device in COM3
- I tried using a blankflash batch file using Qboot 3.4 I found on other threads on the site but didn't work.. thread mentions a 3.85 for Oreo but can not find it
but when I keep running the batch (as stated in the thread, it can take some time to get a lock on the phone) I sometimes get something like this:
Anybody who can point me in the direction of the correct files to get it to work?
Click to expand...
Click to collapse
There is no blankflash file for the Moto G5+ , such a file has to be leaked by some Motorola employee but that didn't happen. There is one for the Moto Z2 play but that one was for Nougat and won't work on Oreo, it was risky on 7.0 too. You can search it here on XDA or Google if you want to give it a shot nevertheless but if you can't reach fastboot mode to flash a firmware you're most likely out of luck.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
There is no blankflash file for the Moto G5+ , such a file has to be leaked by some Motorola employee but that didn't happen. There is one for the Moto Z2 play but that one was for Nougat and won't work on Oreo, it was risky on 7.0 too. You can search it here on XDA or Google if you want to give it a shot nevertheless but if you can't reach fastboot mode to flash a firmware you're most likely out of luck.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Ok thank you for the reply.. ordered the G8 plus for her now
Dieterweireldt said:
Ok thank you for the reply.. ordered the G8 plus for her now
Click to expand...
Click to collapse
Good choice.
Sent from my Moto G5 Plus using XDA Labs
try flashing lineage os 17 but my device was hard brick ed in the February patch update try to use an existing blankflash but it doesn't work I need a newer one and don't exit, someone has it or I have to wait
C:\Users\Windows\Desktop\blankflash (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM9
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 186 (0xba)
[ 0.000] ...cpu.sn = 431154525 (0x19b2e55d)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.322] Handling things over to programmer
[ 0.322] Identifying CPU version
[ 0.322] Waiting for firehose to get ready
[ 63.848] Waiting for firehose to get ready
[124.207] ...MSM8953 unknown
[125.269] Determining target secure state
[125.698] Waiting for firehose to get ready
[186.411] ...secure = no
[190.829] Initializing storage
[201.027] Waiting for firehose to get ready
[266.599] Configuring device...
[266.605] Waiting for firehose to get ready
[328.286] Waiting for firehose to get ready
[388.635] Waiting for firehose to get ready
[448.965] Waiting for firehose to get ready
[509.214] Initializing storage
[510.903] Waiting for firehose to get ready
I have the exact same problem, just on the G7 Power.
florosus said:
I have the exact same problem, just on the G7 Power.
Click to expand...
Click to collapse
Found this on another thread but now it asks for firehose to recover fastboot, need a firehose file so i can boot my phone xt1962-4 RIVER
https://mirrors.lolinet.com/firmware/moto/river/
https://forum.xda-developers.com/mo...ck-moto-g7-t3938342/post81971781#post81971781
lolcos said:
Found this on another thread but now it asks for firehose to recover fastboot, need a firehose file so i can boot my phone xt1962-4 RIVER
https://mirrors.lolinet.com/firmware/moto/river/
https://forum.xda-developers.com/mo...ck-moto-g7-t3938342/post81971781#post81971781
Click to expand...
Click to collapse
currently a developer is creating the file for river, already testie but sends error I hope soon is good
Ivan.coe said:
currently a developer is creating the file for river, already testie but sends error I hope soon is good
Click to expand...
Click to collapse
where did you find that info? Can you share the info you got, have you got any file that i could run on QFIL
lolcos said:
where did you find that info? Can you share the info you got, have you got any file that i could run on QFIL
Click to expand...
Click to collapse
https://t.me/MotoG7RiverDiscussion
I also bricked my G7 River February Patch - XT1962-4 PPOS29.114-134-10, need a new blankflash the provided one is not working...
Ivan.coe said:
try flashing lineage os 17 but my device was hard brick ed in the February patch update try to use an existing blankflash but it doesn't work I need a newer one and don't exit, someone has it or I have to wait
Click to expand...
Click to collapse
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM5
[ 0.008] Detecting device
[ 0.011] ...cpu.id = 186 (0xba)
[ 0.011] ...cpu.sn = 467405420 (0x1bdc0a6c)
[ 0.011] Opening singleimage
[ 0.012] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.014] Loading programmer
[ 0.014] ...filename = programmer.mbn
[ 0.014] Sending programmer
[ 0.298] Handling things over to programmer
[ 0.298] Identifying CPU version
[ 0.299] Waiting for firehose to get ready
[ 61.000] Waiting for firehose to get ready
[121.321] ...MSM8953 unknown
[121.321] Determining target secure state
[121.322] Waiting for firehose to get ready
[181.677] ...secure = no
[181.693] Initializing storage
Click to expand...
Click to collapse
BradXY said:
I also bricked my G7 River February Patch, need a new blankflash the provided one is not working...
Click to expand...
Click to collapse
still nothing, maybe they'll take it out until android 10 arrives
Please someone make the blankflash of the February patch, I have a Moto G7 paperweight
Seems we are completely SOL and totally FUBAR
[SOLVED]
This is solved check for Feb Patch [SOLVED] thread!
So I have been trying to use the blankflash file that is hosted on lolinet for the river device, and I also made my own blankflash image from the latest AMZ software image hosted on lolinet (This is an Amazon Moto G7).
The phone is bricked with the bootloader gone. It is stuck in Qualcomm's download mode. I keep trying to use blankflash, but it keeps giving this same error. I am at a loss on what to try next.
Code:
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM6
[ 0.000] Detecting device
[ 0.010] ...cpu.id = 186 (0xba)
[ 0.010] ...cpu.sn = 753318839 (0x2ce6bbb7)
[ 0.010] Opening singleimage
[ 0.070] Loading package
[ 0.070] ...filename = singleimage.pkg.xml
[ 0.070] Loading programmer
[ 0.070] ...filename = programmer.mbn
[ 0.070] Sending programmer
[ 0.370] Handling things over to programmer
[ 0.370] Identifying CPU version
[ 0.370] Waiting for firehose to get ready
[ 30.959] ReadFile() failed, GetLastError()=0
[ 60.697] Waiting for firehose to get ready
[121.055] ...MSM8953 unknown
[121.055] Determining target secure state
[121.055] Waiting for firehose to get ready
[181.474] ...secure = no
[181.546] Initializing storage
[181.550] Waiting for firehose to get ready
[242.088] Configuring device...
[242.092] Waiting for firehose to get ready
[302.492] Waiting for firehose to get ready
[362.895] Waiting for firehose to get ready
[423.279] Waiting for firehose to get ready
[483.762] Initializing storage
[483.762] Waiting for firehose to get ready
[544.159] Configuring device...
[544.167] Waiting for firehose to get ready
[604.828] Waiting for firehose to get ready
[665.284] Waiting for firehose to get ready
[725.666] Waiting for firehose to get ready
[786.212] Waiting for firehose to get ready
[846.856] Configuring device...
[846.856] Waiting for firehose to get ready
[907.510] Waiting for firehose to get ready
[968.159] Waiting for firehose to get ready
[1028.786] Waiting for firehose to get ready
[1089.412] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1089.412] Check qboot_log.txt for more details
[1089.412] Total time: 1089.412s
[1089.412] There were some hiccups in backup and restore.
[1089.412] Please save the following files and see a Bootloader member.
[1089.412] 1) ./qboot_log.txt
[1089.427] 2) ./backup_0x2CE6BBB7_2020-03-29_021513.img
[1089.427]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
this in the February 2020 update? if you are the only way and using sdcard with debrick, just download the phone up to 0% and try to boot using the sdcard
I've tried using the SDCard with a loader.img file I found and flashed, (Which was supposedly a bootloader for the Moto G7), but it wouldn't boot from it. What is the debrick you are referring to? I haven't tried that. And yeah it is the February 2020 update.
Do I have to let the phone drain to 0% before it will allow me to do anything other than go straight into download mode?
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??