yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] santiagog242:
Hello

I sent my device for warranty because I have ghost touches. I received my phone and they brought it back without any change, I'm still facing ghost touches. BTW thats not the problem.

Previously I unlocked the bootloader and rooted my device, before to send the device for warranty I locked the bootloader again and sent it like it was new.

Now I'm trying to unlock the bootloader but it is impossible to do. When I try to get the fastboot oem unlock data, I put the code on the motorola website and the answer is "Your devices does not qualify for bootloader unlocking".

I tried too to put the old code that Motorola sent me to my email, I put the commands on adb window but also I get an error message "Code validation failure with status 7".

If someone have faced this issue would be great to know how to solve it.

Thanks.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, can you confirm that OEM unlocking is toggled in Settings>Developer Options? It should be toggled, as you've appear to have no issue getting the unlock data.

Can we see your getvar all data please?

1)Reboot your device to the bootloader.

2)Connect your device to your computer via USB.

3)In the ADB terminal, type 'fastboot getvar all' without quotes. Press Enter.

4)Please post/paste the output here, you may wish to remove your IMEI.

I'm wondering if your motherboard got replaced.

You may have to consider posting on the official Motorola forums to request help with unlocking your bootloader: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809 This Motorola thread should assist you in unlocking your bootloader - please follow the instructions on the first post of that thread.
[Moto G4 Plus Guides, News, & Discussion] dsbalu:
My build number is M8952_70025.20.03.52R and device model is xt1643

I am running on soak test baseband version can I flash only firmware to update my baseband?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Easiest and safest way to update would be to flash newer stock firmware, yes. If you wish to only update your baseband, you could try the following fastboot commands.

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

