Develop Bugs

I think I bricked my vogue :'(

I used CoKeMaN's unlocker. I just followed the instructions in the command prompt. No errors. But when I booted the Vogue it was stuck on the boot screen. Also, I seem not to be able to access the rainbow colored screen thing to fix it.
I know this isn't making anything any easier, but I only have a 4GB memory card, which means I don't think I can fix it with the SD card.
I just really hope this can be fixed. I have no warranty on my phone

Reflash to latest stock ROM for your carrier. Then run the unlocker again. To get into the boot screen press the power button, camera button, then the soft rest button. Hope this helps.

neuteboomt said:
Reflash to latest stock ROM for your carrier. Then run the unlocker again. To get into the boot screen press the power button, camera button, then the soft rest button. Hope this helps.
Click to expand...
Click to collapse
Thanks. How do I get the computer to recognize the connection though, if I can't boot the vogue?

if you can get to the bootloader, you probably would be better buying a non HD microSD card and flash this way.
With the PC, I think (correct me if i'm mistaken) you need to fully boot the device before being able to run the default rom installer.
EDIT: You surely get a connexion when plugin while in bootloader, maybe try this fist

t1mman said:
if you can get to the bootloader, you probably would be better buying a non HD microSD card and flash this way.
With the PC, I think (correct me if i'm mistaken) you need to fully boot the device before being able to run the default rom installer.
EDIT: You surely get a connexion when plugin while in bootloader, maybe try this fist
Click to expand...
Click to collapse
I can't get to the bootloader screen

Paraphrasing IMCoKeMaN's sig, it's stuck at the bootloader, not bricked.

st.jimmy said:
Paraphrasing IMCoKeMaN's sig, it's stuck at the bootloader, not bricked.
Click to expand...
Click to collapse
I don't care about the correct terminology, I care about saving my phone

Dave67 said:
I can't get to the bootloader screen
Click to expand...
Click to collapse
Did you try holding the on/off button, the camera button and the reset to get in bootloader? Then the computer should recognize the connection to your pc.

As long as you can get to the boot loader screen you are fine. Your computer should recognize your vogue in the boot loader state. You are not the first person to have this issue & will not be the last.

neuteboomt said:
Did you try holding the on/off button, the camera button and the reset to get in bootloader? Then the computer should recognize the connection to your pc.
Click to expand...
Click to collapse
I was stuck in the same senario also. Just make sure you hold on those buttons.

Ok, after several attempts I was able to get to the bootloader, and the computer recognizes the Vogue. So I can unlock it with CoKeMaN's unlocker when it's in bootloader mode?
Also, for future reference, no matter what I do, I will always be able to get to the bootloader, right? That can never break?

Dave67 said:
Ok, after several attempts I was able to get to the bootloader, and the computer recognizes the Vogue. So I can unlock it with CoKeMaN's unlocker when it's in bootloader mode?
Also, for future reference, no matter what I do, I will always be able to get to the bootloader, right? That can never break?
Click to expand...
Click to collapse
I would flash to a stock rom first from the HTC site http://www.htc.com/us/support.aspx. Then I would make sure your phone is unlocked by running CoKeMaM's unlocker and then try flashing a custom ROM.
By pressing those three buttons you will be able to get into bootloader.

One X bricked?

Big problem. I was copyng pictures from pc to phone. Progressbar in pc stops in 55% and nothing happened after 10 minutes. So i wake up screen but nothing there, only light comes up. But phone seems to be very laggy. I take off usb cable and holding down power button. Phone restarts but finish in bootloader. There was first surprise. Bootloader is "locked", not re-locked and also "security warning". Before that happened, phone was "unloced" and with custom rom. Unlock with fastboot dont work. It asks in phone to unlock and i can choose that with volume key but after restart it is still "locked" and fastboot command says something "fail, too many links" or something like that. I alreadi try install stock RUU and it say`s that installed and phone will be reboot. After reboot it still go in bootloader
Only thing that changed after installing RUU is that "security warning" is gone. Totally bricked right?

Totally bricked, I'd say. But now you can warranty it out because bootloader is locked.
Sent from my One X

TToivanen said:
Totally bricked, I'd say. But now you can warranty it out because bootloader is locked.
Sent from my One X
Click to expand...
Click to collapse
It is difficult. Phone was bought from Germany but i live in estonia and i dont have any papers from Germany store

http://forum.xda-developers.com/showthread.php?t=2115348
you like me !!! THE MID CHIP HAS CRASH MUST REPAIR ONLY WARRANTY HELP YOU !

Ok, thank you guys! I`ll try warranty then.

[Q] [Help] HTCdev bootloader unlock not working

I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks

Dlome said:
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Click to expand...
Click to collapse
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.

xunholyx said:
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
Click to expand...
Click to collapse
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.

Dlome said:
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Click to expand...
Click to collapse
So, have you tried the code again? And/or have you gone back to the HTCDev site for a new unlock code?

I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.

Dlome said:
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Click to expand...
Click to collapse
Are you copying and pasting the very first part of the code?
The part that looks like:
"(bootloader) < please cut following message >
(bootloader)" ?
IMMEDIATELY after that is what you copy and paste.
The copy should start when it says "<<<< identifier token start >>>>"

I am only copying the <<<< identifier token start >>>> and <<<< identifier token end >>>> along with the string between and leaving out the bootloader tag that is on each line.

I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.

Dlome said:
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Click to expand...
Click to collapse
You seem to be doing everything right. I'm stumped. Hopefully someone else comes along with a solution. @redpoint73?

That's what I was afraid of haha. I don't know why but while I am no expert in this area I do not feel I'm ignorant either yet I always seem to have problems even when I follow the steps correctly >.<
I do appreciate the troubleshooting greatly thank you. I will keep trying things and see what I can find and if I figure it out you bet I will add it here because I can't be the only one getting stuck haha.

Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.

xunholyx said:
Hopefully someone else comes along with a solution. @redpoint73?
Click to expand...
Click to collapse
Ummm, yeah . . . in fact I think I do:
Maybe I'm missing something here. But the Dev Edition comes already bootloader unlocked, and therefore should be no reason to do so.
I think the prompt to unlock never comes up on the phone, since its already unlocked.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
bloodhawk said:
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
Click to expand...
Click to collapse
Yes, this will tell us a lot.
Or boot into bootloader and just see if it says LOCKED, RELOCKED or UNLOCKED.
I bet it says UNLOCKED.

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!

Google Pixel 3XL fastboot locked and Recovery not working

Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you

try sideloading the full OTA.
https://developers.google.com/android/ota

robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?

v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!

Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you

v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable

robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?

sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes

robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.

sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.

robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.

sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer

i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,

Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.