Related
So, you've unlocked your bootloader and are enjoying some rooted goodness on your phone. You then realise you've got an issue with the phone and forgot to make a backup of your stock ROM! Not to fear, this guide is for you! This will reset the phone back to it's out-the-box state, locked bootloader and all, running the latest ZNH2KAS3P0 build so you can return it for RMA/sell it. This also works to go back to CM13.1.2 from Oxygen OS.
It's recommended that you have adb/fastboot in your System Path. This makes it easier to run commands as you don't always have to 'in' your adb/fastboot folder to run the commands. This guide should help you with this but if you don't want to do this, please copy/extract any files into your adb/fastboot folder before continuing...
1. Download the factory image
Cyanogen released the factory image for the OPO but didn't include any batch files to automate the process. I've repackaged the images into two seperate ZIPs:
ZNH2KAS3P0 16GB: DOWNLOAD
md5: be471f6bfc707f86a0af1eb175ec9aad
ZNH2KAS3P0 64GB: DOWNLOAD
md5: c371bc0cb4ef67999d21f5275c5a587b
*** These ZIPs are not flashable so cannot be flashed via TWRP ***
2. Extract the factory image
Using your favourite file extraction program to extract the package to your Desktop (I use 7-ZIP). *** Remember, if you don't have adb/fastboot in your Path, extract the image into your adb/fastboot folder ***
3. Flash the factory image
Once you've unlocked the bootloader, and rebooted the phone, turn the phone off and back on into fastboot mode and reconnect it to the PC. You can now run the flash-all.bat (Windows) or flash-all.sh (Linux) file. These automate the flashing process. Once complete, the phone will reboot.
*** Some users have had issues using the script in Linux so in these cases extract the ZIP file and flash each IMG individually ***
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img (the filename is the same in both ZIPs so make sure you're using the right one for your device)
fastboot reboot
4. Reset the tamper flag/lock the bootloader
There is a flag/bit on the phone that is triggered when you unlock the bootloader and even relocking it won't change this flag back to standard. Luckily, @Mnt-XDA has a script that you can flash which resets these flags so OP/anyone else is none the wiser! To do this, read and follow THIS thread
5. Reboot the phone
Says it all really - you're done!
EddyOS said:
3. Unlock the bootloader on your OPO
Click to expand...
Click to collapse
And why do you need to unlock the bootloader to flash the factory image ????
RalphLauren said:
And why do you need to unlock the bootloader to flash the factory image ????
Click to expand...
Click to collapse
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
EddyOS said:
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
Click to expand...
Click to collapse
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
RalphLauren said:
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
Click to expand...
Click to collapse
I know what you mean, but it's the same with Nexus devices - you cannot flash the image unless the bootloader is unlocked
indesisiv said:
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
Click to expand...
Click to collapse
Yeah was looking to add that in at some point, this is still a work in progress as it were...I'll add it in when I get a chance
EDIT: Added
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
lemonspeakers said:
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
Click to expand...
Click to collapse
To be fair, of someone doesn't know how to do that they really shouldn't be here in the first place!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
This should be a sticky!
banjotrold said:
This should be a sticky!
Click to expand...
Click to collapse
I agree! This definitely should be a sticky.
Sent from my One using XDA Premium 4 mobile app
Which one of these files would be the kernel? I am having wifi issues and am wondering if I would be able to reflash and fix it.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock (if you wish to relock the bootloader. If not, ignore this part)
fastboot reboot
boot.img
EddyOS said:
boot.img
Click to expand...
Click to collapse
Thank you. Any reason why I can't just fast boot the boot.img file only (ala carte)? I am on CM11s rooted with TWRP.
I fastboot flashed the boot.img file sucessfully. It did not fix my wifi problem. So, I tried fastboot flashing the NON-HLOS.bin file. It appears to have an error code. Here is the result.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kevin work>cd desktop/android-sdk-windows/platform-tools
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot devices
9f66970a fastboot
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot flash mo
dem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.306s
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot reboot
< waiting for device >
^C
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>
Any idea as to why it failed?
reboot time
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Xeon_IV said:
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Click to expand...
Click to collapse
As you can see from my command prompt script mine did not want to reboot. I ended up unplugging the phone and rebooting.
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
Click to expand...
Click to collapse
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Click to expand...
Click to collapse
Is your phone the Chinese OPO or the CM OPO?
CM OPO coming from paranois android
Hello, I'm trying to help people who installed the soak test of Lollipop but is not enjoying the ROM with lots of bugs and want to go back to KK.
THIS IS ONLY FOR XT1225, BRAZILIAN FIRMWARE RETAIL UPDATED VIA OTA
YOU NEED TO HAVE YOUR BOOTLOADER UNLOCKED
It will work even if you have root on lollipop
Do it at your own risk!
So, this is the procedure:
DOWNLOADS
1 - Download the Stock ROM from here:
RETBR_XT1225_4.4.4_KXG21.50-9
2 - Download Motorola Drivers from HERE
3 - Download Moto Fastboot from HERE
* IT NEED TO BE MOTO FASTBOOT, known as "mfastboot" . Android Fastboot wont handle the system flash.
INSTRUCTIONS
1 - Backup your phone, otherwise you will lose everything on it
2 - Extract ROM files to a folder (I did on " C:\MAXX\ " )
3 - Extract Moto Fastboot files on same folder you extracted the ROM
4 - Shutdown your phone and put it on fastboot mode (when off, press Power Button + Volume down)
5 - Plug your phone on your PC
6 - Install Motorola Drivers NOW. (For me it only install the driver at this time. If you have the proper driver installed already, skip this step)
7 - Open a command prompt and go to the folder that you extracted the ROM and Moto fastboot
8 - Now, you need to type every line, pressing enter when is a new line and waiting the process to be sucessfully
Code:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
For me it worked, now your phone will reboot and boot right again on KK
I had tried to do with RSD Lite but it always fail on flash the partition.
So, this procedure above is tested by me and it works.
Well all i just did was to restore my twrp backup and then flash my radio.img and that's it didn't lose anything and my cell works like charm just like before flashing lollipop
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
remember that this tutorial is ONLY FOR WHO UPDATES WITH OTA.
if u updated the phone with official OTA ,u can t downgrade to 4.4.4
or if the firmware img of 5.0.2 will go out and u will flash it U CAN T GO BACK TO 4.4.4 either.
always make a nandroid backup in twrp of 4.4.4 .it will be useful.
I've received a OTA without TWRP.... so, I did not could make a nandroid
Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
This was the case with the 2013 Moto X, there is no such problem with the 2014 model. It is unlikely to be a problem with the XT1225. Motorola learned from that mistake.
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
arcaneck said:
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
Click to expand...
Click to collapse
Did you install the lollipop via OTA after flashing brazilian firmware ?
yes i did
It's the same procedure but with the mx firmware
works fine thanks
Works for me too
do you have the mx ota?
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
I've installed the zip file of the soak test (I didn't receive it through OTA), will this procedure work for me? Really tired of the instability of 5.0.2
I have the same problem
megadu said:
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
Click to expand...
Click to collapse
I have the same problem.
After the command "mfastboot flash boot boot.img ". Do not process more.
Can anyone help me? Please!
Have you unlocked the bootloader?
boot.img can never been be downgraded. If you downgrade from version 5.x to 4.4.4 you have to skip that file.
I update my motorola using this guide http://forum.xda-developers.com/droid-turbo/general/guideinstall-lollipop-ota-root-ur-moto-t3029690 , can i do the downgrade ?
Thanks!
im have the same question, im using now cm12 with twrp, bootloader unlocked. can i go back to stock 4.4.4 using this tutorial? its safe?
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
I seem to have an issue that appears frequently, yet I cant find an answer.
This is a fix to Remote: FileWriteFailed
So, I was trying to reflash stock again for multirom and it fails. It can erase everything yet cannot flash anything. Basically:
Writing 'bootloader' (remote: (FileWriteFailed))
It shows up Signature Match, so I decided to continue
It sends boot, boot flashes
Anything else, I get the same Remote FileWriteFailed.
I thought that my partitions killed themselves again, so I tried flashing TWRP
Fails with same error.
I looked and found I can just boot it. So I tried and get this:
Command: fastboot boot twrp.img
downloading boot.img...
FAILED (command write failed (No error)
Restarted bootloader to try again
Recovery flashed. Im feeling confident
I go and try to update via update image
Flash bootloader OKAY
Command: fastboot update -w image-nakasi-ktu84p.zip
Archive doesnt contain *.sig
Checks everything, makes partitions
Everythings okay
Fix is (if you have sdk already)
So, basically, you have to erase System, cache, userdata, boot and recovery with fastboot erase.
Then find your factory image from google and download it
Extract everything and move the image-nakasi-*****.zip and bootloader.img to your sdk folder
Flash bootloader
Use command: fastboot update -w image-nakasi-*****.zip
Wait
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?
CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked. That's weird, I thought a phone with open bootloader would not receive OTA, but mine does.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damn thing.
Everything works fine, except for Netflix that can't be installed no longer and my bank software who keeps complaining.
C:\MinimalADBFastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.052s]
writing 'logo'...
OKAY [ 0.099s]
finished. total time: 0.161s
C:\MinimalADBFastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.285s]
finished. total time: 0.689s
C:\MinimalADBFastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.491s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.364s]
finished. total time: 0.861s
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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
-------------------
Flashing:
-------------------
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
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
You can get signed images from Lenovo Moto smart assistant app, just go for rescue and let the firmware gets download, then go to the c/LMSA/ROM there you can find the firmware which has signed, use that image for locking bootloader, then you can lock your bootloader.and don't get anger on wolfcity he just try to help you as, some person don't know how to lock bootloader so they just post on XDA without reading the other thread only.
CanadianGixxerman said:
@Wolfcity
Unlike you supposed, I just did not throw my problem in the forum and waited for someone else to hand me a solution on a silver plate. I did do my homeworks, I did *MANY* searches, I did see the post you pointed me toward, that one and many many others that resembled it closely. But this whole endeavour did not lead me to my expected objective, which is to relock my phone. I am in the same loop I was in when I started trying : The second time I issue the «fastboot oem lock» command, I get this :
C:\Moto potter>fastboot.exe oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.003s]
finished. total time: 0.003s
And the BL does not lock.
Click to expand...
Click to collapse
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.
Wolfcity said:
I don't wanted to sound rude or something like that.
You didn't mention that you used all the fastboot locking commands in you first post, you just posted three lines of flashing boot, recovery and logo.
So no offense.
What sounds strange to me is that Netflix and your banking app aren't working with an unlocked bootloader. Normally these applications are looking for traces of rooting methods like magisk or SuperSU. I'm unlocked and rooted with magisk and Netflix is working for me if I put in on magisk's hide list. Maybe you have some files on your device that trigger these anti rooting mechanisms? Sometimes just a file or folder named magisk could be enough.
Click to expand...
Click to collapse
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.
CanadianGixxerman said:
No hard feelings.
It turns out that with your instructions (1st part : Locking) I was sucessful at my aim, finally. It did whine again about the signed image requirement after line 2, I continued [9 sparsechunks though, not 5 ... ], then, upon hitting «enter» after the last line [fastboot oem lock], Shazam, it locked.
You may be right about some left over garbage files [or traces of] that could still be present in the file system. I have loaded many customs roms last year on this phone, magisk and SuperSu as well.
Last but not least : Thank you.
Click to expand...
Click to collapse
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.
Yeah this same thing happened to me today morning.. most guides have till sparsechunk4.. where as oreo has uptill 8.. so u need to flash the rest i.e 5,6,7,8. And then it will lock..
Wolfcity said:
Good to hear it worked out for you at last.
Seems that these "unsigned" messages are nothing to worry about to much. Sorry for the "sparechunk thing", copied the wrong flashall.bat file, this is the one for Oreo :https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
with 8 sparechunk files.
Last but not least: You're welcome.
Click to expand...
Click to collapse
I also had same error. Followed what you said. Finally locked bootloader. I am very happy now.
Thank you.
Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.
[email protected] said:
Might be good for someone who has gone through it, to make a new write-up, with current info. The longer these phones have been out, and bootloader unlocked, the more fragmented the info gets. It gets harder to know what currently works, and what could possibly "fubar" the phone.
Click to expand...
Click to collapse
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.
Wolfcity said:
What do you mean? An "locking BL guide" or something more complete like "flashing/locking/encrypting/rooting"? I'm willing to that but I have to know what you guys need.
Click to expand...
Click to collapse
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.
[email protected] said:
Sure,,,, all of it! I unlocked my first G5 plus a year and a half ago. I have hard bricked it 3 times, and now use it for a test phone, as it has an addison bootloader. My everyday G5 plus is unlocked and rooted, but I've kept it on stock roms and kernels, due to a little fear of how easily these can be corrupted. I am certainly not ignorant of most of the workings with these, even going so far as to use Qualcomm's factory utilities to dig deep inside. However, that being said, what worked when I first unlocked my original, isn't totally pertinent today. Nougat and Oreo factory roms, nougat, oreo, pie developer roms, 64 bit and 32 bit, all add to a confusing set list of what can be safely done without irreversible consequences. I've kept up on these forums for almost 2 years, but the fragmentation of guides makes it confusing enough for myself, much less a novice. Example of things that can go wrong to unsuspecting, is the loss of touchscreen with stock oreo. I haven't experienced it, but it is out there. I'm just saying it would be hugely beneficial for all, if we could get some current guides, stickied in place of our outdated ones. I have the test phone that I have put through the wringer, and am more than willing to use it as a guinea pig for any other processes that may add to the guides.
Click to expand...
Click to collapse
You're lucky you have the ability to financially purchase a second G5 Plus to use as a failsafe. When I purchased mine it was roughly around $300-400 (was brand new) so to have purchased another at the time wasn't an option, and may as well purchase a 700+ flagship with that money. To this day I've owned over 30 devices and tested well over that. Thus far only the Galaxy S2 and the Motorola G5 Plus were the only two that have surpassed a year with good stable service. I don't even purchase the phone cases cause devices are supposed to be visually appealing like cars, because tech will always be sexxy. Anyways, my point was since the Photon Q back in early 2014 to this G5 Plus, I've really liked Motorola. If you take the time the align this phone purrs. But I need to upgrade soon as.. Thinking of getting a Pixel 3 when it reaches my shores.. Anyways, it's 1:28am, goodnight.
I was able to purchase the second phone for less than $100 US, slightly used. So it was a no brainer to have a guinea pig phone.
Wolfcity said:
An unlocked bootloader has nothing to do with getting OTA updates. At least you get the unlock code from the manufacturer himself.
Only changes in /system or /vendor like rooting or other tweaks make OTA fail.
About locking the BL, a bit of research would have taken you here: https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
For Oreo the whole sets of commands are for
Locking:
-----------------
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
-------------------
Flashing:
-------------------
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
--------------------
Edited because of wrong number of sparechunk files for Oreo firmwares.
Click to expand...
Click to collapse
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them
Mr.BUBU said:
Hi!!
I need to relock my Moto G5 Plus, because my country use a Covid App to transit trough states.
And I need it to use because I´m a essential worker. This App check the locked / unlocked devices.
I Know that Netlix do the same, but it never mattered to me to that app.
Now I really need to Re Locked my phone
I have tried several methods.. and doesn´t work any of them
Click to expand...
Click to collapse
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
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 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
Second set:
Flashing firmware.
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
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.
Wolfcity said:
You can orientate yourself by this guide but as the one is for Nougat you need to correct the number of the sparechunk files:
How to re-lock Bootloader of all Potter version
Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader. DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm...
forum.xda-developers.com
So the first set of commands should be:
First set:
Lock.
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 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
Second set:
Flashing firmware.
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
Device is now full stock with locked bootloader.
For the second set of commands you can use a flashall.bat file like this:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
It may look like the first set would be enough but that's not true, you have to flash the whole firmware afterwards.
Be aware that all of your internal data (apps, settings and everything you have in internal storage) will be erased so make backups of everything. Also backup all partitions with TWRP especially persist and efs!
This tutorial may help you to find the correct firmware for your device (links available) and also guide you through the flashing process of the whole firmware;
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Maybe use also the tools and drivers from there.
Click to expand...
Click to collapse
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?
smartasiankid said:
Wait so I have to run the bootloader lock first and then flash the firmware for my Motorola one p30 play as well?
Click to expand...
Click to collapse
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.
Wolfcity said:
No, the user who was asking wanted to lock his BL so I gave him the lock commands too.
I don't know anything about your device but normally the BL has to be unlocked to flash firmware on a Moto.
Click to expand...
Click to collapse
Oh okay. I tried relocking the bootloader on Moto one p30 play but when repeatedly entering 'fastboot oem lock' it says "still require signed boot.img" and even after I flash the boot.img when it asks to whenever I enter the fastboot oem lock command it says "still require signed boot.img"
Can you help me out please?