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?
Related
I need a little help here, I am trying to unlock my bootloader , I have already able oem unlocking and install the proper driver. But everytime I try fastboot oem unlock , it just reply " failed : oem unlock is disabled " in CMD. Does anyone else have the same problem?
I had problems with an older version. I think you have to try to update your platform-tools (fastboot, adb). Good luck!
So , where can I get an updated version?
e.g. https://developer.android.com/sdk/index.html and there "SDK Tools Only"
I kinda have the same issue I have downloaded all the proper tools and drivers but whenever I try the fastboot oem Unlock command it comes back saying it's completed but my screen just stays on the fastboot logo and does nothing until I restart it this happens on my pc and my mac, I'm not sure what I'm doing wrong and at this point I'm very frustrated.
Sent from my ONE A2005 using Tapatalk
thesickness13 said:
I need a little help here, I am trying to unlock my bootloader , I have already able oem unlocking and install the proper driver. But everytime I try fastboot oem unlock , it just reply " failed : oem unlock is disabled " in CMD. Does anyone else have the same problem?
Click to expand...
Click to collapse
Enable OEM Unlocking in developers option. Check if this solves the issue.
So I updated adb and fastboot with the latest SDK tools , and I still get "OEM unlock is disable" in fastboot even thou I have clearly enable USB debugging and OEM unlocking. I really need another way around here, the stock rom which is a H2OS feels very bloated for me.
Did you enable "" OEM UNLOCK "" from developer options ?
TheDj408 said:
Did you enable "" OEM UNLOCK "" from developer options ?
Click to expand...
Click to collapse
Yes , I have stated that I enable OEM unlock many times, that is why I need help here.
You might want to disable the pattern lock and then try!
I unlocked my bootloader to install Android 7, but now cannot re-lock it. I need to lock it as SafetyNet is now triggering and preventing me from using Android Pay and my Banking App.
I've tried fastboot oem lock, which returns:
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.005s
fastboot flashing lock just triggers the help text. I've completely re-installed the Android SDK so have the latest fastboot etc...
aSystemOverload said:
I unlocked my bootloader to install Android 7, but now cannot re-lock it. I need to lock it as SafetyNet is now triggering and preventing me from using Android Pay and my Banking App.
I've tried fastboot oem lock, which returns:
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.005s
fastboot flashing lock just triggers the help text. I've completely re-installed the Android SDK so have the latest fastboot etc...
Click to expand...
Click to collapse
That should work, one thing I always forget to do when flashing things at least factory roms is to go back to settings and enable developer options again then usb debugging. Did you do that?
Fe Mike said:
That should work, one thing I always forget to do when flashing things at least factory roms is to go back to settings and enable developer options again then usb debugging. Did you do that?
Click to expand...
Click to collapse
I did, yes.
aSystemOverload said:
I did, yes.
Click to expand...
Click to collapse
I haven't yet tried Android 7 because I'm waiting for xposed. When you updated to 7 do you know if google drivers need to be updated? Not sure if that has anything to do with it but worth a shot.
Fe Mike said:
I haven't yet tried Android 7 because I'm waiting for xposed. When you updated to 7 do you know if google drivers need to be updated? Not sure if that has anything to do with it but worth a shot.
Click to expand...
Click to collapse
I did it all on Linux so no drivers required. It connects fine, just the phone refuses the command.
aSystemOverload said:
I did it all on Linux so no drivers required. It connects fine, just the phone refuses the command.
Click to expand...
Click to collapse
I had to do a factory reset, THEN I was able to do the
Code:
fastboot flashing lock
.
Hey guys! Is there any way to unlock Redmi Pro's bootloader without waiting for permission from Xiaomi? Have anybody found a way to bypass it?
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
hello i haven't on my xiaomi redmi pro eom unlock in the devlopper mode help me pls
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
criszz said:
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
Click to expand...
Click to collapse
Sadly there is no oem unlock option in developer options. I'm on MIUI 8.1.2.0 Stable (MHQCNDI)
EDIT: i just switched to Developer ROM and still nothing.
sorry, my mistake i use another laguage, activate usb debuging , conect to the pc and run adb , if some permision asked alow
I can't unlock it using fastboot oem unlock since it's mediatek device =/ When I try I get
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.016s"
Click to expand...
Click to collapse
i unlocked that way, maybe you do something wrong
try another way without unlocking try flash twrp with spflash tool
Do you remember what miui version did you have when you unlocked this way? Maybe I can roll back to it and then try again. Were you using developer or stable rom?
i was on fake/vendor rom this i thinlk http://blog.geekbuying.com/index.ph...ndroid-6-0-smartphone-firmware-212302-161109/
Crissz, your bootloader was allready unlocked when you received your phone. You cannot do a simple oem unlock via fastboot with a xiaomi phone. It's a fact..
@KarKlim please try fastboot oem unlock-go comand too
This method does not work as many say
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Redmi Pro with Latest stable china rom
Is it possible? Xiaomi regoke my unclock previleges and now i have my Redmi Pro stuck in China Developer Rom. No way to install multilanguase Xiaomi.eu... can someone help please?
Maybe try with a new xiaomi account with different sim card.
And then from a different internet ip, from your friend or something.
I have no idea how they collect data or what. I'm just guessing here.
wow great news for Xiaomi lovers:
wow great news for Xiaomi lovers:
GeekBuying offering 73% off ( Xiaomi Redmi Pro 3GB + 64GB) 184.65 EURO
spam, all post of this user is spam
So, I bought my Redmi Pro today and i want to install xiaomi.eu ROM. Do I have to unlock bootloader first? Or can I do it with unlock bootloader?
No OEM in my xiaomi redmi pro
[[/B]
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Can you help me please because I don't have a OEM unlock option in redmi pro and how to unlock bootloader... please man
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Not worked for redmi note 8 pro ......failed.....
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)