yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Questions & Answers] hmmelo:
C:\Users\Henrique\Downloads\blankflash-athene-OPJ28.111-22\blankflash>.\qboot.ex

e blank-flash

Motorola qboot utility version 3.40

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

[ -0.000] Detecting device

[ 4.017] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error

[ 4.017] Check qboot_log.txt for more details

[ 4.017] Total time: 4.017s

FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()

->IO error

C:\Users\Henrique\Downloads\blankflash-athene-OPJ28.111-22\blankflash>pause

Pressione qualquer tecla para continuar. . .
[Moto G4 Plus Questions & Answers] echo92:
Yeah, you used the OPJ28.72 (the OLD Oreo blankflash). What error do you get when using the OPJ28.111-22 blankflash as linked: https://xdaforums.com/showpost.php?p=79714477&postcount=778

---------- Post added at 01:42 AM ---------- Previous post was at 01:38 AM ----------

Hmm, are you using the original USB cable to connect to your device and are you connected to USB 2.0? Try the blankflash a few times, and follow some of the tips in the first post of this thread.
[Moto G4 Plus Questions & Answers] echo92:
These blankflashes were always awkward to use. However, this blankflash has been shown to rescue hard bricked devices previously updated to Oreo.

Try the tips mentioned in the opening post:

Also, make sure you're using a good quality data USB cable and your computer has driver signature enforcement disabled (or is in test mode as per the guide)
[Moto G4 Plus Questions & Answers] hmmelo:
I did all the steps described in the post, it's difficult.
[Moto G4 Plus Questions & Answers] echo92:
Yeah, not much more I can suggest besides trying the blankflash with different USB ports, try a different computer. Else, a hard brick like this is difficult to solve without paying.
[Moto G4 Plus Questions & Answers] hmmelo:
I got it !!!

Bootloader screen

And now?

Which ROM install 8 or 7?

Where do I get the roms?

I want to stay with rom 7, but how to do it so that there is no more problem?
[Moto G4 Plus Questions & Answers] echo92:
Though I would personally recommend flashing back to stock Oreo, since you want to be on Nougat 7.0, I would recommend you flash the latest stock Nougat firmware: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

You do not have to lock your bootloader (and indeed, the oem lock commands would likely fail since you still have an Oreo bootloader), so omit the oem lock begin and oem lock commands. I would recommend you clean flash - include fastboot erase userdata.

Once you have flashed the Nougat firmware (and I hope you still have your IMEI and signal), you will want to disable OTA updates since you'll likely get notifications to the Oreo OTA. Have a look in this thread for ideas on how to do so: https://xdaforums.com/moto-g4-plus/help/how-disable-notification-update-t3459587
[Moto G4 Plus Questions & Answers] hmmelo:
He came back alone with Android 7, did not need to install, but no signal and imei.

How do I install OREO?
[Moto G4 Plus Questions & Answers] echo92:
Your device is indeed on Nougat, but you're likely still on the firmware before or during the OTA update when you hard bricked. If you try to use another old OTA update without updating, you'll likely hard brick again. Hence why I suggested updating to the actual newest Nougat firmware.

If you're having IMEI issues, you could update to Oreo using the guide I mentioned: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Again, up to you if you want to lock your bootloader.

Alternatively, if you want to stay on Nougat (and do NOT use OTA updates), have a look at this guide for repairing your IMEI: https://xdaforums.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068

Personally, I would update to Oreo and forget about downgrading unless you're very careful. As you're now aware, downgrading can be very risky if you're not aware of the risks involved.
[Moto G4 Plus Questions & Answers] iurd2007:
Bro. I recommend you to install Lineage 14.1 custom rom. With Nougat you will ota update at any time and you will kill your phone again. With custom roms you'll not have this risk anymore
[Moto G4 Plus Questions & Answers] hmmelo:
Thanks [MENTION=7970352]echo92[/MENTION]

I installed OREO.

But now it has a problem with audio, sometimes it works and sometimes it does not.
[Moto G4 Plus Questions & Answers] echo92:
Hmm, did you flash OPJ28.111-22 or OPJ28.111-22-1 (the latter supposedly has audio fixes)? https://xdaforums.com/showpost.php?p=79737114&postcount=1368

Failing that, you could flash the NPJS25.93-14-18 April 2018 firmware and disable OTA updates as previously mentioned if you still wanted to stay with stock firmware.
[Moto G4 Plus Questions & Answers] iurd2007:
Search for ota update. They release one update that "solve" sound issues
[Moto G4 Plus Questions & Answers] hmmelo:
I am with the latest version installed 8.1.0

It starts with Hello Moto sound, but after some time the sound disappears.
[Moto G4 Plus Questions & Answers] echo92:
Which Oreo version is that then? Is that OPJ28.111-22 or OPJ28.111-22-1?

If you're on OPJ28.111-22, try flashing the OPJ28.111-22-1 OTA from here: https://xdaforums.com/showpost.php?p=79737114&postcount=1368
[Moto G4 Plus Questions & Answers] hmmelo:
OPJ28.111-22

How to install version OTA_Package_OPJ28.111-22-1.zip?
[Moto G4 Plus Questions & Answers] echo92:
1)Download the OTA update to your device, make sure it's on Internal Storage.

2)Go to Settings>Apps and Notifications

3)Tap See all apps under 'Recently opened apps'

4)In the top right corner, tap the 3 vertical dots and select Show System.

5)Find Motorola Update Services and select. Allow storage permissions.

6)Go back to Settings>System. Tap on System updates to check for updates.

Else, install the update via stock recovery - more info here https://xdaforums.com/moto-g4-plus/how-to/guide-moto-g4-g4-oreo-soak-test-update-t3871136
[Moto G4 Plus Questions & Answers] hmmelo:
Version OPJ28.111-22-1, but still no audio!

It works sometimes!
[Moto G4 Plus Questions & Answers] echo92:
Try running the Moto help app and the speaker test within. If that doesn't work, then downgrade to NPJS25.93-14-18 using the firmware from the same thread as the Oreo firmware or you could install TWRP and use the TWRP flashable here: https://xdaforums.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 . As I mentioned previously, you should disable OTA updates. Alternatively, as others have suggested, use custom ROMs.
[Moto G4 Plus Questions & Answers] hmmelo:
Unfortunately it does not work with any version of ROM the sound.

The test also did not work!
[Moto G4 Plus Questions & Answers] echo92:
One thing to try is to flash TWRP to your device (if your bootloader is still unlocked) and try the TWRP flashable of Nougat - see if that solves your sound issue: https://xdaforums.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
[Moto G4 Plus Questions & Answers] harishnayaka:
please help me moto g4 plus how to repair dead boot

C:\Users\USER\Desktop\Blankflash MG4P\blankflash>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ 0.000] Opening device: \\.\COM3

[ 0.016] Detecting device

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

[ 0.016] ...cpu.sn = 30865131 (0x1d6f6eb)

[ 0.016] Opening singleimage

[ 0.062] Loading package

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

[ 0.078] Loading programmer

[ 0.094] ...filename = programmer.mbn

[ 0.094] Sending programmer

[ 0.312] Handling things over to programmer

[ 0.312] Identifying CPU version

[ 0.328] Waiting for firehose to get ready

[ 60.328] Waiting for firehose to get ready

[120.328] ...MSM8952 unknown

[120.328] Determining target secure state

[120.328] Waiting for firehose to get ready

[180.328] ...secure = no

[180.359] Flashing GPT...

[180.375] Flashing partition:0 with gpt_main0.bin

[180.375] Initializing storage

[180.375] Waiting for firehose to get ready

[240.375] Configuring device...

[240.375] Waiting for firehose to get ready

[300.375] Waiting for firehose to get ready

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

[361.406] Waiting for firehose to get ready

[421.406] Waiting for firehose to get ready

[481.406] 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.406] Check qboot_log.txt for more details

[481.406] Total time: 481.406s

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\USER\Desktop\Blankflash MG4P\blankflash>pause

Press any key to continue . . .
[Moto G4 Plus Questions & Answers] echo92:
The blankflashes included in this thread are far too old. Try the Oreo blankflash https://xdaforums.com/showpost.php?p=79714477&postcount=778

If you do rescue your device, do not use OTA updates until you have updated your firmware formally.
[Moto G4 Plus Questions & Answers] wasteoflife:
My phone's led blinks when connected but doesn't show up on the Device Manager, I assume it's hardware fail?:(
[Moto G4 Plus Questions & Answers] iurd2007:
You need to install Qualcomm drivers, your phone will show as Qualcomm 9008 in device manager. Something like this. Then you need to use a blankflash. Then flash a stock firmware via fastboot
[Moto G4 Plus Questions & Answers] wasteoflife:
I have them installed and it still doesn't show up, if it is in fact dead, do I buy a new motherboard? :confused:
[Moto G4 Plus Questions & Answers] casallas34:
Hello, i have the same problem , please, you find any solution, thanks
[Moto G4 Plus Questions & Answers] sidhya1441:
My Error...Please help me

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

[ 0.001] Detecting device

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

[ 0.003] ...cpu.sn = 30871031 (0x1d70df7)

[ 0.003] Opening singleimage

[ 0.015] Loading package

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

[ 0.022] Loading programmer

[ 0.023] ...filename = programmer.mbn

[ 0.023] Sending programmer

[ 0.242] Handling things over to programmer

[ 0.243] Identifying CPU version

[ 0.248] Waiting for firehose to get ready

[ 60.273] Waiting for firehose to get ready

[120.314] ...MSM8952 unknown

[120.314] Determining target secure state

[120.319] Waiting for firehose to get ready

[180.383] ...secure = no

[180.409] Flashing GPT... [

180.409] Flashing partition:0 with gpt_main0.

[180.409] Initializing storage

[180.413] Waiting for firehose to get ready

:crying::crying::crying:
[Moto G4 Plus Questions & Answers] Pratham Nathyal:
Same buddy. We just need an updated blankflash. I have given my device in the service center today. Let's see what they do.
[Moto G4 Plus Questions & Answers] sidhya1441:
Please let me know .....

ok please let me know ....what happen and how much cost to pay on service center
[Moto G4 Plus Questions & Answers] MarckozZ:
Hi guys, well I just bricked my Moto G5 Plus... And I was wondering, Are blankflash files device specific/processor specific?

Let me know please...
[Moto G4 Plus Questions & Answers] echo92:
Blankflash files are usually specific to processor and device, since I imagine Moto devices may have different programming to other devices, for example.

I had a quick look and here's a blank flash for potter devices. I don't know if it'll work on the 137.67 update but worth a try. https://xdaforums.com/showpost.php?p=71895960&postcount=11

Of course, as you've got a Moto G5 plus, ensure you've got the correct firmware for your device, do not flash athene (G4 plus) builds. Your builds if I recall should be starting with NPN25.137.xx
[Moto G4 Plus Questions & Answers] MarckozZ:
This log is the only thing I get,,, Any thoughts? I have Qualcomm drivers... Should I have Moto Drivers too?
[Moto G4 Plus Questions & Answers] Draconfla:
Friend then you have the same problem as me.

We have to wait for a more up-to-date G4 blankflash
[Moto G4 Plus Questions & Answers] echo92:
I don't have much experience with blank-flashes, from what I'm reading seems like your device isn't communicating properly with your computer. The 'waiting for firehose' seems to be your computer waiting for a suitable response after the programmer has been sent over (at least from what I understand from here: https://xdaforums.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492 )

Hmm, the only other thing I can suggest to try is to attempt reflashing again. The blank-flash was from vache's cloud storage (vache is a well known developer for Moto G4 and G5 devices, amongst others), so it should have worked...

What build did you have prior to attempting to flash 137-67? I read it was LATAM firmware?
[Moto G4 Plus Questions & Answers] MarckozZ:
I had the US variant (XT1687), so I had the NPN25.137-35-5 firmware. I unlocked the bootloader and flashed/downgraded to the LATAM firmware (NPN25.137-15) without gpt.bin and bootloader.bin. Then I adb sideloaded the .67 OTA, it flashed without problems, but it contained another gpt.bin, so it corrupted everything...

Hope to find a solution!

---------- Post added at 14:48 ---------- Previous post was at 14:46 ----------

That's sad, my device has only two weeks old, so imagine how bad I feel about this situation. Hope [MENTION=1829889]vache[/MENTION] help us out! :crying:
[Moto G4 Plus Questions & Answers] echo92:
Ah, so you were on the May security patch, then flashed an OTA/firmware with an older security patch (March if I recall)? Urgh, that seems to be a pattern with the G4/Plus devices here too, seems that Motorola really doesn't want the security hole that got patched with the May security update opened again.

Hopefully there'll be a G5 Plus blank flash soon, or if not, you may have to send your device for service, see if they can fix it without it costing too much :(
[Moto G4 Plus Questions & Answers] MarckozZ:
You mean an official Moto service center? I'll have to wait... Hope to find a solution...
[Moto G4 Plus Questions & Answers] Outfield303:
stuck at

C:\Users\Siddhesh\Desktop\New folder (5)>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ 0.000] Opening device: \\.\COM4

[ 0.002] Detecting device

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

[ 0.003] ...cpu.sn = 26423911 (0x1933267)

[ 0.003] Opening singleimage

[ 0.003] Loading package

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

[ 0.007] Loading programmer

[ 0.007] ...filename = programmer.mbn

[ 0.007] Sending programmer

[ 0.224] Handling things over to programmer

[ 0.225] Identifying CPU version

[ 0.233] Waiting for firehose to get ready

[ 60.305] Waiting for firehose to get ready

HELP

-----------------------------------------------------------------------------------------------------------------

EDIT :

Now I got this :

C:\Users\Siddhesh\Desktop\New folder (5)>.\qboot.exe blank-flash

Motorola qboot utility version 3.40

[ 0.000] Opening device: \\.\COM4

[ 0.002] Detecting device

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

[ 0.003] ...cpu.sn = 26423911 (0x1933267)

[ 0.003] Opening singleimage

[ 0.003] Loading package

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

[ 0.007] Loading programmer

[ 0.007] ...filename = programmer.mbn

[ 0.007] Sending programmer

[ 0.224] Handling things over to programmer

[ 0.225] Identifying CPU version

[ 0.233] Waiting for firehose to get ready

[ 60.305] Waiting for firehose to get ready

[120.382] ...MSM8952 unknown

[120.383] Determining target secure state

[120.385] Waiting for firehose to get ready

[180.477] ...secure = no

[180.507] Flashing GPT...

[180.508] Flashing partition:0 with gpt_main0.bin

[180.508] Initializing storage

[180.513] Waiting for firehose to get ready

[240.601] Configuring device...

[240.607] Waiting for firehose to get ready

[300.699] Waiting for firehose to get ready

[360.780] Waiting for firehose to get ready

[420.867] Waiting for firehose to get ready

[480.954] 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

[480.957] Check qboot_log.txt for more details

[480.959] Total time: 480.960s

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\Siddhesh\Desktop\New folder (5)>pause

Press any key to continue . . .
[Moto G4 Plus Questions & Answers] Pratham Nathyal:
Yeah man. Just go to the service center. Take your bill with you. So they might not check ur imei no. in their system.

And if they accept it. So it's all up to them. Either they'll fix it or replace it. But the whole point is of they accept it under warranty. So take your receipt. And good luck. ?

Don't​ tell them that u unlocked bootloader or something. Just tell them it stopped working.
[Moto G4 Plus Questions & Answers] joaopaulo_:
I did the June update today. And after reboot to install, the device did not power anymore. I have tried all the methods available, but the only one that gives any result is this. But the process stops at "MSM8952 unkown".

I know I have to wait, but is there any way to recover? It's my only device.
[Moto G4 Plus Questions & Answers] echo92:
If we can get hold of an up to date blank-flash (that covers the June patch), then perhaps there's a way to recover.

The only other way at the moment is to send your device for service, I do not know if your data will be recoverable - I imagine the service centre either will try a blank flash or replace the motherboard.

As an aside, it's now appearing to be very risky/highly inadvisable to downgrade with the June security patch involved (or firmware that has the May 2017 or newer security patch).
[Moto G4 Plus Questions & Answers] Pratham Nathyal:
Man. I get it now. I totally get it. I have flashed factory firmware in numerous times on my g4 plus. But it was December build or older. But I never updated. Until one day I updated to June 1 patch and everything was working fine.

But I again went to lineage os. And again decided to come back to factory firmware and flashed the old factory​ firmware of December. And it was working fine even after that.

What I don't get is. When I was updating to March 1 patch. Remember guys updating from December to March. I selected install. It rebooted installed the march 1 update. And never rebooted again. I'm wondering what on god's green earth went wrong.

Anyone.
[Moto G4 Plus Questions & Answers] sanjurasu:
**** Log buffer [000001] 2017-07-16_00:19:24 ****

[ -0.000] Opening device: \\.\COM4
[ 0.003] Detecting device
[ 0.065] ...cpu.id = 2418 (0x972)
[ 0.066] ...cpu.sn = 12733736 (0xc24d28)
[ 0.066] Opening singleimage
[ 0.278] Loading package
[ 0.309] ...filename = singleimage.pkg.xml
[ 0.314] Loading programmer
[ 0.369] ...filename = programmer.mbn
[ 0.370] Sending programmer
[ 0.608] Handling things over to programmer
[ 0.609] Identifying CPU version
[ 0.621] Waiting for firehose to get ready
[ 61.093] Waiting for firehose to get ready
[123.171] ...MSM8952 unknown
[123.172] Determining target secure state
[123.178] Waiting for firehose to get ready
[184.966] ...secure = no
[185.044] Flashing GPT...
[185.059] Flashing partition:0 with gpt_main0.bin
[185.059] Initializing storage
[185.075] Waiting for firehose to get ready
[245.646] Configuring device...
[245.656] Waiting for firehose to get ready
[307.377] Waiting for firehose to get ready
[367.863] Waiting for firehose to get ready
[428.746] Waiting for firehose to get ready
[489.322] 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
[489.618] Check qboot_log.txt for more details
[489.618] Total time: 489.620s
[489.634]
[489.634] qboot version 3.40
[489.634]
[489.634] DEVICE {
[489.634] name = "\\.\COM4",
[489.634] flags = "0x64",
[489.634] addr = "0x22FE6C",
[489.634] sahara.current_mode = "0",
[489.634] api.buffer = "0x1940020",
[489.634] cpu.serial = "12733736",
[489.634] cpu.id = "2418",
[489.634] cpu.sv_sbl = "0",
[489.634] cpu.name = "MSM8952",
[489.634] storage.type = "eMMC",
[489.634] sahara.programmer = "programmer.mbn",
[489.634] module.firehose = "0x39F2B8",
[489.634] cpu.ver = "0",
[489.634] cpu.vername = "unknown",
[489.634] api.bnr = "0x189B7E8",
[489.634] }
[489.634]
[489.634]
[489.634] Backup & Restore {
[489.634] num_entries = 0,
[489.634] restoring = "false",
[489.634] backup_error = "not started",
[489.634] restore_error = "not started",
[489.634] }
[489.634]

[CODE][CODE][CODE]

[/CODE][/CODE][/CODE]

this is what i get in qboot logs when i blankflash my moto g4 plus . it was in android version nougat. what do i do?
[Moto G4 Plus Questions & Answers] echo92:
So, from what you mentioned, you took the June security patch, then flashed Lineage before reverting to the December 2016 build (did you downgrade your GPT/bootloader?) and then bricked after flashing the March OTA?

If it was the March OTA, that would likely have caused the brick:

1)The bootloader is updated in the March OTA/firmware from B1:03 to B1:05.

2)Thus, whilst flashing the OTA, the update may well have attempted to flash B1:05 onto your device, thinking it was on the December update (including bootloader and GPT) and might have corrupted the B1:06 bootloader/GPT partitions (or the various firmware contained within). Should there have been a check to prevent flashing on newer bootloaders? Perhaps (though I can't confirm if there was). I don't know if flashing the fastboot March 2017 stock ROM would have worked.

3)This seems a similar unfortunate pattern to what happened with Moto X devices when Lollipop arrived; users would flash the Lollipop soak test (upgrading their bootloader), then attempted to roll back and either bricked at this point (because they downgraded their bootloader), or successfully downgraded but bricked when using an OTA to update. https://xdaforums.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147 Seems that the OTA patched the system thinking it was the older system and thus corrupted a newer bootloader.

At the risk of sounding like a broken record, it's looking like we need a blank-flash updated to the June patch, with the programmer and single_image.bin files signed by Motorola, to even try to unbrick. As I understand it, it comes from full firmware images (the last one we got was the November 2016 build). However, that depends on Motorola releasing the blank-flash or it leaking from them - unfortunately I've not seen successful attempts to make a blankflash on XDA (correct me if I'm wrong).

Other than that, or if you can't wait, hopefully the service centre will fix it without it costing too much. I honestly wish I had better news to report, I dislike seeing bricks as that means a user is without their device that they paid good money for.
[Moto G4 Plus Questions & Answers] Pratham Nathyal:
Yup. That might be the case.

I already have sent it to service center. They are facing a hard time fixing it. They are trying. Will get to know if they will be able to fix it or not in a few days.
[Moto G4 Plus Questions & Answers] iurd2007:
If your phone white led blinks when connected to pc, probably it is repairable. Press power button for 30 seconds, then release pwr button , then connect and see if it is detected as 9008
[Moto G4 Plus Questions & Answers] wasteoflife:
I tried to make it show up, I think it's not going to. What could be wrong with the phone? I'm starting to consider taking it to a repair shop. :(
[Moto G4 Plus Questions & Answers] iurd2007:
Probably your phone only is hardbricked. Just follow the tutorial. I repaired mine