Develop Bugs

Error while unlocking phone

I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
C:\Users\Ben-Desktop\AppData\Local\Android\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.005s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) Device is unlocked
OKAY [ 0.013s]
finished. total time: 0.020s
Click to expand...
Click to collapse
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0

ganeran said:
I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0
Click to expand...
Click to collapse
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!

Fain11 said:
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!
Click to expand...
Click to collapse
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?

ganeran said:
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?
Click to expand...
Click to collapse
Start reading here:
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133

Modify OTA zip to gain root access

Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you

tcpcd said:
Hello
My device is running on Marshmellow [arm64-v8a] with locked bootloader [i cant able to unlock due to getting unknown command error]
so today i found that OTA which can able to upgrade my marshmellow to android N
so i think if i somehow inject superuser apk in OTA/system/priv-app and then i update my phone using that modified OTA, will it work to gain full root access?
or should i something try another method to inject super user in ota.zip?
so how to do?
Thank you
Click to expand...
Click to collapse
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.

Matt07211 said:
Mostly likely not, bootloader is locked meaning you can only run verified images.
Let's see why you can't unlock the bootloader instead.
What steps have you done, etc.
Click to expand...
Click to collapse
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Code:
+media
+app
+etc
+fake-libs
+fake-libs64
+fonts
+framework
+lib
+lib64
+bin
+nv
+presetapp
+priv-app
+tts
+usr
+vendor
+xbin
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.

tcpcd said:
FIrst i enable usb debugging and oem unlocker in developer setting
then i enter 'adb reboot bootloader' to boot into bootloader
after i entered 'fastboot oem unlock' so i got an error that 'unknown command'
so i guess my device manufacture somehow changed unlocking code.
after googling i found that oem unlock code saved in aboot.img file [https://www.reddit.com/r/Android/comments/54wz8j/how_to_discover_hidden_fastboot_commands/]
therefore i try to grab aboot from /dev/block using dirtycow, but BIG FAILURE
so i thought maybe in OTA Chinese company always hide their backdoor. so what if i inject superuser in my OTA.zip.
EDIT:
File content in OTA.zip
Description about my OTA [1.7gb]
- It can upgrade Marshmellow to Android N, by open recovery mode and choose OTA.zip file from mmc.
- It contain lots of system apk and device mfg apk.
Click to expand...
Click to collapse
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?

Matt07211 said:
What's your device model?
Have you tried searching for <device model> root?
No copy of aboot.img or bootloader etc name I'm a full firmware image?
Is your device the kinda of device where you need to request a unlock code from manufacturers website (I think it's Sony who does that, not sure who else).
Can you give me any more info to work with?
Click to expand...
Click to collapse
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.

tcpcd said:
Model is Coolpad Note5
yes i searched everywhere to find root solution, even in official forum, but no success.
no my device dont need unlock code.
im sending you OTA.zip extracted link so you can see whats inside.
Click to expand...
Click to collapse
I'm wondering, is your device MediaTek based?

Matt07211 said:
I'm wondering, is your device MediaTek based?
Click to expand...
Click to collapse
no its qualcomm/snapdragon based

tcpcd said:
no its qualcomm/snapdragon based
Click to expand...
Click to collapse
Can you be specific?
What fastboot commands work and don't?

Matt07211 said:
Can you be specific?
What fastboot commands work and don't?
Click to expand...
Click to collapse
Code:
fastboot getvar all
^^work only this one
Code:
fastboot reboot
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed

tcpcd said:
^^work only this one
^^this is not woking even. just got output "reboot..." but fone actually not rebooting.
i tried fastboot oem unlock,unlock-go,flashing unlock << all Failed
Click to expand...
Click to collapse
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise

Matt07211 said:
Not even
Code:
fastboot boot boot.img
?
I've sadly never had a device with fastboot, so it ain't my area of expertise
Click to expand...
Click to collapse
i think that command is working, but i didnt checked
i only checked oem commands with fastboot

tcpcd said:
Not even
i think that command is working, but i didnt checked
i only checked oem commands with fastboot
Click to expand...
Click to collapse
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img

Matt07211 said:
If you can boot custom boot.img then you can root it.
I personally rooted the xCover3 by modifying the boot.img
Click to expand...
Click to collapse
no i cant boot custom images

tcpcd said:
no i cant boot custom images
Click to expand...
Click to collapse
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff

Matt07211 said:
Okay. Can you detail, EVERY method you've tried (any apps, fastboot commands Cave's (E.g. Dirty Cow) etc.) So we can get a clear overview and saves us both time as we are not going over the same stuff
Click to expand...
Click to collapse
OKay
I tried Kingroot, kingoroot << Failed
Using dirtycow << Got success :cyclops: for temp root
Used farm-root to pull boot.img << termination after long wait
VIKIROOT << Working but not spawn shell
I only check fastboot oem commands but << failure
Code:
fastbooot oem unlock
fastbooot oem unlock-go
fastbooot oem unlock_go
fastbooot oem flashing unlock
fastbooot flashing unlock
fastbooot oemunlock
Output: FAILED (remote: unknown command)
Big 0
But one command work:
Code:
[stark]:~|$ fastboot getvar all
(bootloader) yl_udiskname:userdata
(bootloader) version:REFRESH_emmccid_new
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4199000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5a7bfbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x140000000
(bootloader) serialno:366da886
(bootloader) kernel:lk
(bootloader) product:MSM8952
all:
finished. total time: 0.022s

So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands

Matt07211 said:
So I believe using dirtycow will probably be your chance at getting root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Unless you figure out the correct fastboot commands
Click to expand...
Click to collapse
Well dirtycow is only option for temp root

would this work on specific firmware, for example a combination firmware (factory binary on samsung) then install a custom recovery from there...?

tcpcd said:
Well dirtycow is only option for temp root
Click to expand...
Click to collapse
Well it's better then nothing, you can work Frkm there if roots such a bug deal for you

I think DC Unlocker Tool Maybe Work.

Security status stuck at S-DBG

Hello everyone,
(was trying to ask this questions to dev thread but my "clearance" is not high enough
I recently played with my HTC10 - unlocked bootloader, did S-OFF, changed CID, etc - well, all that normal usual things
At some point later I decided to go back so I removed root, changed CID back and was trying to put security back to S-OFF when I accidentally used command
fastboot oem writesecureflag 2 (instead of 3).
At the next boot the phone showed me some strange window with some Chinese text, asking me for a password. I put 0000 and the phone told me that the password was Ok, but my data could not be decrypted. It formated everything and that was Ok, but now my security status says "S-DBG".
Now I can't change CID or MID, when I try it tells me:
[email protected]:~/phone# fastboot oem writecid HTC__621
...
FAILED (remote: WRITE CID PERMISSION ERROR)
finished. total time: 0.022s
If I try to change security level to anything, it gives me:
[email protected]:/home/alexr# fastboot oem writesecureflag 0
...
(bootloader) HTC KEY CARD VERSION: 7
FAILED (remote: PERMISSION DENY (NOT_FIND_SMART_IO))
finished. total time: 0.013s
[email protected]:/home/alexr# fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_PASS (0)
(bootloader) Partition verify pass
FAILED (remote: PERMISSION DENY (NOT_FIND_SMART_IO))
finished. total time: 0.974s
[email protected]:/home/alexr#
I tried to use SunShine to reset that but the program told me my phone already had "S-OFF" whereas in fact it does not
Does anybody know what that "S-DBG" mean and more importantly - how to go back to either S-OFF or S-ON??
Thank you!

@beaups
He is one of the Sunshine devs and I'm mentioning him here so that he sees this post. No need to PM him

AlexFlooter said:
Hello everyone,
(was trying to ask this questions to dev thread but my "clearance" is not high enough
I recently played with my HTC10 - unlocked bootloader, did S-OFF, changed CID, etc - well, all that normal usual things
At some point later I decided to go back so I removed root, changed CID back and was trying to put security back to S-OFF when I accidentally used command
fastboot oem writesecureflag 2 (instead of 3).
...
Click to expand...
Click to collapse
I assume you are the same user that opened a support ticket with us. SunShine wasn't written to work with devices in this state. If you want to change your security status you'll need to use another (hardware) solution.
--beaups

beaups said:
I assume you are the same user that opened a support ticket with us. SunShine wasn't written to work with devices in this state. If you want to change your security status you'll need to use another (hardware) solution.
--beaups
Click to expand...
Click to collapse
Yeap, it was me.
Ok, thank you for the answer

Bricked G5 oem blocked

Hi, Yesterday I flashed TWRP recovery in my Moto G5, and as i'm a newbie with Moto's phones i didn't unlock OEM, and I bricked the phone. When I turn on my phone it goes to a bootloop. How can I unbrick my phone, because the phone doesn't boot. I tried to flash the stock rom for my moto g5 XT1670, it wasn't updated and it failed because i'm making a downgrade. My Question is what can I do to "revive" my phone???

LonchoNe said:
Hi, Yesterday I flashed TWRP recovery in my Moto G5, and as i'm a newbie with Moto's phones i didn't unlock OEM, and I bricked the phone. When I turn on my phone it goes to a bootloop. How can I unbrick my phone, because the phone doesn't boot. I tried to flash the stock rom for my moto g5 XT1670, it wasn't updated and it failed because i'm making a downgrade. My Question is what can I do to "revive" my phone???
Click to expand...
Click to collapse
Thats not a Problem, just Google how to unlock and youre fine afterwards.

Unlock the bootloader then flash twrp once more, then flash the rom you want. If it's an oreo rom then flash a 64bit recovery as it's mandatory.
Unlock phone here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

I Tried to unlock bootloader but i don't know if the bootloader is unlocked:
C:\Users\karln\OneDrive\Escritorio\platform-tools>.\fastboot oem unlock BVMF22NAUPPPFUXM3JBP
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.179s]
finished. total time: 0.180s
Is it unlocked or not? if not, what can I do, 'cos I can't boot

LonchoNe said:
I Tried to unlock bootloader but i don't know if the bootloader is unlocked:
C:\Users\karln\OneDrive\Escritorio\platform-tools>.\fastboot oem unlock BVMF22NAUPPPFUXM3JBP
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.179s]
finished. total time: 0.180s
Is it unlocked or not? if not, what can I do, 'cos I can't boot
Click to expand...
Click to collapse
Try to start in Factory mode (Fastboot > Factory Mode). If you can't, you can search about your warranty.

go in settings- about- then type 7 times on build, go back, click on developer options- go to allow oem unlock and turn on. After that retry to unlock via fastboot

LonchoNe said:
I Is it unlocked or not? if not, what can I do, 'cos I can't boot
Click to expand...
Click to collapse
I can't activate oem in settings because i'm in soft brick

Download a fastboot stock ROM and flash it. Since it's official, you shouldn't have any problem. Before flashing, make sure it's a newer ROM version that the one you currently had.

Pixel XL Bootloader Unlock Codes... What to do with KS TOKEN? (Verizon)

Long story short, my OG Pixel XL got an upgrade from Verizon today, and died, one day out of warranty.
Anyhow, I have been searching through the strings in the bootloaders, and I have found some interesting things. There is the option to get unlock tokens.
HTML:
$ fastboot oem get_ks_token
(bootloader) INFO< Please cut following message >
(bootloader) INFO<<<< Identifier Token Start >>>>
(bootloader) INFO70719A130CC737A62AD9E8684FFDF272
(bootloader) INFO6A56EB4CFBD864CE8E8FC43D872F66F4
(bootloader) INFO965A23766AEF80A54BD01A78BE8F018C
(bootloader) INFO99520E4305AA4DA779DA0D948F6F2768
(bootloader) INFO75923D3E2A4662600AFDC3AC357F989C
(bootloader) INFOA0BABDCAB822D06A62FD6AB998954BE5
(bootloader) INFO97CF6B1B29B5651444B3F348AB683C48
(bootloader) INFO9167DBB49A01D526D9895E597C0ADB08
(bootloader) INFO4F9E8C2A306579D4C2392E5776FB67F1
(bootloader) INFO04EDC3D42CA543CFDD5657AD6AF4026A
(bootloader) INFO3B7C2F2B40CD3C5D72D95636377C6F21
(bootloader) INFO520168A6B71480A4BC4C2BCEC13DCD40
(bootloader) INFODBE9CD17162EC0A51C474AFA20FCCC64
(bootloader) INFO4E2C1E22619423C09C6344FB5606C5D8
(bootloader) INFOE180EAF191C69D54272BE57022F11A3C
(bootloader) INFO3D15D1BE88971E43792968A07CA5081A
(bootloader) INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.601s]
Finished. Total time: 0.623s
There is also the option to unlock the bootloader, but the codes just aren't available... When I try the following on a random file, I get...
HTML:
$ fastboot flash kstoken test.txt
target reported max download size of 536870912 bytes
Sending 'kstoken' (0 KB)...
OKAY [ 0.090s]
Writing 'kstoken'...
(bootloader) flash KStoken
FAILED (remote: unlock token check failed)
Finished. Total time: 0.319s
I tried sending the token to HTC at https://www.htcdev.com/bootloader/unlock-instructions/page-2, and they won't help. I get this error:
HTML:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 150.
Error Reason: Extract Token Information Fail.
I am wondering if anybody knows what a code LOOKS like, so I can ask Verizon about the codes, or are the codes programatically generated from the token?