Ensure you have the latest firmware downloaded (which for XT1643, NPJS25.93-14-13 is the latest), extracted and copied to your ADB folder. If you only update your baseband, bear in mind you may have to flash the full stock ROM if you have issues.
[Moto G4 Plus Guides, News, & Discussion] SHUBHr14:
can i install this firmware on unrooted phone
[Moto G4 Plus Guides, News, & Discussion] strongst:
Yes
[Moto G4 Plus Guides, News, & Discussion] SHUBHr14:
thnks
[Moto G4 Plus Guides, News, & Discussion] Heyner_Gomez:
Is there a problem if I go back to the September patch ?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Provided your bootloader is still unlocked and you don't mind being reminded about the December 2017 OTA update, I don't see any problem with going back to the September 2017 firmware. Bear in mind your system will be the September 2017 firmware, but your bootloader would likely be from the December 2017 firmware. However, in this case, as the next update in sequence should be the Dec 2017 OTA update (provided your carrier isn't issuing different updates), then you'd be applying the same patches to your bootloader. Thus, you should experience no hard bricking if you choose to use OTA updates.
[Moto G4 Plus Guides, News, & Discussion] Heyner_Gomez:
Thanks, what happens is that I lost an imei and then I can not find the stock of my operator, what I can think of is to go back to the September patch and update by December and recover the imei.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ouch, the infamous lost IMEI problem - I honestly still do not fully understand why the IMEI gets lost, just a few of the causes.

In that case, you could give it a try, see if the OTA update can do anything.

As a general note (and to anyone else reading this), this downgrade may be okay to use OTA updates on as you're downgrading to the Sept 2017 stock firmware which directly precedes this Dec 2017 stock ROM. Most of the hard bricks I've noted involved downgrading more than that (e.g. downgrading from the Dec 2017 stock ROM to June 2017 or Dec 2016 Nougat or Marshmallow) and then attempting to use OTA updates.
[Moto G4 Plus Guides, News, & Discussion] santiagog242:
OEM unlocking is toggled on.

In this moment is impossible to get the getvar because I don't have a pic near me, I've known that the important thing is the CID, I've done this few days ago and this number is 0x0032, that means that the device is able to unlock.

I don't think my motherboard got replaced because they said that no changes were made to the phone, just a system parameters update, I don't know what that means, but anything they did locked my bootloader permanently.

I'll try to post on Motorola forum btw, thanks.
[Moto G4 Plus Guides, News, & Discussion] santiagog242:
Look at my getvar all

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

(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.07

(bootloader) product: athene_16mp

(bootloader) board: athene_16mp

(bootloader) secure: yes

(bootloader) hwrev: P2A

(bootloader) radio: 5

(bootloader) storage-type: emmc

(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007

(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F

(bootloader) cpu: MSM8952

(bootloader) serialno: ZY223VJWD2

(bootloader) cid: 0x0032

(bootloader) channelid: 0x1b

(bootloader) uid: F18B690200000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 536870912

(bootloader) reason: Volume down key pressed

(bootloader) imei:

(bootloader) meid:

(bootloader) date: 01-13-2017

(bootloader) sku: XT1641

(bootloader) battid: SNN5970A

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time: "Tue Mar 7 0:28:20 UTC 2017"

(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ

(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys

(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta

(bootloader) ro.build.version.full[1]: il.en.US

(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0

(bootloader) version-baseband[0]: M8952_70030.25.03.62.01R ATHENE_LATAM_

(bootloader) version-baseband[1]: DSDS_CUST

(bootloader) kernel.version[0]: Linux version 3.10.84-g498cc0c (hudsoncm

(bootloader) kernel.version[1]: [MENTION=387459]ilc[/MENTION]lbld34) (gcc version 4.8 (GCC) ) #1

(bootloader) kernel.version[2]: SMP PREEMPT Thu Nov 23 09:34:10 CST 2017

(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343

(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead

(bootloader) tz.git: git=69dd24b-dirty

(bootloader) hyp.git: git=69dd24b-dirty

(bootloader) keymaster.git: git=69dd24b-dirty

(bootloader) cmnlib.git: git=69dd24b-dirty

(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba

(bootloader) qe: qe 0/0

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

(bootloader) ro.carrier: retla

all: listed above

finished. total time: 0.297s
[Moto G4 Plus Guides, News, & Discussion] echo92:
Thanks for that, I don't see anything out of the ordinary with that getvar data, apart from the channelid of 0x1B, which I'm not sure what that means. I would therefore suggest posting on the Motorola forum thread I mentioned, as we don't fully know what the service centre did (a 'system parameters update' could mean a firmware update or something else).

Hopefully they can help you - please follow the instructions there, which include posting your getvar including the IMEI and the results of the get unlock code command.
[Moto G4 Plus Guides, News, & Discussion] aman19991234:
I used the oemlock.bat and here is text file for my getvar data
[Moto G4 Plus Guides, News, & Discussion] AmolAmrit:
A forward from my friend [MENTION=8992511]MihirVaja1111[/MENTION] Due to some policy thing, he can't post the reply here, so I am forwarding his message.

This thing occurred to my brother's phone. I flashed a marshmallow rom then updated it to nougat. It got bricked hard, hard bricked seriously. Then it took hours to blankflash. Then I tried everything, ran all commands, partition gpt.bin, bootloader img. oem lock, everything failed.

In the end I got a December patch rom from here.

Opened cmd where rom and fastboot files are kept.

First ran these commands

fastboot devices

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

and then copied all the commands given in that link. This saved that phone, thanks to xda one and all.
[Moto G4 Plus Guides, News, & Discussion] echo92:
1)When using the flashing script, did you confirm each step completed with [OKAY]? Can we see the output from the flashing please?

2)Looking at your getvar info, I'm not convinced the flash and lock went okay - though your bootloader is B1:07 and your system is NPJS25.93-14-13, your baseband is still a Marshmallow baseband (ending in .48R, whereas the correct baseband should be ending in .62.01R)

I would suggest you take some time and flash the OEM locking script manually.

a)Ensure you have OEM unlocking enabled in Settings>Developer Options. Verify that you have the NPJS25.93-14-13 stock ROM extracted/copied to your ADB folder.

b)Reboot your device to the bootloader, connect to your computer via USB (either a high quality USB data cable or the original Motorola cable).

c)Open an ADB terminal on your computer. Verify communication with your device by typing 'fastboot devices' without the quotes - you should see your device's serial appear (ZY223LH8N9).

d)If you got the response in c), then proceed to flash the stock ROM manually.

d_i)Copy the first command in sequence from the script/list of commands. In your case, this would be 'fastboot oem lock begin' without quotes.

d_ii)Paste the command into your ADB terminal. Press Enter and wait for [OKAY] or a prompt - with the first command, it'll request you to re-enter fastboot oem lock begin to confirm you wish to lock your bootloader.

d_iii)If d_ii) completes with a prompt or [OKAY], proceed to copying the next command in sequence individually.

Repeat with d_ii) to d_iii) until you get to the end of the commands list. Because you're flashing each command individually, this will take time as well as concentration. But this method will also let you track if the commands are flashing okay.

Alternatively, if you wish to just check the output, you can add 'pause' (without quotes') to near the end of the flashing script, before the 'fastboot reboot' command, which can let you check the output and verify everything's flashing correctly.
[Moto G4 Plus Guides, News, & Discussion] AniLeo:
Hi..Sorry For bothering you...I'm on RR Oreo 8.1 on 1643 Indian Variant ..I want to update the Baseband version..My current Baseband version is M8592_70025.20.03.52R

I installed the soak test version of Nougat...and then rooted the phone...and have been on custom ROM since then...

Since afterwards Moto Released the Nougat...and some further updates..I need to update the Baseband if changed..

Am I Good to go for this stock ROM..?

And how could I avoid bricking the device...?

I want to switch to RR Oreo Again...

Do I need to root again ?

Thanks..in adv..
[Moto G4 Plus Guides, News, & Discussion] biel.paes:
new February security patch ?!
[Moto G4 Plus Guides, News, & Discussion] echo92:
This stock ROM should work in updating your baseband. You could flash the entire stock ROM, but then you'd have to reinstall the 64 bit TWRP/RR 6.0 and it would erase your data too. You could try just flashing the baseband/modem:

1)Ensure you have this stock ROM downloaded, extracted and copied to your ADB folder. Also, ensure you have a TWRP backup of your RR installation.

2)Boot your device to fastboot and connect to your computer via USB.

3)Flash via fastboot with the following commands:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot

That should update just your modem, without you needing to re-install RR. Bear in mind you may have to flash the stock ROM if you encounter instabilities.

As an aside, you do not need root on the stock ROM to flash custom ROMs, you just require the correct build of TWRP (either 32 bit or the 64 bit depending on the custom ROMs you're flashing).

As for bricking, you can avoid bricks by only flashing stock firmware that is as new or newer than the firmware that matches your bootloader. Thus, if you flash NPJS25.93-14-13, you have to only use NPJS25.93-14-13 or newer stock firmware. As you were previously on NPJ25.75-2 (Nov 2016 soak test, so really old), you could flash any of the Nougat firmwares, but as soon as you've done so, you cannot flash any older stock firmware and safely take OTA updates. If you do flash older stock firmware than the one matching your bootloader, generally do not use OTA updates.

As far as I remember:

Bootloader version: B1:03 - Dec 2016 security patch (NPJ25.93-14)

B1:05 - March 2017 security patch (NPJS25.93-14-4)

B1:06 - June/Sept 2017 security patch (NPJS25.93-14-8/NPJS25.93-14-10 or NPJ25.93-14.5/NPJ25.93-14.7)

B1:07 - Dec 2017/Feb 2018 security patch (NPJS25.93-14-13/NPJS25.93-14-15 or NPJ25.93-14.7-3)

As long as you flash firmware with the matching bootloader version or newer as on your device (you cannot generally downgrade bootloaders), you should be okay.
[Moto G4 Plus Guides, News, & Discussion] minhajul6322:
how can i unroot can anyone help please...
[Moto G4 Plus Guides, News, & Discussion] strongst:
Depending on your root method there are flashable zips. How did you root? Magisk or supersu?
[Moto G4 Plus Guides, News, & Discussion] minhajul6322:
supersu
[Moto G4 Plus Guides, News, & Discussion] strongst:
You can use "unSU script" by osm0sis or just flash system image(rom again). The script is the easiest way ;)
[Moto G4 Plus Guides, News, & Discussion] AniLeo:
Thanks A Lot..!!

It Worked..!!
[Moto G4 Plus Guides, News, & Discussion] themanyax:
Is this update also will flash the recovery? I just wanted to go back fully stock.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Flashing any stock ROM in its entirety will flash stock recovery - if you're coming from the custom ROMs you will also have to wipe your data as well, so ensure you back up.

Be careful to only flash the same stock firmware or newer than your bootloader version, else you may hard brick. As far as I remember:

Bootloader version: B1:03 - Dec 2016 security patch (NPJ25.93-14 stock firmware)

B1:05 - March 2017 security patch (NPJS25.93-14-4 firmware)

B1:06 - June/Sept 2017 security patch (NPJS25.93-14-8/NPJS25.93-14-10 or NPJ25.93-14.5/NPJ25.93-14.7)

