100% stock, unlocking & relocking the bootloader questions - Nexus 6 Q&A, Help & Troubleshooting

I have read all of the info about unlocking and relocking the bootloader, but i have a question, if i was 100% stock with a locked bootloader and wanted to flash the latest factory image would i still need to enable developer options and enable allow oem unlock even if i was to run the commands below from fastboot mode.
fastboot oem unlock
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot oem lock
fastboot reboot
The reason i ask is that you are not booting into android until the bootloader is relocked, so in theory the oem unlock option shouldn't have an effect in this scenario?

@d.chatten,
Yes, you have to unlock the bootloader to use fastboot to flash .img files, or to sideload via ADB.

d.chatten said:
I have read all of the info about unlocking and relocking the bootloader, but i have a question, if i was 100% stock with a locked bootloader and wanted to flash the latest factory image would i still need to enable developer options and enable allow oem unlock even if i was to run the commands below from fastboot mode.
fastboot oem unlock
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot oem lock
fastboot reboot
The reason i ask is that you are not booting into android until the bootloader is relocked, so in theory the oem unlock option shouldn't have an effect in this scenario?
Click to expand...
Click to collapse
You really should boot into Android before re-locking. This is where people have run into trouble. Following the re-lock guide is recommended.

Thanks for your reply, much appreciated, but my question wasn't about the need to unlock the bootloader ot flash, my question was, do i still need to enable "allow oem unlock" in developer options if i use the commands listed above when flashing the latest factory image on a Nexus 6 when 100% stock a locked bootloader, this in theory should work as you are not booting into android until the bootloader is relocked?

The main thing to remember, is to remove all security locks and your Google account beforehand. With this device, when fastboot oem lock is issued, the device is wiped again. This is why it is important to be sure you have a working OS before locking. :good:

Evolution_Freak said:
You really should boot into Android before re-locking. This is where people have run into trouble. Following the re-lock guide is recommended.
Click to expand...
Click to collapse
Thanks for that, i will follow the guide, so this option would effect things regardless?

d.chatten said:
Thanks for your reply, much appreciated, but my question wasn't about the need to unlock the bootloader ot flash, my question was, do i still need to enable "allow oem unlock" in developer options if i use the commands listed above when flashing the latest factory image on a Nexus 6 when 100% stock a locked bootloader, this in theory should work as you are not booting into android until the bootloader is relocked?
Click to expand...
Click to collapse
I understand completely. In a sense, you have outlined the process that is shown on the factory image page, by Google. This information needs to be updated as it does not reflect the security changes made in 5.1. I wouldn't risk your device for a few extra minutes needed to verify the OS boots.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
d.chatten said:
Thanks for that, i will follow the guide, so this option would effect things regardless?
Click to expand...
Click to collapse
I can confirm that several people have bricked by trying to do it the way you were thinking of trying. If for any reason, during the flashing process something didn't flash just right, and a bootloop occurred, you wouldn't be able to fix it with a locked bootloader. That's why it's best to ensure your OS boots before locking.

Evolution_Freak said:
I understand completely. In a sense, you have outlined the process that is shown on the factory image page, by Google. This information needs to be updated as it does not reflect the security changes made in 5.1. I wouldn't risk your device for a few extra minutes needed to verify the OS boots.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
I can confirm that several people have bricked by trying to do it the way you were thinking of trying. If for any reason, during the flashing process something didn't flash just right, and a bootloop occurred, you wouldn't be able to fix it with a locked bootloader. That's why it's best to ensure your OS boots before locking.
Click to expand...
Click to collapse
Thank you for clarification, much appreciated, the process is still easy enough even with these extra steps.

Related

Any change to relock bootloader?

Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
alexhdkn said:
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
Click to expand...
Click to collapse
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Why would you want to relock the bootloader just to get back to close as stock as possible?
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
TechSavvy2 said:
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Device: VZW Moto X
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
Code:
fastboot oem fb_mode_set
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
mfastboot flash system system.img
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 config carrier vzw
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
KidJoe said:
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Click to expand...
Click to collapse
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
nhizzat said:
Why would you want to relock the bootloader just to get back to close as stock as possible?
Click to expand...
Click to collapse
So i can get Lollipop official!
TheBoiledDogs said:
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Already done this but it won't relock the bootloader.
alexhdkn said:
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
Click to expand...
Click to collapse
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
alexhdkn said:
So i can get Lollipop official!
Click to expand...
Click to collapse
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
edit:canceled
KidJoe said:
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
Click to expand...
Click to collapse
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
alexhdkn said:
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
Click to expand...
Click to collapse
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
KidJoe said:
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
Click to expand...
Click to collapse
I know it's an entire process and I did it last night to go back to stock 4.4.4. But I just feel safer (thieves) with the bootloader locked.
Thieves? How will having a locked bootloader protect you from thieves?

Re-lock Bootloader

I have the XT-1052 version of Moto X and its running the Asia Retail firmware. I had unlocked the bootloader and flashed CM12 but returned to stock rom through this guide http://forum.xda-developers.com/moto-x/general/retail-firmware-uploaded-xt1052-t2976596. I will be selling the device and want to re lock the bootloader. Can i type the ''fastboot oem lock'' command in mfastboot tool and re lock the bootloader? Also, will it erase the whole data on the device?
KD25 said:
I have the XT-1052 version of Moto X and its running the Asia Retail firmware. I had unlocked the bootloader and flashed CM12 but returned to stock rom through this guide http://forum.xda-developers.com/moto-x/general/retail-firmware-uploaded-xt1052-t2976596. I will be selling the device and want to re lock the bootloader. Can i type the ''fastboot oem lock'' command in mfastboot tool and re lock the bootloader? Also, will it erase the whole data on the device?
Click to expand...
Click to collapse
Yes, fastboot oem lock will lock it, and no it will not wipe data. Only unlocking wipes data.
But you status code will show relocked you can never get status code back to locked once unlocked.
Travisdroidx2 said:
But you status code will show relocked you can never get status code back to locked once unlocked.
Click to expand...
Click to collapse
Correct. Whoever has the phone will be able to see the "tamper seal" that shows the bootloader was previously unlocked, but is now locked again.
I would provide whoever you sell the phone to the bootloader unlock code so they can unlock in the future if they so desire. Not sure if they can request the code from Motorola again or not.
fury683 said:
Correct. Whoever has the phone will be able to see the "tamper seal" that shows the bootloader was previously unlocked, but is now locked again.
I would provide whoever you sell the phone to the bootloader unlock code so they can unlock in the future if they so desire. Not sure if they can request the code from Motorola again or not.
Click to expand...
Click to collapse
I tried it but it asks me to flash the signed images. The link i mentioned above comes with an XML file which dictates the steps RSD should be following, right? So if i upload the XML file can you edit the command line and add the command? I am not an expert in this stuff.
i have relocked flashing manually with fastboot, not sure if you add the oem lock cmd to the xml will work.
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
hbenz2008 said:
i have relocked flashing manually with fastboot, not sure if you add the oem lock cmd to the xml will work.
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
Click to expand...
Click to collapse
The files that are present in the rom folder are boot.img, fsg.mbn, gpt.bin, logo.bin, motoboot.img, NON-HLOS.bin, recovery.img and system.img. Can you modify the list of commands to add the aditional files. Thanks.
just flashing the above is enough to relock. Flash away
Wireless...
hbenz2008 said:
just flashing the above is enough to relock. Flash away
Wireless...
Click to expand...
Click to collapse
Thanks man. Will update about how it goes.

How to update Moto x (2nd Gen) To marshmallow

Hey There, i just got Motorola Moto x (2nd Gen) and it's currently running android 4.4.4 and is AT&T variant. Can any one tell me how can i update it to Marshmallow with/without international variant ?
Update process from PC will be preferred.
abdullah.ahsan11 said:
Hey There, i just got Motorola Moto x (2nd Gen) and it's currently running android 4.4.4 and is AT&T variant. Can any one tell me how can i update it to Marshmallow with/without international variant ?
Update process from PC will be preferred.
Click to expand...
Click to collapse
As its att and bootloader is locked so you cant go further.. Wait for officially update.. Well why you are on kitkat still? You should get lolipop by now..
Salik Iqbal said:
As its att and bootloader is locked so you cant go further.. Wait for officially update.. Well why you are on kitkat still? You should get lolipop by now..
Click to expand...
Click to collapse
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
abdullah.ahsan11 said:
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
Click to expand...
Click to collapse
Go into Settings, About Phone, tap Build Number 7 times, then go back one screen to Developer Options, enable Allow Bootloader Unlock, and USB Debugging.
Boot into Bootloader Mode and try:
fastboot oem unlock
That may not work on your phone.
Try to get the unlock code from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you are able to unlock the bootloader, you have two choices: you can flash the 6.0 stock firmware from another variant, or you can flash a MarshMallow ROM, such as CyanogenMod.
Here's a link to stock Moto X 2014 firmwares:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
abdullah.ahsan11 said:
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
Click to expand...
Click to collapse
Your bootloader is locked. To unlock it you need to use kingroot, then sunshine to unlock it. After that you can flash a marshmallow rom.
Sent from my XT1095 using Tapatalk
AGISCI said:
Your bootloader is locked. To unlock it you need to use kingroot, then sunshine to unlock it. After that you can flash a marshmallow rom.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am a noob . Can You please refer me a link/tutorial. I know about king root but sunshine is new to me
UPDATE:
I tried to root with kingroot and it failed
For links to relevant guides and tutorials see Tony Stark's sticky at the top of the general forum.
Hi Sir, Gus Ghanem, pleased take two minutes to help me
Gus Ghanem said:
Go into Settings, About Phone, tap Build Number 7 times, then go back one screen to Developer Options, enable Allow Bootloader Unlock, and USB Debugging.
Boot into Bootloader Mode and try:
fastboot oem unlock
That may not work on your phone.
Try to get the unlock code from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you are able to unlock the bootloader, you have two choices: you can flash the 6.0 stock firmware from another variant, or you can flash a MarshMallow ROM, such as CyanogenMod.
Here's a link to stock Moto X 2014 firmwares:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
Dear sir,
I have Verizon xt 1096 and want to install Android 6.0 from other variants like xt 1092 from stock firmwares which links that you provided above. I will unlock my bootloader.
You please guide me how I can install using fastboot on my windows PC. I don't care about CDMA, it should work on GSM networks 2G and UMTS 3G and LTE because now I am in UAE and not using Verizon.
I need marshmallow 6.0. ... and I don't want to install custom recovery, ROM or root it, if it not necessary for upgrade process.
I will be very thankful to you.
Sorry I forgotten to mention, now I am on stock 5.1
Please also post some commands for fastboot. Thanks
abrarakram19 said:
Dear sir,
I have Version xt 1096 and want to install Android 6.0 from other Version like xt 1092 from stock firmwares which links that you provided above. I will unlock my bootloader.
You please guide me how I can install using fastboot on my windows PC. I don't care about CDMD, it should work on GSM networks 2G and 3G because now I am in UAE and not using Verizon.
I need marshmallow 6.0. ... and I don't want to install custom recovery, ROM or root it, if is it not necessary for upgrade process.
I will be very thankful to you.
Click to expand...
Click to collapse
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 system system.img_sparsechunk.9
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
Gus Ghanem said:
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 system system.img_sparsechunk.9
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
Thank you very much sir. I will try and I hope it will be done with your cooperation. If I felt any trouble I will beg some help from you. Thanks again.
Gus Ghanem said:
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 system system.img_sparsechunk.9
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
Great sir, I followed your instructions and I successfully upgraded my moto x2 xt 1096 (5.1) to official 6.0 xt1092 without any trouble or changing my recovery or any thing else. Thanks for your help.
one thing is when I restart my device one warning screen appear like (your device's bootloader is unlocked and some more cautions) and moto boot animation is changed. Is it possible to get rid from these by simply re locking bootloader by fastboot command....... "fastboot oem lock"
Or after changing firmware it's not possible to re lock it simply myself or any other code is required.
And one more question can i later install other update like 6.0.1 if it is available in same way or will you upload any future updated firmware in same location MEGA from where I downloaded earlier.
And will I get any future OTA from Motorola i.e. 6.0.1 or higher and should I install that OTA if arrives, or not?
I will wait for your reply. Thank again
abrarakram19 said:
Great sir, I followed your instructions and I successfully upgraded my moto x2 xt 1096 (5.1) to official 6.0 xt1092 without any trouble or changing my recovery or any thing else. Thanks for your help.
one thing is when I restart my device one warning screen appear like (your device's bootloader is unlocked and some more cautions) and moto boot animation is changed. Is it possible to get rid from these by simply re locking bootloader by fastboot command....... "fastboot oem lock"
or after changing firmware it's not possible to re lock it simply myself or any other code is required.
And one more question can i later install other update like 6.0.1 if it is available in same way or will you upload any futur updated firmware in same location MEGA from where I downloaded earlier.
I will wait for your reply. Thank again
Click to expand...
Click to collapse
Yes, when you unlock your bootloader, the boot logo changes to the warning logo, and the boot animation was changed by Motorola for 6.0.
You should be able to relock the bootloader by "fastboot oem lock". You can also flash a different boot logo and animation, but then the phone will not be pure stock anymore.
Because you flashed pure stock firmware, you should get System updates for XT1092 when they are released by Motorola, you don't need to reflash the full firmware.
The factory firmwares on MEGA are not mine, but thank you to whoever is uploading them there.
Gus Ghanem said:
Yes, when you unlock your bootloader, the boot logo changes to the warning logo, and the boot animation was changed by Motorola for 6.0.
You should be able to relock the bootloader by "fastboot oem lock". You can also flash a different boot logo and animation, but then the phone will not be pure stock anymore.
Because you flashed pure stock firmware, you should get System updates for XT1092 when they are released by Motorola, you don't need to reflash the full firmware.
The factory firmwares on MEGA are not mine, but thank you to whoever is uploading them there.
Click to expand...
Click to collapse
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
1) You don't need to lock the bootloader to receive ota updates. Updates work with the bootloader unlocked.
2) Don't worry about updates, Motorola said marshmallow 6.0 is the last update this phone gets. There will not be anymore OTA updates.
Sent from my XT1095 using Tapatalk
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.?
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please.
---------- Post added at 04:10 PM ---------- Previous post was at 04:10 PM ----------
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.?
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
AGISCI said:
1) You don't need to lock the bootloader to receive ota updates. Updates work with the bootloader unlocked.
2) Don't worry about updates, Motorola said marshmallow 6.0 is the last update this phone gets. There will not be anymore OTA updates.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow*
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.*
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please. Actually I hate this warnings screen and cautions every time when I power on my device and moto boot animation is terrible since I unlocked the bootloader.
verizon unlocked device.
sir i have an unlocked verizon moto x 2nd generation. can i get official motorola 6.0 update? is there any way?
thanks
Yes sure, follow the instructions in first page of this thread given by Gus Ghanem and say thanks to XDA developer team and their members
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
There is also a MEGA link to download stock marshmallow 6.0 firmwares
---------- Post added at 02:25 PM ---------- Previous post was at 02:19 PM ----------
But only proceed to flash marshmallow 6.0 firmwares if you are not using Verizon network because you will loose CDMA but you can use GSM and UMTS networks
abrarakram19 said:
Yes sure, follow the instructions in first page of this thread given by Gus Ghanem and say thanks to XDA developer team and their members
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
There is also a MEGA link to download stock marshmallow 6.0 firmwares
---------- Post added at 02:25 PM ---------- Previous post was at 02:19 PM ----------
But only proceed to flash marshmallow 6.0 firmwares if you are not using Verizon network because you will loose CDMA but you can use GSM and UMTS networks
Click to expand...
Click to collapse
For those who use verizon service there is this rom:
http://forum.xda-developers.com/showthread.php?t=3327345
Verizon cdma works in this custom stock rom.
Sent from my XT1095 using Tapatalk
Hi,
i just got brand new unused Moto X 2nd gen (2014), It has 4.4 Android on it, but OTA update does not want to work anymore, as of 15.1.2020.
It is unlocked XT1095.
I am looking for somebody to help me over Skype to update it to 5.1 and then to 6.0 - the way usual update would go, and would donate to you via PayPal.

Relock Bootloader

Hello,
Im trying to relock my bootloader again, did i just have to use the "fastboot oem lock" command? Because i read it somewhere that i have to flash stock rom before locking the bootloader, if yes can someone give me the link for stock rom and how to flash it, FYI when unlocking im only using "fastboot oem unlock' command, not doing "fastboot unlock critical blablabla".
Any help would be appreciated, thank you
as far as i know, you need to flash stock bootloader of your current android build then uninstall magisk (if you have it) and just use fastboot oem unlock and you're done (note! backup all your data cause it will make a full wipe)
DiesFrae said:
as far as i know, you need to flash stock bootloader of your current android build then uninstall magisk (if you have it) and just use fastboot oem unlock and you're done (note! backup all your data cause it will make a full wipe)
Click to expand...
Click to collapse
I stopped after unlock bootloader only, i didnt root it at all, so you mean after flash just run fastboot oem lock command?
prayogasp said:
I stopped after unlock bootloader only, i didnt root it at all, so you mean after flash just run fastboot oem lock command?
Click to expand...
Click to collapse
Then you don't need to flash anything at all. Just run fastboot oem lock command.
prayogasp said:
I stopped after unlock bootloader only, i didnt root it at all, so you mean after flash just run fastboot oem lock command?
Click to expand...
Click to collapse
[email protected] said:
Then you don't need to flash anything at all. Just run fastboot oem lock command.
Click to expand...
Click to collapse
Exactly, you don't need to flash anything. Just put phone into fastboot and run fastboot oem lock
[email protected] said:
Then you don't need to flash anything at all. Just run fastboot oem lock command.
Click to expand...
Click to collapse
DiesFrae said:
Exactly, you don't need to flash anything. Just put phone into fastboot and run fastboot oem lock
Click to expand...
Click to collapse
Will it wipe data again just like unlocking?
Yes. It will wipe your data. Please becareful.
Oh. Please sure that you have back to original boot image before relock or your device will brick.
Hi, can someone provide stock boot image for 10.0.1.0 build (Android 9.0)
av2032 said:
Hi, can someone provide stock boot image for 10.0.1.0 build (Android 9.0)
Click to expand...
Click to collapse
https://sourceforge.net/projects/xioami/files/Mi A2/
ckpv5 said:
https://sourceforge.net/projects/xioami/files/Mi A2/
Click to expand...
Click to collapse
Can I simply flash boot_a boot.img / boot_b boot.img and then do
fastboot oem lock?
av2032 said:
Can I simply flash boot_a boot.img / boot_b boot.img and then do
fastboot oem lock?
Click to expand...
Click to collapse
I never relock bootloader .. what I know is you must have fully stock ROM installed then only advisable to lock bootloader. Never do on rooted stock & custom ROM.
Maybe someone else can advise you better.
ckpv5 said:
I never relock bootloader .. what I know is you must have fully stock ROM installed then only advisable to lock bootloader. Never do on rooted stock & custom ROM.
Maybe someone else can advise you better.
Click to expand...
Click to collapse
I have fully stock ROM. Done it anyway... restoring from Google backup right now. Thanks.
Can anyone provide stock boot img for 10.0.3
---------- Post added at 04:55 AM ---------- Previous post was at 04:10 AM ----------
Can I use 10.0.2 boot image for 10.0.3
av2032 said:
I have fully stock ROM. Done it anyway... restoring from Google backup right now. Thanks.
Click to expand...
Click to collapse
Did you lose data after relocking? I mean lock bootloader causes a data wipe like unlocking?
prayogasp said:
Hello,
Im trying to relock my bootloader again, did i just have to use the "fastboot oem lock" command? Because i read it somewhere that i have to flash stock rom before locking the bootloader, if yes can someone give me the link for stock rom and how to flash it, FYI when unlocking im only using "fastboot oem unlock' command, not doing "fastboot unlock critical blablabla".
Any help would be appreciated, thank you
Click to expand...
Click to collapse
here is the link for fastboot rom
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
for your sugestion, if your device is arb2, flash 9690 fastboot rom.
saran, jika masih arb2, flash ke rom 9690..ane pas pertama beli mia2, dapet rom 9690 arb 2..
alibr said:
Did you lose data after relocking? I mean lock bootloader causes a data wipe like unlocking?
Click to expand...
Click to collapse
Yes... it erases everything
Lock while using miui
Can I relock my bootloader while using official MIUI rom?
Aside from
Fastboot oem lock
Do i need this?
fastboot flashing lock
fastboot flashing lock_critical
amnher said:
Aside from Fastboot oem lock
Do i need this?
fastboot flashing lock
fastboot flashing lock_critical
Click to expand...
Click to collapse
"Fastboot oem lock" seems to be depreciated for Mi A2, better use "fastboot flashing lock" instead of "OEM unlock" (though probably these are still equivalent).
And yes, full unlock is achieved when after general unlock you are unlocking critical (once more approve on phone, once more user data erased).
For your information. I've just bricked my Redmi 10S with stock ROM with the command ""Fastboot oem lock" :-(

Moto G6 Bricked NEED HELP!!!

ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
ibb.co/QmnK1cB)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
AgentICS said:
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
Click to expand...
Click to collapse
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
pyschodelicbros said:
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
Click to expand...
Click to collapse
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
AgentICS said:
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
Click to expand...
Click to collapse
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.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 flash boot boot.img
mfastboot oem lock
I did this to lock the bootloader, not knowing my OS wasnt installed properly so theres no OS and my bootloader is locked.
"fastboot oem unlock"
says bootloader feature disabled
Picture of my bootloader log
[Copy link and past without the )]
ibb.co/QmnK1cB)
Ragarianok said:
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Lenovo Moto Smart assistant says device isnt recognize, it might be USB debugging due to not being able to get into the OS.
I tried getting the unique key using "fastboot oem get_unlock_data" but i get this in my CMD
[Copy link and past without the )]
ibb.co/QHD0ZcS)
I do have my orginal unique key saved in a file from when i first unlocked my bootloader and when I tried to flash it I get bootloader feature disabled.
[Copy link and past without the )]
ibb.co/0MPsZrp)
I heard that the oem unlock gets disabled for 7 days after relocking wondering if that is true???

Categories

Resources