yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] echo92:
how is your device not recognised? Is it not showing up at all or is it being registered as HS-USB 9008 or similar in device manager? Do you have the Motorola USB drivers installed and, if you're booting your device to fastboot/bootloader, do you have driver signature enforcement disabled on your computer?
[Moto G4 Plus Guides, News, & Discussion] vijairozario:
thank u so much bro. my device got life again
[Moto G4 Plus Guides, News, & Discussion] nittinarya25:
Device Still led blinking after installing Stock rom

Hello Admin, First of all very thankfull and congratulations to you that you are providing steps to the people that bricked his device accidently/ device error.

In my case i have done all your steps, after your first step i got an waiting for device error-> but in next step you mentioned Motorola device drivers -> installed-> waiting for device resolved-> now after your all codes i followed->fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader ******

-> But after this step cmd prompt was showing fastboot reboot -> still moto g4 plus not responding(only led blinking)... i didn't see fastboot screen in my device

-> and when i came to the last step

Download it and then just extract it in and don't forget copy ADB and the fastboot files into that folder. Once done then Hold shift and press right key on mouse then select Open Command window here from that menu.

then use this code to flash stock ROM :

Code:

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash dsp adspso.bin

fastboot flash oem oem.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot erase cache

fastboot erase userdata

fastboot erase customize

fastboot erase clogo

fastboot oem fb_mode_clear

fastboot reboot

pause

And that's it!! You will get your Athene Back to Life

I got my Athene back to life using this method............

********** all cmd commands was gone correct-> in last cmd prompt shows pause-> but device still led blinking

-> Please help admin...:(

THANKS
[Moto G4 Plus Guides, News, & Discussion] echo92:
1) Were you able to run the blankflash? If so, what does your device show up as now in Device Manager?

2)Does typing 'fastboot devices' in ADB (whilst having your device connected in bootloader mode) return your device serial number?

3)Try unplugging your device and reconnecting - perhaps your computer will properly sense the device.

4)What are the results of the commands you entered? Can you paste them here or upload them in a text file please?

5)How did you brick your device initially and what device do you have?
[Moto G4 Plus Guides, News, & Discussion] nittinarya25:
Thanks for replying admin

1) Yes i am able to run bank flash- but bank flash showing waiting for device(even after installing Motorola device manager drivers)

b) In Device Manager- unknown device with yellow icon.

2) no

3) I have tried many times

4)[/IMG]

5) MOTO-G4 plus (XT-1643), first my device was having only led blinking error after i have searched for this error - in result i found that press volume - + power button together for more than 2 minutes. I have tried this many times and after long 4 hours my device got started while holding these two buttons(volume- and power button) and after this my device shows me my phone is charging and after this my device started.

But after this i tried to hard reset my device by choosing wipe all data and delete all user data and while this process my device got stuck in this process for more than 10 minutes. and in the next step was my biggest mistake i have done by pressing volume down key + power button and after this my device gone in previously same situation (only led blinking while charging).

and after this i found your this page, i have tried all this steps but after finishing installation device was not responding only led blinking
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for the response, I'm not an admin but will try to help you as much as you can.

1)That suggests that the blankflash can't communicate with your device (which is supported by the fact your device is showing up as unknown in Device Manager). You wrote in your previous post that the 'waiting for device' was resolved though?

2)Again, supports 1) that your device can't talk to your computer.

Do you have driver signature enforcement enabled if you're using a Windows computer? If so, or are not sure, try to disable driver signature enforcement and attempt to use the blankflash again. I'm aware that driver signature enforcement may block fastboot drivers (or non Windows signed drivers) from loading, so by disabling signature enforcement you may be able to load the fastboot drivers and may be able to use the blankflash. Alternatively, you could right click on the unknown device and try to install the drivers manually (from the Motorola drivers you installed on your computer). The screenshot I've linked is what my device - booted into the bootloader - looks like in Device Manager when it's attached to my computer via USB. Note the red box and the listing of Motorola ADB Interface. You may wish to verify you see something similar, or if not, try to install the drivers shown. I have a Windows 10 PC with a XT1642, with Motorola USB 2.5.4 drivers installed (from here: https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27, )

Also ensure you're using the latest blankflash as provided in the opening post.

However, what you describe in 5) does sound like hardware failure, which a blankflash may not solve. However, try with the suggestions above and see how you get on.
[Moto G4 Plus Guides, News, & Discussion] nittinarya25:
Thanks for the response, I'm not an admin but will try to help you as much as you can.

1)That suggests that the blankflash can't communicate with your device (which is supported by the fact your device is showing up as unknown in Device Manager). You wrote in your previous post that the 'waiting for device' was resolved though?

2)Again, supports 1) that your device can't talk to your computer.

Do you have driver signature enforcement enabled if you're using a Windows computer? If so, or are not sure, try to disable driver signature enforcement and attempt to use the blankflash again. I'm aware that driver signature enforcement may block fastboot drivers (or non Windows signed drivers) from loading, so by disabling signature enforcement you may be able to load the fastboot drivers and may be able to use the blankflash. Alternatively, you could right click on the unknown device and try to install the drivers manually (from the Motorola drivers you installed on your computer). The screenshot I've linked is what my device - booted into the bootloader - looks like in Device Manager when it's attached to my computer via USB. Note the red box and the listing of Motorola ADB Interface. You may wish to verify you see something similar, or if not, try to install the drivers shown. I have a Windows 10 PC with a XT1642, with Motorola USB 2.5.4 drivers installed

Also ensure you're using the latest blankflash as provided in the opening post.

However, what you describe in 5) does sound like hardware failure, which a blankflash may not solve. However, try with the suggestions above and see how you get on.[/QUOTE]

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

Thanks for replying friend

Unknown device error solved now device manager showing motorola adb interface--

But after this still in bank flash waiting for device error even after disable signature...please help! is their any way to flash my moto g4 plus with any flashtool?????

Please help

Thanks
[Moto G4 Plus Guides, News, & Discussion] Fir3lordZuk0:
Thanks a lot man.

I sold this in exchange offer at amazon. The agent was about to come to pick the device and it bricked(stupid Moto updates). I was ****ting my pants that he will not pick the device and wont give me new one. Then i found this post and it unbricked my device.

Thanks a lot again :)
[Moto G4 Plus Guides, News, & Discussion] MOHAMED ASHIK:
Thank you
[Moto G4 Plus Guides, News, & Discussion] duochoi0079:
no signal and not charging

i did the aforementioned commands but i ended up having no signal and device is not charging

i used BP TOOLS in bootloader options and it does solve the problems i mentioned, however it loses the usb transfer option...

im both thankful and scratching my head now

could you help me on this one?
[Moto G4 Plus Guides, News, & Discussion] echo92:
So you've tried the suggestions in this post here: https://xdaforums.com/showpost.php?p=73434849&postcount=2 ? You may have to unplug and re-plug your device again for it to be recognised.

Are you using the original Motorola cable or another good quality USB data + power cable to connect your device to your computer?

Without being able to communicate to your device, I'm not sure if you could use any flash tools. However, as I suggested before, another cause of this behaviour may be a motherboard failure.

---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------

Do you still have no USB transfer if you reboot normally (or power off and boot without using BP Tools)?
[Moto G4 Plus Guides, News, & Discussion] duochoi0079:
on a normal boot, it can perform USB transfers but you lose both the network signal and charging function

this might have been an earlier problem (not charging but it had network signal) from the previous owner, i thought flashing the rom again may help but it turned out that the network signal was totally gone and it cant charge in normal boot.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Yeah, appears that BP Tools switches your USB Interface to BP mode (presumably for developer testing/troubleshooting), possibly why you lost USB transfer when booting with BP Tools https://forums.androidcentral.com/motorola-droid-maxx/312723-weird-mtp-issue.html

Not much info on BP Tools though, apart from it's apparently used for baseband troubleshooting (from an old thread : https://xdaforums.com/showthread.php?t=2121442 )

But either way, that device doesn't sound healthy - do you know the history of the device from its previous owner? Which firmware did you try to re-flash onto the device (and what device is it)?
[Moto G4 Plus Guides, News, & Discussion] duochoi0079:
i seriously have no clue. i just wanted to fix it back to normal but i guess that's rather impossible for now.

the only thing that bugs me is why the network signal disappeared on normal boot after flashing the rom because that wasnt part of the problem before
[Moto G4 Plus Guides, News, & Discussion] r1rony:
Can anyone give qcn file of athene xt1643 plz:crying::crying: how to extract qcn tutorial is here

http://www.androidbrick.com/ultimat...agon-xiaomi-mi5-imei-and-baseband-repair-fix/ if anyone of u kind people help me to get baseband and Imei back and it would help others who lost their baseband and original Imei if someone give me qcn file I will make a thread to recover baseband and original Imei of athene it is only way that I could revive my athene xt1643 now I tried almost all of the method to recover it like pushing hw partition and flashing
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
FYI there is already a thread for recovering the lost IMEI and fingerprint https://xdaforums.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
update your device from following thread https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] Icesmash:
Thank you so much! To avoid a future brick how can I prevent OTA updates?

I plan on using ElementalX, twrp-3.0.2-r4-athene_shreps & Magisk-v15.2.zip so definitely don't want to brick it again perhaps there's a xposed/magisk module?
[Moto G4 Plus Guides, News, & Discussion] echo92:
1) To avoid hardbricks, do not downgrade your device with older firmware and expect to take OTA updates. I noted you flashed the NPJ25.93-14 (December 2016 ) firmware onto your device, which may have likely been far older than the actual firmware on your device. You cannot downgrade bootloaders. Thus, taking an OTA with a mismatched bootloader and firmware in terms of patch levels runs a very high risk of hard bricking. Only flash firmware of the same or newer patch level as on your device, ideally as new or newer than your bootloader patch level. At least the blankflash worked this time.

2)If you're planning to root, you can use shrep's 3.1.1 TWRP as well. For disabling the OTA updater, you can see this thread: https://xdaforums.com/moto-g4-plus/help/how-disable-notification-update-t3459587

However, depending on which firmware you've flashed, you may not receive OTA updates anyway. I recall NPJ25.93-14.7 is the latest US retail firmware; flashing NPJS25.93-14-10 or NPJS25.93-14-13 has been shown to work, but you may not get OTA updates because your builds don't match those expected of your device for your region.

Oh, and always have a backup in TWRP before you do any flashing of magisk/xposed. As always, flash ElementalX before flashing root/xposed, else you'll brick your stock ROM.
[Moto G4 Plus Guides, News, & Discussion] chubi99:
thanks!!!!

you save my phone, thanks a lot!!!!:):):):)
[Moto G4 Plus Guides, News, & Discussion] cooldeepak:
Many Many Thanks [MENTION=7843165]siddhesh9146[/MENTION] and [MENTION=7245484]marcelofilgueira[/MENTION].

No words to describe your work. Salute __/\__
[Moto G4 Plus Guides, News, & Discussion] vishal.mamidi:
Security version downgrade

need gpt.bin more latest one please
[Moto G4 Plus Guides, News, & Discussion] echo92:
1)Can you confirm that the flash files in your ADB terminal folder are that of the NPJS25.93-14-10 (September 2017), or the December 2017 NPJS25.93-14-13 stock ROM, and how are you flashing? Are you using a script or using the commands manually in fastboot? I think you need a complete flash before attempting to proceed.

2)How is your device appearing in Device Manager? Is it fastboot athene s or Moto G4 ?

3)Looks like you have a September 2017 bootloader but still a Marshmallow based system and baseband, hence suggesting the flashes you're performing did not work. When you flash again, can you please paste the flash log here?

4)I would caution against using 'fastboot erase system' with a device in this state.

---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------

Which GPT/bootloader do you need? September and June 2017 are in the main post. If you need the December 2017 GPT/bootloader, it's here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M

They've all been extracted from their respective stock ROMs.

I hope you didn't hard brick by taking an OTA update from Marshmallow...
[Moto G4 Plus Guides, News, & Discussion] vishal.mamidi:
thankkkkkkk youuuuu veryy much brooo

yes i need december 2017 :victory::victory::victory::victory:

---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------

bro is there any way to change Software status : modified to official

as i am unable to play pokemon go

for Safetynet test

thankk youu soo muchh broo
[Moto G4 Plus Guides, News, & Discussion] echo92:
Were you previously on the September 2017 (NPJS25.93-14-10) or December 2017 stock ROM (NPJS25.93-14-13) before downgrading to Marshmallow?

Now you see why I mentioned do not use OTA updates if you downgraded?

If you want to restore SafetyNet, you need to either re-lock your bootloader, or root with magisk to hide your unlocked bootloader status. On the stock ROM, you need to flash ElementalX kernel and magisk in TWRP in order to gain root and be able to clear SafetyNet.

Modified software status should change to official if you install an OTA update. You can only install OTA updates if your entire device firmware (including the bootloader) is on the same patch level, else you'll likely hard brick.

Also, I get that you're desperate for help, please avoid posting the same request in multiple threads please.
[Moto G4 Plus Guides, News, & Discussion] erica butson:
After flashing bootloader and gpt Recovery mode is not working.

After this command.

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot reboot-bootloader

Phone boots into fast boot mode but recovery is not working.

I tried to flash rom but nothing works.

If i'm trying to flash the same file again i get this error

fastboot flash partition gpt.bin

(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.009s]

writing 'partition'...

(bootloader) Security version downgrade

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.065s
[Moto G4 Plus Guides, News, & Discussion] echo92:
What files are you attempting to flash? Do you know which build/security patch they're from? If they're from the GPT/bootloader files, they should all be in folders with their respective security patch dates.

That error suggests you're attempting to flash GPT/bootloader files older than the firmware present on your device.

What stock ROM are you trying to flash?
[Moto G4 Plus Guides, News, & Discussion] vishal.mamidi:
" I hope you didn't hard brick by taking an OTA update from Marshmallow... "

