[Help Thread][Moto G4 Plus] (2016) Ask Any Question, Noob Friendly

[echo92]

Failed (remote failure) OEM can't be unlocked

Okay - what commands are you using to get you that error? Have you changed the USB cable, USB port, perhaps the computer as well?

By OEM can't be unlocked, do you mean you've tried your unlock key and you can't unlock your bootloader?

Can you also verify you're flashing the latest April 2018 NPJS25.93-14-18 stock ROM? Do not flash the NPJ25.93-14 stock ROM.

 

[hemanta12345]

Xda universal command

---------- Post added at 05:38 PM ---------- Previous post was at 05:38 PM ----------

Like gpt.bin

---------- Post added at 05:41 PM ---------- Previous post was at 05:38 PM ----------

The xda thread command I don't know how OEM got locked perhaps OEM.bat file locked the bootloader

---------- Post added at 05:41 PM ---------- Previous post was at 05:41 PM ----------

Now it is showing bootloader is modified

 

[hemanta12345]

This is what the screen looks like

 

[hemanta12345]

The commands are

 

[echo92]

Xda universal command

---------- Post added at 05:38 PM ---------- Previous post was at 05:38 PM ----------

Like gpt.bin

---------- Post added at 05:41 PM ---------- Previous post was at 05:38 PM ----------

The xda thread command I don't know how OEM got locked perhaps OEM.bat file locked the bootloader

---------- Post added at 05:41 PM ---------- Previous post was at 05:41 PM ----------

Now it is showing bootloader is modified

Knowing what flashing commands is useful to diagnose - saying universal XDA commands doesn't mean much as different devices may use different flashing commands. Indeed, using 'universal commands' can brick your device if you're using them without understanding why and if they're suitable for your device.

If you used the blankflash to unbrick your device, it'll default to a locked bootloader until you flash a working GPT and bootloader. Looking at the serial number and the product variant it looks like you're still running the blankflash bootloader. What flashing commands are you using for them? Also, what GPT and bootloader files do you have on your computer?

Also, do you have mfastboot or fastboot on your computer? Those errors look like you're attempting to use mfastboot, despite not having mfastboot on your computer. Do you have minimal ADB/fastboot or the Google fastboot on your computer?

 

[hemanta12345]

Yes I've mfastboot on my pc. Please provide me a link to working gpt and bootloader with exact commands

---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------

And yes those commands are suitable for my device

---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------

I'll do as you say asap

 

[____Mdd]

The commands are

It says mfastboot.exe is not working/found in that directory.

Make sure "mfastboot.exe" is there in folder..

 

[hemanta12345]

Yes it is there

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

Actually I have mfastboot and fastboot both in my pc

---------- Post added at 06:50 PM ---------- Previous post was at 06:38 PM ----------

How to fully re-flash or revert to a completely clean stock firmware build - no TWRP, no root etc.

 

[____Mdd]

Yes it is there

That's powershell !

AFAIK Powershell and Command Prompt are different

You need to open CMD, Google it..

EDIT:
(I know nothing about updated Windows) but in few post, they got successfully flashed with powershell..
You can try with different PC..

 

[strongst]

That's powershell !

AFAIK Powershell and Command Prompt are different

You need to open CMD, Google it..

EDIT:
(I know nothing about updated Windows) but in few post, they got successfully flashed with powershell..
You can try with different PC..

PowerShell works with same commands as fastboot, have a look at my Screenshot

 

[hemanta12345]

I used gpt.bin command and bootloader command

 

[echo92]

I used gpt.bin command and bootloader command

That screenshot indicates you're using an old GPT and bootloader, from the preflash validation errors. Without flashing a working GPT, you may have partition errors as your device does not know the layout of your storage.

Try using either the NPJS25.93-14-18 April 2018 GPT/bootloader/firmware or try the GPT/bootloader from here: https://drive.google.com/open?id=13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI

Also, please try to edit your posts rather than replying - it keeps the thread cleaner and easier to track what's happened. I have seen your PMs and will try to reply to them now.

 

[rajrocksdeworld]

My XT1644 won't boot up unless plugged in when it's not I Just get the moto screen and it turns off

flash a new ROM

 

[Hari Haran]

Is there a way to get slow mo on custom nougat roms?

?? Any hope?

 

[____Mdd]

?? Any hope?

Tried camera mods ?

 

[Hari Haran]

Tried camera mods ?

Link? Nope. I don't know what's camera mods

 

[strongst]

Link? Nope. I don't know what's camera mods

There are several camera mods in the mods section https://forum.xda-developers.com/moto-g4-plus/themes

Just take some time

 

[Hari Haran]

There are several camera mods in the mods section https://forum.xda-developers.com/moto-g4-plus/themes

Just take some time

CAN I enable camera 2 api on Lineage 14.1

 

[babji1994]

which is the best custom rom that gives better battery life and performance more than stock ...? Suggest pls

 

[patate29284]

Hi. I have a weird issue that I have not found anywhere else, so I figured I could get help here...
I was using RR N since its beginnings and wanted to go back to stock, so I flashed NPJS25.93 through fastboot and everything was just fine. However, an update notification kept popping up but I wasn't able to update the device (when trying to update, after download finished it restarted, but process would fail). Given the annoyance of the notification and pop up screen, I decided to go back to RR N... I flashed TWRP3.2.1 64 bits (because I was waiting for a more stable 64 bits Oreo RR) and tried to flash RR N for the meantime... For my surprise, after clearing system, dalvik, data and cache partitions, flashing process wouldn't finish... the progress bar would keep the animation, but the actual progress would stop at about 6mm of the end of the bar (I estimate 90-95 %). I left the device for lie an hour but nothing... So I reflashed stock N through fastboot and tried all over again... The same thing happened three times...
After failing to flash RR N I just decided to stay on stock N, but wanted root, so I reflashed TWRP and flashed ElementalX kernel to later flash super su... However, to my surprise, ever since flashing TWRP, whenever I reboot my device, it boots into recovery, and in order to reboot into the rom, I must reboot into bootloader first and then select either QCOM or BP TOOLS (I know bp tools is for fixing baseband, but don't know what qcom does). I have now flashed latest 64 bits RR O (15/09/18) cause I still can't flash RR N, but the rebooting into recovery persists...

Any ideas on how I could fix this?

I had flashed first 32 bits RR O but I tried to flashed magisk after the first boot and due to the rebooting into recovery issue, magisk never became functional in the rom (I would open the app and it would remain in the mask screen until a message of "Magisk stopped working" showed up). Something similar happened with SuperSu, but this time, I would never get it installed.