So I tried CM13 and wanted to go back to everything official. So I restored the ROM from this place: https://github.com/motoxplay/stock
...using this guide: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Then I tried read the official Motorola guide to re-locking the bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Unfortunately it doesn't work. Using the guide, at the first step, I get this message:
Code:
fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.141s
So I searched more on the web and ended up trying this:
Code:
fastboot oem lock
or
Code:
fastboot oem lock begin
and get this:
Code:
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.023s]
finished. total time: 0.023s
I also found someone around here who said that by flashing the ROM his bootloader was locked again. That didn't work for me. I'm still getting this
Code:
"Device is UNLOCKED. Status Code: 3"
on the bootloader.
What can I do?
My guess is you tried to flash wrong firmware, like Lollipop on the phone that already had Marshmallow. Or something that can't be flashed on locked bootloader, like retail firmware on carrier branded phone.
minimale_ldz said:
My guess is you tried to flash wrong firmware, like Lollipop on the phone that already had Marshmallow. Or something that can't be flashed on locked bootloader, like retail firmware on carrier branded phone.
Click to expand...
Click to collapse
Well for the bootloader they only give us 5.1 and my ROM is 6.1. But when I tried to flash the 5.1 ROM from the same page I got the same message. I'm a bit stuck.
Then I tried to reinstall TWRP and again same message.
I'm stuck...
OK so I was able to install TWRP and then try to go back to 5.1 but that didn't work. It's a shame I thought I could trust that Motorola would give good information.
Oh! Now I got it!
So, just in case someone is confused like I was, here's how to do it. First, find the right ROM. Then, go into fastboot.
Code:
fastboot oem lock begin
You'll get the message that's in the title "Please fully flash the signed build before locking phone" (which should have been obvious I know but I thought it was an error message). Nevertheless, after that message appears you flash the ROM like you would. For me it was:
Code:
fastboot flash partition gpt.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 system system.img_sparsechunk.99
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
To finish the locking I did
Code:
fastboot oem lock
And that was it!!
Prosis said:
Oh! Now I got it!
So, just in case someone is confused like I was, here's how to do it. First, find the right ROM. Then, go into fastboot.
Code:
fastboot oem lock begin
You'll get the message that's in the title "Please fully flash the signed build before locking phone" (which should have been obvious I know but I thought it was an error message). Nevertheless, after that message appears you flash the ROM like you would. For me it was:
Code:
fastboot flash partition gpt.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 system system.img_sparsechunk.99
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
To finish the locking I did
Code:
fastboot oem lock
And that was it!!
Click to expand...
Click to collapse
Which ROM you used (5.1.1 or 6.0)?
Did you get it from GitHub or official site of Motorola?
Which country are you from?
xboysz said:
Which ROM you used (5.1.1 or 6.0)?
Did you get it from GitHub or official site of Motorola?
Which country are you from?
Click to expand...
Click to collapse
That was in my OP : https://github.com/motoxplay/stock
You can't get it from an official source nor Motorola.
I used 6.0.1 the Canada Telus ROM. It also worked with the Bell version.
Prosis said:
That was in my OP :
You can't get it from an official source nor Motorola.
I used 6.0.1 the Canada Telus ROM. It also worked with the Bell version.
Click to expand...
Click to collapse
Thank you so much.
After hours of searching i couldn't find the right way to lock the bootloader.
Your post was like needle in the haystack for me.
Btw what's the status code of your bootloader?
xboysz said:
Thank you so much.
After hours of searching i couldn't find the right way to lock the bootloader.
Your post was like needle in the haystack for me.
Btw what's the status code of your bootloader?
Click to expand...
Click to collapse
You're welcome! I understand the frustration!
My status is 2. You can't get it back to what it was. 2 is an indicator that it was unlocked but that it's now locked.
Related
Hello guys,
I'm trying to downgrade my Moto X Play XT1563, I found a tutorial on the Internet using the fastboot for such a feat. From what I saw, many people use this tutorial to upgrade or simply go back to what it was before "flash".
But in the first command line, when I type in CMD, an error appears:
> fastboot flash partition gpt.bin
target reported max download size of 268435456 byte
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
The tutorial is for this purpose doubt
1) Extract the Fastboot / ADB and images (zip ROM), extract the two zip's to a folder of your choice
2) Restart your phone mode 'Bootloader' (Turn off the cell and then press the volume button (minus) and (power for 2 seconds) and then release the power.)
It would be interesting to have activated in the "Developer options" the option "Allow OEM Unlock"
3) Now the CMD, enter the commands:
NOTE: system.img_sparsechunk may contain name or number, so check if you have only modify the hour.
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fastboot erase userdata
fastboot reboot
I wonder if someone could help me solve this case, please.
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
THANKS!
Wardenn said:
You're lucky that it failed. It's totally okay.
Don't flash the Partition Table - gpt.bin and skip the bootloader.
It's not recommended to do so and there are even threads in this sub forum to warn people.
See: http://forum.xda-developers.com/moto-x-play/general/reminder-how-to-downgrade-6-0-to-5-1-1-t3267253
It can lead to bricking your device.
So just skip fastboot flash partition gpt.bin and fastboot flash bootloader bootloader.img, do everything else.
Click to expand...
Click to collapse
Man you are the ****ing best! You save my phone. Thank you very much! I was so stressed! THANKSSSS!
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Lisandro4m41 said:
Hi, friends. Sorry, but my english is bad.
I tell you, I flash my firmware stock XT1575 6.0, but failed to be carried out correctly. Motorola have installed the drivers, as should be. I tried to flash with RSD Lite 6.2.4, and using commands in both made the same mistake at the same stage flashing. This is the error:
C:\Users\Lisandro\Desktop\platform-tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.041s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.059s
Bootloader is unlocked.
I'm from Argentina, I tried a SIM Personal and working properly, test it with a SIM Claro AR and does not work, try registar network and tells me: "The selected network (Claro AR) is not available".
From already thank you very much.
I hope to resolve this soon.
Regards!
Click to expand...
Click to collapse
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
acejavelin said:
Modem flash fails frequently, repeat the command until it returns OK (may take 2 or 3 times) then continue. Make sure to follow all the steps in order, the order is important.
Click to expand...
Click to collapse
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 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
Lisandro4m41 said:
Ok, thanks. I'll keep trying. Do you think that these commands are properly sorted?
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 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
Click to expand...
Click to collapse
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
acejavelin said:
Depends on the firmware you are using.. according to Moto that isn't the right process, but using the latest MXPE firmware from here it appears correct. It is best to look in the firmware ZIP and find the flashfile.xml file and follow that, open it in a reasonable XML capable editor (not Notepad, but Notepad++ works well) and you can see the exact process step by step.
In looking at the file, pay attention to the steps with "operation" in them, those are the fastboot commands.
Click to expand...
Click to collapse
Thanks! Right now I'm downloading the firmware of the Motorola official page. I hope it works. Thanks again!
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Lisandro4m41 said:
I downloaded the firmware from the official website, but I can not install it, how I go about flashing?
Click to expand...
Click to collapse
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Where is it failing?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Lisandro4m41 said:
I do not know from where to start installing, to decompress the RAR I downloaded, unzip a file I can not open. Basically, once you downloaded the firmware from the Motorola, how do I install it?
Click to expand...
Click to collapse
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
acejavelin said:
It is a .gz file, you extract it like a ZIP/RAR file with a tool like 7-Zip.
The file from Moto is rather old, the one I linked above ( http://forum.xda-developers.com/showpost.php?p=67343754&postcount=171 ) is the current release.
You flash it like you stated earlier.
Click to expand...
Click to collapse
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Lisandro4m41 said:
Yes, I unzipped the .gz file. I managed to get the folder with the files, but following the commands of the Motorola, I pulled the same mistake when creating the thread. You are downloading the most current version. Still I do not understand what the error:
(Bootloader) failed validation Preflash
FAILED (remote failure)
What is the cause of that?
Click to expand...
Click to collapse
Usually it means either the bootloader is still locked (which we know your's is unlocked) or the file is incorrect for your device. Sometimes it's a random error, try erasing the modemst1 and modemst2 first, then flash NON-HLOS.bin a time or two until it gives and OK and continue from there like normal.
I have not retested flash, but I solved my problem. The problem was that the phone was locked in Claro AR. No relation to the Bootloader error, but got what I wanted haha. Thanks for your time.
Greetings from Argentina.
Help needed. NEWBIE alert.
Last week I unlocked my UK G4+ and failed to install SuperU and ended up with a brick. Got it back working using a script to reflash to stock and it was all working fine.
So today tried to install a custom rom and again it killed the phone.
Again, wiped the phone, reflashed as before to stock, now stuck on the Welcome Screen. No touch screen to progress.
When I press the power button, the Power Off prompt comes on and I can power off. So the tough screen is working for that.
I am getting these fastboot errors but carried on anyway.
GPT.BIN
(bootloader) Preflash validation failed
FAILED (remote failure).
How can I get the UK phone back to Stock?
What's your XT model? (in the battery it says the model)
XT1642
I just want it back to original stock and locked now.
Thanks
Try this YouTube video. Make sure you get the correct firmware. This worked for me with no issues. Also make sure you have the correct drivers.
thanks, i'll take a look
Stock ROM: http://www.filefactory.com/file/1pq...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
Commands:
Code:
fastboot oem lock begin
fastboot oem lock begin
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 lock
Hi guys,
How can i relock the bootloader?
There is some guide,please?
Inviato dal mio Moto G (5) Plus utilizzando Tapatalk
I haven't been able to relock it yet.
I unlocked, flashed a custom ROM and then restored everything to stock but after that it was giving me some strange error about system/boot partition "altered" (if I remember correctly).
I said strange because there was no root neither twrp installed, I'm still confused.
So if I flash the stock rom and launch fastboot OEM Lock, it doesn't work?
Inviato dal mio Moto G (5) Plus utilizzando Tapatalk
Firstly you have to flash all the images except boot.img,oem.img and system.img Then run fastboot oem lock.Then it ask for the confirmation Run the same command again.Then flash oem.img,boot.img and system.img.Then run fatboot oem lock again.This locks the bootloader
Use this command
fastboot oem lock begin
Then followed​ by the commands used to flash stock rom.
Then lastly use
fastboot oem lock.
You need signed boot or oem image
coloxim said:
Hi guys,
How can i relock the bootloader?
There is some guide,please?
Inviato dal mio Moto G (5) Plus utilizzando Tapatalk
Click to expand...
Click to collapse
i have tried almost all ways to lock moto g5 plus bootloader but it requires signed boot or oem image to lock the bootloader and without them you can't lock the bootloader.
i searched a lot but was not able to find signed images, as the stock roms available for moto g5 plus are also not signed.
g_chahar said:
as the stock roms available for moto g5 plus are also not signed.
Click to expand...
Click to collapse
Really?
Yes,
manos78 said:
Really?
Click to expand...
Click to collapse
yes as i checked motorola website and for Moto G family there are only available signed roms are for XT1541, XT1543, XT1548, XT1625.. as i tested NPN25.137-33,NPN25.137-35 both but they didn't work. We have to wait for motorola to make the official rom available for moto G5 plus.
g_chahar said:
We have to wait for motorola to make the official rom available for moto G5 plus.
Click to expand...
Click to collapse
OK. Thank you for comment this!
Peharps you can ask in the official Motorola's forum for the signed ROM.
manos78 said:
OK. Thank you for comment this!
Peharps you can ask in the official Motorola's forum for the signed ROM.
Click to expand...
Click to collapse
i will make it available on XDA within a weak as i contacted someone, he will arrange the rom from Motorola Service Centre in 2-3 days.. and after testing it i will upload the same.
I'm thinking on unlocking the bootloader and installing TWRP in my G5 Plus but now I'm curious, why are you after locking it back again?
Lock Bootloader
Any update on this, I also need to lock my G5 plus bootloader.
Thanks
bootimage
is there a signed boot image out there im back to stock adb says i need a signed boot image
g_chahar said:
i will make it available on XDA within a weak as i contacted someone, he will arrange the rom from Motorola Service Centre in 2-3 days.. and after testing it i will upload the same.
Click to expand...
Click to collapse
Perfect
i talked with cutomer service on motorola site an they say to run the g4 software
but i dont know if there an idiot or not
I managed to lock the bootloader, it's fairly simple.
Download the full stock OTA from here: https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
Unzip it and go into fastboot mode.
Code:
fastboot oem lock begin
fastboot oem fb_mode_set
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 oem fb_mode_clear
fastboot oem lock
Sources: http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/ and https://forum.xda-developers.com/showpost.php?p=72494649&postcount=23
mikkoc said:
I managed to lock the bootloader, it's fairly simple.
Download the full stock OTA from here: https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
Unzip it and go into fastboot mode.
Code:
fastboot oem lock begin
fastboot oem fb_mode_set
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 oem fb_mode_clear
fastboot oem lock
Sources: http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/ and https://forum.xda-developers.com/showpost.php?p=72494649&postcount=23
Click to expand...
Click to collapse
Hello can you tell me which firmware u flashed and how you did in detail please
piyushahir said:
Hello can you tell me which firmware u flashed and how you did in detail please
Click to expand...
Click to collapse
I flashed NPN25.137-35
I get a error whene flashing files:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.078s
ADB and Fastboot find my Phone normal.
Schrotty35 said:
I get a error whene flashing files:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
I didn't flash this file at all, only the ones in my previous post.
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
badtlc said:
So I wanted to revert back from lineage OS 14.1 to stock and do all the stock ROM OTA updates to oreo. After flashing retail 137-35 it would not properly update boot.img during that process and would not relock bootloader.
It booted fine though and stock ROM immediately OTA updated each of the following:
137-35-5
137-83
137-93
137-93-4
137-93-8
137-93-10
137-93-14
137-93-18
I'm getting close to the oreo update patch w/ an open bootloader. Is there a concern here? I know the oreo updates have been causing problems for some. Do I need to stop the updates?
Click to expand...
Click to collapse
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Wolfcity said:
It's pretty normal to get OTA updates with an unlocked bootloader, Motorola itself gives you the unlock key. It's a common misconception that the BL status has anything to do with OTA.
Only rooting, twrp and any change in system or vendor prevents the update process.
Just being on untouched stock firmware incl stock recovery and boot.img is enough.
You can install the updates if that's the case for you.
Click to expand...
Click to collapse
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Try locking again with the updated firmware. If the boot.img failed to write then it would have shown error in cmd.
badtlc said:
I dont think the stock boot.img every wrote properly and I cannot seem to get the bootloader locked no matter what I do. Is there a way to verify everything really is stock?
Click to expand...
Click to collapse
Agree, if there was no error in the fastboot log it was ok. If you want to relock the bootloader (there's no good reason for it unless you want to sell the device) here are the locking and flashing commands. You need the exact same firmware you're on for locking!
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
-----------------------------------
The same commands for Nougat:
Flashing:
-----------------------------------
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
--------------------------
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 boot boot.img
fastboot oem lock
I will try those. They look very similar to what I tried already. I always got a fastboot write error for the boot.img and of course the can't OEM lock error.
If the boot.img didn't write properly, would I even be able to boot into the stock ROM? The fact it is working just has me paranoid I'm missing something and about to brick my phone by mistake.
badtlc said:
If the boot.img didn't write properly, would I even be able to boot into the stock ROM?
Click to expand...
Click to collapse
No