Why not use the method to unlock where you pull the SIM card?

xnatex21 said:
Why not use the method to unlock where you pull the SIM card?
Click to expand...
Click to collapse
What method is that? Are you talking about unlocking your bootloader? Or just "unlocking" the phone to use on a different network?

ryandward said:
What method is that? Are you talking about unlocking your bootloader? Or just "unlocking" the phone to use on a different network?
Click to expand...
Click to collapse
Bootloader - https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866

ryandward said:
What method is that? Are you talking about unlocking your bootloader? Or just "unlocking" the phone to use on a different network?
Click to expand...
Click to collapse
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
If you have a Google Pixel XL, I don't think this applies.

xnatex21 said:
Bootloader - https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
Click to expand...
Click to collapse
Unfortunately, I can't use this method because the phone is unable to turn on adb, since it is currently soft-bricked.
Homeboy76 said:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
If you have a Google Pixel XL, I don't think this applies.
Click to expand...
Click to collapse
Right
I heard from a guy that I will need to disassemble the phone and short out the test points. I have been trying to research about this, but I can't really understand what it is that I am trying to short out. The phone is currently disassembled, and I'm waiting to hear back from him. But, I would like to do some reading beforehand.

ryandward said:
I heard from a guy that I will need to disassemble the phone and short out the test points. I have been trying to research about this, but I can't really understand what it is that I am trying to short out. The phone is currently disassembled, and I'm waiting to hear back from him. But, I would like to do some reading beforehand.
Click to expand...
Click to collapse
Good luck!

Homeboy76 said:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
If you have a Google Pixel XL, I don't think this applies.
Click to expand...
Click to collapse
Nope - this works perfectly on a Verizon-bought Google Pixel XL.
The Google Store variants don't even need to follow this guide.

WaseemAlkurdi said:
Nope - this works perfectly on a Verizon-bought Google Pixel XL.
The Google Store variants don't even need to follow this guide.
Click to expand...
Click to collapse
Well, literally the very first step `adb` requires you to have enabled debugger mode on your phone, which I never did.

ryandward said:
Well, literally the very first step `adb` requires you to have enabled debugger mode on your phone, which I never did.
Click to expand...
Click to collapse
USB Debugging.
Believe me, I tried this on mine, a Verizon variant. No messing around w/ bootloaders. Just simply doing it per the guide.

Hey Waseem, one of us must be confused.
I can't turn my phone on, and the USB debugging option was disabled by the latest update.
Am I following the wrong Guide???
I can't turn my phone on, so I can't enable USB debugging, therefore I can't use ADB.

ryandward said:
Long story short, my OG Pixel XL got an upgrade from Verizon today, and died, one day out of warranty.
Anyhow, I have been searching through the strings in the bootloaders, and I have found some interesting things. There is the option to get unlock tokens.
HTML:
$ fastboot oem get_ks_token(bootloader) INFO< Please cut following message >(bootloader) INFO>(bootloader) INFO70719A130CC737A62AD9E8684FFDF272(bootloader) INFO6A56EB4CFBD864CE8E8FC43D872F66F4(bootloader) INFO965A23766AEF80A54BD01A78BE8F018C(bootloader) INFO99520E4305AA4DA779DA0D948F6F2768(bootloader) INFO75923D3E2A4662600AFDC3AC357F989C(bootloader) INFOA0BABDCAB822D06A62FD6AB998954BE5(bootloader) INFO97CF6B1B29B5651444B3F348AB683C48(bootloader) INFO9167DBB49A01D526D9895E597C0ADB08(bootloader) INFO4F9E8C2A306579D4C2392E5776FB67F1(bootloader) INFO04EDC3D42CA543CFDD5657AD6AF4026A(bootloader) INFO3B7C2F2B40CD3C5D72D95636377C6F21(bootloader) INFO520168A6B71480A4BC4C2BCEC13DCD40(bootloader) INFODBE9CD17162EC0A51C474AFA20FCCC64(bootloader) INFO4E2C1E22619423C09C6344FB5606C5D8(bootloader) INFOE180EAF191C69D54272BE57022F11A3C(bootloader) INFO3D15D1BE88971E43792968A07CA5081A(bootloader) INFO>OKAY [ 0.601s]Finished. Total time: 0.623s
There is also the option to unlock the bootloader, but the codes just aren't available... When I try the following on a random file, I get...
HTML:
$ fastboot flash kstoken test.txttarget reported max download size of 536870912 bytesSending 'kstoken' (0 KB)...OKAY [ 0.090s]Writing 'kstoken'...(bootloader) flash KStokenFAILED (remote: unlock token check failed)Finished. Total time: 0.319s
I tried sending the token to HTC at https://www.htcdev.com/bootloader/unlock-instructions/page-2, and they won't help. I get this error:
HTML:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.Error Code: 150.Error Reason: Extract Token Information Fail.
I am wondering if anybody knows what a code LOOKS like, so I can ask Verizon about the codes, or are the codes programatically generated from the token?
Click to expand...
Click to collapse
I pulled my Pixel xl's unlock token. Bunch of random alpha numericals. Gave it to my sister after she dropped her phone so can't pull it now. Have a 2xl but the command doesn't run on LG but should on the 2. If I'm remembering correctly the command is fastboot oem get_ks_token. You can get all the oem commands by running "strings bootloader.xyz123 | grep oem".
Sent from my Pixel 2 XL using Tapatalk
Sorry if it's already been stated.

ryandward said:
Hey Waseem, one of us must be confused.
I can't turn my phone on, and the USB debugging option was disabled by the latest update.
Am I following the wrong Guide???
I can't turn my phone on, so I can't enable USB debugging, therefore I can't use ADB.
Click to expand...
Click to collapse
Dear @ryandward,
Sorry for the late reply ... Didn't know that you responded (you didn't quote me so I didn't get a notification )
Yes indeed, this is the correct guide.
But why can't you power on your phone? Can't factory reset or downgrade? Or you could power on, but can't toggle USB Debugging or OEM Unlocking? (The former is unnecessary, the latter is normal)
Another point: You only need USB Debugging as to disable com.android.phone ... You can simply type the command on a Terminal Emulator shell.
But again, can you turn on the phone? If not, focus on fixing the bootloop, not on the unlock, at least for now.
Please reply soon.

So I have a SM-G988U (21 ultra Verizon) on Jan 2021 security patch and 3.1 ui (it came this way I believe)
So am I out of luck with using this token method?

Deleted.