yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Same error which was in the previous logs.

I tried it on win 10 pc.

I wish it work on win7

on windows 10

**** Log buffer [000001] 2019-03-24_23:13:56 ****

[ 0.000] Opening device: \\.\COM4

[ 0.000] Detecting device

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

[ 0.010] ...cpu.sn = 30750607 (0x1d5378f)

[ 0.010] Opening singleimage

[ 0.050] Loading package

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

[ 0.060] Loading programmer

[ 0.060] ...filename = programmer.mbn

[ 0.060] Sending programmer

[ 0.290] Handling things over to programmer

[ 0.290] Identifying CPU version

[ 0.306] Waiting for firehose to get ready

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

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

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

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

[ 60.837] Waiting for firehose to get ready

[122.416] ...MSM8952 unknown

[122.416] Determining target secure state

[122.416] Waiting for firehose to get ready

[184.046] ...secure = no

[184.062] Flashing GPT...

[184.062] Flashing partition:0 with gpt_main0.bin

[184.062] Initializing storage

[184.062] Waiting for firehose to get ready

[245.518] Configuring device...

[245.522] Waiting for firehose to get ready

[306.808] Waiting for firehose to get ready

[368.288] Waiting for firehose to get ready

[430.026] Waiting for firehose to get ready

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

[491.532] Check qboot_log.txt for more details

[491.532] Total time: 491.538s

[491.548]

[491.548] qboot version 3.32

[491.548]

[491.548] DEVICE {

[491.548] name = "\\.\COM4",

[491.548] flags = "0x64",

[491.548] addr = "0x61FE4C",

[491.548] sahara.current_mode = "0",

[491.548] api.buffer = "0x1287020",

[491.548] cpu.serial = "30750607",

[491.548] cpu.id = "2418",

[491.548] cpu.sv_sbl = "0",

[491.548] cpu.name = "MSM8952",

[491.548] storage.type = "eMMC",

[491.548] sahara.programmer = "programmer.mbn",

[491.548] module.firehose = "0x37D20",

[491.548] cpu.ver = "0",

[491.548] cpu.vername = "unknown",

[491.548] api.bnr = "0x6E71C8",

[491.548] }

[491.548]

[491.548]

[491.548] Backup & Restore {

[491.548] num_entries = 0,

[491.548] restoring = "false",

[491.548] backup_error = "not started",

[491.548] restore_error = "not started",

[491.548] }

[491.548]
[Moto G4 Plus Guides, News, & Discussion] echo92:
[MENTION=8334764]luckilyblack[/MENTION] also Oh, what format is your SD card in, is it FAT or FAT32?
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
Fat 32 brother, any suggestions? [MENTION=7970352]echo92[/MENTION]
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks, just pondering if the DD image was somehow affected by the fat32, but then supercas wrote the image using a Linux system, which likely wouldn't be using fat32. Maybe making the image requires a Linux system (but then again, the last images were made on device via TWRP and a root shell, so it should be the right file format/file system). Just exploring a few things to see if there's any improvements...
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
[MENTION=7970352]echo92[/MENTION] brother you did a lot to us. As per now I think there is something missing. Can we only flash boot & bootloader of latest Oreo for Athens, will it work? Via sd card

:confused:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Without a working fastboot/bootloader on your device, that's very difficult. The whole point of these loader and mmcblk0 images has been trying to get your device to boot into fastboot using the bootloader on the SD card, so you can flash a new bootloader and then flash the rest of the firmware to your device. Evidently, it seems these images to be in a particular format/structure for it to boot or for some setting to tell the device the SD card is an active storage. I'm not sure simply having just the bootloader itself will work, s and besides that's what the loader image effectively is.

Unfortunately, without a working blankflash, or a working image to boot a device with, we don't have free options. Unless you can find something to try, you may have to start looking at paid repairs or a new device.
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Dear friends I read elsewhere that now the fastboot rom for Oreo.zip is available. Can we try it by flashing it on sd card using etcher, is it possible to work????
[Moto G4 Plus Guides, News, & Discussion] echo92:
Not sure if it works, the fastboot ROM has the bootloader, GPT and other key files, I don't know if there's enough there to make a bootable SD card.

You could try etcher with the loader image or the mmcblk files, see if that produces a working SD card.

EDIT - I've used etcher to flash the mmcblk (mmcoreo2) to a 32 GB SD card, and my device boots to the bootloader on powering up with the SD card inserted (and repeated attempts to reboot just boot to the bootloader. Removing the SD card permits booting to system). Again, it may well be these images are device variant specific, so your experience may vary. Good luck.
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
[MENTION=7970352]echo92[/MENTION] can you please explain the procedure how you are able to boot the device from SD?
[MENTION=8334764]luckilyblack[/MENTION] did you tried this?
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
No [MENTION=9761903]SuperCas[/MENTION] not yet brother. You know what I strained my back neck so badly of searching and employing things to boot up :crying::crying::crying:. Now only ok.

I tried loader.img for my xt1643 from telegram group but no use tried Rufus, disk image flasher too but not this app.
[MENTION=7970352]echo92[/MENTION] brother can tell us it boots when we flash it with windows 10?
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Dear i flashed mmcoreo2 via etcher, but results are not successful.

Leela blinking led. No symptoms of life.
[Moto G4 Plus Guides, News, & Discussion] echo92:
On further testing, it looks like my device is booting from the device bootloader rather than the SD card bootloader (same approach - unpack the mmcblk, flash the image to a 32 GB Sandisk U3 Class 10 SD card with etcher and then insert into device. Power button to turn on). I tried it with the Nougat image and the bootloader version reported B1:09 - if it was booting from the SD card, I would have expected it to boot from the Nougat B1:07 bootloader. Apologies for the misinformation and false hope.

Might be worth asking if you can get a mmcblk image instead of the loader image from a working XT1643 - it'd be interesting to see if the XT1643 image may give you better luck. I'm hoping Motorola/Qualcomm haven't disabled this function, and it's just something we're missing, even if it's down to have an image from the same device, or perhaps another way of getting the image?

EDIT - trying one last thing: https://xdaforums.com/showpost.php?p=76921806&postcount=5 Previously let dd copy until the end of mmcblk0, let's see if defining the output size does anything
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Brother is it for xt1643
[Moto G4 Plus Guides, News, & Discussion] echo92:
Probably not given our previous efforts haven't come to much (my device is a XT1642), but could give it a try once I've uploaded it. However, your best chance would be to get an image from an XT1643 - you'd have to see if anyone in India or with an imported device is willing to erase their device and get you an image.
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Definitely,if I found someone, I will post it here.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
[MENTION=7970352]echo92[/MENTION] OK brother I'll try to get xt1643 mmcblk0 then try the same thank you ?
[Moto G4 Plus Guides, News, & Discussion] magno611:
Thank you for the address

Good morning, I know there's someone asking the same thing every hour. Please, I would like a blank-flash of the bike g4 plus xt1640 the latest released (as updated as possible). The bike upgraded from ota from 7.1 to 8.1 and started a bunch of bug. I unlocked the bootload and installed the stock rom 7.0 nogaut (Athene npj25.93-14), the last one released, after updating via ota and giving the hard brick. I'm using google translator, sorry for the grammar. I am also a layman in the area. Thanks in advance.

PS: I have tested several different blank flashes, maybe it did not work because it is not compatible with the model of my phone, I would like one that is compatible.

BR here.
[Moto G4 Plus Guides, News, & Discussion] echo92:
You could try this blankflash here https://xdaforums.com/showpost.php?p=79013024&postcount=523

However, if that does not work, our options are limited. There is currently no newer blankflash (and a new one leaked from Motorola is looking very unlikely). Umm confused why you flashed the December 2016 firmware (NPJ25.93-14), it's very old, and the old OTA likely corrupted your Oreo bootloader.

Else, if you need a working device, the only other options are to pay for a repair (JTAG or motherboard replacement) or buy a new device. Hard bricks caused by downgrading and using old OTA updates are very difficult to resolve.
[Moto G4 Plus Guides, News, & Discussion] magno611:
Thanks for the attention, but it did not work. Will they ever release a blank flash for this problem?

C:\Users\magno\Downloads\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 = 27277923 (0x1a03a63)

[ 0.016] Opening singleimage

[ 0.016] Loading package

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

[ 0.016] Loading programmer

[ 0.016] ...filename = programmer.mbn

[ 0.016] Sending programmer

[ 0.297] Handling things over to programmer

[ 0.297] Identifying CPU version

[ 0.297] Waiting for firehose to get ready

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

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

[ 61.442] Waiting for firehose to get ready

[121.646] ...MSM8952 unknown

[121.646] Determining target secure state

[121.646] Waiting for firehose to get ready

[181.976] ...secure = no

[181.976] Flashing GPT...

[181.992] Flashing partition:0 with gpt_main0.bin

[181.992] Initializing storage

[181.999] Waiting for firehose to get ready

[242.311] Configuring device...

[242.313] Waiting for firehose to get ready

[302.421] Waiting for firehose to get ready

[362.529] Waiting for firehose to get ready

[422.664] Waiting for firehose to get ready

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

[482.779] Total time: 482.779s

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\magno\Downloads\blankflash>pause

Pressione qualquer tecla para continuar. . .
[Moto G4 Plus Guides, News, & Discussion] echo92:
Unfortunately, I do not think so, unless it's a leak. OEMs, including Motorola do not release blankflashes, so any blankflashes we do get are a lucky find.

Your blankflash appears to having difficulty contacting your device for authorisation to flash - either because of an old blankflash or failing to get a firehose connection response before timing out.

If you need a working device now, your best options are unfortunately to repair your device (either a motherboard repair or replacement) or purchasing a new device.
[Moto G4 Plus Guides, News, & Discussion] magno611:
I took in the technical assistance, the repair was the same price of a new cell phone. I'll have to buy another not to be without one. But if he had a way to recover that, he would be happy, it would not be a paperweight at home.
[Moto G4 Plus Guides, News, & Discussion] JulioViana:
It is my friend we are in the same problem, mine neither leaves the black screen with led, let's wait or throw it on the wall, BR here!
[Moto G4 Plus Guides, News, & Discussion] magno611:
Sim mano, vou ter que comprar outro, até aparecer um jeito de acertar esse.
[Moto G4 Plus Guides, News, & Discussion] ajash:
Latest blank Available ?? ?
[Moto G4 Plus Guides, News, & Discussion] Daroas:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Not for now
[Moto G4 Plus Guides, News, & Discussion] ajash:
Sir Latest Blank Flash Available ? :(
[Moto G4 Plus Guides, News, & Discussion] echo92:
No newer blankflash than the OPJ28.72 version. Unlikely to have a newer one leaked, your best bet for repairs is either a JTAG repair, motherboard replacement or a new device altogether.
[Moto G4 Plus Guides, News, & Discussion] jhon8500:
i amm help

I have a problem, with the "fastboot devices" command if it recognizes the device but when I am going to do the black flash it appears "waiting for device" help :(
[Moto G4 Plus Guides, News, & Discussion] Tetcare99:
Any good news for bricked brothers..?:crying:
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you are able to use the 'fastboot devices' command, then the blankflash won't work/likely isn't needed for you. The blankflash is there to restore a working GPT/bootloader over a damaged version - if you're able to use fastboot commands, that means you should already have a working bootloader. Thus, you may not need the blankflash, unless you can force EDL mode.

What are you trying to accomplish? Is your device not booting properly?
[Moto G4 Plus Guides, News, & Discussion] jhon8500:
Yes, it really is not starting well. the device starts in fastboot (secure) mode, and displays an invalid CID error
[Moto G4 Plus Guides, News, & Discussion] Jester1214:
Could it be solved ??

my M g4 plus this brick, I tried with several blank flash files and they all throw me error.

someone could already solve it?

:confuso::confuso:
[Moto G4 Plus Guides, News, & Discussion] ajash:
Its available in future???
[Moto G4 Plus Guides, News, & Discussion] echo92:
Depends on how long you're willing to wait - we could get a new one leaked tomorrow, or maybe never. Motorola never intended for our devices to be downgraded (and we've repeatedly warned about using OTA updates whilst downgraded), and OEMs in general do not willingly give out their blankflashes/similar utilities. Most of these utilities we've gained from leaks, so their availablity is very rare. I would honestly not count on getting a blankflash, get your device repaired or replaced and use this as a learning opportunity to be very careful when flashing stock firmware.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, with the firmware flash, did RSDlite confirm the flashes and erasing of data worked? Did you erase your data and the caches as well?

Do you have a SD card in your device? Does your device still fail to boot if you take out the SD card and SIM card?

Though I would normally caution against downgrading to the original firmware, this sounds like a hardware fault if the above don't work - from the sudden failure to boot even though there was no indication of any updates.

Your getvar log doesn't show anything out of the ordinary - looks like a device updated to Oreo. I would consider contacting a Motorola service centre. Hopefully you're resident in the UK or EU and thus have good consumer protection (2 year warranty, if I recall), and may be able to get this repaired without cost or at least at reasonable cost.
[Moto G4 Plus Guides, News, & Discussion] graphicsxp:
Thank you fore replying !

Indeed, RSDLite confirmed the flashing and erasing passed. Data & Cache were both deleted (I even typed the command manually to be sure).

SD card & SIM cards were all removed prior to attempting anything.

You are confirming my fears... Honnestly I cannot help thinking there is something odd about a hardware fault happening just as I was trying this new feature (keeping screen on while looking at it). My phone never shown any signs of fault and had never crashed before. I would very much like to get the opinion of Motorola engineers about this.

I live in the EU, but I purchased the phone 2 years and 3 months ago, so I'm out of luck. I'll try to grab a second-hand G4, at least I'll have spare parts in case anything goes wrong with it :p
[Moto G4 Plus Guides, News, & Discussion] Elleo1422:
Hola gente yo tengo ese problema tambien conecto el cargador y solo prende el led blanco o manteniendo volumnes menos y power va como a un menu recobery pero no hace nada y marca boot loock algo asi

Probe hacer esto y no hay forma de que la oc lo tome como dicem qualqoom nose como se escribe

Me lo toma como loader y algo mas pero estando en ese modo tiño recobery
[Moto G4 Plus Guides, News, & Discussion] echo92:
1) What happened before this, did you downgrade and use an OTA update, or did the problem happen suddenly?

2)Was your bootloader locked or unlocked?

3)What have you tried to troubleshoot?

Please reply in English or provide a translation of your reply as well.
[Moto G4 Plus Guides, News, & Discussion] Elleo1422:
Moto g4 plus

the phone stopped giving a picture change the module and suddenly it iso me that before it turned on without picture now the screen works ok
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ah okay - so your device boots okay now as well?
[Moto G4 Plus Guides, News, & Discussion] Elleo1422:
it does not light more but only with the charger connected the white led light and pressing less volume and power enters that mode but disconnecting the charger

the g4 plus motorcycle did not fire anymore and I did not detect it as they say or I can not follow the tutorial or will it be another problem?:Rodar los ojos:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, did the device get dropped at some point?

You could try the procedure, but I'm wondering if you've got a hardware fault. Did you say if there was an update before losing picture or did this happen suddenly?
[Moto G4 Plus Guides, News, & Discussion] Elleo1422:
the g4 plus motorcycle did not fire anymore and I did not detect it as they say or I can not follow the tutorial or will it be another problem?

---------- Post added at 12:29 AM ---------- Previous post was at 12:24 AM ----------

if the phone was shut up he had a blow that's why the screen broke could have caused this problem the hardbrick hit
[Moto G4 Plus Guides, News, & Discussion] echo92:
Do you see Qualcomm HS-USB 9008 or similar appear in your computer's device manager when you connect your device? If so, then this procedure may work, depending on your previous firmware.

If the brick is from the device falling, with the screen breaking, I am not sure. You could try to use the blankflash.
[Moto G4 Plus Guides, News, & Discussion] Elleo1422:
friend already solve it ise the following disarm the phone disconnect the battery and mantube pressed the power button for 30 seconds and start I think it is reset or something like that to do that
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Is the thread is not monitored by [MENTION=325565]rajat[/MENTION]
[Moto G4 Plus Guides, News, & Discussion] echo92:
What are you hoping to get from Rajat? If it's a new blankflash, it'd have to be leaked from Motorola. Someone with access to a new blankflash would likely link it here, when or if that may happen, no idea. OEMs are typically not willing to let users have access to blankflashes.
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
There is no hope to update previous version blankflash with some binary update?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Unlikely, the main issue is the programmer included in the blankflash, which as far as I understand is responsible for the firehose connection and flashing of the new bootloader. Editing it would likely break the OEM cryptographic signature, meaning the flash might be rejected, and that's if we can work out what parameters would have to be changed to trick the blankflash into flashing over a newer bootloader.

Without access to the private OEM keys and no related devices (no other Moto SD617 devices), we're very limited.

https://github.com/openpst/sahara
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
[MENTION=7970352]echo92[/MENTION] Any idea about this bro

https://www.youtube.com/watch?v=3gJIpH7Mj58
[Moto G4 Plus Guides, News, & Discussion] echo92:
May work, but you'd need to find someone with an emmc flasher or someone willing to buy it, and have a working device to generate the raw files. No guarantees it'd work for our device
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
true bro one minute haste wasted my device, never experienced :(. Poor Moto:crying:
[Moto G4 Plus Guides, News, & Discussion] echo92:
You could contact mobile unbrick http://mobileunbrick.com see what they say and how much they'd charge. They're a JTAG service in India, amongst others.

No free solutions unfortunately, someone had to pay money somewhere
[Moto G4 Plus Guides, News, & Discussion] Nodrex:
I was updating my moto g4 to nuget and it turned off. I was not able to torn it on, but after first stab in got fastboot screen, but bootloader is locked and when i am trying to unlock it shows: 'Allow OEM Unlock' in Android Settings > Developer.

But i cant boot, because there is no boot image , so is there any way to unlock boot loader without 'Allow OEM Unlock' in Android Settings ?
[Moto G4 Plus Guides, News, & Discussion] echo92:
If anyone's still watching this thread, apparently this user managed to get their Oreo device unbricked by paying a Russian repair service - they seem to have a newer blankflash available: https://xdaforums.com/showpost.php?p=79539984&postcount=1300
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Echo92 bro, they will avail the file after 10$ payment?
[Moto G4 Plus Guides, News, & Discussion] echo92:
I do not know, never used that service. All I can do is to point you to a user who's apparently used the service and ask you to be wise. Check out the service and see whether or not you trust them enough to spend $10. I doubt they'll give you the file, since else they'd lose revenue.
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Tried to contact that person on the post but still unanswered
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
He's offline since yesterday, but he says he can recover the phone so wait for him. I spoke to him yesterday :highfive:.
[Moto G4 Plus Guides, News, & Discussion] JCAMACHOM:
Hi guys, well I will try to be understood as best as possible, since I am from Argentina and I do not handle English very well .. I own an XT1641, from one day to the next I stop walking, I am not very related with the Motorola in Regarding Softwares, Bootloader or firmwares. The only thing that is that my cell phone to turn it on or plug it in Bootloader mode and I see "Start Up Failed" below "failed to validate boot image" "ERROR: Failed to pass validation, backup to fastboot." The BL is in version: B1.07 (2017-11-07). If they were kind, would they guide me in what I have to do? Which Firmware to download or which files to flash. I tried to flash a firmware but it gave me FAIL. I was watching this post and they were talking about a flash that revives the phone, but I do not know how to download all of those that are there throughout the post.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
OMG I got my phone recovered :highfive::highfive::highfive::highfive: Dead to alive wow

bro [MENTION=7970352]echo92[/MENTION] how to get rid of the bad key issue?
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Share me the post link
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
hey bro that russian guy is true he got the latest blankflash i got my phone back
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Share me your number I am calling you
[Moto G4 Plus Guides, News, & Discussion] bs7799de:
please give me your number as well