yes bro

my mobile was on December 2017 bootloader

i flashed android 6 ROM and tried OTA on the home that my Software status : Modified on fastboot becomes Official

to play pokemon GO

because of Modified status SafetyNet test Returning false and i am unable to play game

thanks a lot

---------- Post added at 04:05 PM ---------- Previous post was at 04:01 PM ----------

Sorry bro, i don't do next time

if i simply flash the OTA from the stock recovery,

will i still get Hard brick ??

or

hard brick is only installing OTA normally ?

Thank you soo much bro
[Moto G4 Plus Guides, News, & Discussion] erica butson:
I will provide the flash logs which rom you want me to flash now?

1) I have downloaded both

a) ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

b) ATHENE_NPJS25.93-14-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

I have tried flashing both rom but for the first time when my device got booted into fastboot i flashed a) ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml as per your guide.

I'm flashing the rom by typing all the commands manually. However i get some error info like this

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:partition: not found

but says OKAY once flashing the rom by manually typing all the commands one by one.

2) The device appears as Fastboot athene_16mp S. I tried to automatically detect and install the driver but failed hence i manually added the device drives as Android phone and the phone gets detected in fast boot. Here is the image

Can't post the url. [After approximately 10 posts, you will be able to post outside links. Thank you for understanding!]

3)Can you please provide me a link of marshmellow rom?. The device was hardbricked when I was trying the root the phone the phone rooted successfully but then i received an nougat update which bricked my phone.

4) i wanted to know the exact problem of the phone. I thought it would work if i erase existing bootloader and system and flash. Sorry.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hard bricks only appear to happen if you downgraded and then take OTA updates. Doesn't matter if you install OTA normally or via recovery, if you've downgraded you will likely hard brick.

In your case, you had December 2017 firmware, then downgraded to MM.

You would have had December 2017 bootloader (you cannot downgrade bootloaders), but a MM system. You then took a MM OTA update, which likely corrupted your December 2017 bootloader (as the OTA appear to assume your bootloader is the same patch level as your system, and has no apparent checks). Hence the corruption of your newer bootloader with older OTA patches and the hard brick.

Only take OTA updates if your device is completely the same firmware or if you really want to downgrade, only downgrade to the most recent build (e.g. from Dec 2017 to Sept 2017), so the OTA applies the same patches.

At least we know now that the latest blankflash still appears to work on the NPJS25.93-14-13 B1:07 bootloaders.

---------- Post added at 06:24 PM ---------- Previous post was at 06:14 PM ----------

1) Hmm, do you see the GPT being flashed successfully (completing with [OKAY])? Do you also get a serial number response if you type 'fastboot devices' (without quotes)?

I'd delete all the stock ROM files in your ADB folder. Then extract a fresh copy of the NPJS25.93-14-10 stock ROM and copy all the fresh files to your ADB folder. Then repeat the flash, try using each flashing command manually, waiting for [OKAY] before proceeding. Post the output here please.

2)Okay, so looks like your device is being detected okay, as you likely only have a functioning bootloader at this point.

3)You do not want to use a Marshmallow ROM right now - else, as I wrote in the post above this, you would likely hard brick again. If we get your device working, then I'll provide a MM link. I'm here to try to help you get your device working again, and the safest way to do that is to flash your device to have firmware and bootloader of the same patch level, not to mix patch levels.
[Moto G4 Plus Guides, News, & Discussion] erica butson:
I'm trying to flash stock rom ATHENE_NPJS25.93-14-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.

The GPT/bootloader was flashed from september 2017 build. NPJS25_93_14_10_Sept2017_GPT_bootloader

The firmware present on my device is september and the rom im trying to flash is december 2017
[Moto G4 Plus Guides, News, & Discussion] echo92:
Okay, whenever you're ready, I'd be interested in seeing the flashing output from either September or December 2017.
[Moto G4 Plus Guides, News, & Discussion] erica butson:
Here is the logs

here is the log when i tried to flash december stock rom.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for that.

1)You may wish to copy paste each command rather than typing them out manually. You can copy each command individually and paste into the ADB terminal, then press Enter. I noted a few mistyping errors and flashing firmware is a procedure that you don't want to cause errors in.

2)For boot (kernel) and stock recovery, that 'Image is signed with bad key' error appears normal when you re-flash stock firmware with an unlocked bootloader.

3)Hmm, your log otherwise looks okay. So when you press 'Recovery' in the bootloader menu or 'Start', your device is just blank and fails to boot? How long do you leave it for?

Can I ask for another fastboot getvar all output please, to see if the flash actually worked and whether you have the B1:07 bootloader of Dec 2017 and the NPJS25.93-14-13 stock ROM on your device?