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?
Related
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.
Hey guys
I have a Moto X XT1052- The Indian Version.
I rooted my phone a few weeks back and I've decided that I don't want root access anymore.
I have unrooted my phone from the SuperSU app by clicking the clean up button.
Now I can't find anything as to how to relock the bootloader. I don't really need the warranty to be active again but if there is a way to do that it would be appreciated.
Also I need help to remove the bootloader unlocked warning message to be removed as well.
Please be clear in your explanations as I'm new to all this.
I have attached details about my phone to this post.
Thanks in advance
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
bronko15344 said:
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
Click to expand...
Click to collapse
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as you are re-flashing the EXACT same rom that is on your phone, and your battery is 100% charged before starting. In other words,as always, if the battery goes dead during the process, there is a potential to brick, and DOWNGRADING your ROM is not good.
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
KidJoe said:
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as your battery is 100% charged before starting. (in other words,as always, if the battery goes dead during the process, there is a potential to brick)
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
Click to expand...
Click to collapse
Thank you so much
RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
If you used the "Full Unroot" option in the app it should revert all changes which are made during the root process. To be sure that your system partition is completely stock you can flash it with fast boot (this won't delete your installed apps and data)
To do this look into this guide
guide-moto-x-return-to-100-stock
Short version:
1.
Download and extract the sbf flies matching your phone and carrier from here:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
To decide which file you need to download:
info-tip-web-sites-official-leaked-roms
2. (this step is necessary to remove your warning message)
ghost-original-bootanimations-unlocked
download the standard boot animation and extract the logo.bin and overwrite the logo.bin from the sfb files.
3.
now flash the system partition, kernel, recovery and the new logo (without the warning) with the following commands: (Note: For flashing system.img you MUST use mfastboot instead of fastboot. It's to big for the normal fast boot. So no typo here)
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
Don't execute the following command as this will delete all your data/installed apps etc.
Code:
fastboot erase userdata
That should be sufficient to revert everything what was changed during the root process. Check if everything looks like it was was on stock rom (including the recovery and the bootlogo)
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
But actually I would not relock your boot loader since you gain nothing and if you want to unlock it again all your data will be erased during the unlock process. and since you are not rooted you can't backup everything before...
Edit: Like @KidJoe said. If you accepting an OTA than the warning comes back. so if you relock your bootloader you can't hide that message without unlocking (and loosing all your data) again. Just stay on the unlocked bootloader
bronko15344 said:
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
.
Click to expand...
Click to collapse
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
KidJoe said:
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
Click to expand...
Click to collapse
Oh wasn't aware that you directly have to flash a firmware to relock the bootloader. Thank you
hey how u do u unlock ur moto x t1052 .
Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?
http://motofirmware.center/
Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse
Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.
Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png
dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.
The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.
TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
When in fastboot, type "fastboot oem lock" (without the quotations"
Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")
dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk
dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.
Firstly I will say this before I get a slew of why's and how come's that you are locking the bootloader. Personally it shouldn't matter "why" but I guess that'ss me. Anyways, I am locking the bootloader because I want to give the phone to my daughter, and trust me when I say she is nowhere tech savvy, so giving her a phone with an unlocked bootloader/rooted phone is like giving a 1 yr old a loaded gun, not a good idea. She also uses a bank app, and currently cannot use it, due to the bootloader being unlocked. This is the main reason I want to lock the bootloader.
Now that we have that out of the way....my specs:
Moto g5s plus
XT1806
32gb/3gb
US variant
I have tried fastboot command "fastboot oem lock", I have also added this to a flash batch file no luck.
I have searched online at some of the how-to's and tried them, such as flashing this:
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
But have not had luck with that either.
Currently I am on stock with root, nothing custom at all.
The current build I am on is NPSS26.116-45-14 and I got this from an OTA I recieved, because as far as I am aware of there is no 14 build out there for download. The latest one I found if I recall right is NPSS26.116-45-12, and you have to OTA up to 14 from that one.
So I am curious why I cannot for whatever reason lock my bootloader at all no matter what I do. Do I have the wrong variant of zip file.....ie: xt1806 is the 45 correct?
It's been a bit but if I recall right I did something one time to get it locked, it notified me that it had locked, but when I rebooted the bootloader message was still present.
So, given all that I am open for ideas.
45-12 is April security patch for US, that's right zip.. ( update to 45-14will be June's ? )
Did you check system sparschunk in zip up to 6 or 7 ?
Flash all system sparschunk, here you listed only up to 4..
Also check Command Prompt result, when command ends..
Your are right, there are 6, that was my bad.
I did however find later about a method I had not tried yet.
I was reading on Lenovo forums, a guy with the exact same issue and nothing worked until he tried this.
When you issue the oem lock command, and a message something like you need a verified stock rom, or something ( I don't recall right now what it said exactly) but once you see this message, proceed with flashing the above commands. After he did that he said it locked just fine.
I was always under the impression that was a generic message or something and always hit out of it and could never move on because I thought I had a wrong zip file I was flashing.
The "one" thing I did not try, so I will try that and report back with my findings and let you know how it went.
I found out why I can't lock the bootloader now.
With the g5s plus, it's a must that you have the latest firmware to lock the bootloader.
Scenario:
You updated to firmware B, which is the absolute newest there is, but only have firmware A zip file. In this scenario firmware A is not the newest, and since you updated to B the latest, you now need B firmware in a zip file to flash it, because flashing firmware A will no longer work now.
Don't get this confused with flashing will not work, it works fine with ANY flash, ANY firmware, only difference is you cannot lock the bootloader unless you have the latest firmware.
Since I do not have the latest firmware zip file, I cannot simply flash it and lock the bootloader, because it's looking for B not A.
If no one ever releases a B firmware, the bootloader is not lockable indefinitely.
Sad that motorola did this without giving us the latest firmware to download.
I am growing a great disdain for Lenovo company.
Anyways, there you have it, bootloader cannot be locked except in the case someone releases the latest zip.
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???