Related
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.
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
chetana22 said:
Dear Team, I have MotoG4 Plus (Model XT1643).
Post selecting the data migration from internal storage to SD card, the phone stopped booting.
[[ Upon pressing the vol + power key ]] __
Restart bootloader screen shows
*oem_locked
*Software status: Modified (in yellow) __
Navigating to Bootloader logs screen, it shows
*failed to validate boot image
*ERROR: failed to pass validation, backup to fastboot Fastboot Reason: Fall-through from charger boot mode
Kindly suggest
Click to expand...
Click to collapse
Are u using dummy bootloader I guess not orginal
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
@ Echo
Hmm, what were you trying to do prior to the soft boot? You mentioned data migration, how were you transferring data?
<<<< I was transferring data from phone memory to memory card via an option which says move media to SD card >>>>
Given your bootloader is locked (OEM_locked), then something's corrupted your boot kernel and thus the bootloader isn't letting your device boot, as it can't verify your stock kernel signatures.
You may have to re-flash your stock ROM - can you remember which stock ROM build you had on your device?
<<<< I have no idea about stock ROM build. If you can help, how would I know since my device is not starting? >>>>
@ usha55
Are u using dummy bootloader I guess not orginal
<<<< I do not know >>>>
---------- Post added at 07:32 PM ---------- Previous post was at 07:26 PM ----------
No need to reflash u have to upgrade the bootloader then u have to flash the stock rom
<<<< How do I upgrade? Please guide >>>>
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
____Mdd said:
@chetana22 thas makes confusion if you write post like that.
You just need to reflash boot.img only not whole ROM. To know the correct version of ROM and boot.img, post your phone's baseband/bootloader version, which is visible on bootloader screen.
Click to expand...
Click to collapse
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
chetana22 said:
Hi.
Im not able to upload the image. Pl. find baseband details below.
Baseband: M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
Pls let me know steps to reflash boot.img
Click to expand...
Click to collapse
If you have locked bootloader, flashing of older boot.img may not work. You need to flash whole firmware.
See here,
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/page8
Download it and flash it, instructions are given there.
If you have important data on your phone, say photos/videos/or any file, then skip "erase userdata" command.. when you get device working, copy your data and then wipe your device.
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
chetana22 said:
Tried the method as given.
At the end ..it is repeatedly showing
FAILED (remote failure)
Click to expand...
Click to collapse
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
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
It does not work
echo92 said:
Which stock firmware are you flashing that gives you this error? Please mention the build number.
You may have to try flashing with the NPJS25.93-14-10 stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash as per below commands if you want to save your data (no need to re-lock your bootloader).
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
Click to expand...
Click to collapse
It does not work
al3al3al3jandr0 said:
It does not work
Click to expand...
Click to collapse
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Now the error sends it to me in the boot.img
echo92 said:
What didn't work, please describe more about what happened?
From your other post, I saw that gpt and bootloader worked. Did you ensure that all the firmware files in your ADB folder are from the same patch? Some of them appear to have different dates. I would delete all the firmware files in your ADB folder (except your minimal ADB filled) and extract a fresh copy of the stock ROM to your ADB folder and try again. Double check you're extracting the NPJS25.93-14-10 ROM.
Click to expand...
Click to collapse
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
al3al3al3jandr0 said:
Now organize the original firmware and download the December OTA, replace the gpt.bin file with the OTA one. Now the error sends it to me in the boot.img
Click to expand...
Click to collapse
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
thank you
echo92 said:
1) Why are you adding the December 2017 GPT.bin to the NPJS25.93-14-10 flash files? Mixing and matching patch levels especially with you re-locking the bootloader can be very risky, and could result in you bricking your device.
2)Are you getting the same error with flashing the boot.img? Can you confirm with an md5 checksum tool (http://www.winmd5.com/ ) that your boot.img (the kernel) has the md5 checksum: 61473507904cc98b5dcc508a1a35e657 If the checksum is different, I urge you again to doublecheck you've copied the right files from the stock ROM. If you're re-locking, you generally must have only the flash files from the same stock ROM patch level, you cannot mix and match old and new stock ROMs.
Again, if you're not sure, delete all the stock ROM files from your folder and re-extract clean, fresh copies from the stock ROM zip.
3)If you've updated to NPJS25.93-14-13 previously via OTA update (the December 2017 stock ROM), then you cannot use this method to re-lock your bootloader and flash the stock ROM. The stock ROM used to re-lock a Motorola device must be of the same build/newer than what you had on your device. You'd have to wait for the NPJS25.93-14-13 stock ROM.
Click to expand...
Click to collapse
ok thank you very much, you're right I'll have to wait
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Adityashankar said:
Sir, how to fix no found bootimage in m0t0 g4plus XT1643
Click to expand...
Click to collapse
Did this happen suddenly, and is this with the stock firmware or using a custom ROM?
You could try flashing the Oreo stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Hello team, I have the same problem like chetana22 but with motorola one xt-1941-4. When i was transfering (probably) virus file from internal storage to usb flash memory, the phone stopped booting.
I have inportant and private files on internal storage, phone have quarantee... What can i do? Pls help
flash latest stock rom and skip the following instruction while flashing
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
MOTOROLA G5S PLUS - Start up failed
My phone is G5s PLUS ... Sorry
Hi All,
Moto G4 Plus XT1643 is my phone model.
Was not being used for past 6 months, and it got stuck the boot screen .
Tried the factory reset, it got stuck in the fast boot.
Then tried the tool given by Lenovo, no luck. The "fast boot" option in the software fails.
Anyway, came to our good old XDA.
tried the options in the forum https://forum.xda-developers.com/t/...c-01-security-patch-fastboot-7-0-8-1.3608138/
Now, i am stuck with the below screens, i have attached them
Allso, do i need to start a separate thread?
Kindly help me out.
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
tried to pass the last stock if I am not mistaken version that is or updated passes without being with bootloader unlocked.
Pranav_dp said:
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
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
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
echo92 said:
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
Click to expand...
Click to collapse
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Pranav_dp said:
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Click to expand...
Click to collapse
If you flashed the April 2018 security patch stock firmware, there are currently no OTA updates, the April 2018 security patch is the latest available.
If you fully flashed the latest firmware as I mentioned, you should be okay to use OTA updates. Just in future please remember to not use OTA updates if you downgraded your device by flashing old stock firmware.
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Daroas said:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Click to expand...
Click to collapse
Without a blankflash new enough to flash to the device, I don't think so. You'd have to consider a JTAG repair, a motherboard replacement or buy a new device.
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 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: