Related
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
ive tried fastboot oem unlock using nexus toolkit and direct through the command line with same results
is this guide any good?
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
Otherwise you have this GUIDE
Phone:I9100P
Kernel:Dorimanx
ROM:4.2.1 Vanilla RootBox
Tablet:Nexus 7
Kernel:M-Kernel
ROM:4.2.1 AOKP PUB
MOD:JusTunBean
welly_59 said:
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
Click to expand...
Click to collapse
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
liamwli said:
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
Click to expand...
Click to collapse
i managed to get it working after erasing everything as in the guide above. I had to keep unplugging the device and trying again though and after a few attempts it worked
when encountering this error i simply cycled through the options (using volume) and said boot into bootloader, familiar windows device dis/connect and then tried the fastboot flash boot boot.img cmd again, worked a treat, currently flashing the system part.
hope this helps!
Update V20E 6.0 T - Mobile
H901 - T Mobile
V20e (6.0)
https://drive.google.com/open?id=0B3R77elw9JjNSmVsVjhjbWdLcEU
V20j (6.0)
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1FRFU652MMA4P3503B0ON/H90120j_00_0712.kdz
V20l (6.0)
http://pkg03.lime.gdms.lge.com/dn/d...1478794859&h=59e2525cdab042c7ac78e39941ad3362
Woww. Thánks for sharing
reachedxyz said:
Woww. Thánks for sharing
Click to expand...
Click to collapse
Bày đặt nói tiếng anh
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?
Sent from my LG-H901 using XDA-Developers mobile app
diamantericos said:
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?[/URL]
Click to expand...
Click to collapse
KDZs are factory firmware files, untouched.
Is it possible to root? Bootloader remains unlocked?
jonsat said:
Is it possible to root? Bootloader remains unlocked?
Click to expand...
Click to collapse
Bootloader can be unlocked. No word on root yet
Do you have to have stock recovery to used the kdz file
I'll wait for the rooted stock version, but I'm sure we'll be seeing it this week!
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
I nand back to a stock build thru twrp. Booted to Android ran LG bridge and it worked fine
Sent from my LG-H901 using XDA-Developers mobile app
shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
sikander3786 said:
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
SmileBigNow said:
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
No I don't think so. Not with MM KDZ.
sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
sikander3786 said:
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
Click to expand...
Click to collapse
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Eliminater74 said:
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Click to expand...
Click to collapse
That's bad, real bad.
The first thing most of us will want to know here is if downgrade to 5.1.1 is safe? If yes, which build? I don't think we have many options there.
For rooting, can we try opening the LG Com port using the old 9% method? Maybe then we can try flashing a root injected system image? I am away from PC so can't try this right now. Won't be asking otherwise.
I will wait for a flashable zip. And hope it will have root. Or maybe stick with the Korean Mm port
Sent from my LG-H901 using XDA-Developers mobile app
Yep. Flashable zip is the way to go for now (if it somehow becomes available). I am not sure how to read system dump from a locked-down device and create a Flashable zip.
I will try downgrading to 5.1.1 in the morning.
Just wondering, why allow bootloader unlock if LG and T-Mobile want to lock down everything else?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (22732 KB)...
OKAY [ 0.489s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.499s
How do i fix this error? It's preventing me from installing twrp on my device. I have my bootloader unlocked and yet it refuses to work everytime.
Bootloader and frp unlock ?
jac10000 said:
Bootloader and frp unlock ?
Click to expand...
Click to collapse
I lost patience and decided to relock my bootloader and unlock it again. Now i face another mess of a problem.
jac10000 said:
Bootloader and frp unlock ?
Click to expand...
Click to collapse
Somehow, after relocking the bootloader, the android keyboard has refused to function anymore. And if i can't set up a wifi connection and configure my phone to start up, i'll be stuck and unable to use my phone any longer. So much for locking my phone to start the rooting process from scratch.
Ribombee said:
Somehow, after relocking the bootloader, the android keyboard has refused to function anymore. And if i can't set up a wifi connection and configure my phone to start up, i'll be stuck and unable to use my phone any longer. So much for locking my phone to start the rooting process from scratch.
Click to expand...
Click to collapse
Make sure to unlock your bootloader and FRP is unlocked. Which firmware/region are you currently using?
dexz said:
Make sure to unlock your bootloader and FRP is unlocked. Which firmware/region are you currently using?
Click to expand...
Click to collapse
I attempted to unlock the bootloader, which was the original plan, but my keyboard doesn't show up at all when i try to set up my wifi and sign into my phone to unlock the FRP. I'm stuck with Google Voice and i still can't find a way to start using my phone again because of it.
Ribombee said:
I attempted to unlock the bootloader, which was the original plan, but my keyboard doesn't show up at all when i try to set up my wifi and sign into my phone to unlock the FRP. I'm stuck with Google Voice and i still can't find a way to start using my phone again because of it.
Click to expand...
Click to collapse
So I assumed you are in Nougat. Reflash update_data.zip again via twrp (if you are using it)
dexz said:
So I assumed you are in Nougat. Reflash update_data.zip again via twrp (if you are using it)
Click to expand...
Click to collapse
I can't do that either. My bootloader is locked as we speak. I was planning on trying to lock it back and then unlock it again then attempt to install TWRP again. However, my keyboard magically disappeared from existence after i locked the bootloader.
Ribombee said:
I can't do that either. My bootloader is locked as we speak. I was planning on trying to lock it back and then unlock it again then attempt to install TWRP again. However, my keyboard magically disappeared from existence after i locked the bootloader.
Click to expand...
Click to collapse
The one way now you need to unlock your bootloader and install twrp. Since internet storage will be encrypted. You have to format data then install update_data.zip and update.zip again.
P/S: You can't install nougat via dload that's why you need twrp.
dexz said:
The one way now you need to unlock your bootloader and install twrp. Since internet storage will be encrypted. You have to format data then install update_data.zip and update.zip again.
P/S: You can't install nougat via dload that's why you need twrp.
Click to expand...
Click to collapse
But how do i unlock bootloader now if i can't enter the device to enable usb debugging and oem unlock?
Ribombee said:
But how do i unlock bootloader now if i can't enter the device to enable usb debugging and oem unlock?
Click to expand...
Click to collapse
You need to go bootloader mode. Shutdown your phone then press volume down and plug in usb cable. You will automatic go to bootloader mode the one with white background then type fastboot oem unlock your-unlock-password
P/S: You don't need to enable usb debugging to unlock your bootloader.
dexz said:
You need to go bootloader mode. Shutdown your phone then press volume down and plug in usb cable. You will automatic go to bootloader mode the one with white background then type fastboot oem unlock your-unlock-password
Click to expand...
Click to collapse
When i do that, it gives me this error.
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock 2044045691602471
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
I can only unlock the bootloader if i unlock the Oem Unlock setting in Developer Options and USB Debugging, both of which i cannot do since my keyboard isn't working anymore. And Google Voice is below useless.
Ribombee said:
When i do that, it gives me this error.
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock 2044045691602471
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
I can only unlock the bootloader if i unlock the Oem Unlock setting in Developer Options and USB Debugging, both of which i cannot do since my keyboard isn't working anymore. And Google Voice is below useless.
Click to expand...
Click to collapse
If you are in Nougat. You can't enable oem unlock. Either it won't showing or in greyed color. You need to enable it from EMUI 4/4.1
dexz said:
If you are in Nougat. You can't enable oem unlock. Either it won't showing or in greyed color. You need to enable it from EMUI 4/4.1
Click to expand...
Click to collapse
Well that just made things ten times better.
I should probably just give up on the phone.
You can just "rollback" to Emui 4.0 and unlock the Oem Unlock setting in Developer Options.
Hi
I am trying to relock the BL for warranty.
I did a EDL-FULL-Nougat, then found out that Nougat does not boot into bootloader.
So I downloaded A2017G_NrollbackM from ZTE, which worked nicely. I'm in bootloader now and see
Code:
C:\>fastboot getvar unlocked
unlocked:
finished. total time: 0.008s
which was expected.
... just I don't understand, why I can't lock or get oem device-info
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
please help, thanks alex
did you enable 'oem unlock' on the developer settings?
yes, sorry forgot to add
lxlx said:
yes, sorry forgot to add
Click to expand...
Click to collapse
so i guess you have been able to lock it?
No, I mean I forgot to add that info in my first post.
I can not run device-info or lock, log posted.
Cheers :/
your Fastboot.exe is too old
Choose an username... said:
so i guess you have been able to lock it?
Click to expand...
Click to collapse
but you didn't even respond to my question
did you enable 'oem unlock' on the Developer settings?
skdubg said:
your Fastboot.exe is too old
Click to expand...
Click to collapse
that sounds promising, where to get the up-to-date fastboot.exe?
Choose an username... said:
but you didn't even respond to my question
Click to expand...
Click to collapse
I tried, but my non-native english failed apparently.
So to be clear:
Choose an username... said:
did you enable 'oem unlock' on the Developer settings?
Click to expand...
Click to collapse
yes I had oem unlock in dev-options enabled. Then I tried
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Post deleted. Didn't notice you are on mm.
lxlx said:
that sounds promising, where to get the up-to-date fastboot.exe?
Click to expand...
Click to collapse
The 15 seconds ADB installer should install the newest fastboot available. But be sure to get rid of the old installation
How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...
lxlx said:
How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...
Click to expand...
Click to collapse
This hasn't got anything to do with the drivers. I mean, delete the fastboot.exe and adb.exe that you have, then download the "15 seconds ADB installer" and install it, and try again
OK, a bit more digging.
I have 15sec-adb installed systemwide in C:\adb>
Code:
C:\adb>dir /B
aboot.img
aboot_lock.img
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
strings.exe
as you can see, I put my aboot dumps there as well, and a strings-linux-like tool - after
reading this thread.
so, I got the ZTE driver to have my Axon7 visible to adb/fastboot (otherwise no device) ... and I have the latest 15sec adb here.
Code:
C:\adb>fastboot devices
823b48f5 fastboot
... but that's the only thing that works. not even easy things like this do
Code:
C:\adb>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.015s
quoting the other thread
What’s missing in this list are fastboot oem commands. These commands are specific to Android device manufacturers, and there is no comprehensive list or documentation anywhere for what fastboot oem commands are available.
Click to expand...
Click to collapse
so I'm not sure if my fastboot version is the problem. I rather think that the Nougat->MM stock thingy, overwrite my Axon7 aboot.img with only a small set of fastboot commands available.
in my backup I see
Code:
C:\adb>strings aboot* | findstr /i oem
C:\adb\aboot.img: 04 0004 OEM_ID1
C:\adb\aboot.img: oem unlock is not allowed
C:\adb\aboot.img: oem unlock
C:\adb\aboot.img: oem unlock-go
C:\adb\aboot.img: oem lock
C:\adb\aboot.img: oem device-info
C:\adb\aboot.img: is_oem_unlock_allowed
C:\adb\aboot_lock.img: 04 0004 OEM_ID1
C:\adb\aboot_lock.img: oem unlock is not allowed
C:\adb\aboot_lock.img: oem unlock
C:\adb\aboot_lock.img: oem unlock-go
C:\adb\aboot_lock.img: oem lock
C:\adb\aboot_lock.img: oem device-info
C:\adb\aboot_lock.img: is_oem_unlock_allowed
so in old and new aboot I had oem-commands available, back then...
I'm not an expert, but do you guys really know that my problem is related to the PC-config I have, and not to the device-config?
I can not check aboot on device, as I'm not root.
update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck
lxlx said:
update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck
Click to expand...
Click to collapse
Pretty sure miflash cannot lock your bl.
Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.
lxlx said:
Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.
Click to expand...
Click to collapse
I think it is still unlocked. I read something weird about the message not appearing after having a full stock system
But if you're gonna sell it/claim warranty, who cares?
update, ZTE repaired the display
lxlx said:
update, ZTE repaired the display
Click to expand...
Click to collapse
Did you lock the bootloader after all?
I guess they wouldn't even notice if the 5 sec screen didn't show up lol
BL still unlocked.
I sent it with MM-B10-FULL-EDL, where 5sec screen was not displayed.
And got it back with MM-B06 ... with 5sec screen
so I guess what happened:
- ZTE turns on, does not see 5sec, repairs display, does usual EDR 'update' which is actually a downgrade to MM-B06, then sees 5sec-warn and thinks of what to do now, but as screen is repaired, what else than return
OR
- ZTE repairs screen (VIP) although bootloader unlocked
either way, all good.
what I learned is
- fastboot parameters need to be in aboot.img
- I can't do getvar or oem-lock until I flash another aboot.
Anyone with A2017G and unlocked BL who needs to send back:
EDL to A2017G_B10_FULL_EDL.zip
and hope you also have hidden 5sec screen (BL still unlocked)
Hi guys. So I finally found a way to unlock a bootloader on a Verizon Pixel. Without further ado, let's get started. This method works on Pixel and Pixel XL.
1. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.
2. Eject sim card from your device.
3. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of screen lock.
4. Go to Developer Options and enable USB debugging.
5. Connect your phone to PC.
6. Open CMD in adb directory and type
Code:
adb shell pm uninstall --user 0 com.android.phone
7. Restart your device.
8. Connect to WiFi, open Chrome and go to google.com (or any website really).
9. Go to Developer Options and enable OEM unlocking.
10. Reboot into bootloader and via CMD run
Code:
fastboot oem unlock
or
Code:
fastboot flashing unlock
11. Profit
Be aware that unlocking bootloader removes everything from your device.
amend said:
Credit to members LeoTheRomRasta and Qu3ntin0 for making this method available to the community on the Bounty thread yesterday. https://forum.xda-developers.com/pi...rizon-pixel-bootloader-unlock-t3740911/page14 There is an ongoing discussion there about variations on this method.
Click to expand...
Click to collapse
UPDATE: Confirmed that this method works on Android Oreo as well as Android P Developer Preview.
Uhm, how do you skip Wi-Fi setup?
EDIT: Guys, can confirm. It works!!! Just tested this as of now. The trick is to factory reset twice because the first reset leaves an indicator to the phone that you did a factory reset just now. Therefore, not allowing you to skip Wi-Fi connection in Setup Wizard. As for the steps, once you opened Google Chrome and visit a website, Go to Developer Options and wait until 3-5 minutes if the option to unlock is still grayed out. You might want to go back and forth one more time to see if the option to unlock is now enabled.
First try, didn't work. Gave it a second go, got it to work. If after you try to enable OEM Unlocking and its still locked, just wait 2-3 minutes with the screen on. Eventually it just unlocked and let me toggle it. Fully unlocked on a 8.1 VZW Pixel.
I think it's better if you remove screen lock and Google account from device before you reset it.
can confirm. It works
Credit to LeoTheRomRasta and Qu3ntin0 on the Bounty thread
Credit to members LeoTheRomRasta and Qu3ntin0 for making this method available to the community on the Bounty thread yesterday. https://forum.xda-developers.com/pi...rizon-pixel-bootloader-unlock-t3740911/page14 There is an ongoing discussion there about variations on this method.
burduli said:
Hi guys. So I finally found a way to unlock a bootloader on a Verizon Pixel. Without further ado, let's get started. This method works on both Pixel and Pixel XL. Haven't tested on Pixel 2/XL yet.
1. Eject sim card from your device.
2. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of lock screen.
3. Go to Developer Options and enable USB debugging.
4. Connect your phone to PC.
5. Open CMD in adb directory and type
Code:
adb shell pm uninstall --user 0 com.android.phone
6. Restart your device.
7. Connect to WiFi, open Chrome and go to google.com (or any website really).
8. Go to Developer Options and enable OEM unlocking.
9. Reboot into bootloader and via CMD run
Code:
fastboot oem unlock
or
Code:
fastboot flashing unlock
10. Profit
Be aware that unlocking bootloader removes everything from your device. It'd be great if someone tested this method on Pixel 2/XL.
UPDATE: Confirmed that this method works on Android Oreo as well as Android P Developer Preview.
Click to expand...
Click to collapse
amend said:
Credit to members LeoTheRomRasta and Qu3ntin0 for making this method available to the community on the Bounty thread yesterday. https://forum.xda-developers.com/pi...rizon-pixel-bootloader-unlock-t3740911/page14 There is an ongoing discussion there about variations on this method.
Click to expand...
Click to collapse
Thanks for pointing that out! I'll copy this into OP.
Confirmed working on Android P DP2
Remove your Google account before factory reset so it let's you skip wifi setup
I just tested this method on a Verizon Pixel XL 2 on the latest security patch and it is working perfectly.
I did a double factory reset and followed the rest of the instructions and then did a double reboot after connecting to WiFi and I can toggle the OEM Unlocking.
Thank you so very much for discovering this!
Thawte
After a reboot the toggle is off and grayed out again... *spoke too soon*
thawte said:
I just tested this method on a Verizon Pixel XL 2 on the latest security patch and it is working perfectly.
I did a double factory reset and followed the rest of the instructions and then did a double reboot after connecting to WiFi and I can toggle the OEM Unlocking.
Thank you so very much for discovering this!
Thawte
Click to expand...
Click to collapse
Thank you for testing and confirming that method works on Pixel 2/XL too!
Good Job Burduli R.I.P Smail Amzdak
burduli said:
Thank you for testing and confirming that method works on Pixel 2/XL too!
Click to expand...
Click to collapse
It did enable the OEM unlock and i toggled it and then tried the unlock commands in the bootloader and they were denied. Once I rebooted the phone, the OEM unlock was disabled and grayed out. Trying steps again...
thawte said:
It did enable the OEM unlock and i toggled it and then tried the unlock commands in the bootloader and they were denied. Once I rebooted the phone, the OEM unlock was disabled and grayed out. Trying steps again...
Click to expand...
Click to collapse
Report back please.
burduli said:
Thank you for testing and confirming that method works on Pixel 2/XL too!
Click to expand...
Click to collapse
burduli said:
Report back please.
Click to expand...
Click to collapse
Just did the same as above and the double reboot on wifi step enabled the OEM Unlock and I agreed. Did a reboot after enabling unlock and the setting persisted.
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.016s
C:\platform-tools>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
C:\platform-tools>
Just rebooted after this and the toggle is grayed out once more and disabled.
I wonder if there is another step for the Pixel XL 2?
thawte said:
Just did the same as above and the double reboot on wifi step enabled the OEM Unlock and I agreed. Did a reboot after enabling unlock and the setting persisted.
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.016s
C:\platform-tools>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
C:\platform-tools>
Just rebooted after this and the toggle is grayed out once more and disabled.
I wonder if there is another step for the Pixel XL 2?
Click to expand...
Click to collapse
Did you try fastboot oem unlock?
burduli said:
Did you try fastboot oem unlock?
Click to expand...
Click to collapse
I will re-do all of my steps and try out this.
thawte said:
I will re-do all of my steps and try out this.
Click to expand...
Click to collapse
Good luck. Looking forward to the results.
burduli said:
Good luck. Looking forward to the results.
Click to expand...
Click to collapse
I am at the fastboot mode and tried the oem unlock:
C:\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\platform-tools>
thawte said:
I am at the fastboot mode and tried the oem unlock:
C:\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\platform-tools>
Click to expand...
Click to collapse
Damn
burduli said:
Damn
Click to expand...
Click to collapse
Here are the usual commands for the Pixel 2...
Unlocking the bootloader
WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution.
On your phone, open Settings, navigate to "System" then "About phone", and tap on the build number 7 times.
Go one menu up, click on "Developer options", and turn on USB debugging and OEM unlocking.
In your terminal, type the following command:
Code:
adb reboot bootloader
Next, decide if you want to do a standard unlock or critical unlock. A critical unlock allows you to directly flash bootloader files, otherwise you will get an error when you try to do so.
Depending on what you decided in the previous step, run the following commands:
Code:
fastboot flashing unlock
(OPTIONAL)
Code:
fastboot flashing unlock_critical
Follow the prompts on your device then reboot!
Not quiet sure why it's rejecting the commands even though the switch is toggled?