yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Alright, I'm uploading a different mmc image written by dd (which has a different md5), so you might have better luck if that doesn't work. Apologies for this.
[Moto G4 Plus Guides, News, & Discussion] MATHEUS1213:
has not resolved yet

the led still blinks and it does not initialize even with this procedure :(
[Moto G4 Plus Guides, News, & Discussion] echo92:
[MENTION=8334764]luckilyblack[/MENTION] [MENTION=9761903]SuperCas[/MENTION] Can you try this mmc image instead: https://drive.google.com/open?id=1Sp64p3yCdrbqUhvrsfBDoLLpgF-RX5am

This was copied using dd with a default block size, comes up to the same size (in Windows) but has a different md5. Let me know if you have any luck. Same procedure, different file name - this file is mmc.7z with md5 7bc365a1ff009245a535971c915b5240 (expanding to mmc.img with md5 of afe5c3a9c7e8f4e9a3b43cc06e4522f9).
[Moto G4 Plus Guides, News, & Discussion] MATHEUS1213:
has not resolved yet

still unsuccessfully this second file gave the same thing as the first, I think the solution and wait for someone to bring the updated white file to that device anyway so thanks for the help
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
[MENTION=7970352]echo92[/MENTION] Thanks for you efforts, but unfortunately this image file does not seem to work producing the similar result as previous one with led blinking.

---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------

[/COLOR [MENTION=7970352]echo92[/MENTION] any suggestions?
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
Brother [MENTION=9761903]SuperCas[/MENTION] can you try flashing the img file using Linux to the SD and see if it is working?

Also brother [MENTION=7970352]echo92[/MENTION] my Samsung Evo 32gb after formatting shows only 29 something but our mmcblk is 30.5, problem? :confused: I also inspected the SD after flashing using mini partition tool it showed all system gpt partitions but no booting. Any idea?

Conclusion: Bricking a moto without blankflash is a head ache :p:D:crying::crying:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for trying, got one more trick for now: Oreo mmcblk is here https://drive.google.com/file/d/1Iei2kOFwGp3KCPjlZANIJgdtX7WRlZzZ/view?usp=drivesdk

I'm reviewing if there's any other ways to get a mmcblk working, whether I'm missing a setting ( these images were copied using DD to an SD card, via ADB shell).

Else, the only other ways to fix your device are, as I understand:

Hope someone else comes up with a mmcblk (possible), pay for your device to be fixed (either a motherboard change, expensive, or a local JTAG service) or buy a new device. I'm not sure if we'll ever see a new blankflash for a 2+ year old device.

---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------

Hmm, the file on Windows shows up as 29.1 GB (30 gigabytes), depending on what file system you use to read it. It's more concerning that these methods are not working. You could try the Oreo image, see how you get on, perhaps it'll be more successful with the newer bootloader?
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
[MENTION=7970352]echo92[/MENTION] sure brother this time I'm gonna try this oreo file using the linux way and see what happens. I read the last working blankflash was from Google+ Brazil community and I'm posting requests periodically on G4 plus forums, as i see some new brickers - hope blooms lol. :good::highfive::crying::crying::crying:
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
Right now I am trying to flash SD via Linux.

---------- Post added at 03:17 AM ---------- Previous post was at 02:26 AM ----------

@echo92 Can you please tell me which bootloader version does the image file mmc_oreo.img contains?
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
[MENTION=7970352]echo92[/MENTION] Tried flashing the sd card with oreo image you have provided using linux but still no luck. Any suggestions?:confused:
[Moto G4 Plus Guides, News, & Discussion] echo92:
The bootloader on the Oreo image is v.B1:09, whereas on the Nougat images they were B1:07.

Hrm, I'm honestly not sure, I'm afraid - I appreciate you trying and apologies that it's not working. I'll have a read around and see if there's any alternative solutions. If you find any before, feel free to try and report. I get the general impression that a newer blankflash (i.e. created on or after 11/01/2019, which is when the B1:09 bootloader was built) is unlikely to be coming any time soon, if at all. If you really need a working device now, the only options I see are to pay for a motherboard replacement, or a JTAG repair service, or buy a new device altogether. Depending on where you are, I would check your local consumer laws, see if they cover hardware repair or at least limit the repair cost. Apologies for not having better news, hard bricks, especially involving the bootloader are not easy to fix. I'm hoping that others may come along to offer other tips/solutions.
[Moto G4 Plus Guides, News, & Discussion] alekz117:
Help ..... have connection problems

I have the problem that I can not connect the device and I rewind the driver and also the driver version. I repeated several times step 3 of the previous guide plus I already probe all files bat ......... no I know that I'm waiting for your help.

Thank you

Pd. Cel is a moto xt1601

[IMG="cmd"]https://image.ibb.co/eqVj7Q/im2.png[/IMG]

[IMG="dispositivo"]https://ibb.co/m9XLgk[/IMG]
[Moto G4 Plus Guides, News, & Discussion] HeyArnie:
I can't install stock rom

Hi, I used this method to revive my Moto G4 Amazon Variant and it worked! Thanks! But I'm unable to install stock rom, maybe because it has a different bootloader.

Anybody have the stock rom for XT1625 of Nougat to revive my phone? Or should I wait for Amazon to update this model to the June security patch?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Unfortunately, this blankflash is only for Moto G4 and G4 Plus models - if the info you posted is right, you've got a Moto G4 Play. The blankflash appears to be specific to the CPU and the bootloader, which is different for the Play compared to the other models ( SD 410 vs SD 617 for the G4/Plus), and thus this blankflash won't work for you.

Your only hope is that there's a blankflash for the G4 Play around (or it gets leaked from Motorola...)
[Moto G4 Plus Guides, News, & Discussion] Geek_manoj:
Does not enter recovery or boot up system

as soon as the blankflash file is updated i flashed it and worked

then i flashed updated gpt and bootloader

then i tried to enter recovery mode but its not entering

and also when i unplug usb cable it is turning off

then i flashed stock rom

but still recovery and system booting are not working,enters only to fastboot that too on charging.

guyss please help me it means a lot to me.Thanks in advance.
[Moto G4 Plus Guides, News, & Discussion] carrlossss:
I really love u guys. It worked here too.

Even though everytime that I try to update by OTA the phone gets bricked again..

I'm sure that you guys already solved this problem before and I could be searching for the fix right now, but the happiness is so big that I think I'll actually stay with this version as long as it works.

Thank you guys, again, for making my day. :highfive:
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you've rescued your device by flashing the June 2017 bootloader and GPT as described, trying to update your device with an OTA from an earlier stock build will brick your device. This is likely due to the mismatch between your bootloader and the system, as the OTA may patch your device without being aware that you have a bootloader different to that expected.

Easiest way to update properly is to download and flash the June 2017 fastboot ROM, so you don't have to update via OTA and your device is fully updated. This should be the latest build generally available.

https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for the fastboot ROM. It's up to you if you choose to lock your bootloader or not.
[Moto G4 Plus Guides, News, & Discussion] carrlossss:
It worked too, thank you very much!!!!!!

Now my phone is perfect again :victory:
[Moto G4 Plus Guides, News, & Discussion] m.swastik:
I have owned 4 android phones and always followed xda threads for these models. I have never seen so many bricked devices of these of a single models that too while doing official update. There is something definitely wrong with Motorola. Is the problem same for other models of Motorola?

Also I want to ask is it possible to solve https://xdaforums.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912 problem with this method.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Yep, you can have a look at Moto Z, Moto G5 Plus and Moto X forums, for starters, as well as other devices (e.g. LG G4) for similar incidents. The update itself isn't the issue though. It's the act of downgrading your device and then updating via OTA that has appeared to cause all these bricks. The OTA appears to be programmed to patch files (rather than flash a whole file) as per the block based OTA, however the update appears to patch assuming that your system version is the same as your bootloader. As you've downgraded, that isn't the case, you've got a mismatched bootloader and system and thus the update patching corrupts the bootloader. This then causes the hard bricks you've been seeing. With the June 2017 update, Motorola also appears to have patched the critical bootloader vulnerability as described in the May 2017 security patch notes, so I'd imagine that's contributing to the number of hard bricks.

Should there be checks in the OTA for whether you have a mismatched bootloader and system, rather than assuming you never downgraded? Perhaps. However, this isn't unique to Motorola as I previously mentioned, downgrading is risky and as security increases, even more so. I'm not here to tell members what to flash on their devices, but perhaps we need to make it more apparent that downgrading comes with increasing risks.

This blankflash won't solve your issue though, as it looks like your hw or modem partitions might be corrupted (perhaps by a wrong firmware flash?), which the blankflash doesn't touch.

However, lCrD512 has kindly uploaded the hw and modem partition files from XT1643 for you. https://xdaforums.com/showpost.php?p=73293050&postcount=28 adb command to flash: https://xdaforums.com/showpost.php?p=73293379&postcount=30 You may have to boot into TWRP to be able to execute the adb commands, else the system may stop you from copying the partitions over.
[Moto G4 Plus Guides, News, & Discussion] krishna8691:
i used the guide mentioned in the OP and successfully unbricked my phone and got it running

so i just wanna ask if everything is fine now like the bootloader and gpt that i flashed according to guide and also the stock rom NPJS25.93-14-8 (is this the latest one ?)

so now if any ota update comes then should i go for it or not ?

also one more thing if now i can flash twrp and root my phone will it be ok?

and after flashing twrp can i flash any custom rom ?
[Moto G4 Plus Guides, News, & Discussion] xperiaworld:
thanks lot for this! its really great job...!
[Moto G4 Plus Guides, News, & Discussion] echo92:
1) stock rom NPJS25.93-14-8 (is this the latest one ?) As of writing - yes, the June 2017 fastboot ROM is the latest stock ROM we have.

2)so now if any ota update comes then should i go for it or not ? Provided you fully flashed the NPJS25.93-14-8 stock ROM and used the GPT/bootloader provided, you should be okay to take OTA updates. If you want to be super safe, wait for the fastboot ROM for that OTA and then flash the fastboot ROM.

3)also one more thing if now i can flash twrp and root my phone will it be ok? Should be okay. As usual, ensure you flash a custom kernel before you root.

4) after flashing twrp can i flash any custom rom Again, as the custom ROM only replaces your system and data, should be okay. However, if you choose to revert back to stock firmware, only use the June 2017 fastboot ROM. Do not downgrade your firmware and attempt to update via OTA.
[Moto G4 Plus Guides, News, & Discussion] krishna8691:
thank you very much :)
[Moto G4 Plus Guides, News, & Discussion] m.swastik:
How long does it take to flash hw partition, my terminal is flashing it since 15 min.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, I'm not sure - hopefully someone more familiar with the flashing can assist - you could try PM'ing tywinlannister7 or lCrD512, for example.
[Moto G4 Plus Guides, News, & Discussion] krishna8691:
if i go on a custom rom and lets say next month or in coming months motorola releases android oreo soak test and so to try it out if again i flash the latest ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC stock rom following this guide https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 (and i have flashed the gpt and bootloader following this thread itself) will i be able to flash that soak test zip without hardbricking again ??//

lets say if i skip the soak test and then come back to stock rom following above procedure to get official android oreo update via ota so without risk of hardbrick will i be able to take that or any other relevant ota ? (coz last time while updating via ota to latest version the device got hard bricked)

btw i had read this : https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761/post73571140 but still just want to ask the above mentioned question/scenario

Sorry for my Stupid Questions but i just want to know bcoz not every time we are going to get the blankflash file :( to our rescue
[Moto G4 Plus Guides, News, & Discussion] echo92:
The GPT and bootloader from this thread are the same as that from the NPJS25.93-14-8 stock ROM that you mentioned. I specifically pulled the files from the stock ROM and you're welcome to check the md5 checksums of both. Given that you're on a custom ROM, your GPT and bootloader would still be on the June firmware level. As they both are the same patch level, you should be able to flash the June 2017 stock firmware completely and be okay to use the soak test OTA if it comes out. Of course, with the soak test, you'll need all the soak test updates released by Motorola to be brought back to the official OTA update path, else you'll be stuck on the soak test otherwise and would have to wait for the Oreo fastboot ROM.

Same should apply to your second scenario, as you're bringing your device back to the June update which you are on and then taking the update, that should be okay.

The post you refer to applied to if you downgraded your system but did not downgrade your bootloader, which appears to be the cause of the bricks when you accepted an OTA update (e.g if you had a June 2017 bootloader but downgraded to a December 2016 system, taking the march 2017 OTA would patch your bootloader thinking you had a December 2016 bootloader, causing a brick).

As you're referring back to the same patch level with the June update, that doesn't appear to apply and you should be able to take an OTA. However, once you've updated past the June update with an OTA update, it is no longer safe to downgrade (which includes using the June 2017 firmware).

Thus, a way to not brick is to flash the June 2017 firmware (assuming that you used the GPT and bootloader in this thread) and once you've updated via OTA past the June 2017 update, do not downgrade by using this or older firmware. Wait for the updated Oreo stock firmware to safely flash back to stock (if we get it....)
[Moto G4 Plus Guides, News, & Discussion] HACK3DANDR0ID:
Worked Great Here....pulled phone outta pocket....Black Screen. I dont understand how doing nothing to the phone would cause the bricking...
[Moto G4 Plus Guides, News, & Discussion] krishna8691:
Thank You Very Much for all the info learned a lot of new things :)
[Moto G4 Plus Guides, News, & Discussion] Skull7770:
Thank you, this step by step process really helped to restore my phone again.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
Thanks for your care brother [MENTION=7970352]echo92[/MENTION], [MENTION=9761903]SuperCas[/MENTION]. I gotta say one thing I'm flashing ROMs and messing things from my galaxy Y (hope you remember that thing;)) previously galaxy note 4 I never ever failed to boot a phone. My first Moto turned worst Moto. :(:(:good:. They even can't boot it from their service center too very very poor support. Shoot.
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
[MENTION=7970352]echo92[/MENTION] Thanks for providing us with various images to test on device, we really hope you will find some solution.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
Brother need to know one thing, what is the OS you run on your PC? I read many G5 brickers reported W10 can't flash the img correctly but they all got it successful with a windows 7 pc. Most of us got the same problem we've. So pls confirm your PC os.
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Dear friend i try that method on win7 using rufus2.18.

But it is not working
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
:( Brother if possible try flashing the img with disk image flasher and after flashing insert the SD card and connect the phone to your pc with the volume down button pressed on and hold it for 3 minutes, in some cases this helped. :confused:

---------- Post added at 04:55 AM ---------- Previous post was at 04:42 AM ----------

@echo92 brother is the loader.img is different from the mmcblk.img?noob!:D
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
I had used Linux to flash the SD card but it's not working.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
What's your device brother? XT16?

---------- Post added at 05:24 AM ---------- Previous post was at 05:04 AM ----------

Brother [MENTION=7970352]echo92[/MENTION] can you make a loader.img? https://xdaforums.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860/page14

Preferably oreo brother, let's give it a one last try??.
[Moto G4 Plus Guides, News, & Discussion] echo92:
I'll have a look, our device partition layout may be different to the X style, so the parameters might need adjusting. To to answer your other question, as far as I know the loader.IMG seems to be the first part of the flash storage, containing the bootloader, modem, etc but no userdata. No ideas if it'll work.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
[MENTION=7970352]echo92[/MENTION] Little hope brother, saw many people got Unbricked. :angel::(:confused:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Some, though others mentioned it didn't work for them. Without knowing exactly why your device got bricked by the OTA (whilst others seemed to have been okay), I'll give it a go, maybe generate the loader image and another mmcblk via DD on my device rather than via ADB shell. Since I've updated my device to Oreo, you'll only be getting Oreo, under no circumstances am I downgrading my device.

I'm reading through that thread, see if there are any ideas. Give me some time.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
You're giving us the hope, debted to you brother [MENTION=7970352]echo92[/MENTION]. ??
[Moto G4 Plus Guides, News, & Discussion] echo92:
I'm not promising anything, please be patient.
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
I have got XT1624 variant.
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
No update on blank flash?
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
Answer is Big NO brother. Wait for it or any other fix but not anytime soon. :crying::crying::crying:
[Moto G4 Plus Guides, News, & Discussion] echo92:
As requested, here's a loader.img as generated by the Moto X Style guide: https://drive.google.com/open?id=14OeSCh-ybYEZ7yYCqdEc9sz01iOWmKpC Again, I have no idea if this will work, hopefully it'll get your device to fastboot (which is all you really need). As far as I understand, it's the same procedure - write to an SD card, then try to boot (or hold down power and volume down to boot to fastboot).

Here's another mmcblk0 from my device, this time generated on my device via TWRP and root, in case there was anything odd introduced by an ADB shell on Windows 10: https://drive.google.com/open?id=1dhYciSmFRrAYoam6lk-cKOU18QesCsgX This time, I've also zipped the file to rule out any oddities introduced by 7-zip (shouldn't be, but for a procedure as fickle...).

Again, thanks for trying. I'm curious if there's enough differences between G4 Plus (athene_f) and G4 models (athene) that the images may not work, though I would have thought they'd boot to fastboot at least. Good luck.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
Thank you so much brother [MENTION=7970352]echo92[/MENTION] I'll try and inform you :highfive:
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
I will try and let you know ASAP [MENTION=7970352]echo92[/MENTION]
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
[MENTION=8334764]luckilyblack[/MENTION] have you tried the images?
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
tried loader.img brother but no luck:crying::crying: I'm going to try burning img on windows 8 and report you brother.
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
Same here, I tried loader.img but it didn't work, right now I am trying the MMC IMG.
[Moto G4 Plus Guides, News, & Discussion] luckilyblack:
any luck [MENTION=9761903]SuperCas[/MENTION]?

[MENTION=9131463]Vikassir33[/MENTION] did you try flashing loader img on windows 7 brother?

---------- Post added at 09:34 AM ---------- Previous post was at 09:26 AM ----------

@echo92 thank u for your efforts brother, as u thought i think we need device specific loader img to boot brother no luck for me on xt1643 hope anyone with same device will offer one or wait for the blankflash file.:(:(:confused:
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
I tried flashing loader image as well as mmcoreo2 image first using windows then using Linux using dd command but nothing worked, I think we might have to wait for blank flash.

[MENTION=7970352]echo92[/MENTION] thanks for providing images, but they doesn't seem to work.

---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------

[/COLOR [MENTION=7970352]echo92[/MENTION] i tried everything I mean I tried flashing with Rufus, win32diskimager, dd command but nothing seems to work. Any suggestions?
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
I will try it in evening
[Moto G4 Plus Guides, News, & Discussion] echo92:
We may need device specific images as mentioned above, or there's a more serious issue behind the scenes. Unless you know of a sympathetic Motorola engineer, there seems to be a very slim chance of getting another newer blankflash.

I see some activity regarding this on the Moto G4 plus telegram channel, someone's testing a XT1643 loader image, let's see if they have better luck. Unfortunately, for the time being, your only options still are to pay for the repair yourself or buy a new device. In theory, you could buy the same working device and see if you could get a clone off that device.

If you see anything else to try, let me know. QFil/QPSTmay have the same issues as the current blankflash, we don't have the necessary updated files.
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
Hey guys can you try the provided blank flash file and let me know if that works for you please do it immediately?
[Moto G4 Plus Guides, News, & Discussion] Vikassir33:
Testing this one, hope it works

---------- Post added at 03:55 PM ---------- Previous post was at 03:24 PM ----------

Not works for me
[Moto G4 Plus Guides, News, & Discussion] SuperCas:
What error you are getting?