[Captured OTA]Nougat OTA for Moto G4 Plus - XT1643 India
- Thread starter jeash
- Start date
No, the system OTAs can be flashed using stock Recovery only. Make sure you have unmodified system and boot partitions or else you may proceed with fastboot. :good:
Bear in mind this OTA is the Nov 2016 NPJ25.93-11 build.
Generally, for OTA:
Download the file.
Reboot to stock recovery.
In stock recovery, select 'Install zip from SD card...' (or similar)
Navigate to where you downloaded the OTA.
Flash.
Note, this may only work if you were on Marshmallow, you may not be able to flash 93-11 over later versions of Nougat in this way. Also, won't relock your bootloader - use either of the firmwares I posted in your other post.
about blur version
sir what is it the blur version please explain this .... in hindi if possible Thanx
sir what is it the blur version please explain this .... in hindi if possible Thanx
The Blur version appears to be Motorola's naming of its OTA updates. This update is Blur_Version.24.31.64.athene.retail.en.US.zip - the NPJ25.93-11 November 2016 update.
The latest update is the NPJS25.93-14-8 June 2017 update - here is the stock ROM for flashing in fastboot: https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
30Hi All - I have managed to capture the OTA Zip file for MotoG4 Plus India edition (XT1643)
I have been running in this version for last two days and haven't faced any issues.
Guess Moto/ Lenovo has done a good job here.
OTA Link:
https://drive.google.com/file/d/0Bz4VlDySg4OlQTRTX0ljWTUweHc/view?usp=drivesdk
Jeash6Abou nougat security and root ( found in a website)
When Nougat boots, it checks to see if anything in the system partition has been tampered with. Google calls this Verified Boot and it's something they also use on Chromebooks and OnHub routers. We also knew it was coming, along with a handful of other big changes on the security front. The short version of how it works — the system partitions (this is tied in tightly with Seamless Updates and Direct Boot) are verified and given a hash file. Any changes to the partition will change the crypto hash. When you boot the phone up, this hash is checked against the known "right" value, and if they don't match your phone won't boot. The public crypto key is stored on the boot partition and when the people who made your phone want to update (which changes the hash file) they have to verify things with their own private key to change the software. This will create a new hash file and the phone can boot. These changes also include the ramdisk (which is where systemless root worked) so modifying it is out of the picture, too. And yes, this is the short version.
Fastboot for life
What this means is new hardware designed for Android 7.0 isn't going to boot if we try to change any files to give us root. If we change even one bit on either system partition or the ramdisk it will fail the verified boot check. There are no known root methods that will ever work with this system. Period. Very smart people will try, and if somehow they find a way Google will patch it within 30 days. And this is not an accident.
Google is always trying to beef up the security in Android. They do a pretty good job and Android, as it comes directly from the source code, is really secure. But since anyone can change any of it to their liking, much of that gets undone. One of the things this change does is fix things so that no matter what you download or what it tries to do, if it tries to inject anything that gives it elevated permissions your phone won't start up. I love that idea, and you should, too.
Every phone that's sold should be damn near impossible to root without custom firmware.
This means that those drive-by root exploits — both the intentional ones as well as the malware ones — all stop working if the people who made your phone update it to 7.0 or you buy a new one with Nougat installed. That means everyone who just bought their phone to chat with friends, pay for stuff at Walgreens, or even clash against other clans or catch 'em all have a lot less to worry about. The factory software (and this is the important part) is secure.
The rest of us who like to root and do "stuff" can't do it while running the factory software, but we can still do it. With a new boot image, things can be altered so we can do whatever we want to do. Everything needed to create the Android boot image is open source and builds with no changes and little effort.5Sir many users reported that update not working over previous soak
Plz help
Sent from my Moto G (4) using Tapatalk
You will need either of these roms.
Package expects build thumbprint of 7.0/NPJ25.93-11/12:user/release-keys or 6.0.1/MPJ24.139-63/64:user/release-keys
Obviously the previous soak test was released had build thumbprint of 7.0/NPJ25.75-2/1:user/release-keys which means there was another soak test with build thumbprint of 7.0/NPJ25.93-11/12:user/release-keys which we didn't get.
So we need to flash 6.0.1/MPJ24.139-63/64 Marshmallow rom for the update to get thru.
Hope it makes sense.3
No ideas :/
Made a boot/system TWRP backup :
http://vache.cloudapp.net/G4/tmp/TWRP_BACKUP/
https://dl.vache-android.com/athene/Firmwares/TWRP_BACKUP/
