Related
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
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.
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
guillermohs9 said:
Hi! I currently have NPNS25.137-92 running thanks to a TWRP backup I did before going custom Pie on my G5+. I'd like to go back to stock so that TWRP is removed, bootloader locked and I can take official OTAs up to Oreo or whatever it is. What is the best way to achieve this? I could flash the latest Oreo TWRP flashable build, but that way it won't accept OTAs right?
Any help will be greatly appreciated.
Cheers
Click to expand...
Click to collapse
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, with a TWRP flashable build you won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
You will lose your data so backup your stuff.
Wolfcity said:
First thing: You don't have to lock the bootloader to receive and install OTA, this is a widespread fallacy.
And yes, a TWRP flashable build won't be able to apply OTA updates.
To get back on track you will have to flash a full fastboot ROM, best would be the latest one available for your region.
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Oreo builds for the US are ending on 85-17-x (where 17-4 is the latest), for other regions it's 85-13-x , here the latest one is 85-13-5 (December security patch).
Click to expand...
Click to collapse
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
guillermohs9 said:
Thanks for your answer, I'm looking but I guess firmwares for my region (retar) are difficult to find. Flashing retus won't affect the usage? Finally, to flash that image you must unzip it and paste that long chunk of fastboot commands I've seen around here right?
Click to expand...
Click to collapse
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Yes, you have to unzip the firmware in your adb/fastboot folder on your PC and enter all fastboot commands, you can also use a flashall.bat with all commands in it. You have to copy that bat into your adb/fastboot folder too and just click it.
Here's one:https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
There are some tutorials around how to do it all but some are a bit outdated. I'm about to write an actual one.
You need Motorola drivers on your PC:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
and something like Minimal Adb & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=sharing
If you're not familiar with this procedure you can also give Lenovo Motorola Smart Assistant a shot:
https://support.lenovo.com/de/de/downloads/ds101291
Wolfcity said:
No, flashing the US variant won't affect usage. It's possible that you don't receive OTA updates in the future anymore because the ones pushed in your region may be for the other update channel. Would be good to find out which Oreo build has been pushed to your region, maybe you can elaborate it via Google.
Click to expand...
Click to collapse
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
guillermohs9 said:
I'm searching for images for retar channel but with no luck. Having flashed retus image, won't I be getting OTA updates pushed on retus?
You should write that tutorial, there is no such thing as too many well written tutorials!
I'm comfortable using fastboot and adb, I just never used them to go back to stock and finding the right firmware for potter seems hard for what I'm reading.
Click to expand...
Click to collapse
I'll take a look what firmware has been pushed to your region. If you're on the wrong update channel you won't receive OTA updates because Motorola/Lenovo only pushes one update for every location, either the US version (17-x) or the other one (13-x).
I'm writing on that guide but it will be a bit extensive because it should cover unlocking/flashing/rooting/decrypting/locking, the whole thing.
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
BartKey said:
Sorry for interrupting but I would like you have your advise.
I returned from custom pie to 8.1 stock flashed through fastboot. I'm from Belgium, I took the build OPS28.85-17. Reteu channel. This is sept 18 security patch.
I don't receive an ota for an updated security patch.
How can I flash OPS28.85-17-4 without losing data? With some fastboot commands? Wich ones? Tnx for help:good:
Click to expand...
Click to collapse
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Edit: flashed Twrp now it says "bad key" on the unlocked device screen but it boots into stock Oreo.
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
guillermohs9 said:
I flashed the retus Oreo firmware you suggested with the commands you uploaded to Dropbox but upon rebooting I get a "No command" screen and it's stuck there.
Click to expand...
Click to collapse
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Wolfcity said:
Have you omitted the "erase userdata" line?
If that screen appears the device seems to be waiting for a reboot.
Edit: Ok, good to hear it's booting now.
The " bad key" screen is normal, you should have seen it after unlocking the bootloader.
Click to expand...
Click to collapse
It used to say N/A instead. I don't mind. The problem now is that it always tries to boot into recovery.
guillermohs9 said:
....
I get the thing about the region. The device still says it's on retar so with retus firmware it will not take OTAs if I understood correctly.
Click to expand...
Click to collapse
As I said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
wolfcity said:
as i said, depends on which firmware has been rolled out in your country.
What's your actual firmware number?
Click to expand...
Click to collapse
opss28.85-17-4
guillermohs9 said:
opss28.85-17-4
Click to expand...
Click to collapse
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Wolfcity said:
Ok, that's the latest US build, so it can't find OTA now. Btw I don't think that we will see too many updates as the Moto G5+ isn't that new anymore so it's not such a big thing.
I haven't found out which firmware is the right one for your country, if I find out something I'll let you know.
As you said, no need to care about the bad key screen, I just flashed a custom bootlogo to get rid of it.
About booting into recovery, here's a thread about it: https://forum.xda-developers.com/showthread.php?p=74109609#post74109609
First try to wipe cache/dalvik in TWRP.
Than try enter "fastboot oem fb_mode_clear" from PC.
If that doesn't help try the mentioned dd commands from the thread in TWRP terminal.
It's a known problem.
Click to expand...
Click to collapse
Thanks! I figured the same about the future updates, now Motorola is focused on newer devices so december security patch is enough.
I am on stock, unrooted, relocked bootloader now. I used the commands you provided (included erase userdata) then had to flash TWRP, flash magisk, use adb shell and dd to clear that misc partition (so it boots into system), and finally did
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
to relock bootloader. It works as expected now and it's ready to be used by anyone.
Thanks a lot
Wolfcity said:
No need to apologize for interrupting, this is not a private chat. 17-4 is the US firmware, you'll have to change to OPS28.85-13-x to receive OTA updates here in Europe. Even when your "about phone" setting tells you you're on reteu, the firmware number is what makes the difference.
If your main goal is not to lose your data you can flash the 17-4 firmware by fastboot and omit the line "erase userdata". But you still won't receive future OTA updates as you're on the wrong firmware. You can try to flash the latest available fastboot firmware for Europe which is OPS28.85-13-3 and omit the "erase userdata" line too. The source for the firmwares is posted above, it's https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
As written above, a guide how to do it will follow.
The fastboot commands are the same as in the flashall.bat also posted above:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thanks a lot @Wolfcity
I came from OPS28.85-17, without updates available.
Now I flashed OPS28.85-13 with your instructions not to erase userdata.
Checking for updates: 13.3 available -> installed
13.5 available -> installed and "up to date" security patch dec 2018
:good:
@guillermohs9 @BartKey: Great to hear everything is working! I will add your experiences to the upcoming tutorial.
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Flash the complete stock rom using fastboot and lock the bootloader and then update the device through OTA.
ksamm97 said:
I received an update Oreo, when I tried to install it failed and displayed a message "Error" and restarted. Help me to update my mobile to latest version. I cleared cache partition, still no luck.
I have unlocked bootloader and on latest stock ROM.
Screenshot attached !!!
Click to expand...
Click to collapse
Facing the exact same issue here.I think the latest stock oreo needs locked bootloader to flash
No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
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 reboot
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.
I've custom Oreo installed on my phone. Which firmware package should I install?
echo92 said:
No need to relock the bootloader, but you must revert back to unmodified stock firmware on your device before updating. Without seeing what error it is, it's difficult to say. A locked bootloader strictly enforces having the unmodified stock furnace, which is why an OTA update is more likely to work.
Try this:
1) download the NPJS25.93-14-18 firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Only use this if you have not updated to Oreo and you are still on NPJS25.93-14-18.
2)unzip the fastboot ROM, delete any old stock ROMs from your ADB folder and copy the stock ROM over.
3) assuming you had NPJS25.93-14-18 already on your device, flash the firmware with the following instructions - no need for the GPT/bootloader. Ensure you have your data backed up, as you may have to factory reset if you encounter instability.
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 reboot
That should get your device into an OTA friendly state without erasing your data. If that doesn't work, I suggest waiting for the Oreo fastboot ROM.
Click to expand...
Click to collapse
tobey_onk said:
I've custom Oreo installed on my phone. Which firmware package should I install?
Click to expand...
Click to collapse
At the moment, we only have the stock Nougat firmware to revert to - Oreo firmware doesn't seem to be out yet. However, flashing stock Nougat over custom Oreo may appear to come with some risk of losing IMEI, so be careful. You could try the TWRP flashables, be aware the stock ROM is only 32 bit.
I do not know whether my EFS and Persist are intact but I have backed them up. I had installed Pixel Experience 9.0 and then restored my TWRP backup to go to Stock Oreo, Build Number: OPSS28.85-13-5. This is my current Build, unlocked, rooted and has TWRP.
Can I follow this (https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738) guide to go back to Stock Nougat and then upgrade to the latest official update from moto?
I am asking to confirm as the Stock ROM given in the guide is Nougat ROM and I am on Oreo as mentioned above. I won't have any problems right? I do not want to lose VoLTE and my IMEI.
Any help will be appreciated.
Installed Oreo ROM via fastboot on my Moto G5 Plus [RETIN/Indian/ XT1686]
I am sharing my experience here so that it might help someone looking to flash stock ROM via fastboot. This is not meant to be a tutorial, but I will list out the steps I followed. I am not responsible if you mess up or hard/soft brick your device when following the steps I mentioned below. Always make a backup of your data/photos/videos/music and whatever else. Also make a backup with TWRP to be safe.
So instead of following the guide linked in the above post, I followed this one and successfully unrooted and returned to stock: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
But I did not use the ROM linked by the OP in that thread. Instead I downloaded this one : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This RETIN ROM works for me because I have the Indian XT1686. I don't know if it matters but I had the same version (13-5) before, but I am not sure whether it was RETAIL or RETIN.
Anyways guys make sure you download the right ROM for your device if you are going to install via fastboot. You can download the right ROM for your device from here: https://mirrors.lolinet.com/firmware/moto/potter/official/
There are different folders for ROMs of different regions in the above link. So carefully download the one your device is compatible with.
Also, I installed fastboot drivers from here: https://forum.xda-developers.com/showthread.php?t=2588979
Follow the instructions and also follow the video tutorials in the post to install fastboot drivers if your phone isn't detected in fastboot.
Then once I had downloaded the ROM and installed ADB, I extracted the ROM zip into a folder. Copy pasted ADB Files into the same folder (download ADB Files that worked for me _ attached to this post below).
FInally I put my phone in fastboot (turn off phone, then press volume down and power simultaneously till fastboot shows up). Connected the phone to my PC. Then opened CMD in the folder where I had extracted the ROM and copy pasted the ADB Files. To open cmd in a folder, just type cmd in the address bar of the folder and press enter.
And then I copy pasted the following code into the cmd window:
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
The above commands will run when pasted in cmd and your phone will be flashed with the ROM. It took a couple minutes to install and then I had to press enter while still in cmd to reboot the phone. Then the phone rebooted. Took a couple minutes more to boot, so stay patient. Then once the phone booted, I disconnected it from my PC and set the phone up as usual. DO NOT disconnect the phone when the fastboot commands are running and the ROM is being flashed. Note that the above fastboot commands will only flash the ROM. It will not lock the bootloader.
If you want to lock the bootloader then follow the instructions here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
Note that I haven't locked my bootloader. So you will have to try and see for yourself whether it locks your bootloader.
Also once I booted up I got update notification and was able to update to the Feb 2019 OTA security update. So I can for sure say that updates work. VoLTE, calling, camera, almost everything I checked works.
Cheers. :victory: