yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] joaopaulo_:
is there working on lastest stock rom? NPJS25.93.15?
[Moto G4 Plus Guides, News, & Discussion] Shreekarg:
Yes it works
[Moto G4 Plus Guides, News, & Discussion] echo92:
It's likely due to the old version you have - you've got the Dec 2016 firmware, whereas you likely had a much newer GPT/bootloader on your device when you bricked (you cannot usually downgrade bootloaders or GPT).

From that link, do you mean you're getting the remote failure and no other reason, or are you seeing 'security downgrade error' as well? If you're getting readblock errors then that suggests a flash memory partition failure and warrants a motherboard repair.

Try the Feb 2018 GPT/bootloader I've uploaded: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M This is from the (as yet unverified) stock ROM here, so be careful. If this does work, then I would strongly recommend flashing the latest stock ROM. AFH appears to be working at the moment.

If you try to flash the NPJS25.93-14-13 after flashing the GPT/bootloader, expect to see security downgrade errors with the GPT/bootloader as NPJS25.93-14-13 is the Dec 2017 stock ROM. However, it should be safe to use OTA updates as the Dec 2017 firmware directly precedes the Feb 2018 update. Do not use any firmware older than this (or in the future, do not use a stock firmware version older than the firmware version directly preceding the firmware version on your device, ideally use the same firmware or newer than the firmware on your device), else you may hard brick again if you take OTA updates.
[Moto G4 Plus Guides, News, & Discussion] gourav343:
you need to install this driver first.
[Moto G4 Plus Guides, News, & Discussion] sathishkanna:
my mobile connects only as motorola adb interface...what shall i do guys??
[Moto G4 Plus Guides, News, & Discussion] Emmglory:
still not detected. I do not know what to do.

installed this also driver also.... Installed before also... but again re-installed but still the phone is not detected. I am totally helpless now.
[Moto G4 Plus Guides, News, & Discussion] vinay lucy:
Thanks a lot

Thanks a lot man.

You just saved me over here. Phone was completely numb without LED indication.

Flashed with Feb Bootloader zip and back to Stock rom again.

:):)
[Moto G4 Plus Guides, News, & Discussion] StAr1oRd:
getting 'remote failure' error while flashing partition

[IMG="screenshot"]https://drive.google.com/file/d/1a9vTeAzxk-YqGTmEMu6y2LBRl8nbBYNh/view?usp=sharing[/IMG]

Please get me through this.
[Moto G4 Plus Guides, News, & Discussion] echo92:
What files are you flashing to get this error? That error suggests you're flashing a GPT/bootloader that is older than the one on your device, and so is blocking the flash.

Try one of the later GPT/bootloader files, and then flash the latest stock ROM for your device. If you do downgrade, please do not use OTA updates, else you may hard brick again.

https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M for the GPT/bootloader collection
[Moto G4 Plus Guides, News, & Discussion] suva12296:
Moto g4(4th gen)

My moto g4(4th gen) got hard bricked while using factory reset and I have updated my phone to feb security update and you also mention there feb security updated phone won't be apply this process. then how can I unbrick my phone .
[Moto G4 Plus Guides, News, & Discussion] abhi212b:
As far as i know, you only need gpt.bin... As the bootloader is not updated.. So just check out the Feb OTA file already posted in this forum..

https://xdaforums.com/moto-g4-plus/how-to/ota-february-2018-npjs25-93-14-15-t3770286

download it and extract gpt.bin... Nd use the same old December 2017 bootloader and rom that's in the op... Your phone will boot and you'll have OTA notification... Update your phone and you are done!! :D
[Moto G4 Plus Guides, News, & Discussion] suva12296:
Yep it worked , Thanks a lot
[Moto G4 Plus Guides, News, & Discussion] oldie60:
That worked perfectly. Instructions are flawless and detailed. Thank You Very Much!
[Moto G4 Plus Guides, News, & Discussion] jalbarran:
Can not flash anything!

Guys, my Moto G4 Plus XT1644 is bricked, I can see fastboot in the screen when I turn it on, but if I try to flash anything, I get only errors.

This is what I get when I try to flash partition gpt.bin:

NPJS25_93_14_15_Feb2018_GPT_bootloader # fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.072s

Please Help!
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, what happens when you try to boot? If you have fastboot, that suggests your bootloader is okay (as fastboot mode is enabled by the bootloader).
[Moto G4 Plus Guides, News, & Discussion] jalbarran:
More details in this post

My phone boots into fastboot mode only, and shows an error saying that it could not boot into normal mode, that is the only thing my phone does!

I wrote more details in this post a few weeks ago, this is the post: https://xdaforums.com/showpost.php?p=76045343&postcount=318

There are a lot more details about my phone bricked!

Thanks for the reply!
[Moto G4 Plus Guides, News, & Discussion] Nihar:
Stuck on waiting for firehose to get ready

Motorola qboot utility version 3.40

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

[ 0.001] Detecting device

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

[ 0.004] ...cpu.sn = 23377026 (0x164b482)

[ 0.004] Opening singleimage

[ 0.004] Loading package

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

[ 0.008] Loading programmer

[ 0.008] ...filename = programmer.mbn

[ 0.008] Sending programmer

[ 0.228] Handling things over to programmer

[ 0.228] Identifying CPU version

[ 0.229] Waiting for firehose to get ready

[ 60.334] Waiting for firehose to get ready

[120.445] ...MSM8952 unknown

[120.445] Determining target secure state

[120.447] Waiting for firehose to get ready

[180.545] ...secure = no

[180.554] Flashing GPT...

[180.555] Flashing partition:0 with gpt_main0.bin

[180.555] Initializing storage

[180.557] Waiting for firehose to get ready

[240.666] Configuring device...

[1494.755] Waiting for firehose to get ready

[1554.848] Waiting for firehose to get ready

[1614.944] Waiting for firehose to get ready

[1675.044] Waiting for firehose to get ready

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

[1735.152] Check qboot_log.txt for more details

[1735.152] Total time: 1735.153s

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

I'm having this issue when i am trying to get the g4 plus to boot.. Any help?? It doesn't boot into fastboot or anything.. just stuck on the blank screen with white led blinking. It happened when an update was installing and the phone switched off on its own when it had more than 80% charge.. Any help?
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
Read the OP Carefully Please
[Moto G4 Plus Guides, News, & Discussion] rvinyk:
its not working
[Moto G4 Plus Guides, News, & Discussion] echo92:
What is not working, can you describe what steps you are taking and where the procedure is not working?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Okay, thanks for that post. Here's a few things I noted:

1)Did you use the blankflash from this thread? Your screenshots point to it being used, with no baseband, a default serial number and showing OEM_locked. It seems that using a blankflash 'locks' your bootloader until you can flash a GPT/bootloader onto your device.

2)Are you able to find another PC to flash the stock ROM with? Ensure you're using the original Motorola cable or a high quality USB cable. You may wish to try the Feb 2018 GPT/bootloader too, see if that flashes https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M then try to flash the firmware.

3)However, those errors don't look good - failed to program partition table and a read datablock error do suggest a hardware fault (and a fairly major one, it may be flash memory failure as per your hypothesis 1.). However, I'd try to flash the stock ROM again and see how you go. If the flash doesn't work, despite fastboot/bootloader being active, that does point to either block corruption or flash memory failure. I'm hoping the flash does work and repairs what ever data corruption was encountered...
[Moto G4 Plus Guides, News, & Discussion] jalbarran:
I tried to use blankflash, but blankflash never connected, I guess because the phone was in fastboot mode already.

I tried to flash in a linux and windows computer, with the original motorola cable, and had no success, I also tried to use the Feb 2018 GPT, but it shows FAILED when trying to flash anything.

I still hope my phone is not hardware bricked, anything else I could try to make my phone work again?
[Moto G4 Plus Guides, News, & Discussion] rameshcvk:
my moto g4 plus unbricked thanks

Thanks for your support, Successfully Unbricked my Moto g4 plus. Thanks
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, without being able to flash anything, it's difficult to suggest anything. What does the FAILED message also report, is it still the 'read datablock failed' or 'failed to program partition table'?

I'm hoping others can contribute, as otherwise your device is likely needing a hardware service. It could be that the flash memory controller or portions of your flash memory have failed, which a service centre or repair shop might be best able to help you with.
[Moto G4 Plus Guides, News, & Discussion] Blueman1990:
any one try this method with February Security Patch ? Please tell me :)
[Moto G4 Plus Guides, News, & Discussion] echo92:
I would suggest re-flashing the Dec 2017 NPJS25.93-14-13 stock ROM or the NPJS25.93-14-15 Feb 2018 stock ROM. Your device is still reporting it has the last stock Marshmallow firmware on it, so attempts to flash OTA updates would still likely hard brick your device if it was working.

https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for the NPJS25.93-14-13 firmware or https://xdaforums.com/showpost.php?p=75947456&postcount=710 for the NPJS25.93-14-15 firmware (copy and paste the mega link)

I would recommend a full flash for stability - if the full flash doesn't work, you may have to begin considering a service repair. Ensure your ADB folder does not have any Marshmallow stock firmware (delete if necessary), only the latest stock firmware.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for that - just as a tip, for long logs like this, may be worth pasting it into a text file and uploading the text file, that way we don't miss the important info!

But yeah, your device does not look happy. From the flash log it looks like the flash went okay, but the getvar info suggests you still have Marshmallow on your device, despite having a up to date bootloader. From what you've described, it sounds like a hardware fault - possibly the flash memory is not writing or reading properly, and despite your bootloader loading, it appears to be unable to load the rest of your system. I do not know if this has anything to do with the Marshmallow flash. You mentioned your device soft bricked, can you describe what happened before the brick?

Also, when you're flashing the stock ROM, are you using a script or copy pasting each of the commands manually?

If it was a sudden brick and the flash doesn't work, you may have to submit your device to a service centre for repairs.
[Moto G4 Plus Guides, News, & Discussion] lcavrj:
Other method?

IMPORTANT NOTE:

If You've Updated your Device to the February Security Patch Then this method probably won't work because the GPT and boot-loader version is higher then the version included inside the BlankFlash

So Be Careful...!

I Update my Device to the February Security Patch, :(:( any other method?
[Moto G4 Plus Guides, News, & Discussion] echo92:
You could still give the blankflash a try if your device hard bricked, though you'd need the Feb 2018 GPT and bootloader.

If that doesn't work, you'd either have to wait for a newer blankflash or go to a service centre for a repair.
[Moto G4 Plus Guides, News, & Discussion] nachtfrost23:
It worked for me and I can't tell you how glad I am.

I struggeld with the "Waiting for device" error for a long time. The hints in the second post did't help.

Pushing the power button finally did the trick! I didn't notice any change on the phone, but my PC said something about a device getting configured (german: "Gerät wird eingerichtet"). The name was not Qualcom... but some alphanumeric combination that contained the letters QC...

This info might be worth adding to the second post.
[Moto G4 Plus Guides, News, & Discussion] galaxynova:
I was not able To install Resurrection Remix 8.1(error 255),I thought it might b due to old twrp

So I tried to update my twrp to 3.2.1.0 without computer watching a video on YouTube...now when I go in in Recovery it says "connect to computer to repair"...mobile is rebooting normally,but if I screw up anything now I won't be able to restore it through bootloader....plz help its URGENT (only problem is my twrp recovery not working,everything else is fine)..

P.S---when I was unable to flash 8.1 i flashed RR 7.1 and I think without rooting I flashed twrp.
[Moto G4 Plus Guides, News, & Discussion] echo92:
1) are you using the 64 bit TWRP to flash RR 8.1 as noted in the RR instructions? That error 255 is commonly associated with using the 32 bit TWRP to flash a 64 bit custom ROM. https://xdaforums.com/moto-g4-plus/development/recovery-twrp-3-2-1-unofficial-touch-t3722206 for the 64 bit TWRP.

2) are you still able to boot to the bootloader? If so, try reflashing the 64 bit TWRP via the bootloader (ensure you flash TWRP to the recovery partition) then reboot straight to TWRP. Then you should be able to flash RR 8.1 with the appropriate GApps.

3) you do not require root to flash TWRP, only an unlocked bootloader.
[Moto G4 Plus Guides, News, & Discussion] galaxynova:
Thanks for the reply

I might be having a 32bit twrp

I can boot in bootloader but when i enter recovery it shows ""

Start up Failed:-your device didn't start up successfully.Use software repair assistant on computer to repair your device,connect your device to the computer to get software repair assistant""

InShort i cannot flash anything from there...otherwise everything my phone is booting normally,all functions works except root cuz after installing rom i directly tried to update twrp to 3.2.1.0 with my mobile,due to which twrp is not working and i am not even able to root it
[Moto G4 Plus Guides, News, & Discussion] echo92:
Okay, what OS are you booting into?

Are you able to re-flash TWRP via fastboot, then boot into recovery? What commands are you using to flash your TWRP in fastboot (NOT using TWRP recovery to update, this needs to be a fresh flash of TWRP to the recovery partition)? What build of TWRP are you flashing?
[Moto G4 Plus Guides, News, & Discussion] galaxynova:
I was able to reflash TWRP with pc...and got everything fine now....Thanks for help ?
[Moto G4 Plus Guides, News, & Discussion] r1rony:
Does anyone know how to get into edl mode without bricking the phone?..... my phone bootloader is locked :)

Thanks in advance
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you really want to boot to edl mode, you could try 'adb reboot edl' (without quotes) from the ADB terminal whilst your device is booted and attached to your computer via USB. https://www.theandroidsoul.com/boot-edl-mode-qualcomm-android/ I'm guessing you can escape out of EDL mode by rebooting?

If your device is running though, why do you want EDL mode?
[Moto G4 Plus Guides, News, & Discussion] r1rony:
Coz no matter what ever I try I am unable to unlock bootloader of moto g4 plus xt1643 which has null Imei number so the unlock key doesn't work anymore shows key validation(verification) error

So hav to unlock bootloader somehow to escape form stock
[Moto G4 Plus Guides, News, & Discussion] makinox:
Hello i followed all the steps but at the end in the bootloader when ai want to start or enter to recovery show me 'No bootimage found, Skip to fastboot'.

also logs said always 'failure, permission denied'.

what can i do?

My model is xt1621 moto g4.

thanks for your time
[Moto G4 Plus Guides, News, & Discussion] echo92:
Did you flash the stock ROM in the guide or the latest stock ROMs as mentioned in this thread https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ?

If so, did you verify that each file was written to your device and reported [okay] ? That error suggests that no kernel was flashed or the kernel partition cannot be accessed.

Is your bootloader locked (oem_locked status in the bootloader) or flashing_unlocked?
[Moto G4 Plus Guides, News, & Discussion] makinox:
Yes i did, i downloaded the first option and all okay
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, that's odd, if the kernel flashed okay, then that message shouldn't appear unless there's an issue with the hardware. By first option, are you referring to the December 2017 NPJS25.93-14-13 stock ROM that you flashed?

Can you post your get var info please?

1) boot your device to the bootloader. Attach your device to your computer.

2) open ADB on your computer. Type 'fastboot getvar all' without quotes into the ADB terminal. Press enter.

3) please copy the output and paste it in a text file and upload the file here or paste the output in a reply post. You may wish to remove your IMEI but the output should tell us what state your device is in.
[Moto G4 Plus Guides, News, & Discussion] makinox:
Well i had the stock factory version, so i wanted to update and thas it my cellphone dies.

So i followed the steps and here i am.

----- log ----

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) version: 0.5

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

(bootloader) product: athene_13mp

(bootloader) board: athene_13mp

(bootloader) secure: yes

(bootloader) hwrev: P2A

(bootloader) radio: 5

(bootloader) storage-type: emmc

(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4

(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F

(bootloader) cpu: MSM8952

(bootloader) serialno: 4f350574

(bootloader) cid: 0x0032

(bootloader) channelid: 0x18

(bootloader) uid: 3983680100000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 536870912

(bootloader) reason: Failed to initialize partition table

(bootloader) imei: 000000000000000

(bootloader) meid:

(bootloader) date: 01-01-1970

(bootloader) sku: 000000000000000

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) ro.build.version.full:

(bootloader) ro.build.version.qcom:

(bootloader) version-baseband:

(bootloader) kernel.version:

(bootloader) sbl1.git: sbl1.git

(bootloader) rpm.git: rpm.git

(bootloader) tz.git: tz.git

(bootloader) hyp.git: hyp.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d

(bootloader) qe:

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

(bootloader) ro.carrier:

all: listed above

finished. total time: 0.125s

----- log -----

Also fastboot is in red says ' AP Fastboot Flash Mode (Secure)'
[Moto G4 Plus Guides, News, & Discussion] echo92:
I'm confused, by factory ROM, which one are you referring to? If you mean a marshmallow ROM, then if you flash that onto a device formally updated to stock Nougat, attempting to use OTA updates will hard brick your device. You cannot flash old stock firmware and then safely use OTA updates in most cases.

From the get var log, it looks like the flash failed to work at all, you've got no partition table, a default serial number, no kernel, no baseband. That's why your device didn't work. Did the flash of just the GPT and bootloaders work?

please try to flash the latest stock firmware for your device, I do not think old firmware will flash onto your device especially as your bootloader is locked for the time being. Delete any old Nougat or marshmallow firmware files from your ADB folder. If you need NPJS25.93-14-15 (Feb 2018) or NPJS25.93-14-18 (April 2018) firmware links are here https://xdaforums.com/showpost.php?p=76337066&postcount=769 https://xdaforums.com/showpost.php?p=76416801&postcount=785
[Moto G4 Plus Guides, News, & Discussion] debashisbiswas737:
always showing "waiting for any device " very thankful to all of you for successful blank flashing my hard bricked moto g4 plus .. but when I am trying to flash with command promt by adb always "waiting for any device " is showing .... how to solve this problem ??? pls. help me.
[Moto G4 Plus Guides, News, & Discussion] Bluemoon:
Okay.. firstly if you have Motorola drivers installed, uninstall it and then reinstall.

Then disconnect your device and connect it again and proceed.
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
is your phone is detected in fast-boot mode? you can see the connected devices in the device manager by simply searching 'device manager' in start menu.
[Moto G4 Plus Guides, News, & Discussion] nidhinkk20:
thanks bro?

U r my new god.lots of thanks man .?
[Moto G4 Plus Guides, News, & Discussion] debashisbiswas737:
sir pls. check this screen shot ..

sir pls. check this screen shot ..
[Moto G4 Plus Guides, News, & Discussion] debashisbiswas737:
Thank you very much . It is successfully done .. I am just speechless .... you are our true friends for ever .... God bless you all of my friends !!! :)
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, what drivers do you have installed (do you have minimal ADB 1.4.2 or do you also have Motorola's drivers) and as you're on Windows 10, have you disabled driver signature enforcement ( only if you're running a PC with an UEFI motherboard if I recall)?
[Moto G4 Plus Guides, News, & Discussion] ad_anu143:
successfully unbricked. Got to the bootloader and fastboot.Flashed the firmware link you provided.Mine is XT1643 indian variant..after flashing everything worked and thanks alot for that,,but it shows US baseband and only one sim didnt check fingerprint.It's a wrong firmware flash i think but is there anything i can do?/i have tried flashing every firmware from december to june one but same

custom roms but same

Anything that can be done???:rolleyes:
[Moto G4 Plus Guides, News, & Discussion] debashisbiswas737:
using minimal ADB on win 10 but the problem was I forgot to install Motorola drivers .... thank u one time more for giving me light regarding this complex situation my friend !! You great ... that's all !!!

we all are really indebted to you ... forever ... thank u again
[Moto G4 Plus Guides, News, & Discussion] kkr1999:
Worked like charm!!

THANK YOU SO MUCH!!!!!

had lost all hope, was about to go to the service center but this method solved everything. :good:
[Moto G4 Plus Guides, News, & Discussion] VivekBhagat:
Thank you brother for guide i was thinking selling spare part my device but this saved my device :laugh:
[Moto G4 Plus Guides, News, & Discussion] iampsycho:
Tested and Working on XT1643

thanks this method is working on XT1643
[Moto G4 Plus Guides, News, & Discussion] marcelofilgueira:
good job [MENTION=7843165]siddhesh9146[/MENTION] , you're helping so many with this post :)
[Moto G4 Plus Guides, News, & Discussion] Outfield303:
But special thanks to you for providing the Blankflash file. without that our devices were dead:angel:

thanks again:good:
[Moto G4 Plus Guides, News, & Discussion] Janderson Santos:
It worked, thank you. :good: