Stock N/O Firmware [Apr 01/Dec 01 Security Patch][fastboot][7.0/8.1]

[sujeet_kumar]

Is it with June 1 Security Patch ?

Is it with June 1 Security Patch ?
Because with march security patch on moto g4 plus I have build no. NPJS25.93-14-4 4, which stock rom available on xda-froum is not officially signed.
And you said its the June 01 security patch then
1. why same build number as of march security patch and
2. this thread is created in may,then how it is possible that it has June 01 security patch ?

I am on June 01 Security Patch with build number NPJS25.93-14-8.

 

[peladoro]

Is it with June 1 Security Patch ?
Because with march security patch on moto g4 plus I have build no. NPJS25.93-14-4 4, which stock rom available on xda-froum is not officially signed.
And you said its the June 01 security patch then
1. why same build number as of march security patch and
2. this thread is created in may,then how it is possible that it has June 01 security patch ?

I am on June 01 Security Patch with build number NPJS25.93-14-8.

Lol ??? 14-4+4=14-8

 

[justbfree]

If u like to play with custom ROMs, I'd skip 6/17 stock ROM and stay on 3/17 stock ROM.

If u want to stay stock and not flash back and forth, then go ahead and use 6/17 stock rom

So if I flash 6/17 stock rom I won't be able to use custom roms afterwards?

 

[HueyT]

So if I flash 6/17 stock rom I won't be able to use custom roms afterwards?

High brick risk to downgrade to older stock or custom ROMs

 

[justbfree]

High brick risk to downgrade to older stock or custom ROMs

Is stock rom better than custom roms? I never really used the stock rom actually... I flashed a custom on the very first day I bought the phone

 

[HueyT]

Is stock rom better than custom roms? I never really used the stock rom actually... I flashed a custom on the very first day I bought the phone

I like both so I'm staying on 3/17 Nougat base. Stock gives me more reliable LTE for Verizon than custom

 

[echo92]

So if I flash 6/17 stock rom I won't be able to use custom roms afterwards?

If you're on the June 2017 update and want to use a custom ROM, perhaps it's wise to make a TWRP backup of your stock ROM before flashing the custom ROM. That way, instead of having to flash a stock ROM via fastboot, you could revert to your stock TWRP backup, then flash a stock recovery (and logo/boot images if need be) from the June fastboot ROM. Now, you've reverted back to stock without having to flash an older firmware via fastboot (which is the risky bit)

 

[HueyT]

If you're on the June 2017 update and want to use a custom ROM, perhaps it's wise to make a TWRP backup of your stock ROM before flashing the custom ROM. That way, instead of having to flash a stock ROM via fastboot, you could revert to your stock TWRP backup, then flash a stock recovery (and logo/boot images if need be) from the June fastboot ROM. Now, you've reverted back to stock without having to flash an older firmware via fastboot (which is the risky bit)

Which exact partitions are bricking people on this latest June stock rom?

I don't think people realize the xtra partitions that FASTBOOT flashes onto the phone compared to TWRP. Flashing \system, \data, \boot, \FSG, \Persistent via TWRP rarely causes hard brick. Fastboot flashing can mess up your partitions, IMEI, etc. I use fastboot to restore stock as last resort. It's much safer to use TWRP to flash, backup, restore roms.

Here is a link that explains the different partitions in TWRP and in FASTBOOT flashing:
https://forum.xda-developers.com/moto-g/general/motorola-moto-g-partitions-explained-t3418644

 

[rybshik]

Tested on: ...... XT1625

So it works on Athene XT1625 Moto G4 (without "Plus")? Sorry for my OCD

twrp-3.1.1-0-athene.img or twrp-3.1.1-athene_shreps.img
Which one do you use?

 

[echo92]

Which exact partitions are bricking people on this latest June stock rom?

I don't think people realize the xtra partitions that FASTBOOT flashes onto the phone compared to TWRP. Flashing \system, \data, \boot, \FSG, \Persistent via TWRP rarely causes hard brick. Fastboot flashing can mess up your partitions, IMEI, etc. I use fastboot to restore stock as last resort. It's much safer to use TWRP to flash, backup, restore roms.

Here is a link that explains the different partitions in TWRP and in FASTBOOT flashing:
https://forum.xda-developers.com/moto-g/general/motorola-moto-g-partitions-explained-t3418644

From what I've observed, the likely culprits seem to be either the GPT or bootloader partitions (or both) that are included with the June update. The bricking incidents I've been tracking appear to have involved a full firmware downgrade (including bootloader/GPT), or alternatively downgrading without touching GPT/bootloader (which does not appear to brick, from the few reports I've seen), then accepting an OTA (which does brick).
Seems to have echoes of what happened when users flashed the Lollipop soak test and attempted to downgrade.... https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147)

As you mentioned, TWRP only backs up and restores a limited (though all useful and relevant) number of partitions, seems to make a copy of the partitions themselves (as an aside, I wonder why the stock recovery can't back up in a similar fashion?). Thus, a TWRP restore should be a genuine copy of your device when the backup was taken. I've just restored my TWRP backup of the stock June ROM (made in TWRP 3.1.1 shrep's version) from AOSPExtended 4.4 to the stock NPJS25.93-14-8 and it looks to be running okay.

Furthermore, TWRP doesn't seem able to see/flash the bootloader/GPT, whereas fastboot certainly has access to those partitions and more, making fastboot a more powerful tool, but more dangerous too. That being said, the fastboot firmware images generally should be safe to flash for updating/flashing on the same ROM, though as both you and I have mentioned, using fastboot firmware to downgrade is seriously not recommended when the June update is involved...

 

[rybshik]

TWRP restore should be a genuine copy of your device when the backup was taken.

not necessarily . OTA updates are very picky (probably, for a good reason) and check many fine and minor ROM details including if the system image was previously mounted read-only or not

 

[echo92]

not necessarily . OTA updates are very picky (probably, for a good reason) and check many fine and minor ROM details including if the system image was previously mounted read-only or not

That's a fair point - as I understand it, TWRP takes a partition level copy of those partitions as a backup. Of course, it doesn't know what alterations may have occurred on those partitions prior to the backup. OTAs, especially the last one, appeared to be patches rather than full files (and probably do a signature verification of the partitions

As for your other questions, I've not seen any reports of the XT1625 being flashed with the June fastboot ROM yet, so it's up to you if you wish to try and report back. Given it's a Motorola stock ROM, it should work, but ensure you back up your data first and move it off your device. Up to you if you choose to re-lock your bootloader or not.

Of course, if you flash this fastboot ROM, it'll remove TWRP and root from your device. You may be able to avoid a wipe of your data by omitting these fastboot commands:

fastboot erase userdata
fastboot erase customize
fastboot erase clogo

But be prepared to perform a factory reset if your system is not stable.

 

[alejo.z]

Thanks! working fine on XT1621 :highfive:

 

[rajatgupta1998]

Is it with June 1 Security Patch ?
Because with march security patch on moto g4 plus I have build no. NPJS25.93-14-4 4, which stock rom available on xda-froum is not officially signed.
And you said its the June 01 security patch then
1. why same build number as of march security patch and
2. this thread is created in may,then how it is possible that it has June 01 security patch ?

I am on June 01 Security Patch with build number NPJS25.93-14-8.

I had earlier created this thread for the March firmware. And now updated it with the June firmware. The end of OP shows the last updated date/time [emoji57][emoji58]

Sent from my Moto G4 Plus using Tapatalk

 

[Loren_James]

Here is my bottom line noob question: I am most interested in flashing the June 1 update because it has a more secure bootloader, so if I flash it at all, it will be via fastboot so the bootloader is the latest. I will then flash the sheep's 3.1.1 TWRP and make a backup. If I am understanding what I am reading correctly, as long as I flash a ROM is a post-June security patch, there should not be an issue. The trouble is with downgrading. Thanks in advance for confirming...

 

[echo92]

Here is my bottom line noob question: I am most interested in flashing the June 1 update because it has a more secure bootloader, so if I flash it at all, it will be via fastboot so the bootloader is the latest. I will then flash the sheep's 3.1.1 TWRP and make a backup. If I am understanding what I am reading correctly, as long as I flash a ROM is a post-June security patch, there should not be an issue. The trouble is with downgrading. Thanks in advance for confirming...

1)Yes, you'll be flashing this June stock update with fastboot.
2)Don't forget in order to flash TWRP/any custom recovery/ROM, you'll need an unlocked bootloader (which voids your remaining warranty and wipes your device in the process). If you've already unlocked your bootloader, then you could choose to boot into TWRP rather than flash TWRP, so your stock recovery is still in place.
3)Yes, the trouble has been with downgrading with stock (Motorola) ROMs from the June stock update. I have seen reports that users have been able to downgrade without flashing the GPT/bootloader, but it's risky. Once you're on the June update, it seems that June stock ROMs and above are safest for flashing. Custom ROMs do not appear to be affected by this requirement (since they don't affect the bootloader/GPT), but the newer the custom ROM, the better for bug fixes and features.

 

[Loren_James]

Thank you...I see you are all over this!

 

[jyoti.id]

I read all the comments! I understand that if I flash the latest update it will be risky to DOWNGRADE! Here is my question! Is it also risky if I flash the Exact Same Latest June Firmware (means NO DOWNGRADING "Theoritically") whenever i need to go back to Stock? Though I hardly use stock, I use custom roms most of the time!

 

[lCrD512]

I read all the comments! I understand that if I flash the latest update it will be risky to DOWNGRADE! Here is my question! Is it also risky if I flash the Exact Same Latest June Firmware (means NO DOWNGRADING "Theoritically") whenever i need to go back to Stock? Though I hardly use stock, I use custom roms most of the time!

For me downgrading has always been risky. Flashing latest firmware is safe but if you wish to stay on current firmware its better not to upgrade than upgrading and downgrading back.

 

[peladoro]

I read all the comments! I understand that if I flash the latest update it will be risky to DOWNGRADE! Here is my question! Is it also risky if I flash the Exact Same Latest June Firmware (means NO DOWNGRADING "Theoritically") whenever i need to go back to Stock? Though I hardly use stock, I use custom roms most of the time!

Hey! I was on my carrier's ota for 14-4...had to fastboot to completely return to stock (14-4) then used the file to update to 14-8 provided in other thread. I was on lineage and yesterday used the full 14-8 provided here to return to stock...so all good

Sent from my Moto G4 Plus using XDA-Developers Legacy app