Related
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...
gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.
since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin
THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM
First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)
There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img
I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S
use the galaxy nexus toolkit to unlock bootloader, root
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.
Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250
OP, OMAP flash?
Hello all,
I've got an Arc S that I've been trying to unlock the bootloader on using Sony's method, without success.
1. I have fastboot and adb installed on my machine (Linux Mint 14 32bit)
2. I've pulled the unlock code from Sony's website
3. I set my udev rules as laid out in this tutorial.
4. I have checked my bootloader to confirm that it can be unlocked (and currently is locked)
5. Fastboot is working (When I type in sudo fastboot devices, I get a hexadecimal string in response)
6. However, when I try to unlock, it always fails.
Initially, it gave me a "oem unlock failure code". After I rebooted thought, the code changed. Instead of something like this
Code:
oem unlock failed!
it gave me this
Code:
...
and did nothing. I let it sit for a few minutes and then forcibly shut down terminal, no damage done to the phone.
I'm quite confused at this point. From all my google searching I can't figure out why the booloader won't unlock. I'm pretty sure that I have the right unlock code.
A second and curious thing that may or may not be related is that the phone is rooted, but when I tried to transfer CWM via fastboot it threw an error, saying that the phone needed to be rooted first. However, it is rooted and apps such as Titanium Backup work just fine, verifying the root. Can anyone give me some direction on this?
I know there is a video on the how to unlock lt18i bootloader. It also has step by step process on fixing issues for unlocking bootloader. Lemme get.it for ya.
Sent from my LT18i using xda premium
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
I don't believe that it is simlocked. I don't believe the phone was purchased through a carrier. For clarification, this is a friend's phone so I would need to ask them as to where they purchased it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Someguyfromhell said:
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Click to expand...
Click to collapse
As taken from the Cyanogenmod Wiki page for Anzu devices:
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY was the bootloader unlock I received from Sony.
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
MarcSinger said:
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
Click to expand...
Click to collapse
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Guanfy said:
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Click to expand...
Click to collapse
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
MarcSinger said:
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
Click to expand...
Click to collapse
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Guanfy said:
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Click to expand...
Click to collapse
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Someguyfromhell said:
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Click to expand...
Click to collapse
Yup, that I have. I originally entered the 15 digit code and the website threw an error, so I deleted the last digit to get the unlock code that I tried.
same issue as LT26ii
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
nkiy said:
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
Click to expand...
Click to collapse
oem unlock failed
Problem solved!
Hey guys, I just unlocked my LT26ii after many times of "oem unlock failed". Here's my solution:
0. well first just remember your IMEI code, cause later it will changed.
1. Download a new firmware in ftf format.
2. Update firmware with Flashtool.
3. Turn on your phone and get you imei code. Now you should got a new one different from the previous one.
4. Use the NEW imei to unlock your phone.
Good Luck !
PS: dont guarantee that worked but if it does please let'me know.
Hi all, I need to relock the bootloader, flashing back stock MM or LP didn't solve the issue for me, neither hard resetting, bootloader is still unlocked and the message appears on every start in the high left corner.
Can You help relock or it's impossible for now please?
It's not possible to relock once it's unlocked. It does tell you this when u unlock it.
Sent from my LG-H815 using Tapatalk
awes0me1 said:
It's not possible to relock once it's unlocked. It does tell you this when u unlock it.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
thanks for the answer, I did not remember that message. Strange for me that noone found or searched a method to relock for selling the phone :good:
Getting it relocked is the only way to send it back for warranty claim. I wasn't able to get it recognized by my computer so that I can run fastboot comands on it - the right one is ./fastboot oem lock
maildaemon said:
Getting it relocked is the only way to send it back for warranty claim. I wasn't able to get it recognized by my computer so that I can run fastboot comands on it - the right one is ./fastboot oem lock
Click to expand...
Click to collapse
Did you use the proper fastboot.exe? What OS is your computer? If it's windows try these.
It seems that in order to get fastboot operational, you need to have a working bootloader. So, after a couple (hundred) of tries - DO NOT FLASH KDZ (REFURBISH) your LG G4, it still boots once in a while and if it has your account and data and it will be faster to get to fastboot mode and get the bootloader locked again. Can somebody confirm that you can execute "fastboot oem lock" on an unlocked device? This will save us a lot of time trying to get the device to that state...
for me it is impossibile. If you have a g4 with bootloader locked and you doing fastboot oem unlock it says that it is no possibile...you must follow the instructions that lg provides with file unlock.bin
So is impossibile relock bootloader with fastboot oem lock...I hope that anyone find the way to do it...
Well unfortunately it is not posible to lock the bootloader via "fastboot oem lock" I'm waiting for user @warloxfre for some more info on his ideas (fingerscrossed)
As title suggests, didn't know if this is possible or not.
Nitemare3219 said:
As title suggests, didn't know if this is possible or not.
Click to expand...
Click to collapse
I recommend against it. What's your reason for wanting to do this? There's really not much benefit to doing it.
But it's certainly possible and simple to do.
jollywhitefoot said:
I recommend against it. What's your reason for wanting to do this? There's really not much benefit to doing it.
But it's certainly possible and simple to do.
Click to expand...
Click to collapse
I may be wanting to return my 10 - was a purchase directly from HTC. Just not sure if it fits my wants as a device. Their return policy doesn't say anything about reusing unlocked devices, but I felt that may be bad if I returned it unlocked.
Nitemare3219 said:
I may be wanting to return my 10 - was a purchase directly from HTC. Just not sure if it fits my wants as a device. Their return policy doesn't say anything about reusing unlocked devices, but I felt that may be bad if I returned it unlocked.
Click to expand...
Click to collapse
Well if you received an unlocked code from htcdev, they will be able to tell you unlocked it, so I'm not sure how much it matters. Also, even if they didn't check the htcdev database, when you relock, your bootloader will show "relocked" instead of "locked".
I'm not sure what their return policy is on unlocked devices. Good luck.
Oh, and if you want to relock it, just go to download mode and enter "fastboot oem lock" in a command window.
Moderator Information,
I have removed the above two posts. The commands given are device specific commands. If used on another device, it could brick the phone.
If you want to relock your bootloader for warrenty, you'll have to S-OFF first and use some device-specific procedure(which hasn't released yet) to make it completely stock-like again.
Stephen said:
Moderator Information,
I have removed the above two posts. The commands given are device specific commands. If used on another device, it could brick the phone.
Click to expand...
Click to collapse
thank you I apologize for the mishap
Mark112887 said:
thank you I apologize for the mishap
Click to expand...
Click to collapse
As an aside if you do run that specific command on this device you will end up with some serious problems.. the adb echo command of the past devices is more.
Sent from my HTC6545LVW using Tapatalk
jollywhitefoot said:
Well if you received an unlocked code from htcdev, they will be able to tell you unlocked it, so I'm not sure how much it matters. Also, even if they didn't check the htcdev database, when you relock, your bootloader will show "relocked" instead of "locked".
I'm not sure what their return policy is on unlocked devices. Good luck.
Oh, and if you want to relock it, just go to download mode and enter "fastboot oem lock" in a command window.
Click to expand...
Click to collapse
I tried "fastboot oem lock" but it bounced back with a failure saying it's an unknown command. I tried a few other commands as well.
Fastboot flashing lock
Fastboot lock_bootloader (which was in the command list )
Fastboot OEM relock
But none worked. Need help.
Rijul30 said:
I tried "fastboot oem lock" but it bounced back with a failure saying it's an unknown command. I tried a few other commands as well.
Fastboot flashing lock
Fastboot lock_bootloader (which was in the command list )
Fastboot OEM relock
But none worked. Need help.
Click to expand...
Click to collapse
You can use All in one toolkit to relock bootloader
https://forum.xda-developers.com/htc-10/development/tool-htc-10-m10-one-toolkit-v1-0-t3538317
adriano25028 said:
You can use All in one toolkit to relock bootloader
https://forum.xda-developers.com/htc-10/development/tool-htc-10-m10-one-toolkit-v1-0-t3538317
Click to expand...
Click to collapse
Will it wipe the device ?
Rijul30 said:
Will it wipe the device ?
Click to expand...
Click to collapse
Yes.
adriano25028 said:
Yes.
Click to expand...
Click to collapse
Thanks !
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Az Biker said:
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Click to expand...
Click to collapse
Only if you want to update the bootloader. That's the only thing I can see that critical does.
Sent from my Pixel 2 XL using Tapatalk
I believe unlock_critical is necessary if you want to be able to flash updates manually..
"For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock "
Above quote is from Google Factory Image page.
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Badger50 said:
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Click to expand...
Click to collapse
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Wickidmasshole said:
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Click to expand...
Click to collapse
This is why I asked the question. I wasn't sure if doing the basic unlock prior to the critical unlock would be an issue.
I'm running the critical unlock when I get home tonight (I want to be able to update the bootlader in the future), I'll let you know what I run into, if anything.
Az Biker said:
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Click to expand...
Click to collapse
Didn't use any toolkits, just these 2 guides....
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176 https://forum.xda-developers.com/pixel-2-xl/how-to/guide-magisk-root-snoke-kernel-t3701930
....and didn't run into any problems at all. My P2XL is just humming right along. The battery on this thing is phenomenal! Takes me a good 2 days to knock it down to 10% :good:
Now we just need some TWRP to get Beans up and running :good::good:
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
iamjimmy said:
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
Click to expand...
Click to collapse
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Badger50 said:
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Click to expand...
Click to collapse
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Click to expand...
Click to collapse
This one :good:
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
marbertshere said:
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
Click to expand...
Click to collapse
I've unlocked the ordinary bootloader first, then the bootloader_critical without any problems :good:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
jaybird779 said:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
Click to expand...
Click to collapse
The bootloader_critical unlock has to be performed only if you want to flash the bootloader (e.g. when you flash a factory image), but, if you want to perform all the other operations, such as rooting, kernel flashing, etc., you have to unlock the ordinary bootloader, too.
So, these are the two Fastboot commands:
fastboot flashing unlock_critical (for bootloader flashing, you've already performed this)
fastboot flashing unlock (for all the other operations)
The request which appears on your phone, when you enter these two commands, is the same, and you have to allow the bootloader unlock in both cases :good: