Nexus 10 can't unlock bootloader - Nexus 10 Q&A, Help & Troubleshooting

Hello,
I have a friend's tablet Nexus 10 who has a problem with booting the system. I should be flashing it via fastboot but I can't do that because the bootloader is locked. When I try to unlock the bootloader via fastboot, it offers me 'YES' or 'NO' options on the screen. When I click 'NO' the tablet restarts properly and enters bootloop (which is a problem). And when I click 'YES' to unlock it, the tablet locks up and doesn't respond to any commands until I get into fastboot or bootloader unlock again. Do you know what to do?
Thanks in advance,
Uros.

I'm on the same boat here. Tried to unlock the bootloader but happens the same thing you are describing.
Did you have any luck in the end?
Thanks in advance.
SPQR.

Related

Help relocking RAZR M bootloader

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

Is it possible to relock the bootloader?

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.

Cannot boot Mi A1 after locking bootloader

Hi could I ask because i lock my bootloader on Mi A1 but unfortunately the device didn't boot up.
Now, I am trying to unlock bootloader to fix my device and it won't unlock FAILED (remote: oem unlock is not allowed).
I am on May latest security patch build. Please help me.
Did you try reflashing ROM with Mi Flash tool? Use "Save user data" option there.
hulicow said:
Hi could I ask because i lock my bootloader on Mi A1 but unfortunately the device didn't boot up.
Now, I am trying to unlock bootloader to fix my device and it won't unlock FAILED (remote: oem unlock is not allowed).
I am on May latest security patch build. Please help me.
Click to expand...
Click to collapse
I think you tried to lock your phone after rooting your device. You'll have to try to switch to fastboot mode by volume down + power after vibration. Then use flash using Mi flash tool
I cannot do that, the bootloader is locked and I am on May security patched. Those fastbook oem unlock and fastboot flashing unlock methods won't work. I believe only testpoint is the solution to my problem.
Stuck with the exact same problem....did u find the solution
hulicow said:
I cannot do that, the bootloader is locked and I am on May security patched. Those fastbook oem unlock and fastboot flashing unlock methods won't work. I believe only testpoint is the solution to my problem.
Click to expand...
Click to collapse
Reboot to fastboot power+volume down then reboot to edl mode by typing "fastboot oem edl" in your adb your phone will turn black. Open miflash and click "refresh" if you see "com#X" it means its connected then flash the fasboot file you downloaded in mi forums after finish press and hold power until it restarts.

How to relock the bootloader?

Hi,
I have Axon 7 2017U on B35 but I am really struggling to lock the bootloader. Not sure why it's so hard to lock it. I tried axon 7 toolkit also, it fails after booting into recovery, or fastbooting.
I ran fastboot manually using volume keys but it just shows the same "your device can't be checked for corruption, please re-lock your bootloader".
Anyone knows how I can lock the bootloader? I am on stock B35.
Thanks in advance!
lachdanan said:
Hi,
I have Axon 7 2017U on B35 but I am really struggling to lock the bootloader. Not sure why it's so hard to lock it. I tried axon 7 toolkit also, it fails after booting into recovery, or fastbooting.
I ran fastboot manually using volume keys but it just shows the same "your device can't be checked for corruption, please re-lock your bootloader".
Anyone knows how I can lock the bootloader? I am on stock B35.
Thanks in advance!
Click to expand...
Click to collapse
EDL back to MM B19, enter Fastboot, fasboot oem lock

OEM unlocking won't work

Hi everyone,
Today I tried unlocking the bootloader on my Lenovo Z6 Pro to root my phone but I've hit a dead end.
I've enabled OEM unlocking and USB debugging on the developer options before using "adb reboot bootloader". I managed to get to bootloader mode alright, but neither "fastboot flashing unlock" nor "fastboot oem unlock-go" works; I always get "remote: flashing unlock is not allowed" or "remote: oem unlock is not allowed".
This makes it seem like I didn't enable OEM unlocking before, but I made sure it was enabled. Any ideas how I might solve this?
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Sayi Keshkar said:
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Click to expand...
Click to collapse
Thanks for the reply. I gave up rooting my device for a while but I got tired of my phone bugging all the time so decided to give it another shot. This time I have another problem and it's driving me crazy: ADB wouldn't detect my phone when it's connected so I still can't unlock my bootloader. I tried installing every driver I could find but nothing works, but I can transfer files through explorer just fine. It occured to me that the USB might be the problem but it's the exact same one I used the last time I tried rooting it and I didn't have this problem back then.

Categories

Resources