Hello folks. I need help getting back to stock firmware on my Moto G4 Plus Indian Variant (xt1643). I have flashed resurrection remix that's on android 7.1.2. I tried to flash the stock firmware (november 1, 2016 security build) through fastboot. As soon as I entered the command to flash the stock boot image, I get a pre-flash validation error message and had to abort the flashing procedure immediately. I was on the latest march build before flashing resurrection remix. I don't know how to go about with it and need to get back to stock firmware asap. Any help is always appreciated.
Thanks in advance,
Krishna16
I am running resurrection remix (7.1.2) on my moto g4 plus currently and have an unlocked bootloader and twrp recovery installed.
Krishna16 said:
I am running resurrection remix (7.1.2) on my moto g4 plus currently and have an unlocked bootloader and twrp recovery installed.
Click to expand...
Click to collapse
If you previously were on the March 2017 security build (should be NPJS25.93-14.4), you may wish to download this stock ROM, which is the latest build that we have available (NPJS25.93-14.4, March 2017 security patch). https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 This stock ROM thread also has scripts to help you flash, though you may wish to edit them to match the commands below. You may also verify if you're on the latest firmware previously by booting to your bootloader - I recall the March 2017 bootloader version is B1.05.
Regardless, you're likely getting that pre-flash validation error due to an attempt of flashing an older bootloader and/or attempting to relock your bootloader with an older firmware. You can only relock your bootloader with firmware of the same build you had previously or newer.
I'd suggest using the latest stock firmware, and provided you were on the March 2017 update previously, omit flashing the GPT and bootloader partitions (whether you're using the latest stock build or your November build - just keep those partitions as they are):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
You may also wish to omit the locking commands if you don't wish to lock your bootloader. Your commands should look therefore like:
Code:
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 erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
If you wish to relock your bootloader, use the commands as follows (if the commands complain of needing a signed image, try booting into your flashed stock system, toggle OEM Unlock in Developer Settings and re-flash the stock ROM with the re-locking commands)
Code:
fastboot oem lock begin
fastboot oem lock begin
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 erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
I've used the 1st list of flashing commands - the non-locking version - to revert from RR 5.8.3 27/05/2017 to the stock NPJS25.93-14.4 ROM on my XT1642 without issue (apart from the unlocked bootloader warning). Be aware that re-flashing a stock ROM will wipe your device clean (including internal storage) and may result in your SD card being non-functional until wiped. Back up your important data accordingly (you may wish to use Titanium Backup to preserve your app data), and transfer backups off your device until you have flashed.
EDIT - tweaked a couple of sentences for clarity.
echo92 said:
If you previously were on the March 2017 security build (should be NPJS25.93-14.4), you may wish to download this stock ROM, which is the latest build that we have available (NPJS25.93-14.4, March 2017 security patch). https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 This stock ROM thread also has scripts to help you flash, though you may wish to edit them to match the commands below. You may also verify if you're on the latest firmware previously by booting to your bootloader - I recall the March 2017 bootloader version is B1.05.
Regardless, you're likely getting that pre-flash validation error due to an attempt of flashing an older bootloader and/or attempting to relock your bootloader with an older firmware. You can only relock your bootloader with firmware of the same build you had previously or newer.
I'd suggest using the latest stock firmware, and provided you were on the March 2017 update previously, omit flashing the GPT and bootloader partitions (whether you're using the latest stock build or your November build - just keep those partitions as they are):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
You may also wish to omit the locking commands if you don't wish to lock your bootloader. Your commands should look therefore like:
Code:
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 erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
If you wish to relock your bootloader, use the commands as follows (if the commands complain of needing a signed image, try booting into your flashed stock system, toggle OEM Unlock in Developer Settings and re-flash the stock ROM with the re-locking commands)
Code:
fastboot oem lock begin
fastboot oem lock begin
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 erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
I've used the 1st list of flashing commands - the non-locking version - to revert from RR 5.8.3 27/05/2017 to the stock NPJS25.93-14.4 ROM on my XT1642 without issue (apart from the unlocked bootloader warning). Be aware that re-flashing a stock ROM will wipe your device clean (including internal storage) and may result in your SD card being non-functional until wiped. Back up your important data accordingly (you may wish to use Titanium Backup to preserve your app data), and transfer backups off your device until you have flashed.
EDIT - tweaked a couple of sentences for clarity.
Click to expand...
Click to collapse
I am out of words to thank you??. Thanks a lot for your efforts and time echo92. I still have a perpetual problem and that is my speaker volume is too low while playing YouTube videos. Is there a way to fix that??
now should i update from marshmello to nougat???
after reverting back to stock?
sarang25 said:
now should i update from marshmello to nougat???
after reverting back to stock?
Click to expand...
Click to collapse
No. You must flash nougat with latest security patch
sarang25 said:
now should i update from marshmello to nougat???
after reverting back to stock?
Click to expand...
Click to collapse
If you previously had stock Nougat (doesn't matter about custom ROM Nougat) before reverting back to Marshmallow stock, I too would recommend you flash the latest stock Nougat via fastboot. For India, Brazil, EU and UK devices, that stock ROM is the NPJS25.93-14-18 firmware ( https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 )
We've seen previously that attempting to use OTA updates on a device with downgraded stock firmware (again, does not matter what custom ROM you had, what matters is what stock ROM builds you had flashed previously and now) can hard brick your device. Thus, if you want to update, using OTA updates can be potentially risky. Safest way is to use fastboot flashes to update.
I have a Moto G4 (XT1625) Unlocked with 32GB of storage. Bootloader Unlocked and TWRP Bootloader or Recovery, IDK how to word it, but I attempt to update from Android 6.0.1 to Android 7 and the update fails. When the device reboots it reboots into the TWRP Recovery Menu. How do I proceed. Please help.
Haven't used adb, drivers, or anything and cannot seem to remember the process. Any pointers in the right direction are appreciated. Thank you.
Update 1: I am able to boot into TWRP 3.0.2-0 and see files on my MicroSD. However I downloaded a .ZIP file that was suppose to be the Nougat factory image and when I went to flash it, it says "Installing zip file.... could not find 'META-INF/COM/GOOGLE/ANDROID/UPDATE-BINARY' in the zip file. Error installing zip file."
Update 2: Can someone confirm that I would need to first somehow remove TWRP in order to update? How do I remove TWRP and get phone back to FULL STOCK.
Okay, accepting OTA updates requires a stock recovery (as you've discovered), stock kernel and unmodified system. Furthermore, the stock Nougat zip that you've downloaded needs to be extracted on your computer and flashed via fastboot, it's not flashable in TWRP.
If you're wanting to update and update to the latest Nougat build (which for US devices - XT1625 and XT1644 - appears to be NPJ25.93-14.5, June 2017), the easiest way is to download the stock Nougat ROM from here: https://www.androidfilehost.com/?fid=673368273298984458 . Download to your computer and extract the files. This build is for retail US (non-Amazon devices), with a retus software channel as listed in Settings>About Phone.
Then follow the instructions here, but using the above NPJ25.93-14.5 stock ROM instead. https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Beware that this process may erase your data in the process, so back up as necessary. If you do not wish to erase your data, then you can use the following fastboot commands instead of the commands in the guide. Back up anyway and you may have to factory reset (thus losing your data) if your device is not stable. Also, either process will remove TWRP, root and any other modifications. Xposed is still not officially released for Nougat. It is up to you if you choose to re-lock your bootloader or not (of course, re-locking the bootloader will prevent you from flashing TWRP/root/any other modifications).
Code:
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
pause
One word of warning, once you have formally updated to June 2017 (B1:06 bootloader), do not attempt to downgrade and accept OTA updates. You may wish to downgrade, but I don't recommend it - if you forget to not accept OTA updates, you may hard brick your device. If you think you'll forget, do not downgrade.
Hello,
So I've been trying to update my XT1265 which is currently on build number NPJS25.93-14-4. I my phone is rooted with TWRP installed. The phone was unlocked through the motorolla site. There's an OTA update that keeps annoying me so I'm trying to update it. If I try the update it updates, then when it reboots it stops in TWRP. (My phone actually always boots into TWRP when it reboots/boots but I'm able to reboot bootloader and get it booted.) I've read that I need to get back to stock recovery to get it to update. I've yet to be able to find a stock recovery that I can fastboot to reinstall.
What do I need to do to get this to update?
Generally, OTA updates require stock recovery, stock system and stock kernel - any modifications to these and the OTA update fails, as you've found (e.g. the TWRP boot issue). By modifications, I mean TWRP, root, even letting TWRP modify the system read/write status.
If you really want to flash OTA updates, then you'd be best served by re-flashing the stock ROM. The following commands in fastboot should preserve your data and roll back your device to an OTA friendly state. However, back up and be aware that this will remove TWRP, any modifications (including custom logos) and restore your system partition to a read-only status.
Link for NPJS25.93-14-4 (non Amazon): https://androidfilehost.com/?fid=673368273298955218
Amazon: https://androidfilehost.com/?fid=889764386195899718
Extract the correct stock ROM zip to your ADB directory (it's about 2 GB expanded) and flash with the following commands in your ADB terminal:
Code:
[B]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/B]
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
[B]fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn[/B]
fastboot erase cache
fastboot reboot
Up to you if you choose to flash the steps in bold, as you should be flashing the same firmware onto your device as what you currently have.
Upon rebooting, your device should be back to where it was (though the initial boot might be longer as the cache is re-built) and then you should be okay to take OTA updates.
If you simply want to silence the updater, have a look at this thread (requires root) : https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
As for the TWRP boot issue, you may wish to look at this thread too (though I've not tried this, so be careful) : https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
I've lost volte support after flashing 64 bit rr oreo
Using 1643 Indian model.......I restored my stock rom backup and flashed jx's modified rom still no help...plzz some one help me....im avoiding fast boot flash...plzz help me asap
Thx in advance
Un bootloader Mode, can you see both IMEIs?
Ismael034202 said:
Un bootloader Mode, can you see both IMEIs?
Click to expand...
Click to collapse
Yes i can see both imei's and whts unbootloader...do you mean relocking bootloader ?
No, the corrector.... Try to flash the Stock Rom with this commands, I mean, flash the Stock Rom first without wiping data and then if is still not working wipe also 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
You can skip erase userdata and oem lock but you have to follow rest steps.
This is how i get back my volte working back.
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Harshseth said:
I've lost volte support after flashing 64 bit rr oreo
Using 1643 Indian model.......I restored my stock rom backup and flashed jx's modified rom still no help...plzz some one help me....im avoiding fast boot flash...plzz help me asap
Thx in advance
Click to expand...
Click to collapse
Reflash stock rom and then flash rr
Someone managed to get the RSD Secure link for the FASTBOOT files of the final Oreo 8.1 release for RETAIL Moto G5/cedric.
With these files you'll be able to update to official oreo, relock your bootloader or simply go back to stock.
Using the guide I'll write below you'll be able to flash it from Linux, Windows and MacOS.
The new firmware is named OPP28.85-16 and Blur Version listed within the firmware package is:
Code:
Blur_Version.28.41.15.cedric.retail.en.US
whereas the OTA file for the corresponding Firmware lists it as:
Code:
Blur_Version.25.361.10.cedric.retail.en.US
I dont know which is "correct", but anyways, this should not alter your results when flashing this with fastboot.
DOWNLOAD
Gdrive: https://drive.google.com/file/d/1gNB7vNM8xH5ueTPKh5Qwev87gJpSpyyK/view?usp=sharing
RSD Secure: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
FLASHING IT
If your seeing this post long after Setember 2018 it may be the case you have updated your firmware past this one and got a different bootloader version, in that case, make sure to check you bootloader version is BELOW B8.31. Flashing bootloader of equal or minor version will hardbrick your device
UPDATING FROM PREVIOUS ANDROID VERSION
1. If you're on Windows/Mac, download motorola USB drivers here. (You shouldn't need these on Linux)
2. Download Android Platform Tools (ADB & Fastboot ) for Windows/Mac/ Linux here (if you're on Linux, get these from your distro's repo instead).
3. Extract the platform tools somewhere
4. Extract the firmware's ZIP too (I recommend extracting it to the same directory as platform tools, this will make your life easier).
5.Open a command prompt/terminal where you extracted platform tools (To do that on windows, Hold SHIFT + right Click some blank area within platform-tools directory, then click "Open Command Prompt Here".
6. Reboot into fastboot (power off and connect USB while holding Vol Down) and Execute the following commands
Code:
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
PS: Do not execute commands related to erasing the modemst1 and modemst2 partitions. This has been related to people losing their IMEI's.
RELOCKING YOUR BOOTLOADER
edit
Seems like my instructions on how to relock didn't work, but I want to thank Andrej_SK, who managed to do it and posted instructions on how to do it. Just remember that you should Not flash bootloader if you're already on B8.31 or past it. Flashing gpt.bin can also hardbrick your phone and there have been reports of it happening here on XDA and on telegram. I personally didn't flash it when moving from NPPS25.137-93-2-5 and had no problem at all, and I think you shouldn't too, unless you know you absolutely need it (which I think is unlikely, since the partition scheme looks the same on both nougat and Oreo)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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 system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (do not flash this if you're on B8.31 or further, so as not to hardbrick the device)
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
DOWNGRADING FROM A FIRMWARE NEWER THAN OPP28.85-16
1. Follow steps one 1 up to five described in the first section UPDATING FROM PREVIOUS ANDROID VERSION
2. Omit these lines from step 6:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Notice that omitting these two lines is VERY IMPORTANT if you're downgrading, otherwise you'll hardbrick your device.
3.7. Reboot your phone by typing fastboot reboot or by selecting the "START" option in phone's screen and then pressing the power button
That's it. If you liked, press thanks
Ps: some of my friends have reported phone is rebooting right after flashing sparsechunk.5.
phone will apparently boot normally and show the setup wizard screen, but in actuality there will be missing files on the system partition.
in that case, reboot into fastboot and finish flashing the system normally, then boot your phone
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
I believe the two threads are separate updates. One being OTA and this thread being fastboot firmware. I was wondering if this would work on my Moto g5 xt1670 (137-93-8)?
Woooow
Thanks
Ahasverus said:
Thank you very much! Excuse me if I'm wrong but with this file it's safe to install Oreo from stock Nuggat right? I just need to unlock the bootloader and flash normally?
Click to expand...
Click to collapse
no need to unlock BL to flash this. If you're on stock Nougat just make sure you're on NPPS25.137-93-2-5 (July security patch), then grab the ota here and sideload or flash it using the stock recovery
if you're not on NPPS25.137-93-2-5 then you'll need to flash it before flashing the ota.
AndroidenKalle said:
Thank, you to provide the firmware.
On another thread (https://forum.xda-developers.com/g5...eo-8-1-0-release-opp28-t3849273/post77771786) you wrote it's necessary to be on firmware NPPS25.137-93-2-5. Maybe you forgot to mention that!?
Click to expand...
Click to collapse
if you're going to install it from fastboot there's no need to be on NPPS25.137-93-2-5
TWRP v3.2.3.0 for Cedric: works
Magisk v17.1: works (don't use safetynet)
Thank you very much for this! I've been using the soak Oreo and could not be happier until this thread, time for the final Oreo for my beloved G5.
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't think so since this is definitely a retail version.
BUILD REQUEST INFO:
SW Version: cedric-user 8.1.0 OPP28.85-16 0400 release-keysM8937_22.29.02.70R
MBM Version: B8.31
Modem Version: M8937_22.29.02.70R
FSG Version: FSG-8937-02.65.33
Build Fingerprint: motorola/cedric/cedric:8.1.0/OPP28.85-16/0400:user/release-keys
CQATest App Version: 6.0.6
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 28.41.15.cedric.retail.en.US
Model Number: Moto G (5)
Android Version: 8.1.0
Baseband Version: M8937_22.29.02.70R
Build Id: OPP28.85-16
SW Display Build ID: OPP28.85-16
Build Date: Wed Sep 5 09:46:09 CDT 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.28.41.15.cedric.retail.en.US
Version when read from CPV: cedric-user 8.1.0 OPP28.85-16 0400 release-keys
slsmaster said:
Hello,
the bootloader locking seems not to be working. At the last "fastboot oem lock" it says that it needs a signed boot.img. Has anyone else experienced this issue ?
Click to expand...
Click to collapse
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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 system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
......
......
Click to expand...
Click to collapse
Thank you very much, worked like a charm.
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
PsyClip-R said:
The thing I don't like in your instructions is lack of DDR errase command.
Please explain your point. Also please compare with flashfile.xml from Oreo firmware.
Click to expand...
Click to collapse
never heard about this command before, I have never used it ever and I flashed this firmware without any problem so far
Andrej_SK said:
So "fastboot erase ddr" command should be included while flashing stock Oreo through fastboot? What does that command do?
Click to expand...
Click to collapse
As I said above, I and other people I know who flashed this didn't have any problem by flashing without typing "fastboot erase DDR" and in fact I'm curious to know what does this command do.
JoeDoe0 said:
Blur_Version.28.41.15 for OPP28.85-16 is correct!
I'm on the 2nd soak test update OPP28.85-13 and tried the OTA update from your other post. This failed due to wrong version (E3002) since it expects the last NPPS25.137-93-2-5 version.
How can I update from OPP28.85-13 to the latest OPP28.85-16 via fastboot flash without losing my current data and settings?
Can I flash without "erase userdata"?
Click to expand...
Click to collapse
I think it's very unlikely anyone has this OPP25.85-16, otherwise it would've already surfaced somewhere.
(edit)
seems like I was wrong, I just reflashed the firmware and managed to keep my data by not using fastboot erase user data.
(/edit)
regarding the "fastboot erase user data" it doesn't matter if you use it or not, since once you flash all sparse chunks you'll lose your data partition anyways.
what I'd suggest you to do is
1.backup your data partition using twrp and your internal storage to a pc/sdcard/whatever (twrp doesn't backup your internal storage)
2. flash the firmware just as described on the main thread
3 fastboot boot twrp.img PRIOR to the first boot
4. restore your data
5. connect your phone to USB cable with twrp still open and copy back your internal storage through TWRP's MTP(or use twrp's file manager/aroma FM in case you backed internal storage to sd card)
5. boot your phone.
I never tried backing up internal storage but I already did this when fastbooting and managed to keep my data (settings, apps, etc) .
I just advice you to remove any screen lock prior to backing up your data since your previous pattern/pin/password generally won't work after restoring a twrp backup, but in case you forget it use twrp and go to /data/system and delete locksettings.db and your
lock screen protection will be gone
achintyakv said:
I am on amzin software channel and my build number is NPPS25.137-93-14 (July Security Patch). Will this fastboot method work for me?
Click to expand...
Click to collapse
I don't know, this could brick your phone, but I'm not sure
tapan8914 said:
need cedric amzin oreo update before was on soak oreo ,after upate this phone stay in fastboot mode
Click to expand...
Click to collapse
as I said idk what'd happen if someone did this. the best you can do now is to find some old amzin firmware and fastboot it (do not flash gpt.bin or bootloader.bin, so as not to hard brick your device)
Andrej_SK said:
I was able to lock my bootloader with this firmware (but I wasn't satisfied with official Oreo at all so I unlocked it again and downgraded to Nougat).
Try this (on your own risk only): input "fastboot oem lock" twice (first time for starting the whole process of locking, second time for confirmation). Then, execute commands below, one by one
Code:
fastboot flash oem oem.img
fastboot flash boot boot.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 system system.img_sparsechunk.8
Then, input "fastboot oem lock" for the last time. Your phone should immediately reboot, as mine did. If there will be problem with booting into OS, just reflash the whole system with commands below:
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Edit: as you can see at the screenshots in the attachment, I'm able to lock bootloader with this firmware. First, I reflashed the whole Oreo firmware, then rebooted into bootloader using "fastboot reboot-bootloader" command and at last I tried to relock bootloader which was (once again) successful.
Phone specs: XT1676 (3/16), DualSIM, reteu soft. channel
Click to expand...
Click to collapse
many a thanks, I'll put this on the main thread
Currently on OPP28.85-3
Currect me if I'm wrong, but by what I have been reading,
I cant go from OPP28.85-3 to OPP28.85-16
What I've read, I can't be on bootloader B8.31 (which I am) and since this isn't a "full system" image, just a "patch" for official Nougat to upgrade to offical Oreo, I need to be on Nougat.
If this is the case, could I go back to nougat through a TWRP Zip, or would this need to be done through fastboot commands. I know I need a downgraded Bootloader and I don't think ROM flashing affects anything else but /system
PLEASE correct me if I'm wrong. Just a curious guy who loves learning.