yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ah, I've been on stock, rooted with magisk, for about a couple of months now, just dipping in and out of the custom ROM scene :)

I mainly switched to stock to test out the camera processing and the changes the March and June patches brought, and just stayed on stock. For me, I think the later patches seem to have improved performance and battery life. Not to Invicta levels but for my usage I seem to be getting a battery to last 20-24 hours on standby and usage, with 4-4hr30 SoT (with just being on LTE/4G all day, and with weak-ish signal) - of course, your experience may vary. I'm not sure about the later builds of Invicta, I noted on custom ROMs my mobile signal gauge would randomly drop to zero, whereas on stock it seems to hold.
[Moto G4 Plus Guides, News, & Discussion] Danny1976:
Thanks for the info. I may give it a try. Specially, that I read that it may get the 7.1 update, if I read correctly.

Two more questions. Did you experience reboots while on Invicta? On the Invicta 2.0 builds not so much, but on the 4.0 builds, I have experience more reboots while using different apps.

To go from Invicta to stock, flash stock nougat and keep updating until 14-8? I think the full stock nougat firmware goes back 14. Do magisk systemless root so I can get the OTAs?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Oh, that'd be nice if we got the 7.1.1 update... Knowing our luck, we might get it as Android O is released :P

Hmm, I did experience 1 random reboot with Invicta, but that was on the 1.0 build of Invicta. With the 2.0 builds, I didn't recall any issues and I've not tested the 3.x/4.x builds. Are these reboots with the M or N kernel and sensorhubs and are any of them reproducible?

I'm not sure if the NPJS25.93-14-8 update is out for Amazon devices yet, so you may wish to wait for that update to come out. We do have the Amazon fastboot firmware for the March update though https://www.androidfilehost.com/?fid=889764386195899718 but yep, the procedure you outlined should work. Be careful on NPJS25.93-14-8, as downgrading from that June 2017 stock build has created a lot of bricks, if you choose to revert to a custom ROM, try to make a TWRP backup of your stock ROM before reverting. That way, you could change back to your stock ROM without having to worry about fastboot flashing.

Magisk does appear to be systemless, and thus if you uninstall it and flash a stock kernel and recovery (and stock logo.bin), then in theory the OTA update should be okay with it. In practice, your experience may vary (but if the OTA errors out, there are workarounds that may mean your data is retained and you can still update).
[Moto G4 Plus Guides, News, & Discussion] Danny1976:
Since version 4, Invicta is on the N Kernel. Since I have the bootloader unlock.... Could I flash the retail stock version on the Amazon XT1625?

Edit: I installed a retail version from rootjunkie, but as soon as it installs the OTA update it reverts back to amazon ads. The Software channel remains AMZ and all updates will be amazon. I would assume if I have the bootloader unlock I could install anything on it.
[Moto G4 Plus Guides, News, & Discussion] autoradio78:
Hi guys...I've been away from the forum for so long...now..I want ask: I have Moto g4 xt1622 with:

- NPJS25.93-14-4 March security patch;

- Bootloader: B105.

Can I flash fastboot rom NPJS25.93-14-8 June security patch without brick my device?

I ask because many people bricked their devices.

Sorry for my english :)
[Moto G4 Plus Guides, News, & Discussion] echo92:
You should be okay to flash the fastboot stock ROM https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 or this OTA if you wish.

The reports of bricks seem to have come from downgrading whilst on the June update (either downgrading fully with stock, or downgrading without flashing GPT/bootloader, then attempting to update via OTA). Given your bootloader is B1:05, you'll likely not have flashed the June update, but as soon as you update, be very careful with downgrading.

Currently, our blankflash does not work in rescuing hard bricked devices in this manner and the only resolutions at this moment are to have your device repaired or save for a new device.
[Moto G4 Plus Guides, News, & Discussion] autoradio78:
So...sorry..my Enlgish is rusty. People that brick their devices was on B:106 and reverted back to NPJS25.93-14-4 (with B:105 bootloader)?
[Moto G4 Plus Guides, News, & Discussion] palorent:
It is very strange that the Old G4 Plus gets June Patch Update,and the newer Moto G5 is still on March 2017 Patch.
[Moto G4 Plus Guides, News, & Discussion] rajatgupta1998:
Doesn't really matter. Potter has better hardcoded encryption than athene. Kicks in even when you flash twrp.[emoji106]
[Moto G4 Plus Guides, News, & Discussion] Danny1976:
I have read that this update causes the battery to heats up very fast and charger does not charge the battery as fast. It that any true?
[Moto G4 Plus Guides, News, & Discussion] autoradio78:
Forget it...flahed..all ok:D
[Moto G4 Plus Guides, News, & Discussion] GokulChandran:
Well am one among those who tried to downgrade to march trying to lock the bootloader but my bad that was not possible

Then Downgraded to stock without flashing GPT/Bootloader and updated to June patch using OTA without any issues
[Moto G4 Plus Guides, News, & Discussion] Kwipper:
Is there a changelog for NPJS25.93-14-8 that shows what was changed/updated from the previous version? I just want to know if it's worth upgrading to this version, or should I remain using my stock NPJS25.93-14-4?
[Moto G4 Plus Guides, News, & Discussion] echo92:
I've not seen a changelog, as far as I know I think the main change is updating the Android security patch level from March 1st 2017 to June 1st 2017.

Also, new baseband version to .62.01R and a few other things I mentioned here. https://xdaforums.com/showpost.php?p=72933121&postcount=5

As an aside, I've had good performance and decent battery life on the NPJS25.93-14-8 update, your experience may vary.

However, the June update brings the bootloader version to B1:06, meaning that downgrading with this build runs a very high risk of hardbricking your device (the number of posts on the Question and Answer Thread about hard bricks recently are attributable, or at the very least connected to having this June update and downgrading) and currently the only fix for this is to have your motherboard replaced (at about 70-80% of the base cost of the device) or saving up for another device. If you ever see yourself downgrading, then it might be best to stay on the March 2017 NPJS25.93-14-4.
[Moto G4 Plus Guides, News, & Discussion] Kwipper:
Thanks for the prompt response and the warning. I guess this would also mean you shouldn't go from the stock NPJS25.93-14-8 to LineageOS since I think LineageOS uses the older bootloader, if I remember. Right?
[Moto G4 Plus Guides, News, & Discussion] echo92:
On the contrary, you shouldn't have issues going to LineageOS (or any other custom ROM), since they don't and shouldn't touch/flash anything related to the GPT or bootloader. You might be thinking of the boot kernel, which all ROMs need to have, but that boot kernel is different to the bootloader :)

The issue arose when users attempted to revert back from a custom ROM (when we didn't have the June fastboot stock ROM) or attempted to downgrade, both involving an older stock (Motorola) ROM. The resulting downgrade of the GPT/bootloader - which a fastboot ROM can do - or a downgrade without flashing GPT/bootloader, and then taking an OTA (which then may have overwritten parts of the newer bootloader) both resulted in a hard brick. Downgrading isn't formally supported by Motorola, so any bricks means having to pay for the repair.

You should be able to flash custom ROMs without issue (and I've done it on the NPJS25.93-14-8 bootloader), just ensure if you were to revert back to stock, you use the June 2017 fastboot ROM: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Alternatively, if you wish to keep TWRP, you could make a TWRP backup of your stock ROM before flashing a custom ROM, thus you can revert to a near stock ROM by re-flashing your TWRP stock ROM backup.

Good luck whatever you choose :)
[Moto G4 Plus Guides, News, & Discussion] Rakesh8857:
Is it working in Indian phone?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Should be, ensure you're fully updated on the March 2017 firmware before you flash this OTA. Also, any modifications to your device (including root, TWRP, but excepting your bootloader unlocking), will cause the update to fail. If you have modifications, you may wish to look into flashing the fastboot June 2017 update.

After you're flash this update, do not attempt to downgrade with stock ROMs - if you wish to revert back to stock, please use only the June 2017 stock ROM. Link for the fastboot ROM: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] GokulChandran:
Hey if i have just flashed june firmware image using fastboot from the custom rom

Will my device gets bricked if i update the future ota

(As am not flashed the older image files)
[Moto G4 Plus Guides, News, & Discussion] echo92:
Provided you flashed everything from the fastboot ROM and the flash went okay (and your device is functioning okay), I don't see a reason for the OTA to cause you problems. Once the OTA arrives, assuming that no TWRP, custom kernel, or root (or any other modifications, unlocked bootloader doesn't matter) are on your device, it should flash okay. If you do have said modifications, then you'll need to re-flash the June firmware again before accepting the OTA.
[Moto G4 Plus Guides, News, & Discussion] GokulChandran:
One more thing

Having restored stock rom using twrp and then using fastboot installing the stock recovery and then updating via ota in future is there any issue
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you've restored a TWRP backup after you allowed TWRP to make modifications to your system, the OTA may fail if it detects an attempt to make the system read/write. Also, if you flashed a custom logo.bin, then TWRP won't restore your stock logo.bin either.

In both those cases, easiest way is to reflash the recovery, logo and system chunks from the fastboot ROM (assuming your GPT and bootloader are from the June 2017 update, and your baseband is ending in .62.01R for the June update):

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

After this, your system should be stock (with no TWRP and root), and stable, and be ready for an OTA. Your data should also be preserved, but be prepared to factory reset/wipe your data should your system be unstable.
[Moto G4 Plus Guides, News, & Discussion] APrezzi:
Hi!

Unlock the bootloader, install TWRP, back up Stock 7.0, swap the Kernel with ElementalX and do root with Magisk. What would be the correct and safe procedure to go back to stock and receive updates via OTA? If you just want to go back to the Kernel Stock or if you install a custom rom and want to go back to Stock, is it going to be the same procedure? Thanks in advance.
[Moto G4 Plus Guides, News, & Discussion] torq1337:
My phone wasnt bricked, but with your tut I got back to stock! Thanks mate! <3
[Moto G4 Plus Guides, News, & Discussion] Shubham shukla 555:
Unable to download

Havent update my security level patch since oct 2016

Help me
[Moto G4 Plus Guides, News, & Discussion] echo92:
Yeah, that's likely happening as the Oct 2016 update was the soak test (NPJ25.75-2, if I recall)? If you were not on the soak test program, then you wouldn't have received the updates to bring you back onto the official OTA path.

Easiest way would be to flash the fastboot June 2017 stock ROM: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

You do not need to re-lock your bootloader if you do not wish to, but be aware you may have your data erased. You could use the following commands to flash, which may preserve your data. However, backup and keep your device backups off your device until you have finished flashing, and be prepared to factory reset if your device is unstable.

Assuming your device is already locked and you wish to keep your data:

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 reboot

You may wish to edit one of the provided flashing scripts to make it easier for you, so instead of copy pasting the commands individually, you can run your edited script.

After you are formally updated to June 2017, please do not downgrade to an earlier stock Motorola ROM (this includes Marshmallow and earlier Nougat builds), as you run the risk of bricking your device.
[Moto G4 Plus Guides, News, & Discussion] Danny1976:
I finally received the notification for the June security update for the Amazon version. I did the fastboot commands to get back to stock recovery and stock boot, but the OTA is giving me an error. My fastboot commands change a little since is the Amazon version on the oem.img to:

fastboot flash oem oem.img_sparsechunk.0

fastboot flash oem oem.img_sparsechunk.1

I did notice that on system.img_sparsechunk.7 it doesnt give me sending, writting and then finished like the others.

Error says: E1004: system partition fails to recover.

Edit: I was able to get the last system image to install and the update was completed successfully.
[Moto G4 Plus Guides, News, & Discussion] echo92:
Ahh, glad you got the system images to flash eventually - does that allow you to take the Amazon OTA?
[Moto G4 Plus Guides, News, & Discussion] Danny1976:
Yes, I was able to install the OTA. I am now on the June security update. Thank you for the fastboot commands to get me back to stock unrooted.

One question. I was able to go back to fully stock, because I had the ATHENE_AMZ_NPJS25.93-14-4 stock image. I want to root and install Elemental X kernel on the phone again. Since I don't have the ATHENE_AMZ_NPJS25.93-14-5 stock image, then I wont be able to go back to stock for the next OTA. Flashing stock recovery and boot wont bring it back to stock only, right? I did flash stock recovery and boot and I could not do the OTA, until I flashed the system files with the fastboot commands you provided.

How I can backup the files needed to go back to stock next time I need to update?

Thanks again
[Moto G4 Plus Guides, News, & Discussion] echo92:
As far as I know, as of writing you are correct - because of there being no stock image for NPJ25.93-14-5, you may not be able to roll back to full stock (though a fastboot ROM might come out in future). Even if you flashed stock recovery and stock boot, your system may still be detected as modified so an OTA may not work (I recently read that OTA updates check if your system is modified, even if it's simply read only or read-write, the read-write conferred by allowing TWRP to make modifications could cause an OTA to fail More info here: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html .)

One way to possibly get around this, though I've not tried it is:

1)Boot your device in TWRP. This should ensure you keep your recovery stock. Do not 'swipe to allow modifications'

2)Backup your device (the normal choices of partitions should suffice), make a note of this being a clean, read-only copy of your system and device. You may wish to transfer this backup to your computer.

3)Reboot to TWRP again, this time swipe to allow modifications (making your system read-write).

Flash ElementalX and root as before.

Thus, the theory is that to restore back to stock ready for a future OTA, you'd revert back to your backup you made above in step 2 once you've booted into TWRP. This should reflash a clean, read-only copy of your kernel and system. As you've still got your original recovery by booting into TWRP, your system should be stock enough for an OTA to be happy. Of course, rebooting back into TWRP requires a computer, which might get a little annoying depending on how often you flash. Again, I've not tried this but it likely should work. Good luck though.
[Moto G4 Plus Guides, News, & Discussion] Danny1976:
Thank you for taking the time to reply to my question. I really appreciate all the help you've given me.

You should add a donate option on your profile.
[Moto G4 Plus Guides, News, & Discussion] corlatemanuel:
Can someone give me the recovery.img from NPJS25.93-14-8? This is the latest build that I had a backup of, now I restored it after months of using Resurrection Remix and I want to update it to NPJS25.93-14-10 through OTA, but I don't have the stock recovery. The backup that I'm using is fully stock, except for TWRP recovery and the boot logo. So can someone give me some help? I don't want to reflash it all through fastboot, I just need the recovery.img so that I can do the OTA update.
[Moto G4 Plus Guides, News, & Discussion] shantam22:
Please update the dead link
[Moto G4 Plus Guides, News, & Discussion] echo92:
This OTA page is for the June 2017 OTA update; the latest firmware is the April 2018 NPJS25.93-14-18 build. If you need that, have a look at this page: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
[Moto G4 Plus Guides, News, & Discussion] CMKdaGreatest:
Released in India?
[Moto G4 Plus Guides, News, & Discussion] echo92:
If you're referring to the NPJS25.93-14-8 June 2017 update, it was released in India.

Same goes for the NPJS25.93-14-18 April 2018 update https://www.reddit.com/r/MotoG/comments/8mzpre/april_update_is_out_for_retin_moto_g4/ https://xdaforums.com/showpost.php?p=76660262&postcount=34
[Moto G4 Plus Guides, News, & Discussion] CMKdaGreatest:
Oh.....I thought June 2018 came out lol
[Moto G4 Plus Guides, News, & Discussion] echo92:
I'm confused as my post you quoted above stated this page was for the June 2017 OTA update....

I've not seen mentions of a June 2018 security patch for the G4/+ at the moment.
[Moto G4 Plus Guides, News, & Discussion] SnoopDoge:
i don't think it's for g4+ as well, haven't seen anyone getting it

EDIT: tf this post from last year doing now? this confused me
[Moto G4 Plus Guides, News, & Discussion] Langpang:
My IMEI SV is showing 11 on April security patch.
[Moto G4 Plus Guides, News, & Discussion] echo92:
That's the correct IMEI SV for the April 2018 security patch firmware. As mentioned above and in the post you quoted, this thread was for the June 2017 security patch
[Moto G4 Plus Guides, News, & Discussion] Langpang:
Why there is no update for me (xt1643)
[Moto G4 Plus Guides, News, & Discussion] echo92:
This OTA page is for the June 2017 security patch (as mentioned on the last page), there's been no June 2018 or any patch newer than the April 2018 security patch yet for our devices.
[Moto G4 Plus Guides, News, & Discussion] Langpang:
So ,it's for non plus variant only ?...
[Moto G4 Plus Guides, News, & Discussion] echo92:
No - this patch is for both G4 and G4 Plus variants, but this patch is from the June 2017 security patch (i.e. last year as of writing this). At the moment, there is no newer patch than NPJS25.93-14-18 (April 2018 security patch). If you're on NPJS25.93-14-18, you shouldn't be receiving this patch as it's too old.
[Moto G4 Plus Guides, News, & Discussion] Langpang:
Oho !!! I didn't saw "2017" ...... Anyway ,thanx for your reply .
[Moto G4 Plus Guides, News, & Discussion] strongst:
[MENTION=2976528]georgeiulian89[/MENTION] can you please change title and attach "2017" after June? Thanks!
[Moto G4 Plus Guides, News, & Discussion] georgeiulian89:
Done.
[Moto G4 Plus Guides, News, & Discussion] zeroibis:
I recently installed this update on a phone and it basically broke the phone. I am looking for any advice on how to fix.

1) The phone is 100% stock it is not rooted and is/was not running a custom ROM

2) After the update the phone will crash if it connects to a cell network. If you turn on airplane mode you can use the phone as long as you want. You can also get on and us WiFi. If you turn airplane mode off the phone will work up until the moment before it connects and then it restarts.

3) I have tried to clear the cache via recovery and that did not resolve the issue.

4) I have tried to do a factory reset via recovery and that did not resolve the issue.

Is there anything else I can do or should try?
[Moto G4 Plus Guides, News, & Discussion] echo92:
Hmm, I'd recommend a re-flash of the firmware. You could look into flashing the latest April 2018 firmware, NPJS25.93-14-18 and see if that fixes your issues. https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 The NPJS25.93-14-8 June 2017 patch is pretty old by comparison.
[Moto G4 Plus Guides, News, & Discussion] zeroibis:
Oh woops, I thought this was the thread for the 2018 patch!

So it looks like the possible solution is to download the patch and reapply it?
[Moto G4 Plus Guides, News, & Discussion] echo92:
There is no June 2018 security patch present at the moment. The latest patch for G4/Plus devices is the April 2018 security patch.

You could try to re-download the NPJS25.93-14-18 security patch via OTA/sideloading, though I would consider a full firmware flash from that previous link to make sure your device is clean. If you want to try to keep your data, omit the OEM locking commands and the fastboot erase userdata command. As always, back up your device before flashing anything.
[Moto G4 Plus Guides, News, & Discussion] zeroibis:
Ah I see was that the phone was actually a G4 play not G4 plus.
[OnePlus 5 Questions & Answers] partisano:
Hi all,

I want to know if the audio quality in videos when recording concerts with OnePlus 5 is good. I have OnePlus One and audio quality in concerts videos recorded with the camera is awful: distorted sound which mess the video.

Thanks!

Enviado desde mi A0001 mediante Tapatalk
[OnePlus 5 Questions & Answers] DSF:
Idk how legit is this:

[youtube]SfMbKZXSjGc[/youtube]
[OnePlus 5 Questions & Answers] partisano:
Thank you for the link! Sound is really bad :(

Enviado desde mi iPad utilizando Tapatalk
[OnePlus 5 Questions & Answers] DSF:
No problem. To me it sounds pretty good and so much better than the OP3, at least in that comparison video anyway

Ps: i haven't received my op5 yet
[OnePlus 5 Questions & Answers] antonior93:
https://goo.gl/photos/sEo55JKczHotFm5A8

Not bad at all, even video stabilisation at 1080p@60fps is pretty good in my opinion: consider that, except for the initial right panning, my hand were shaking.
[OnePlus 5 Questions & Answers] shrubbie:
You do realize this is a phone? There is no phone that can record at high volumes. Mics just can't handle that, they're supposed to record human voice at normal volumes.

It will sound good enough if the volume is low enough though. So, no concerts.
[OnePlus 5 Questions & Answers] ylialokas:
Ou yes there is. Lumia models. Like Lumia 1020. Those had HAAC mics that could record very high desibels.

Even OLD Nokia 808 pureview had this.

There are videos on youtube.