Related
How long will we have to wait?
Lol
btort1 said:
How long will we have to wait?
Click to expand...
Click to collapse
You never have to wait to unlock the bootloader on a Nexus device.
You can unlock it by simply enabling usb debugging in developer options (and enabling oem unlock option if present) then boot to fastboot and do a fastboot oem unlock in a command prompt. Follow the on screen prompt and you will be bootloader unlocked (your system will be wiped).
If you got a bit lost by those instructions you can use my android toolkit to do everything automatically *HERE*.
Mark.
ITGuy11 said:
Lol
Click to expand...
Click to collapse
Can we have a bounty for it? I got $100 to donate
jk
mskip said:
You never have to wait to unlock the bootloader on a Nexus device.
You can unlock it by simply enabling usb debugging in developer options (and enabling oem unlock option if present) then boot to fastboot and do a fastboot oem unlock in a command prompt. Follow the on screen prompt and you will be bootloader unlocked (your system will be wiped).
If you got a bit lost by those instructions you can use my android toolkit to do everything automatically *HERE*.
Mark.
Click to expand...
Click to collapse
Made this page before researching
Sorry it's my first nexus device (came from moto x pure) and I thought it was the same as motorola and asking for a token It's actually much faster and easier haha
btort1 said:
Made this page before researching
Sorry it's my first nexus device (came from moto x pure) and I thought it was the same as motorola and asking for a token It's actually much faster and easier haha
Click to expand...
Click to collapse
Congrats on your first Nexus device! Nexus devices are easier in everything
mskip said:
You never have to wait to unlock the bootloader on a Nexus device.
You can unlock it by simply enabling usb debugging in developer options (and enabling oem unlock option if present) then boot to fastboot and do a fastboot oem unlock in a command prompt. Follow the on screen prompt and you will be bootloader unlocked (your system will be wiped).
If you got a bit lost by those instructions you can use my android toolkit to do everything automatically *HERE*.
Mark.
Click to expand...
Click to collapse
0.0 said:
Congrats on your first Nexus device! Nexus devices are easier in everything
Click to expand...
Click to collapse
Thanks, yeah I wish I tried a Nexus sooner. In 2013 I came from an iphone 4s to S4, xperia z1, s5, m7, g3, note 4, g3 again, htc desire eye, xperia z3c, moto x pure and now a nexus 5x! (I know I lost a few hundred bucks from depreciation and reselling )
What turned me away from the nexus 5 before was the battery drain people kept complaining about. I wish I just went ahead and bought one, I'd probably still be using it instead of trying out all those phones...especially the ones with touchcrap ui :crying: After owning 5.5+ inch phones, I've realized phablets aren't for me.
Nexus 5x with 6p specs would have been my perfect phone but this will do until next year
oh common
jk[/QUOTE]
I was installed with Twrp and had rooted my oneplus 3.
I unticked root access in supersu.
Booted to bootloader and typed on my pc in command prompt ,"Fastboot oem lock"
This gave a confirmation on my device,I confirmed locking.
And after that my device did not booted up.I managed to get in bootloader again as I was not even able to open the recovery and unlocked the bootloader once again by this my device booted up.
I flashed stock recovery and repeated the relocking process,this time I was able to open recovery also but no able to boot up.
I again unlocked the bootloader and installed twrp back turned my device up.
Then I unchecked oem unlocking under developer options.
Relocked the bootloader once again.
And now I am stuck at bootloader,not able to unlock it even this time as I turned off oem unlocking.
Now I can only open bootloader.
Please help!
thanks in advance
There is a thread about Hard Brick fixing.
Normally it should work it's using low level tools.
I just can't understand this obsession to relock, there is absolutely no need to and can lead easily to a cold brick.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
EDIT: Solution: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
frap129 said:
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
Click to expand...
Click to collapse
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Sent from my MHA-L29 using Tapatalk
danon.brown said:
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Click to expand...
Click to collapse
I already tried that command as I said in my post (unless there's one other than "fastboot flashing unlock" that I'm not seeing in the essential forum)
Can you see your phone with fastboot devices?
Sent from my MHA-L29 using Tapatalk
A few others with the phone have reported the same issue in the "rooting" thread...not sure what's going on!
I had the essential phone and had to get a more current Version of adb.
Sent from my MHA-L29 using Tapatalk
did you enable developer settings and see if there is a setting to allow OEM unlock?
Code:
fastboot flashing unlock
will unlock it
When I first booted the phone and enabled USB debugging, the OEM Unlock was greyed out. I had to put my sim card in for it to allow me to enable it. Then using the fastboot flashing unlock worked from bootloader.
fastboot flashing unlock worked for me.
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
@frap129 hope you get it sorted. Glad to see you got a 2 XL as well! Would love to eventually see Carbon and Electron on the 2 XL. Have been missing them since I RMA'd my 6P for an XL. :good:
What is the point if the stock android phone has locked bootloader!
I miss NEXUS phones
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Thanks for all the responses, I guess it's just my fastboot version. I have the latest that's on the aur, but I'll try manually downloading from Google's site.
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
cryppie said:
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Click to expand...
Click to collapse
Disagreed. This was not necessary with the OG Pixel.
Further, I think most people here know that the chances of unlocking a Verizon bought Pixel are slim to none.
dirtyfingers said:
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
Click to expand...
Click to collapse
Ive been using adb reboot the whole time and can't get it to work, thanks for the heads up!
UPDATE: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Sorry for the double post, I just wanted to make sure anyone following this with the same issue gets the solution.
cwalker0906 said:
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
Click to expand...
Click to collapse
You could have also used the sdk manager to update the platform-tools.
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:
Hello,
I have a Pixel C that I looking to sell and wanted to return it to stock recovery/image. After attempting to manually flash the image files and getting a error on all, I double checked my bootloader status and it appears to be unlock as indicated on the device. However, after using the skipsoft unified android toolkit, it shows my device as locked. I have unlocked and locked, and repeated this process so many times and I still cannot flash the stock image onto the device.
All and any help is appreciated.
Thank you,
Michael
mbrecchia said:
Hello,
I have a Pixel C that I looking to sell and wanted to return it to stock recovery/image. After attempting to manually flash the image files and getting a error on all, I double checked my bootloader status and it appears to be unlock as indicated on the device. However, after using the skipsoft unified android toolkit, it shows my device as locked. I have unlocked and locked, and repeated this process so many times and I still cannot flash the stock image onto the device.
All and any help is appreciated.
Thank you,
Michael
Click to expand...
Click to collapse
Try method from Google site
Gesendet von meinem Pixel 2 XL mit Tapatalk
Google site method does not work. I have tired every method I can find, but for some reason I am unable to flash any data.
What error you getting? We need more info than " getting a error on all"