B1:07 - Dec 2017/Feb 2018 security patch (NPJS25.93-14-13/NPJS25.93-14-15 or NPJ25.93-14.7-3)

You can see your bootloader version on the fastboot/bootloader screen on your device.

If you're not sure, then you can flash this NPJS25.93-14-13 stock firmware (Dec 2017 security patch), but please double check it's the correct build for your device/region.
[Moto G4 Plus Guides, News, & Discussion] CMKdaGreatest:
[MENTION=6324159]rajatgupta1998[/MENTION]

Will there be a new firmware update in this thread once the Feb 2018 patch is or leased in India?
[Moto G4 Plus Guides, News, & Discussion] rajatgupta1998:
The thread will be updated as soon as the firmware is available. :good:
[Moto G4 Plus Guides, News, & Discussion] cldio:
link, typo

rajatgupta1998,

First of all, thanks for this life-saving thread.

Second: a guy @ Moto G4/G4 Plus Telegram group sent this link claiming it's a copy of stock image with Feb 18 update:

<https://mega.nz/#!lbw2CKbB!QhOg4JRrKQjAvp42byIm0iz_JJz1QOMbSDfnftZX54I>

The name (ATHENE_NPJS25.93-14-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml .zip) makes sense, but I haven't tried it yet.
[Moto G4 Plus Guides, News, & Discussion] Romano2K:
Hello there!

I'm selling my Moto G4 XT1622.

I've been able to restore the firmware, the kernel, the bootloader and everything else to stock, then relock the bootloader, following this tutorial. Thank you!

But when I power on the device, it goes to the bootloader screen.

I want it to boot Android. How should I do, please?

________

Found the answer:

This command makes the phone boot straight to Android:

fastboot oem fb_mode_clear

Maybe it should be added to the first post?
[Moto G4 Plus Guides, News, & Discussion] niyas90:
Anyone tested ?
[Moto G4 Plus Guides, News, & Discussion] mexifunk:
Yes, it works!
[Moto G4 Plus Guides, News, & Discussion] Heyner_Gomez:
Work fine XT1643 !
[Moto G4 Plus Guides, News, & Discussion] echo92:
Usually, that fb_mode_clear command is only needed if you set fastboot mode with fastboot oem fb_mode_set, else I don't think the command is needed.

The pair of fastboot commands is: fastboot oem fb_mode_set (sets fastboot mode - usually used at the start of the flash), and fastboot oem fb_mode_clear (clears fastboot mode, lets you boot, used at the end of the flash).
[Moto G4 Plus Guides, News, & Discussion] cldio:
I just tested on my XT1640, and the image worked perfectly! Signed image, allowing bootloader relocking.

As a reference, I calculated the file hashes.

Name: ATHENE_NPJS25.93-14-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Android Security Patch Level: Feb 1st, 2018.

Link: <https://mega.nz/#!lbw2CKbB!QhOg4JRrKQjAvp42byIm0iz_JJz1QOMbSDfnftZX54I>

MD5: B11E70BE627F2B7B262DAEEF81DD5DFD

SHA-1: 7DF392A277FDF8ED71E3CA6DD1B30FB14BBAC96A

SHA256: B2985DB688B4DCD61F4232EB8C8D9EEC0B8772FB82BABEABF405E30C46322F54
[Moto G4 Plus Guides, News, & Discussion] thorin0815:
No problems with XT1622 Reteu.

Edit: Magisk 16.0 seems to not pass SafetyNet (ctsProfile:false) anymore.

Edit2: Universal SafetyNet Fix solves the problem.
[Moto G4 Plus Guides, News, & Discussion] rajatgupta1998:
Keep in mind that I (and the community) won't be providing support to people who're flashing things available on the internet without any genuine source.

Older firmwares have been taken off motorola's RSD Cloud.

My testers' group will verify the firmware and then only I will update this thread and the OP.
[Moto G4 Plus Guides, News, & Discussion] pastorbob62:
And we appreciate your work very much. But I too have been using the mentioned February 18 update on my XT1625 for two weeks now with no problems or issues whatsoever. As with any custom or stock ROM update, there is always risk involved in flashing, but that is why I always buy unlocked phones, to be able to stay up to date without waiting on the snail pace at which most manufacturers (and sometimes developers) move (present company excepted). Looking forward to seeing this thread updated when the time comes. :good:;)
[Moto G4 Plus Guides, News, & Discussion] wfantasma:
Installed and working fine in my xt1621 (retmx)

Flashed successfully with the no data loss method and then rooted with phh's SuperUser
[Moto G4 Plus Guides, News, & Discussion] kitoide:
Help me

I have the following error when trying to block the boatloader

C: \ Users \ Test \ Desktop \ a> fastboot oem lock

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

...

(bootloader) Still require signed boot.img

OKAY [0.031s]

finished. total time: 0.031s
[Moto G4 Plus Guides, News, & Discussion] echo92:
What device are you using and which firmware are you trying to re-lock your device with?
[Moto G4 Plus Guides, News, & Discussion] gutosilva:
Can I downgrade NPJS25.93-14-15 to NPJS25.93-14-13 without problems?
[Moto G4 Plus Guides, News, & Discussion] John256145:
Are there any drawbacks to not flashing gpt.bin and bootloader.img? I assume it would be safer to avoid a brick by not flashing those two files.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, I don't see a problem except you may be continuously prompted to find the February 2018 OTA update (if it's been released in your region/software channel). What reason are you needing to downgrade? Bear in mind that you cannot downgrade your bootloader and you will need an unlocked bootloader to downgrade your firmware.

---------- Post added at 09:41 PM ---------- Previous post was at 09:33 PM ----------

I would generally recommend flashing GPT and bootloader with a stock firmware provided it's the same build or newer than the most recent stock firmware on your device. This should mean your device is on the same firmware patch level and so there's a reduced chance of bricks if you choose to use OTA updates.

Bricks generally occur if you flash an old stock firmware and then try to use OTA updates (as you cannot downgrade bootloaders, that leaves your device with a newer bootloader but older system firmware, the OTA would overwrite your newer bootloader and brick your device). In that case, you may choose not to flash GPT and bootloaders, but do not use OTA updates if you downgrade. If you want to update, only use the newest stock ROM for your device.
[Moto G4 Plus Guides, News, & Discussion] John256145:
I actually tried to perform an OTA update to Nougat yesterday but it kept failing, probably because there's something in my /system that is modified. I even tried FlashFire.

Because of this, I'm not going to try to use OTA updates again since they never worked for me. I think I'll go with these commands on my XT1644. Thanks for the info though, I had trouble finding anything about not flashing those two files.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Yeah, OTA updates will not flash onto devices with modified stock firmware (regardless of if it's root or simply allowing read write access to your system partition). You need a clean system, recovery, OEM, logo, and boot (kernel) partition to take OTA updates.

Easiest way to get your system to a OTA friendly stage is to flash those firmware files you linked, preferably from the same stock firmware as your device bootloader. That way, you shouldn't have to worry about your bootloader as the firmware and your bootloader should match.

Though those instructions do not require you to wipe your device, I would still strongly recommend backing up your device, or at least files and data important to you, before proceeding to flash.
[Moto G4 Plus Guides, News, & Discussion] gutosilva:
I'm considering install LineageOS on my device (actually with feb/2018 security patch), so if I need back to stock and lock bootloader I could install the January version....
[Moto G4 Plus Guides, News, & Discussion] John256145:
Alright so I flashed the rom with the aforementioned commands, and it worked! I'm now on Nougat without losing any data! Thanks a ton! :good:

Update: I lost all my text messages, but easily got them back thanks to a backup I made prior to flashing.
[Moto G4 Plus Guides, News, & Discussion] tcoffin014:
After flashing this ROM, how do we get the latest Feb security patch?
[Moto G4 Plus Guides, News, & Discussion] CMKdaGreatest:
[MENTION=6324159]rajatgupta1998[/MENTION] I think the Feb security patch update has come out in India now. Will the firmware be out soon?
[Moto G4 Plus Guides, News, & Discussion] eta82:
New firmware avalible in xt1622 eu

NPJS25.93-14-15

Wysłane z mojego Moto G (4) przy użyciu Tapatalka
[Moto G4 Plus Guides, News, & Discussion] minhajul6322:
i am getting February 1 security update...when will we get it here???
[Moto G4 Plus Guides, News, & Discussion] hernaner28:
I am not getting it after going back to main post stock rom.
[Moto G4 Plus Guides, News, & Discussion] wfantasma:
Not enough testing yet to verify if that firmware ATHENE_NPJS25.93-14-15_cid50 published in the mega link Is a genuine Motorola firmware?

I've tested it for two weeks now with no issues (xt1621 retmx)