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?
So I was trying to unlock my bootloader with LG Laf Recovery MultiTool v1.2 (You can find it on android fourms) I choose Automatic unlock, and it went through fine. Until it got to the fastboot location. When it tried to use a command it returned: FAILED (remote: unknown command). Now its stuck booting into fastboot, but it won't accept any commands. They all return with the above error. Is there anyway that i can fix this?
What is your phone model? Can you enter download mode? If yes, then you can flash stock kdz ROM with LG Flash tool, see tutorial about returning to stock. Good luck.
[Q] fastboot oem unlock with correct code fails with "command did not succeed"
Hi,
I recently got an xperia Z into my hands and wanted to unlock the bootloader.
I checked the IMEI in the system settings and requested and received an unlock code for the device.
I unlocked the bootloader with the code,
but now I am not able to flash or boot anything via fastboot (device still boots normally though).
When trying to flash e.g. twrp to the boot partition
(
Code:
fastboot flash boot boot.img
)
it fails with "remote: command not allowed"
Also trying
Code:
fastboot boot boot.img
does not work properly:
In this case it just reboots into Android.
I am using Linux to flash stuff.
I already tried using the flashtool, which also didnt bring me any success.
Does anyone have an idea or a solution to this problem?
Best regards
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
xdafanboii said:
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
Click to expand...
Click to collapse
there is a firmware for the phone
unpack it
u will find there file Checksum.ini
and unlock‐secro.img(or diferent name point is unlock)
rename checksum.ini on checksum.oem
then turn off all checks in flashtool leave marked only SECRO line
u must choose unlock‐secrom.img for SECRO line
once u'll flash SECRO u will have to flash twrp, to do that u must turn off all checks except RECOVERY, for RECOVERY u must open recovery 1.72.img then flash it, after u can just flash supersu.zip via twrp
i've done it all on my 1.76 device it will also work on 1.79
twrp u can find here(u need to register on that forum)
https://4pda.ru/forum/index.php?showtopic=756527&view=findpost&p=53228248
i was following this guide https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 and i did everything up until "fastboot flash recovery twrp_james.img
fastboot reboot recovery" and it says the image isnt signed or corrupted any help would be nice thanks.
skyrimman33 said:
i was following this guide https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 and i did everything up until "fastboot flash recovery twrp_james.img
fastboot reboot recovery" and it says the image isnt signed or corrupted any help would be nice thanks.
Click to expand...
Click to collapse
Have you successfully unlocked bootloader?..I get same error messages when flashing on e5 play with unlockable bootloader..Motorola will not add the Verizon James variant to oem unlock list..but a locked bootloader will give you that error message..