yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Questions & Answers] wasteoflife:
It's been aprox 4 days of me trying to make my phone show up on my computer. I've installed a lot of drivers, I tried running on test mode, I've tried many different usb cables, I've tried holding buttons for minutes and nothing works. :(

I know what to do in case of it being hardbricked, I just need it to show up, but it's taking sooo long I can't get it to show up. Not even as an unrecognized device. So I think it's probably hardware failure. :(
[Moto G4 Plus Questions & Answers] nischait:
Unbricked but when I power on it then screen fluctuates and then auto power off. Have any working solutions.

In charging or recovery mode display working properly and no fluctuations.
[Moto G4 Plus Questions & Answers] iurd2007:
Did you tried to install a custom rom to see if the issue continues?
[Moto G4 Plus Questions & Answers] nischait:
No I didn't tried . Bootloader is locked and don't know how to unlock it( First time using Moto device)
[Moto G4 Plus Questions & Answers] iurd2007:
How to unlock bootloader:

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

Read and follow the steps
[Moto G4 Plus Questions & Answers] blue_ranger:
Device not detected

Hey guys, I moved to iPhone a few months ago and my G4 Plus has just been sitting unused in a drawer. So today, I took it out and it wouldn't turn on.

Tried charging it, and the LED would just keep blinking,

Connected it to the computer...same thing.

Used the button combinations to try and get into fast boot mode, or recovery mode, nothing.

The phone doesn't respond at all.

So I followed this thread, apparently it needs to be detected as "Qualcomm HS-USB QDLoader 9008" so I can fix it with the blankflash, but its not being detected at all.

I disabled secure driver signing, installed both the Qualcomm driver, and the Motorola drivers and ADB drivers, still nothing when I plug in into the PC, just the blinking LED.

Any suggestions?
[Moto G4 Plus Questions & Answers] maxzboy:
i tried it. but no works .( its shown blank flash greet device error reading packet).

hi, i tried it.... but no works . ( its shown blank flash greet device error reading packet). My Phone Wiko highway pure msm8916 410 snapdragon . may you can help me create this blank flash file. please ? thanks
[Moto G4 Plus Questions & Answers] shawgluz:
i can help me :(?

---------- Post added at 07:20 AM ---------- Previous post was at 06:59 AM ----------

I followed the steps and it worked !!!

https://youtu.be/m2NqpY6X-X4
[Moto G4 Plus Questions & Answers] durgahembram987:
Thank You very much!! It worked perfectly for me..
[Moto G4 Plus Questions & Answers] flash713:
I don't use windows at all so all i have is ubuntu 18.04 LTS

Here's what my moto g7 power (metro) reads once I get it going:

sudo ./blank-flash.sh

Motorola qboot utility version 3.40

[ 0.000] Opening device: /dev/ttyUSB0

[ 0.000] Detecting device

[ 2.520] ...cpu.id = 186 (0xba)

[ 2.520] ...cpu.sn = 839264944 (0x32062ab0)

[ 2.520] Opening singleimage

[ 2.521] Loading package

[ 2.524] ...filename = singleimage.pkg.xml

[ 2.527] Loading programmer

[ 2.527] ...filename = programmer.mbn

[ 2.527] Sending programmer

[ 2.815] Handling things over to programmer

[ 2.815] Identifying CPU version

[ 2.820] Waiting for firehose to get ready

[ 5.820] serial_write(), line 280: Input/output error

[ 64.538] Waiting for firehose to get ready

[ 67.538] serial_write(), line 280: Input/output error

[127.265] ...MSM8953 unknown

[127.265] Determining target secure state

[127.268] Waiting for firehose to get ready

[130.269] serial_write(), line 280: Input/output error

[187.504] ...secure = no

[187.550] Initializing storage

[187.553] Waiting for firehose to get ready

[190.553] serial_write(), line 280: Input/output error

[252.648] Configuring device...

[252.655] Waiting for firehose to get ready

[255.655] serial_write(), line 280: Input/output error

[315.265] Waiting for firehose to get ready

[318.265] serial_write(), line 280: Input/output error

[378.203] Waiting for firehose to get ready

[381.204] serial_write(), line 280: Input/output error

[439.669] Waiting for firehose to get ready

[442.670] serial_write(), line 280: Input/output error
[Moto G4 Plus Questions & Answers] echo92:
Unfortunately, the blankflashes in this thread will not work on a G7 power, the files here are simply too old. Your best bet is to hope for a G7 power blankflash and I see you've tried one here https://xdaforums.com/g7-power/help/help-blank-flash-moto-g7-power-t3930168/page8

I hope you can find one that's up to date or at least compatible with your device, looking at the flash log the blankflash seems to have trouble verifying your device (suggesting either the blankflash is too old or not for the correct device/model).
[Moto G4 Plus Questions & Answers] flash713:
When i Googled the part of the log that failed after running it at the end of the Ocean/G7 Power blank flash I found a site that led me to believe it's bootloader related. Also it told me to get ahold of a bootloader member. :confused: I'll keep doing a search every few days, maybe something will come up some day. I see there was one user who had same log as me so who knows. Appreciate the reply.
[Moto G4 Plus Questions & Answers] echo92:
You're right in thinking it's bootloader related; these blankflash files contain a basic bootloader, designed for rescue in the event of a corrupted bootloader. The corruption seems to occur mainly from a bad flash or using old OTA updates (e.g. when you've downgraded). The waiting for firehose message suggests the blankflash is waiting for a response from your device - the blankflash programmer seems to be attempting to verify your device is eligible for flashing the bootloader included with your blankflash. I do not know if G7 power blankflashes are the same structure as G4 plus blankflashes, from what I've observed, this message can arise from a bad connection with your device or your bootloader version on your device is too new. Thus, the programmer would fail to verify and deny the flash, and as programmers are likely digitally signed to a particular bootloader version, are not easy to modify.

Unfortunately, these tools are internal to Motorola, likely explaining the reference to a bootloader member. As such, the tools are rare and I do not know of where an updated tool might come from. You could try the mmmcblk images as noted in that thread. I hope a result that doesn't involve a service centre happens soon.
[Moto G4 Plus Questions & Answers] papsr6:
What did you mean with the other blankflash of 3 are for other devices?

Is combatible with moto x2014 perchaps?
[Moto G4 Plus Questions & Answers] echo92:
You could give the blankflashes a try if you've got a bricked Moto X 2014 - no guarantees however. The original post author has not been seen for a long time, so we cannot ask them for sources (even if they remember).

Else, you'll likely have to have your device serviced/motherboard replaced if such repairs are still possible.
[Moto G4 Plus Questions & Answers] papsr6:
Thank you for your responce.

I dont want to spend any more money for an old device and i never buy motorola again after thus mess.
[Moto G4 Plus Questions & Answers] echo92:
That's reasonable - the Moto X is an old device, and if I recall, lots of people hard bricked from downgrading between Jellibean and Lollipop and mistakenly used an old OTA update. Motorola, as far as I know, has not issued blankflashes, presumably regarding them as internal tools and by unlocking the bootloader, you agreed to absolve them of responsibility. No comfort, I understand.

I hope you have better luck with Xiaomi (either through shorting pins or via registering your device with them) for unbricking.
[Moto G4 Plus Questions & Answers] papsr6:
I know that i am angree for the unlocked bootloader but never will thought brick my phone with official firmware and official ota update.

I had use 2 devices xiaomi with no problem at all..

Redmi note 4x is very hard.

I flashed all the custom roms all the official many times and all is ok so far.now i have a non rooted mi a3 full stock for calm.
[Moto G4 Plus Questions & Answers] ozgur_erdogan:
C:\Users\KUZEY\Desktop\blankflash>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ 0.000] Opening device: \\.\COM3

[ 0.000] Detecting device

[ 0.000] ...cpu.id = 2418 (0x972)

[ 0.000] ...cpu.sn = 29365295 (0x1c0142f)

[ 0.000] Opening singleimage

[ 0.084] Loading package

[ 0.100] ...filename = singleimage.pkg.xml

[ 0.100] Loading programmer

[ 0.100] ...filename = programmer.mbn

[ 0.100] Sending programmer

[ 0.323] Handling things over to programmer

[ 0.323] Identifying CPU version

[ 0.339] Waiting for firehose to get ready

[ 61.204] Waiting for firehose to get ready

Moto g4 plus is not going to happen. What should I do?
[Moto G4 Plus Questions & Answers] echo92:
Have you tried this blankflash? https://xdaforums.com/showpost.php?p=79714477&postcount=778 This is the latest Oreo blankflash we have leaked to us.
[Moto G4 Plus Questions & Answers] ozgur_erdogan:
C:\Program Files (x86)\Minimal ADB and Fastboot>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ -0.000] Opening device: \\.\COM3

[ -0.000] Detecting device

[ -0.000] ...cpu.id = 2418 (0x972)

[ -0.000] ...cpu.sn = 29365295 (0x1c0142f)

[ -0.000] Opening singleimage

[ -0.000] Loading package

[ -0.000] ...filename = singleimage.pkg.xml

[ 0.016] Loading programmer

[ 0.016] ...filename = programmer.mbn

[ 0.016] Sending programmer

[ 0.238] Handling things over to programmer

[ 0.238] Identifying CPU version

[ 0.238] Waiting for firehose to get ready

[ 62.072] Waiting for firehose to get ready

[122.338] ...MSM8952 unknown

[122.338] Determining target secure state

[122.342] Waiting for firehose to get ready

[182.523] ...secure = no

[182.561] Flashing GPT...

[182.567] Flashing partition:0 with gpt_main0.bin

[182.568] Initializing storage

[182.575] Waiting for firehose to get ready

[243.301] Configuring device...

[243.305] Waiting for firehose to get ready

[303.453] Waiting for firehose to get ready

[484.315] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[484.318] Check qboot_log.txt for more details

[484.319] Total time: 484.334s

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:\Program Files (x86)\Minimal ADB and Fastboot>pause

No, I tried it too :(

---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------

C:\Program Files (x86)\Minimal ADB and Fastboot>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ -0.000] Opening device: \\.\COM3

[ -0.000] Detecting device

[ -0.000] ...cpu.id = 2418 (0x972)

[ -0.000] ...cpu.sn = 29365295 (0x1c0142f)

[ -0.000] Opening singleimage

[ -0.000] Loading package

[ -0.000] ...filename = singleimage.pkg.xml

[ 0.016] Loading programmer

[ 0.016] ...filename = programmer.mbn

[ 0.016] Sending programmer

[ 0.238] Handling things over to programmer

[ 0.238] Identifying CPU version

[ 0.238] Waiting for firehose to get ready

[ 62.072] Waiting for firehose to get ready

[122.338] ...MSM8952 unknown

[122.338] Determining target secure state

[122.342] Waiting for firehose to get ready

[182.523] ...secure = no

[182.561] Flashing GPT...

[182.567] Flashing partition:0 with gpt_main0.bin

[182.568] Initializing storage

[182.575] Waiting for firehose to get ready

[243.301] Configuring device...

[243.305] Waiting for firehose to get ready

[303.453] Waiting for firehose to get ready

No, I tried it too :(
[Moto G4 Plus Questions & Answers] echo92:
Hmm that's odd. The blankflash does require a few tries to get the flash to connect properly.

What happened to your device for it to brick? Was it an OTA update?
[Moto G4 Plus Questions & Answers] ozgur_erdogan:
there was android 7 updating from phone
[Moto G4 Plus Questions & Answers] echo92:
I guess you had stock Oreo previously on your device and a downgrade does not downgrade your bootloader...

Are you using a high quality USB data cable or the original Motorola USB cable and can you try another USB port?

Have you turned BCD testing ( or Windows driver verification) off and have you tried the tips mentioned in the opening post? I've copy posted them here:

That Oreo blankflash is the latest we have and has been shown to work in rescuing devices bricked by old OTA updates.
[Moto G4 Plus Questions & Answers] ozgur_erdogan:
Whatever I did, unfortunately, I'm about to go crazy
[Moto G4 Plus Questions & Answers] echo92:
Can you remember what firmware you had on your device before the update (if you can't, can you recall what security patch the OTA update had)?

What have you tried so far, and what results are you getting from your device?

Can you verify you're using a good USB cable (ideally an original, genuine Motorola cable), that you know has data transfer ability, and have you tried other USB ports? The blankflash can be very picky at times (probably why it was never intended for customer use).
[Moto G4 Plus Questions & Answers] ozgur_erdogan:
I have installed android 7 and then I checked if there is an update from the phone. I made an update, the phone turned off, it was not turned on again

My cable is not the original motorola, I will buy and try a higher quality cable. I tried with a few wires, but no progress after a while

C:\Program Files (x86)\Minimal ADB and Fastboot>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ -0.000] Opening device: \\.\COM3

[ -0.000] Detecting device

[ -0.000] ...cpu.id = 2418 (0x972)

[ -0.000] ...cpu.sn = 29365295 (0x1c0142f)

[ -0.000] Opening singleimage

[ -0.000] Loading package

[ -0.000] ...filename = singleimage.pkg.xml

[ 0.016] Loading programmer

[ 0.016] ...filename = programmer.mbn

[ 0.016] Sending programmer

[ 0.238] Handling things over to programmer

[ 0.238] Identifying CPU version

[ 0.238] Waiting for firehose to get ready
[Moto G4 Plus Questions & Answers] sd_shadow:
One thing you could try open and run the blankflash in several different Windows at the same time.

Start one then the next...

I've seen a few posts that it works.
[Moto G4 Plus Questions & Answers] ozgur_erdogan:
I solved the problem with Western digital Cable Thank you very much everyone
[Moto G4 Plus Questions & Answers] DouglasAndre:
How do I solve this? "Waiting for firehose to get ready"?
[Moto G4 Plus Questions & Answers] alepsito:
help

Hi i have months reviewing this post, i have made this process more than one time with the 3 options of files That I have. NPJS25_93_14_13_Dec2017_GPT_bootloader for flashing the bootloader and also tried june's and september's files. none of them working. it is the last step before installing the rom and i have not seen someone with this issue.

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot: partition: not found

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.006s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.074s

I really dont have a clue on how to solve this. Can please someone help me?
[Moto G4 Plus Questions & Answers] echo92:
That error may be a result of using an old blankflash (i.e. older than your bootloader version). If you downgraded your firmware, your bootloader does NOT get downgraded, hence you'll need a blankflash of the same or newer version than your bootloader to work.

Here's the link to the OPJ28.111-22 blankflash https://xdaforums.com/showpost.php?p=79714477&postcount=778

If you hardbricked using old OTA updates, I would strongly recommend to flash the Oreo stock firmware in full after using this blankflash. Failure to do so may mean you hard brick again if you choose to use old OTA updates. If you do not wish to flash the full stock firmware, do NOT use stock OTA updates.

---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------

That preflash validation error is usually a result of attempting to flash a bootloader version older than the one currently on your device. If you have not updated your device previously to stock Oreo, then you can try the NPJS25.93-14-18 April 2018 Nougat (7.0) bootloader and GPT from here: https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI I have taken these GPT and bootloader files from their respective fastboot images. If you are able to flash those GPT and bootloader files, I would recommend you flash the rest of the NPJS25.93-14-18 firmware as detailed here: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 If you previously hard bricked from a stock OTA update having downgraded, you will keep hard bricking until you fastboot flash a firmware that matches your bootloader version. You can see your bootloader version in fastboot - e.g. B1:07 is December 2017-April 2018 security patches, B1:09 is Oreo December 2018 security patch.
[Moto G4 Plus Questions & Answers] Envyon:
I have Lenovo P2 with Snapdragon 625 i did blankflash but always stuck at:

Handling things over to programmer

Waiting for firehose to get ready ......

Identifying CPU

Does anyone have similar experience? what do when it stuck?
[Moto G4 Plus Questions & Answers] nandakis4:
I have been trying to revive Moto G4 plus since many days..

i tried blankflash01, latest oreo blankflash also.

it never worked for me ,same thing is happening again and again.

D:\Phone Tools\Moto G4 plus\blankflash-athene-OPJ28.111-22\blankflash>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ -0.000] Opening device: \\.\COM5

[ 0.282] Detecting device

[ 2.063] ReadFile() failed, GetLastError()=0

[ 2.568] ...cpu.id = 2418 (0x972)

[ 2.568] ...cpu.sn = 23938967 (0x16d4797)

[ 2.568] Opening singleimage

[ 2.598] Loading package

[ 2.608] ...filename = singleimage.pkg.xml

[ 2.608] Loading programmer

[ 2.608] ...filename = programmer.mbn

[ 2.608] Sending programmer

[ 2.822] Handling things over to programmer

[ 2.822] Identifying CPU version

[ 2.822] Waiting for firehose to get ready

[ 65.019] Waiting for firehose to get ready

[125.586] ...MSM8952 unknown

[125.586] Determining target secure state

[125.586] Waiting for firehose to get ready

[189.169] ...secure = no

[189.177] Flashing GPT...

[189.177] Flashing partition:0 with gpt_main0.bin

[189.177] Initializing storage

[189.178] Waiting for firehose to get ready

[251.247] Configuring device...

[251.249] Waiting for firehose to get ready

[313.819] Waiting for firehose to get ready

[376.374] Waiting for firehose to get ready

[436.436] Waiting for firehose to get ready

[496.475] ERROR: do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->get_fh()->no response

[496.475] Check qboot_log.txt for more details

[496.475] Total time: 496.476s

FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->do_configure()->get_fh()->no response

D:\Phone Tools\Moto G4 plus\blankflash-athene-OPJ28.111-22\blankflash>pause

Press any key to continue . . .

Things i did :

1) used good wires.

2) tried all blankflashes.

3) Tried different ports. :(

can anyone tell me what the problem is , and how do i revive phone back.:mad:
[Moto G4 Plus Questions & Answers] sd_shadow:
Try running the blankflash flash in several windows at same time.
[Moto G4 Plus Questions & Answers] Sekiryuutei_1924:
Would this work for other devices as well? Such as the Pixel etc
[Moto G4 Plus Questions & Answers] auroraguy123:
My problem is my LG Qstylus plus phone was in black screen and won't be rebooted again, even in fastboot mode because the bootloader was locked. I have seen a light after I saw your method to boot the phone. Can you help me ? The original post is https://xdaforums.com/t/my-lg-q-stylo-plus-bricked-please-help-save.4223161/
[Moto G4 Plus Questions & Answers] Lighto97:
curious that blankflash 3 give a error for moto g5 (xt1672)

- Unexpected packet: 4. Was expecting: 3

and any other file scattered around did not worked that far. ive tries using another singleimages,replacing files around,tried z play 2 singleimage, one from g4 plus thats not this one but sadly no result it says that could not open the image file.

i dont know if an g4 plus model is compatible with g5 cedric to boot up bootloader like g4plus could with z 2 play blank flash (someone mentioned that both have similar chipsets, cedric is Snapdragon 430)

note that g6 have the same chipset, but im not sure if it will work and if it work i can use the sd card method to unbrick (did not blank flashed)

whoa there is a lot of motorola devices from different gens that has the same chipset one of these has to work for blank flash
[Moto G4 Plus Questions & Answers] zitronenmelissa:
have you tried blankflash file for cedric (xt1672) ?

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com
[Moto G4 Plus Questions & Answers] Lighto97:
cedric blank flash does not exist, there is few around that does not work cuz they arent official, i tried use the g4 plus g6 play z2 play g3, no succes, the onlym ethod is with sd card.
[Moto G4 Plus Questions & Answers] joelcapture:
Hi everybody! I'm trying to unlock my moto g4 plus XT1641 but I only get errors.

This is the info of the device. I tried with several firmware.

C:\mfastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8952-B1.07(*)

(bootloader) product: athene_16mp

(bootloader) board: athene_16mp

(bootloader) secure: yes

(bootloader) hwrev: P2A

(bootloader) radio: 5

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F

(bootloader) cpu: MSM8952

(bootloader) serialno: 37c16072

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: 36999D0200000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 536870912

(bootloader) reason: Last time flashing failed

(bootloader) imei: 000000000000000

(bootloader) meid:

(bootloader) date: 01-01-1970

(bootloader) sku: 000000000000000

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sbl1.git: sbl1.git

(bootloader) rpm.git: rpm.git

(bootloader) tz.git: tz.git

(bootloader) hyp.git: hyp.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba

(bootloader) qe:

(bootloader) frp-state: no protection (err)

(bootloader) ro.carrier:

all: listed above

finished. total time: 0.253s

Please tell me if is there something I can do. Thanks!
[Moto G4 Plus Questions & Answers] sd_shadow:
The bootloader is locked, you cannot try other firmware only the one for the same software channel.

Getvar all says nothing anymore.

Do you know which channel it was on before you started flashing?
[Moto G4 Plus Questions & Answers] joelcapture:
Hi! I have no idea which channel was on before. How can I find that?
[Moto G4 Plus Questions & Answers] sd_shadow:
It should be in the getvar all as ro.carrier:

Did you buy through a carrier?

Was the bootloader unlocked before?

Did you relock?
[Moto G4 Plus Questions & Answers] joelcapture:
No, I didn't buy it through a carrier. Everything was normal in the phone.

It blocked itself, I didn't install or flash anything.

Maybe it's a hardware problem. I don't know.