Related
First, let me say this because i've used xda for a while and i know im going to get these responses:
I know this wont reinstate my warranty...
Why? Because I want to. I understand you think it's useless but it's not your phone...
I have tried "fastboot oem lock" and it doesnt work...
I've searched Motorola's site, got on a chat with them which was useless, and searched xda...
So I booted into AP fastboot and connected to my computer. Opened CMD and typed "fastboot oem lock begin"
That seemed to start the process so then ran RSD lite (as admin) and flashed a signed xml of 4.1.2
Yes, I edited the XML first and removed the 2 lines with "getvar" in them
RSD finished and the phone rebooted (which was great because before it was hung up on the unlocked bootloader warning)
Unfortunately after turning the phone off and then back on, the unlocked bootloader warning screen still came up.
And after booting back into AP fastboot it still said UNLOCKED.
did i miss a step?
I need to relock the phone. if anyone has useful information it would be extremely helpful. in the event it just cant be done thats fine. but i feel like it can, because after fastboot oem lock begin the command prompted told me that now i can flashed the signed images.
well crap. i may have just answered my own question. do i have to flash manually through CMD (ie fastboot flash system system.img) AND THEN run fastboot oem lock at the bottom? i'll try it tomorrow.
before i started this the phone was stuck on the bootloader warning screen so if anyone is stuck at that point this will allow you to boot up your phone. and if my results are typical, it did not relock the bootloader (obviously). hope I helped someone. hope someone can help me. thanks.
most likely not feasible
unlocking razr m involves phisically blowing a q-fuse, so you can't go back to locked
even if you could, it would be traced forever that you've unlocked the BL
You can relock the boot loader on the Dev edition, but once unlocked you can never go back to original status 0 of the boot loader and the boot logo will always display the warning even if you relock the boot loader. You have to flash that partition with another logo image to avoid that.
You also need to wipe the user data partition in fastboot first for the fastboot oem lock begin command to complete successfully.
Once that is done, when it reboots you will see that in fastboot it will display status 2 locked instead of status 3 unlocked.
This is a physical change that happens to the hardware when you unlock the boot loader an efuse on the board is blown and that memory location is permanently programmed. Its not even a question of them knowing, even though they do of course, the device itself is altered.
From my goodies
http://forum.xda-developers.com/attachment.php?attachmentid=2201206&d=1376991889
Flash from cwm or twrp.
Trade a locked one for your unlocked one? Lol I'm stuck locked on the newest ota
Sent from my XT907 using Tapatalk
So a while ago I rooted my phone but messed it up because I uninstalled a few too many system apps. I just dealt with it for a few months since I could still make calls (but not much else). I finally bit the bullet to look into flashing the stock rom again, but to do so it looked like I had to install a custom recovery, but to do that, unlock the bootloader. So I first unlocked the bootloader using motopocalypse (batch file didn't work but apk did), and got the expected BOOTLOADER UNLOCKED message at bootup, with fastboot saying unlocked, code 3. I then tried flashing CWM recovery via Rom Manager, and it seemed successful, but I was unable to boot to it either from the UI of ROM manager or from holding the buttons during bootup, it would just hang for a few more minutes than normal at the BOOTLOADER UNLOCKED screen, then boot up like normal. So I kept reading, found RSDlite, and was able to flash the stock rom, which I downloaded from the internet and the phone boots up fine, but now fastboot says locked, status code 2, and motopocalypse does not unlock it again (either the batch file or the apk), but I still get the BOOTLOADER UNLOCKED message at bootup. So I'm not sure if my bootloader is unlocked or not and if I can proceed with installing CWM recovery again, so i can make a full backup in case I mess something up again.
So how do I reunlock the bootloader, or verify if it's locked or not?
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
RikRong said:
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FB screen:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 00:54:39)
eMMC Info: Size 8GB
Device is LOCKED. Status code: 2
Battery OK
Transfer Mode:
USB connected
Fastboot reason: Reboot to bootloader
usb connected
I've tried reflashing with RSD previously but no change. I could try it once more if you want.
Not entirely sure what you're asking for with the firmware version, but the image I used was for android 4.4.2, version 183.46.10.XT907Verizon.en.US.
modemman11 said:
Device is LOCKED. Status code: 2
Click to expand...
Click to collapse
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Code 3 as well.
Sent from my XT907 using XDA Free mobile app
rahimali said:
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
Click to expand...
Click to collapse
Yes, that's why I'm asking. So I've got one vote for unlocked, one for locked. As I said though, motopocalypse isn't working a 2nd time.
AndyYan said:
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Click to expand...
Click to collapse
I would like to flash custom ROMs later down the road, but for now I just want to get the stock stuff going.
On a side note, the version of the image I downloaded was 183.x.x, but my mother, who has the same phone, purchased at the same time, and has never rooted it or anything, has version 182.something, and that is also the version I had before I started messing with the bootloader/recovery stuff. The two versions were released at the same time, but I don't know what determines which version you got if you just did OTA updates, or if it even matters. Speaking of OTA updates, the version I downloaded is prompting me to do an OTA update now to another 183.x.x version. I wonder if I'd be able to grab the 182.x.x ROM from my mom's phone without rooting it via fastboot or something.
The 182/183 does not matter regarding root/boot loader unlock its the .10/.15 that matters do not take the .15 without unlocking your boot loader....
We cannot teach people anything; we can only help them discover it within themselves.
So no other thoughts? What would happen if I flashed a custom rom/recovery with a locked bootloader? I tried flashing the ROM again and fb still says locked, code 2, and motopocalypse still doesn't do anything like it did the first time.
modemman11 said:
What would happen if I flashed a custom rom/recovery with a locked bootloader?
Click to expand...
Click to collapse
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
modemman11 said:
So how do I reunlock the bootloader, or verify if it's locked or not?
Click to expand...
Click to collapse
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
lem22 said:
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
Click to expand...
Click to collapse
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.031s]
finished. total time: 0.031s
Still locked code 2 though. Looks like it wants an unlock code from Motorola's website, I tried following the steps to get the code but it says I'm not eligible for bootloader unlock. So unless there's another way to get the unlock code...
modemman11 said:
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
Click to expand...
Click to collapse
A "Code 0" locked device would refuse flashing an unofficial or older recovery. I have no idea about Code 2 though.
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Same here, I can see what it means but cannot find any way to get back to code 3 other than using the unlock code from Motorola, which I am unable to obtain because it says I am not eligible. Surprising that someone hasn't cracked the unlock code yet or made a keygen, people are so eager to do it with pirated computer software before the software is even released.
I've read of someone getting locked status code 2 b4 from flashing an older gpt with rsd (if I remember correctly) I think all that was required to fix it and get unlocked again was to flash the latest gpt. Very important..... Are you sure when you were unlocked you didn't ota update to .15? Because flashing .10 gpt while on .15 may be what caused your false relock
Nope, no OTA update to .15. The ZIP I have of the rom does include the gpt.bin file with the same timestamp as all the other files. I suppose I could try reflashing the whole rom once again later...
Hmm strange, I went to find the old thread I read about the gpt relock issue but it's not exactly the same as your situation.
http://forum.xda-developers.com/showthread.php?p=51436123
Until now I didn't think relock was possible due to the way unlocking works. It's a physical change, a qfuse was blown when the motopocalypse apk was run the first time. It can't be unblown lol. Wish I knew what went wrong here.
Hello Guys
I have a question how to look bootloader?
Because maybe if i want to sell this phone or send to service i must have locked bootloader because they are checking if the bootloader is locked or not...
i think you need a locking code, have to ask huawei for that
then use the adb command to lock bootloader
+1
if find please post!
i found something
type this "fastboot oem relock YOUR CODE"
where YOUR CODE its the unlocking code provided by huawei
try and comment
anyways, the phone will say "relocked" not "locked" as factory locked.
Confusion?
jabonloco said:
i found something
type this "fastboot oem relock YOUR CODE"
where YOUR CODE its the unlocking code provided by huawei
try and comment
anyways, the phone will say "relocked" not "locked" as factory locked.
Click to expand...
Click to collapse
Assuming you already have your code...
adb reboot bootloader
then when it's at the bootloader and it mentions "phone unlocked"
fastboot oem lock
The lock and relock confusion ... was this ever tested with the relock command? Is there a difference?
I tried to lock back the phone with the following command:
Code:
fastboot oem lock
Phone got restarted into bootloader directly, without locking it. I read about this around the net, and found that the system may have to be unrooted in order to get the above command working.
I think, when you unlock your bootloader you never can how back.
once unlocked, always unlocked.
that is why they say you lose all warranty when you unlock your phone.
By the way, I tried to do the relocking with the TWRP Recovery installed. Maybe after reflashing a stock ROM, and flashing the stock recovery back, it'll work.
Does this work for anyone? Really need to lock my bootloader again and it's not working.
Bomn said:
Assuming you already have your code...
adb reboot bootloader
then when it's at the bootloader and it mentions "phone unlocked"
fastboot oem lock
The lock and relock confusion ... was this ever tested with the relock command? Is there a difference?
Click to expand...
Click to collapse
I think if you install a update.app of your stock firmware the bootloader will be locked..This may be work though I didn't check it yet.
Rifat Nurr said:
I think if you install a update.app of your stock firmware the bootloader will be locked..This may be work though I didn't check it yet.
Click to expand...
Click to collapse
Sadly not. Then bootloader is still unlocked.
As far as I know there's no way to relock the bootloader after unlocking it. By default it should allow such an operation, but looks like our fastboot framework was modified in this way.
works
http://huaweip8lite.blogspot.hu/2016/01/tutorial-how-to-lockrelock-bootloader.html
For unlock your bootloader
The command is :
"Fastboot oem unlock *********"
For relock it
The command is
"fastboot oem relock **********"
The stars was your unlock/lock code from Huawei.
It's the only way, other's command was wrong.
Install update don't relock your bootloader and you can update with your bootloader unlock.
It's only necessary to relock it in case of warranty.
Having his bootloader unlock is a great help when you have bad trouble like brick or softbrick.
Also you have to know exactly what you are making on your device's. And you are the only one to blame for the modifications you make on your device's
Lock the bootloader with DCUnlocker... it'll lock the bootloader without the 'relocked' on the screen.
Rifat Nurr said:
I think if you install a update.app of your stock firmware the bootloader will be locked..This may be work though I didn't check it yet.
Click to expand...
Click to collapse
No...Not Will Be Locked
For relock it, you have to use your unlock code too.
In fastboot type
fastboot oem relock ************
(the stars is your unlock code)
And now your bootloader become green and locked.
Sent from my ALE-L21 using XDA-Developers mobile app
And now your bootloader (maybe, i don't know for sure) become green and RE-locked.
If you use DC-unlocker it only reads "locked"
Lähetetty minun ALE-L21 laitteesta Tapatalkilla
Bazilli said:
If you use DC-unlocker it only reads "locked"
Lähetetty minun ALE-L21 laitteesta Tapatalkilla
Click to expand...
Click to collapse
We are talking about warranty, i think that huawei doesn't use DC-unlocker!
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Yes. Flash complete stock everything, boot into bootloader, connect to PC, and "fastboot oem lock".
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Kevinkuensken said:
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Click to expand...
Click to collapse
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Kevinkuensken said:
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Click to expand...
Click to collapse
Boot into bootloader, not EDL.
Erahgon said:
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Click to expand...
Click to collapse
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Locking it again is good for when you want to sell the device or send it in for warranty repair.
BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Yeah, the unlock procedure is the same as before. If you didn't restore the original boot image before the relock, then it's just a matter of booting into fastboot and unlocking the device. Note that this will cause your data to be wiped as well!
If you restore your boot.bin backup file from when your device was locked, does this lock the bootloader? "fastboot oem lock", "fastboot flashing lock" nor "fastboot oem device-info" does nothing for me. Is there any other way to check if your bootloader has been relocked?
Thanks
H0lmEd said:
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Click to expand...
Click to collapse
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
joaste said:
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
Click to expand...
Click to collapse
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
sauerkraut17 said:
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
Click to expand...
Click to collapse
Thanks for the answer.
But there are a few files to flash before using that command according to this thread.
Doesn't anything need to be flashed again (e. g. stock files or anything)?
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
sauerkraut17 said:
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
Click to expand...
Click to collapse
My phone is only a few days old. I'm debating whether to keep it or not (considering the Mate 9, but the price is not the same - love the form factor and bigger screen though - sound won't be the same and I think I'll miss the MiPop button on the Axon (never thought that would happen )).
I'm on the latest MM (B10 - the A2017G model).
Following the mentioned thread, I got to the point of installing TWRP (the signed version), only to realize that besides making backups, there is not much else I can do with that without unlocking the bootloader. I really just wanted to flash supersu and install adaway fro the time being until development matured for this phone (maybe also play around with viper - had great results on my LG G4).
HI, I get the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock". Any way to fix this?
Guys, can anyone help me? I really need to lock the bootloader!
How can I fix the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock"?
I'm on MM B11 Stock.
https://i.imgur.com/fdkgYs6.jpg
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
I did not see this posted anywhere, nor do I see it on Google's Factory Image website/instructions.
Based on testing... When re-locking the bootloader, "fastboot flashing lock" does NOT seem to lock the critical partition.
After following Google's steps to a T and locking the regular bootloader, It was indeed locked. I even attempted to lock regular bootloader again, and received a message stating it was already locked. Bootloader screen also says everything is locked. All is fine and dandy, right?
For ****s and giggles, I tried performing "fastboot flashing lock_critical". It indeed asked me if I wanted to lock the critical partition. After re-locking critical, I was not able to lock critical again. Safe to say, critical does not get re-locked when re-locking regular bootloader.
Safe to say... to re-lock the bootloader completely, you probably want to perform "fastboot flashing lock_critical" then perform the regular "fastboot flashing lock".
bigblueshock said:
I did not see this posted anywhere, nor do I see it on Google's Factory Image website/instructions.
Based on testing... When re-locking the bootloader, "fastboot flashing lock" does NOT seem to lock the critical partition.
After following Google's steps to a T and locking the regular bootloader, It was indeed locked. I even attempted to lock regular bootloader again, and received a message stating it was already locked. Bootloader screen also says everything is locked. All is fine and dandy, right?
For ****s and giggles, I tried performing "fastboot flashing lock_critical". It indeed asked me if I wanted to lock the critical partition. After re-locking critical, I was not able to lock critical again. Safe to say, critical does not get re-locked when re-locking regular bootloader.
Safe to say... to re-lock the bootloader completely, you probably want to perform "fastboot flashing lock_critical" then perform the regular "fastboot flashing lock".
Click to expand...
Click to collapse
we unlocked bootloader then unlocked critical
so it makes sense to lock critical then lock bootloader as you said
abogrhen said:
we unlocked bootloader then unlocked critical
so it makes sense to lock critical then lock bootloader as you said
Click to expand...
Click to collapse
Oh believe me, I agree. I thought it was strange re-locking the critical isn't part of Googles Instructions. Not even sure if it matters, but just an extra security precaution
Thank You very much for the heads up. Saved me a headache
So the process for stock and locked would be to install a factory image to wipe and bring back to stock, fastboot flashing lock_critical, and fastboot flashing lock?
rester555 said:
So the process for stock and locked would be to install a factory image to wipe and bring back to stock, fastboot flashing lock_critical, and fastboot flashing lock?
Click to expand...
Click to collapse
Correct :good: However, I wouldn't do it unless you plan to RMA it, or sell it
Badger50 said:
Correct :good: However, I wouldn't do it unless you plan to RMA it, or sell it
Click to expand...
Click to collapse
Hmmmm what about if you are worried about theft. You can still wipe the phone and login with another account can't you with the bootloader unlocked? Where as the phone will always be tied to the last google account logged in if the bootloader is locked, making the phone useless to sell even overseas. I could be wrong though.
When re-locking my bootloader on my Pixel 2 XL, I only needed to enter "fastboot flashing lock_critical" first. When I entered "fastboot flashing lock" afterwards, this error was returned:
FAILED (remote: ' Device already : locked!')
Seems you only need one step not both. My device is now 100% stock and bootloader is locked and ready for RMA.
rspkt said:
When re-locking my bootloader on my Pixel 2 XL, I only needed to enter "fastboot flashing lock_critical" first. When I entered "fastboot flashing lock" afterwards, this error was returned:
FAILED (remote: ' Device already : locked!')
Seems you only need one step not both. My device is now 100% stock and bootloader is locked and ready for RMA.
Click to expand...
Click to collapse
Yes. just "fastboot flashing lock_critical" will completely lock your bootloader
Looking to sell my phone. So is there detailed instructions I can follow to return to stock and relock bootloader?
def-g said:
Looking to sell my phone. So is there detailed instructions I can follow to return to stock and relock bootloader?
Click to expand...
Click to collapse
Clean fastboot the factory and let it wipe your device. Then factory reset, then lock the bootloader. You must be 100% stock before you lock it down my friend :good:
Badger50 said:
Clean fastboot the factory and let it wipe your device. Then factory reset, then lock the bootloader. You must be 100% stock before you lock it down my friend :good:
Click to expand...
Click to collapse
If data is wiped once I flash the factory image. Why would I need to factory reset it? Your wisdom is appreciated.
def-g said:
If data is wiped once I flash the factory image. Why would I need to factory reset it? Your wisdom is appreciated.
Click to expand...
Click to collapse
Just an extra precaution my friend to make sure that puppy is squeaky clean!
Badger50 said:
Just an extra precaution my friend to make sure that puppy is squeaky clean!
Click to expand...
Click to collapse
Hahaha. :good:
Is the OEM unlocking supposed to be grayed out?
JarMagic said:
Is the OEM unlocking supposed to be grayed out?
Click to expand...
Click to collapse
Usually it's greyed out if it's already unlocked or a verizon phone