So, who is going to take the plunge and test the bootloader unlock commands from the Pixel XL 2? I'll try it when I get home but we're talking 3 more hours.
That's what I'm waiting to hear, especially on a VZW model. Mine won't be here until tomorrow.
I'll have to wait till I get home to do this as well. Won't be for another 5ish hours.
The commands for the pixel 2 xl seemed to work, however the unlock_critical send an invalid argument.
efan0388 said:
The commands for the pixel 2 xl seemed to work, however the unlock_critical send an invalid argument.
Click to expand...
Click to collapse
Be careful isn't the Titan M chip supposed to prevent this?
efan0388 said:
The commands for the pixel 2 xl seemed to work, however the unlock_critical send an invalid argument.
Click to expand...
Click to collapse
Have you tried flashing or sideloading anything yet?
efan0388 said:
The commands for the pixel 2 xl seemed to work, however the unlock_critical send an invalid argument.
Click to expand...
Click to collapse
Then unlock critical is unnecessary.
---------- Post added at 09:35 PM ---------- Previous post was at 09:35 PM ----------
vwgti18 said:
Be careful isn't the Titan M chip supposed to prevent this?
Click to expand...
Click to collapse
No. Has nothing to do with unlocking
Golf c said:
Then unlock critical is unnecessary.
---------- Post added at 09:35 PM ---------- Previous post was at 09:35 PM ----------
No. Has nothing to do with unlocking
Click to expand...
Click to collapse
Ahh yeah I read this wrong.
"It prevents malicious attacks from moving your device to an outdated version or attempting to unlock the bootloader"
TheBobMiller said:
Have you tried flashing or sideloading anything yet?
Click to expand...
Click to collapse
No not yet just wanted to unlock it before inset it up so I wouldn't have to set it back up after unlock.
efan0388 said:
No not yet just wanted to unlock it before inset it up so I wouldn't have to set it back up after unlock.
Click to expand...
Click to collapse
That's pretty smart! Although they've made it considerably easier to set up the phone again but it makes sense.
Too bad Verizon versions will be locked down
Bootloader unlocked. Didn't attempt unlock critical since another person said it came back with invalid argument. Will see. Waiting for factory images to attempt root. Love this phone. My Pixel 2xl is at the bottom of the Wisconsin river. Or maybe in the Gulf of Mexico by now . Lol. Don't need it anymore anyway. Would have been nice to give it to one of my woman though.
Golf c said:
Bootloader unlocked. Didn't attempt unlock critical since another person said it came back with invalid argument. Will see. Waiting for factory images to attempt root. Love this phone. My Pixel 2xl is at the bottom of the Wisconsin river. Or maybe in the Gulf of Mexico by now . Lol. Don't need it anymore anyway. Would have been nice to give it to one of my woman though.
Click to expand...
Click to collapse
Hopefully Google is faster than they were last year with factory images. It took a few weeks after release to get factory images.
efan0388 said:
The commands for the pixel 2 xl seemed to work, however the unlock_critical send an invalid argument.
Click to expand...
Click to collapse
From Google's factory image page, you should NOT do an unlock critical on anything OTHER than the P2XL with a specific bootloader version.
For Pixel 2 XL only with loader version prior to TMZ20a: 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:
Click to expand...
Click to collapse
skaforey said:
Hopefully Google is faster than they were last year with factory images. It took a few weeks after release to get factory images.
Click to expand...
Click to collapse
I was trying to remember. I thought I waited a week. But got my 2xl in late October
Golf c said:
I was trying to remember. I thought I waited a week. But got my 2xl in late October
Click to expand...
Click to collapse
I just double checked and it only took about 4 days. Apparently those 4 days (without root) felt like a few weeks to me since that how I remembered it
skaforey said:
I just double checked and it only took about 4 days. Apparently those 4 days (without root) felt like a few weeks to me since that how I remembered it
Click to expand...
Click to collapse
It felt like a week to me. Lol. I wonder how long it will take this year? We got are phones alot quicker. I'm hopeful for soon
Enabled wifi, skipped everything else.
Settings, system, about Phone, build number, Tap tap taparoo until developer is enabled
Go into Developer options, enable OEM unlocking.
Start latest ADB
Enter into fast boot, I just restarted with hold power and volume down
Or you can simply paste
Code:
adb reboot bootloader
Paste
Code:
fastboot flashing unlock
Then I started transferring to the new device.
Now that it's unlocked you won't have to reset to default when root comes available.
OK not sure why this isn't working, but I can't get it to work. I have the unlocked version from google direct. I have installed adb and fastboot (I have done this with past phones, past pixels so I'm familiar...).
I enabled oem unlock and usb debugging in developer options...
adb devices detected the phone, I was able to "adb reboot bootloader", then I checked "fastboot devices" and again I saw my device. I tried "fastboot flashing unlock", "fastboot flashing unlock_critical", and "fastboot oem unlock".
With oem unlock I got an invalid command error. with the other 2 all I got was the list of available fastboot commands.
Do I have the wrong fastboot somehow?
largeselection said:
OK not sure why this isn't working, but I can't get it to work. I have the unlocked version from google direct. I have installed adb and fastboot (I have done this with past phones, past pixels so I'm familiar...).
I enabled oem unlock and usb debugging in developer options...
adb devices detected the phone, I was able to "adb reboot bootloader", then I checked "fastboot devices" and again I saw my device. I tried "fastboot flashing unlock", "fastboot flashing unlock_critical", and "fastboot oem unlock".
With oem unlock I got an invalid command error. with the other 2 all I got was the list of available fastboot commands.
Do I have the wrong fastboot somehow?
Click to expand...
Click to collapse
I think USB Debugging and OEM unlock are toggles in Developer options after you activate Developer options (look at the post above yours)
Do you have the latest SDK Platform-tools r28.0.1?
I think you have to open a Command Prompt in the adb/fastboot folder then type fastboot flashing unlock and press enter.
Homeboy76 said:
I think USB Debugging and OEM unlock are toggles in Developer options after you activate Developer options (look at the post above yours)
Do you have the latest SDK Platform-tools r28.0.1?
I think you have to open a Command Prompt in the adb/fastboot folder then type fastboot flashing unlock and press enter.
Click to expand...
Click to collapse
Thanks for responding! Yes, it is r28.0.1, yes I toggled usb debugging and oem unlock in developer options, and yes I opened the command prompt in the fastboot folder....so I feel like it should be working...but here I am.
Related
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.
There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.
plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.
Anyone root the Pixel 4 XL from Google Play store yet?
Can the Pixel 3 XL Android 10 root method be used for Pixel 4 XL Android 10 root?
*Update2 (10/24/2019 6:00PM): Factory Images have been released!
They are available at below links. Multiple users say they have root working now.
*Note: Multiple images are listed. For my Pixel 4 XL 128GB purchased directly from Google Play store, the image is the first one "10.0.0 (QD1A.190821.007, Oct 2019)". You can verify in "Settings" >> "About Phone"... near bottom you will see "Build Number"
Factory: https://developers.google.com/android/images#coral
OTA: https://developers.google.com/android/ota#coral
According to @Samg381 the method to gain root is to follow the guide outlined here: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Below are steps I personally followed:
Download latest Magisk Manager - https://github.com/topjohnwu/Magisk/releases/download/manager-v7.3.5/MagiskManager-v7.3.5.apk
Install Magisk manager on my Pixel 4 XL
Download latest factory image with build number that matches my phone's version from this URL: https://developers.google.com/android/images#coral
Extract the zip file contents
You will see one more zip file, extract those contents
Copy the boot.img file to your phone (you can plugin USB to your PC and put it in your "Downloads" folder
Open Magisk Manager, click "Advanced" >> "Recovery Mode"
Click the top "Install" button
When prompted click Install again, then "Select and Patch a file" >> Select the boot.img file you copied to your pixel 4 xl earlier.
it will create a new file "/storage/emulated/0/Download/magisk_patched.img"
Plugin your phone to your PC again via USB, copy this new file in same folder as your adb sdk files.
open cmd prompt type:
adb devices
*Note: unlock your phone and approve ADB access if prompted
adb reboot bootloader
fastboot devices
fastboot flash boot magisk_patched.img
If it works you should get somthing like
fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot_a' (32092 KB)...
OKAY [ 1.167s]
writing 'boot_a'...
OKAY [ 0.325s]
finished. total time: 1.494s
Reboot your phone, open Magisk manager again, and verify it shows you now have root!
I would recommend everyone who plans to root unlock their bootloader NOW as it does wipe your data just like other Pixel phones have when unlocking bootloader... I already unlocked my bootloader.
FYI, the process to unlock Pixel 4 XL bootloader is easy:
Boot Pixel 4 XL, go through initial setup guide (do not bother adding account as you will wipe data shortly)
"Settings" >> "About Phone" >> Tap "build number" about 10 times till "You are a developer"
"Settings" >> "System" >> "Advanced" >> "Developer Options"
Check "OEM unlocking"
If "OEM Unlocking" is greyed out, either "Bootloader is already unlocked", or you need to do factory reset, then go through steps 1-4 again. On my phone I had to wipe data once, then OEM Unlock
Check "USB Debugging"
Connect Pixel 4 XL to your PC with SDK tools installed
adb devices
unlock your Pixel 4 XL... you will see a prompt asking for ADB permissions, say yes
adb reboot bootloader
fastboot devices
fastboot flashing unlock
Pixel 4 XL will now ask if you want to unlock bootloader, press volume up or down once... then power button once to confirm. WARNING it will wipe all your data...
You didn't try since you have unlocked your bootloader
Mine is still locked.
Waiting for John to root his first.
It's not possible to root without the factory image. We probably won't see the factory image until the 24th.
And if we bought through carrier will there be any way to root? I've always bought from Google, but I couldn't afford it this time, so I went with the T-Mobile jump plan. Then went to unlock the bootloader on it today and says not available for carrier devices. Feel like I'm dying a bit on the inside
Maybe there will be an unlock method in the future, but I wouldn't count on it anytime soob
Unlocked my google version right out of the gate through settings. No ADB required. Waiting on a root method now.
Samg381 said:
Unlocked my google version right out of the gate through settings. No ADB required. Waiting on a root method now.
Click to expand...
Click to collapse
That only enabled your ability to unlock. You still have to do it through fastboot and wipe your data.
jruizdesign said:
And if we bought through carrier will there be any way to root? I've always bought from Google, but I couldn't afford it this time, so I went with the T-Mobile jump plan. Then went to unlock the bootloader on it today and says not available for carrier devices. Feel like I'm dying a bit on the inside
Click to expand...
Click to collapse
Verizon is a different animal, they apparently won't allow you to unlock it at all. But the other companies, I don't see why, after you pay it off, that you couldn't unlock it. Carrier locked = sim locked. You pay off a device, you get the sim unlocked. I'm actually rather surprised that there are that many people out there that would expect carriers to allow their devices to be unlocked, even if they're not paid for. You may have to wait a bit, but I see no reason why they won't let you unlock after it's paid off.
mitchdickson said:
That only enabled your ability to unlock. You still have to do it through fastboot and wipe your data.
Click to expand...
Click to collapse
Ah, gotcha. It's been a while. Thanks.
mitchdickson said:
That only enabled your ability to unlock. You still have to do it through fastboot and wipe your data.
Click to expand...
Click to collapse
Lol, must be a noob ?
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Looks like the process is fairly straightforward for this device as well. about as easy as any other unlocked device, I would say
ZeroKool76 said:
Lol, must be a noob
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Looks like the process is fairly straightforward for this device as well. about as easy as any other unlocked device, I would say
Click to expand...
Click to collapse
Be humble.
No luck unlocking my Verizon XL. With a quick glance at the VZ 3 XL posts - I'm assuming I shouldn't hold my breath?
vanydotk said:
It's not possible to root without the factory image. We probably won't see the factory image until the 24th.
Click to expand...
Click to collapse
Oh? I was not aware that was required. Thanks for the information.
Looking forward to root so I can re-enable Google's Daydream View app. Dumb Google, why would you bother to set the phone as not supported? If Google does not support Daydream View, why not "let it free" for anyone to use, especially phones like Pixel 4 XL with 90Hz display!
I did manually install the APK and while it does the prompt saying not supported, it does still render smoothly (did not try forcing 90hz, feel like it should have been smoother... it rendered without any issues, but not sure if it was 90hz smooth or not).
Anyone try any of the other VR apps like VR Ridge? I had tried that with my original Pixel XL but the framerate was never very good, I wonder if Pixel 4 XL is good enough to make the purchase worth it (of VR Ridge that is)
boneriffic said:
No luck unlocking my Verizon XL. With a quick glance at the VZ 3 XL posts - I'm assuming I shouldn't hold my breath?
Click to expand...
Click to collapse
People on the Verizon pixel 2 and P2XL are still holding their breath....so yeah!
Please heed my warning, I have spent months of my life waiting on XDA for root methods on Verizon phones.
Don't expect root anytime soon (if at all) if you have the Verizon version. I hate to be defeatist, but I don't want others to suffer as I have in the past.
Your best bet is to return, or sell your verizon phone and purchase a google version.
Picture 24th, the factory images should drop, we can then patch the boot.img and obtain root. Version users probably are getting the shaft again...
What about other carriers? T-Mobile shows OEM unlocking is not available for carrier devices
None of you guys tried pulling your boot.img and patching it in magisk?
---------- Post added at 12:09 AM ---------- Previous post was at 12:08 AM ----------
jruizdesign said:
What about other carriers? T-Mobile shows OEM unlocking is not available for carrier devices
Click to expand...
Click to collapse
On similar devices such as OnePlus you have to get it carrier unlocked and then you can unlock the bootloader afterwards, this one is likely going to be the same.
krabman said:
None of you guys tried pulling your boot.img and patching it in magisk?
---------- Post added at 12:09 AM ---------- Previous post was at 12:08 AM ----------
On similar devices such as OnePlus you have to get it carrier unlocked and then you can unlock the bootloader afterwards, this one is likely going to be the same.
Click to expand...
Click to collapse
As far as I can tell we need factory images or a working custom recovery to grab it from the phone and we have neither at the moment.
In order to allay concerns about security, the major carriers don't want their phones to have an unlocked bootloader. This is an effort to be more enterprise user friendly.
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking
Thats great thanks
I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too
Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?
Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.
Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch
Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!
underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock