Related
This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
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 boot boot.img
fastboot oem lock
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !
Thank you so much, my Bootloader is locked again.
̶C̶a̶n̶ ̶y̶o̶u̶ ̶p̶l̶e̶a̶s̶e̶ ̶g̶i̶v̶e̶ ̶u̶s̶ ̶f̶i̶r̶m̶w̶a̶r̶e̶ ̶f̶i̶l̶e̶ ̶t̶h̶a̶t̶ ̶y̶o̶u̶ ̶u̶s̶e̶d̶?̶
First its the command to relock de BL?
before the commands to flash system?
AlmapekeDj said:
First its the command to relock de BL?
before the commands to flash system?
Click to expand...
Click to collapse
You need to reflash system
With me didn't worked. It says "Not signed rom"
CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Redownload stock
CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Did you get it already? Still need it?
Anyway, if anyone else needs it https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
This is the only one that worked signed for me, XT1672
my imei is 0 already tried everything but I did not have any results help me please it's an xt1672
jonathars said:
my imei is 0 already tried everything but I did not have any results help me please it's an xt1672
Click to expand...
Click to collapse
Reflash stock rom
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work
infixremix said:
This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
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 boot boot.img
fastboot oem lock
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------
You are amazing !!
Hi,
doesn't work for me. Tried from here:
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Moto G5 - Jan 2017 firmware NPP25.137-15 and
Moto G5 - Nov 2017 firmware NPP25.137-93 (Moto G5 - Aug 2017 firmware NPP25.137-33/NPP25.137.33-10 not tested yet).
Error when flashing boot.img:
C:\g5\010117\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.583s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 1.035s
anyone an idea what's going wrong?
D.
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions
TheFixItMan said:
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions
Click to expand...
Click to collapse
thanx!!!
carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
RSD Lite only emulates Fastboot inside the application.
Idk if you can flash the stock rom with an locked bootloader, if it is signed, you can, otherwise, no.
My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.
lmacmil said:
My XT1625 has an unlocked bootloader and TWRP installed. Today I got a notification that the Sept security patch was available so I downloaded it and tried to install. I was paying attention until I noticed it booted back into TWRP and does it everytime so I guess accepting and installing that patch was a no-no. I got it to boot into Android from instructions in another post.
Can I locate the patch in TWRP and flash it from there? Btw, I did notice that the patch was only 49MB so it clearly wasn't the entire Nougat ROM.
Click to expand...
Click to collapse
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please use always search function as this happens every week a few times and same question is answered already enough.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.
strongst said:
You cannot flash an official OTA update. You need to be on official recovery for this. Have a look at here, same question https://forum.xda-developers.com/moto-g4-plus/help/luck-moto-g4-plus-flashable-logo-bin-t3701652
I saw that other post and edited mine to acknowledge that I saw the fix (see last sentence of 1st paragraph.)
For update its advisable to use the full stock rom to be flashed with fastboot like this one https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Thanks. I probably won't go to that much trouble.
Please use always search function as this happens every week a few times and same question is answered already enough. I generally do.
Also worth having a look here https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 and also ask here.
Click to expand...
Click to collapse
I rebooted and it went back to TWRP again. I will ask how to fix this in the help thread.
lmacmil said:
I rebooted and it went back to TWRP again. Will I have to boot to fastboot mode and select factory mode every time now or is there a fix that will boot into Android instead of TWRP?
Click to expand...
Click to collapse
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I will give it a try.
lmacmil said:
I will give it a try.
Click to expand...
Click to collapse
use the following script :
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 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
____Mdd said:
Try to run these commands from fastboot..
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Got error messages:
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.008s
siddhesh9146 said:
use the following script :
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 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
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?
@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
lmacmil said:
Is this going to wipe my system like a factory reset? If so, can I just restore the backup I made after I installed TWRP initially? Or just do a factory reset?
Click to expand...
Click to collapse
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...
____Mdd said:
@lmacmil ignore it, use both commands then try to boot.
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
Don't use it if you are thinking to just run script and not to flash... since it has "erase modemst1 & 2" it will erase modem, but will not flash fsg/modem, also "erase data" will wipe everything on phone.. this can put you in trouble..
Instead of doing this, as strongst said in his post, flash complete firmware, see the link for september's update he gave in his post.
Then move everything from your phone to PC (images / video/ etc)
Then flash firmware...
Click to expand...
Click to collapse
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.
lmacmil said:
Still boots to TWRP. Maybe this is the time to move to LineageOS 14.1. I was going to wait until 15 was stable but if I'm going to lose everything, I might as well get more up to date.
This seems to have killed my cell signal too. Just noticed that last time I booted to Android.
Click to expand...
Click to collapse
Did you flash complete stock ROM ?
Move your files to External Storage then try it.
____Mdd said:
Did you flash complete stock ROM ?
Move your files to External Storage then try it.
Click to expand...
Click to collapse
I decided since I would have to reinstall all my apps anyway that I would flash LineageOS 14.1, which I did. I did the appropriate wipes (data, system, cache, Dalvik/ART), then flashed the latest nightly and Gapps. It was successful but it's still booting into TWRP and I still have no cell service. I thought that a complete wipe and installation of new ROM would correct those issues but it did not. And since it didn't, I'm not confident that flashing the stock ROM would either but unless there's something else to try, I will do it. One concern I have is I have a plain G4 and the ROM is for the G4 Plus. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Maybe I should restore my original Nandroid backup first and see if that fixes things.
lmacmil said:
. My build was NPJ25.93-14.5 and I think the Plus build is NPJS... Not sure if that makes a difference.
Click to expand...
Click to collapse
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here
____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
If this too doesn't work, then you have to find correct firmware for your phone and flash it..
EDIT: for easiness to find correct firmware, restore backup, then see "about phone" for build number, it will help to find firmware..
EDIT-2:
I found 2 firmware of version you said,
But one says Amazon and another doesn't. You have Nandroid, restore and check your phone build..
Then go for following one correctly..
AMAZON : Click here
Non-AMAZON : Click here
Click to expand...
Click to collapse
Mine was the non-Amazon version. See attachment. The software channel was "retus" and the baseband version also said "ATHENE_RETUSA_CUST" The Amazon version software channel is amz.
I was able to get the bootloader unlock code from Motorola and they don't allow the Amazon versions to be unlocked.
I'll try your suggestions. Thanks for your continued help.
____Mdd said:
NPJ25.93-14.5 was for Amazon variant if i am not wrong.
I don't know but in past that two commands [fb_mode_set and fb_mode_clear] worked fine for this problem.
Try this thing, [reboot to bootloader and flash TWRP but with fb_mode_ commands]
- fastboot oem fb_mode_set
- fastboot flash recovery twrp(name).img
- fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is what I got:
D:\Computer\Minimal ADB and Fastboot>fastboot devices
ZY223N5GLF fastboot
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Computer\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12530 KB)...
OKAY [ 0.402s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.190s]
finished. total time: 0.595s
D:\Computer\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.001s]
finished. total time: 0.001s
=================================
Not sure why I'm getting the bootloader error messages but I backed up just the bootloader recently so am going to restore that and see what happens.
@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...
____Mdd said:
@lmacmil that "not found" is ignorable, just check you get "OKAY" after one command ends... Since GPT and Bootloader commands got "OKAY" they are flashed successfully..... Go for complete firmware...
Click to expand...
Click to collapse
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right? If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.
lmacmil said:
I guess I need to bite the bullet and do this. It will install stock recovery and erase TWRP, right?
Click to expand...
Click to collapse
Yes, it will install stock recovery, you will have to install TWRP again.
If that's the case, and I don't relock the bootloader, will I be able to accept the OTA update? Or does an unlocked bootloader prevent OTA updates?
Click to expand...
Click to collapse
It will be fine, You will have successful installation with unlocked bootloader too, no need to lock back..
Last question: I just extract the firmware .zip file to the same folder where fastboot and adb reside? Then type the commands one by one (or copy/paste from the script shown in the thread about flashing stock firmware.)
Thanks again.
Click to expand...
Click to collapse
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..
____Mdd said:
Yes, it will install stock recovery, you will have to install TWRP again.
You did right, that's why there is "OKAY" when command end, see your own post where you asked for "not found" error... Keep Going..
Click to expand...
Click to collapse
Success! Just flashed the stock Nougat ROM and as soon as it booted up, I let it download and install the Sept security patch. I am now on NPJ25.93-14.7.
Thanks again for all your help.
Lee
Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11
if anyone knows anything about this PLEASE post I'm desparate.
OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?
beatlesfan5858 said:
OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?
Click to expand...
Click to collapse
I think once you leave stock, you won't receive OTA's again, even if you re-flash and lock bootloader. You will have to download the updated ROM and manually install it.
lol... You are a lot newer than mine (which I thought was current) and I have NPN25-137-83 (August 1, 2017) and I am completely stock with locked bootloader, never touched it. Are you sure you flashed the right software channel image for your device, retus?
There has only been a couple OTA updates for this device ever, your not missing anything. And BTW, your "modified" status is normal until you get your first OTA, it should then become official. Note that Bootloader Status will ALWAYS be a 2 and will never go back to 0, it isn't possible for anyone but Moto to do that.
beatlesfan5858 said:
Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11
Click to expand...
Click to collapse
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.
reCoded said:
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.
Click to expand...
Click to collapse
OK where can I find the stock ROM NPN25.137-83? So the steps would be....
1. Download stock rom
2. oem lock device
3. Flash stock rom/ erase everything?
EDIT: to clarify where I'm at right now, I re-unlocked bd and rooted with Magisk, but have root access gives me nothing but trouble. I have a broken camera now since I've rooted, the app doesn't want to open. No doubt about it, I want to go back to the way everything was normally, receiving OTA updates and have official software. I never should've messed with anything.
OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?
beatlesfan5858 said:
OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?
Click to expand...
Click to collapse
You'd likely have to wait for the next US retail firmware to be leaked to be able to lock your device.
Given that you've flashed the NPN25.137-92 firmware, you've likely still got the bootloader from that firmware, and so using an older NPN25.137-83 firmware won't permit you to re-lock your bootloader. You cannot downgrade bootloaders (and probably reports a security downgrade error if you try).
Also, now that you likely have a different system to your bootloader, I would caution against taking OTA updates until you've flashed the newer US firmware. I don't know if bootloaders for US firmware are different or the same as other region's firmware, and hopefully someone knows (or can compare firmwares), but mixing builds with different patch levels or regions could lead to a hard brick if taking OTA updates. Be careful.
Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!
Please someone tell me! I really need my phone to be functional.
beatlesfan5858 said:
Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!
Click to expand...
Click to collapse
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.
reCoded said:
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.
Click to expand...
Click to collapse
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps
beatlesfan5858 said:
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps
Click to expand...
Click to collapse
When your device starts up, does it say "ID: bad key" by chance?
reCoded said:
When your device starts up, does it say "ID: bad key" by chance?
Click to expand...
Click to collapse
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way
beatlesfan5858 said:
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way
Click to expand...
Click to collapse
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
Code:
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 boot boot.img
fastboot oem lock
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
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 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
Hopefully, you should be back to stock and able to receive software updates.
reCoded said:
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
Code:
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 boot boot.img
fastboot oem lock
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
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 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
Hopefully, you should be back to stock and able to receive software updates.
Click to expand...
Click to collapse
Alright i'm going to do everything exactly like you said. I'll be about 15 minutes, will report back. stick around please, and thanks so much for all your help.
Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.
beatlesfan5858 said:
Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.
Click to expand...
Click to collapse
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?
reCoded said:
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?
Click to expand...
Click to collapse
It wouldn't re-lock because it said the boot img wasn't signed. I know if I try with the current potter version I have, that it will relock, but I was afraid I wouldn't receive OTA updates if I did that.
edit: to clarify, I had downloaded 137-92 from the above link, and managed to relock it before on that version. However I was paranoid about ota updates so i re-unlocked, and re-rooted, which turned out to be a mistake. I'll try re-locking and flashing 137-92, which is the nov 1 2017 security update btw.
Hi! I could really need some help over here!
I have a G5 Plus that i bought in Sweden, Europe. I unlocked bootloader, and flashed a ROM.
But now i´m going to sell it, so i need to reflash the stock image (ROM). Also i need to relock bootloader.
Can someone help me find the latest, working firmware, and also with the right commands to use with fastboot to do this?
Modell is: X1685.
Why would you need to relock the bootloader? I guess you will sell the device warning the person that it doesn't have warranty, right?
I was going to type this but then found this post....
lvvine said:
NPN25.137-35
https://drive.google.com/file/d/0B3G...ew?usp=sharing
Watch the Video which will help you to flash the firmware.
https://www.youtube.com/watch?v=blYQ28DZJQk
Use FastBoot Command to flash the firmware (Backup you data as it would erase the internal Memory)
Fastboot command:
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 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
eemgee said:
I was going to type this but then found this post....
Click to expand...
Click to collapse
Be careful, it will flash the bootloader. If you have a newer version of the bootloader than th one you sumbitted, you will harfbrick your device.
M1810 said:
Be careful, it will flash the bootloader. If you have a newer version of the bootloader than th one you sumbitted, you will harfbrick your device.
Click to expand...
Click to collapse
If the stock ROM is older than what you have on your device, then the bootloaders usually prevent you from downgrading.
Hard bricks usually do not happen when you downgrade, they happen if you've downgraded and then take OTA updates (mismatches between the bootloader patch level and system patch level are a culprit). Best way to avoid this is to not downgrade.
At any rate, you cannot lock a bootloader with a build older than your existing stock firmware, regardless of custom ROMs flashed. You need a firmware of the same or newer build than your device stock firmware to relock. To the best of my knowledge, NPNS25.137-33-11 appears to be the newest or nearly newest firmware for EU devices. You can download from here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ please confirm that this firmware is suitable before flashing.
You could try re-locking with other firmware, however NPN25.137-35 is for US devices, so would not likely receive OTA updates if flashed onto EU devices. As for warranty, the warranty isn't transferable as far as I know and as Motorola's got a record of the device being unlocked, the warranty is void. However, under EU consumer laws, you or the buyer could still get repairs if you're both resident in the territory. Would be wise to check this and let the buyer know.
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
syl0n said:
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
Click to expand...
Click to collapse
Original current gb version is as screenshot, anything else may screw up you phone.
syl0n said:
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
Click to expand...
Click to collapse
hi, i have similar issue. can you tell me how you fixed it?
Smeagal192 said:
Original current gb version is as screenshot, anything else may screw up you phone.
Click to expand...
Click to collapse
There appears to be no fastboot flashable file for this version available anywhere on the internet. I've searched for days and had absolutely no luck!
Looks like both the OP and I are stuck on custom ROMs. Why Lenovo don't make these available I don't know...
If anyone knows of anywhere to get this please help us.
EDIT: Oh, also mine is XT1684 which I've seen virtually nothing about on XDA.
darkglobe87 said:
There appears to be no fastboot flashable file for this version available anywhere on the internet. I've searched for days and had absolutely no luck!
Looks like both the OP and I are stuck on custom ROMs. Why Lenovo don't make these available I don't know...
If anyone knows of anywhere to get this please help us.
EDIT: Oh, also mine is XT1684 which I've seen virtually nothing about on XDA.
Click to expand...
Click to collapse
Mines a 1684, seems moto made 2 models for UK with same specs.
Regarding fastboot did you extract download zipped archive into fastboots folder.
When I say download follow the link above to firmware centre, if using phone to browse you need phone in landscape otherwise you cannot get name.
Smeagal192 said:
Mines a 1684, seems moto made 2 models for UK with same specs.
Regarding fastboot did you extract download zipped archive into fastboots folder.
When I say download follow the link above to firmware centre, if using phone to browse you need phone in landscape otherwise you cannot get name.
Click to expand...
Click to collapse
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it. Thanks though.
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.