Database Users

Powering down, and re-powering problem

So let me begin with what I'm running.
Stock bootloader-locked.
Nougat 7.1.2 Beta from Google (On the beta program)
No root. Completely stock.
When I updated to 7.1.2 I started having this problem, the phone did not start up right after the update. It took a few hours to finally get the phone to come on, when I did I opted out of the beta and went back to 7.1.1, flashed back, phone started, yay!
Except.....
Now if I shut the phone down now I cannot get it to power on at all, doesn't respond to anything, no stock bootloader by pressing power+vol down, nothing.
The only way to get this phone to load up is I have to wait until the battery fully dies, charge to full and then power on the phone and it will start. Even after all this I still can't power down and enter stock recovery/bootloader.
Any idea on what's going on?

Chewmasey said:
So let me begin with what I'm running.
Stock bootloader-locked.
Nougat 7.1.2 Beta from Google (On the beta program)
No root. Completely stock.
When I updated to 7.1.2 I started having this problem, the phone did not start up right after the update. It took a few hours to finally get the phone to come on, when I did I opted out of the beta and went back to 7.1.1, flashed back, phone started, yay!
Except.....
Now if I shut the phone down now I cannot get it to power on at all, doesn't respond to anything, no stock bootloader by pressing power+vol down, nothing.
The only way to get this phone to load up is I have to wait until the battery fully dies, charge to full and then power on the phone and it will start. Even after all this I still can't power down and enter stock recovery/bootloader. Any idea on what's going on?
Click to expand...
Click to collapse
Interesting. You can't button press and get into bootloader? That's hard wired. Maybe a bad power button? I was going to suggest wiping cache from recovery as a first step, but you NEED recovery mode to do anything. At a minimum I would go into Dev Settings and allow both OEM unlocking and USB debug straight away. This way you can use ADB, and if you end up in a bootloop you can still unlock the bootloader and flash images and maybe a recovery . Do you know which 7.1.1 build you are on? Set up ADB/fastboot and try adb reboot recovery from within the OS. Maybe get you into recovery so you can at least wipe cache to start. Later, you may also be able to sideload an OTA from stock recovery (if adb reboot works). If the OTA doesn't fix it, you may need to do a factory reset. ADB will also allow you to pull any valuable files off the device.

I've actually signed up again and am running the beta 7.1.2 OTA Google beta program.
Security patch: January 5/2017
Baseband version: angler-03.79
Kernel version: 3.10.73-geac7D674
[email protected] #1
Tue Dec 13 10:11:12 UTC 2016
Build Number: NPG05F
I've been back and forth with 7.1.1 and 7.1.2 and it does the same thing with each build.
I tried unlocking with Wugs toolkit but as soon as I get to power off device and go into bootloader I can't get the bootloader screen to show up and I need to wait until the phone dies and charge to 100% and then start the phone regularly.
I do have ADB installed on my PC but anytime I need to get into bootloader I'm screwed.

Chewmasey said:
....I do have ADB installed on my PC but anytime I need to get into bootloader I'm screwed.
Click to expand...
Click to collapse
Thanks for providing lots of good info on where you are at.... most ppl dont. I'm also on 7.1.2 but with zero issues. OK gotcha, so using NRT, under advanced tools you have tried rebooting to both bootloader and recovery, and it failed. You didn't say YES, I enabled USB Debug/ OEM Unlock in developer options. By any means possible get into your OS and enable OEM Unlocking and USB Debugging now before it's too late. You've got to get into your bootloader/recovery and you are still locked with no access to ADB. There is a great driver install/ diagnostic tool in NRT to help you confirm all drivers are there and working. Sounds like you are ready to unlock/wipe in an effort to recover your phone. I think you can recover from this, but you'll probably lose your userdata.

I have the phone up and running right now. I have already went into developer options and checked OEM unlock and have debugging enabled.
When I go into NRT and go to unlock, it connects etc but when it comes to the point of power off device and boot into bootloader the screen is blank. My PC only recognizes the phone as an Android Interface after this and then I have to wait until the phone completely dies and a recharge to power up the phone.
I would try NRT again right now but I'm scared I will be without my phone all day tomorrow.
Damned if I Do, Damned if I don't.

Chewmasey said:
I have the phone up and running right now. I have already went into developer options and checked OEM unlock and have debugging enabled. When I go into NRT and go to unlock, it connects etc but when it comes to the point of power off device and boot into bootloader the screen is blank. My PC only recognizes the phone as an Android Interface after this and then I have to wait until the phone completely dies and a recharge to power up the phone.
I would try NRT again right now but I'm scared I will be without my phone all day tomorrow.
Damned if I Do, Damned if I don't.
Click to expand...
Click to collapse
When the phone is not responsive and you have been discharging it, have you tried holding the power button down for at least 2 minutes? In many cases this forces the phone to restart, but it takes a long time. That may shorten the wait between getting the phone back up.
Did you only start using NRT after the problem, or it was working fine beforehand in bootloader mode (fastboot). There is a separate driver for fastboot, I'm trying to see if that was working before. Since you are trying to unlock, it sounds as if you are past trying to save any data on the phone. NRT uses both ADB and fastboot, but you may have better luck using the command line from your PC. In my previous post I linked to Google's ADB/Fastboot binaries. Instructions are pretty basic. If you can get that setup you can try communicating with the device from the command line. Even if the is screen off, try sending fastboot devices.

Tried everything, gave up bought a used 64gb Nexus 6p.
Last time fiddling with the phone Everytime I touched the power button the red LED blinked.
I'm thinking either the motherboard or the battery.

L31 bricked by flashing rollback package

Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!

Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk

Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.

Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk

Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.

Thanks! I sent you a PM.

Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.

OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??

Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore

Thanks, but the Toolkit says it can't find the device.

Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot

dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk

Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.

I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.

markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.

dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!

Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.

Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!

I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.

Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?

nexus 6p bootloop after oreo update please read full to know more

hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.

alijaved154 said:
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
Click to expand...
Click to collapse
Tried factory reset and reboot?

tropical cactus said:
Tried factory reset and reboot?
Click to expand...
Click to collapse
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude

alijaved154 said:
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
Click to expand...
Click to collapse
You can select factory reset by pressing the volume button . Factory reset will come up. Select by pressing power button and press again to wipe.

tropical cactus said:
You can select factory reset by pressing the volume button . Factory reset will come up. Select and wipe.
Click to expand...
Click to collapse
in fastboot only the options are:
start
barcodes
recovery
bootloader

alijaved154 said:
in fastboot only the options are:
start
barcodes
recovery
bootloader
Click to expand...
Click to collapse
I have factory reset as an option. Not sure why you don't.

tropical cactus said:
I have factory reset as an option. Not sure why you don't.
Click to expand...
Click to collapse
in fastboot? i dont have it i dont know what hapoened to it

alijaved154 said:
in fastboot? i dont have it i dont know what hapoened to it
Click to expand...
Click to collapse
Try reboot bootloader and scroll through options again.

tropical cactus said:
Try reboot bootloader and scroll through options again.
Click to expand...
Click to collapse
comes back to the same screen but will still try today

alijaved154 said:
comes back to the same screen but will still try today
Click to expand...
Click to collapse
Very strange, unless it only shows up if you enable developer options before.

Same problem after update
Exactly same problem after update, no way to factory reset phone, developer option was unlocked

Erroras said:
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Click to expand...
Click to collapse
you are not alone...?

Same issue on one I have my hands on. This could get interesting.

From fastboot can anything be pushed/flashed like a previous actually functional firmware? Is there other specific software to do so? Only got my hands on the defective non functional device today but I'm planning and scheming a fix if possible.

One thing is really interesting. Why only after this update???? Why not after update from 6 to 7 then 7 to 7.1 and after 7.1 to 8.0. I think Google or Huawei is cheating us and forcing us to buy Google pixel.

I also have this issue (I'm using a nexus 5x, but this thread is the closest to my issue I've found), but it came incrementally. First, I started getting reboots every 20m or so, while doing normal phone things (reading, mostly). Then it started getting into bootloops that were 2-3 boots long, and would then work normally for the 20m mentioned above. I tried a factory reset, but it just got worse, and now either reboots on the Google logo or during the Android animation. My fastboot menu only has the regular "Start" as green. The only other options are Restart Bootloader, in red, and Recovery mode, also in red. Power off is there, obviously, but that's it. It started happening yesterday, and worsened to its current point within only a few hours.

Well. I have just joined the club. What is going on with that?

Happened to me today and I was using the latest build of SuperXE 6P.

Guys! lol
1. Dev options in ROM is same old. Settings/about and tap build 10 times to see count down to developer. Back to settings. In there for OEM unlock
2. Factory reset can be done any number of ways.
a. In ROM. Settings/backup and reset/factory reset.
b. From anywhere, hold power+volume down until you see the bootloader. There are 2 possible screens in there. One of them has factory reset. Beware! From here it will likely wipe your sdcard!
c. From recovery. You can get there from bootloader. You can also flash an up to date recovery image from bootloader.
The rest of your recovery process should be provided by the ROM thread by which you will get your choice of ROM.
Make sure you have access to a PC with adb. You will likely need to flash a vendor image

My device is only recognized in fastboot mode. No ADB, no recovery. Tried to uninstall and manually install latest USB drivers, it didn't work. My Nexus is now just stucked in a bootloop. I even tried to flash factory images to no avail. Really don't know what to do...
FYI I have no screen in bootloader allowing me to factory reset: only Start/Reboot/Reboot bootloader/Barcodes, as others stated above.

[How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled -

[How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled -
I experienced the mishap of locking back the bootloader after flashing the device with my signed custom build. The result was that i was no long able to activate the "OEM unlock" in the "Developer options".
The fact is that If you Signe your build you will not be able to rollback to stock build with ADB update / ADB Sideload / SDRAM zip ... because your Bootloader check the signature.
The only way to do it is to flash the OTA or google Factory Build by Fastboot and for that you need your Bootloader to be unlocked.
Here's in red what i did wrong :
- Activate the "OEM Unlock" in Developer options.
- Unlocked the bootloader with Fastboot
- Flash my signed ROM
- At this time the "OEM Unlock" will turn Gray and we can no more use it to activate or desactivate.
- To test some security functions, i did re-lock my bootloader with fastboot. (Forgot that the OEM unlock is disabled).
Here's what i tryed in order to solve :
I did the steps discribed in [How-to] Unlock bootloader on Verizon Pixel/XL by burduli.
That did not solve my issue but it gives me an idea where to look for. Big Thanks to @burduli (Cedit to @Qu3ntin0 and @LeoTheRomRasta)
Here's the steps i did to solve :
No need to be on internet or so on
I did notice on the Device that there was a Guest User account but i had no way to remove it.
To do so i managed to :
1 - Wipe (factory reset) : Setting / System / Advanced / Reset options / Erase all data (Factory reset) => (Find the entry according to your Built / Android version)
2- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volum down button until the device finish booting.
3- Go to setting / System / Advanced / Multiple users
4- tap on Guest, then on "Menu" the [...] on top right of the window
5- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
6- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
7- Your Device will reboot and at this time hold pressed the volum down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
8- Enable Developer mode (tap 7 times on Build number under "About phone")
9 - Goto Developer options and you are done (The OEM unlock option is back and you can enable or disable it)
You can now reboot your device in normal mode .
In Booltloader mode you can use the "Fastboot flash unlock" or Fastboot OEM unlok command to unlock the bootloader

Will this work on Verizon Android 10 ? Thanx

BelligerentGnome said:
Worked for me.
Click to expand...
Click to collapse
Really ? It worked for u on a Verizon locked bootloader ???

Do you think will work on 2xl verizon?

I just tried it out. Android 10, October update. It didn't work. There's nothing we can do at this point, I'm afraid.

BelligerentGnome said:
It did. I just got one off of Swappa, and the OEM Unlock option was greyed out. This fixed it. I'm running Lineage OS 16 now.
Click to expand...
Click to collapse
You didn't happen to take any screens during the process did you? No offense meant, but it's kind of strange that other than the OP, there's no one else confirming their success. Was it Android 10 with the October update?
Confirmed for myself, does not work. I have only taken the Android 10 update, no other updates since. OEM unlocking still disabled.

Oh verizon, still no one else to hummer this? I will donate who can sure to unlock oem method, hahaha

Going into safe mode there's no way for me to delete the guest user...was hoping it'd work for me - Pixel3/Verizon/Android 10

after doing this (unsuccessfully) my sim card is not being recognized?
This happen to anyone else?
jb

Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.

Verizon Pixel 1 - unable to get it working still. as a note, when holding down the power down button during the 'erasing data' phase, the phone goes into Android Recovery Mode (shows me the BL, Baseband, Product/Variant, SN, CPO, UFS, DRAM, Boot-slot, Console (DISABLED), Secure Boot (PRODUCTION), Device is (LOCKED)). From here I can enter recovery mode, see barcodes, Power off, or Start.
I tried the following steps:
. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.
. Eject sim card from your device.
. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of screen lock.
- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volume down button until the device finish booting.
. Go to Developer Options and enable USB debugging.
. Connect your phone to PC.
. Open CMD in adb directory and type
Code:
adb shell pm uninstall --user 0 com.android.phone
- Go to setting / System / Advanced / Multiple users
- tap on Guest, then on "Menu" the [...] on top right of the window
- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
- Your Device will reboot and at this time hold pressed the volume down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
- Enable Developer mode (tap 7 times on Build number under "About phone")
- At this step i went to OEM Unlock and saw it was still disabled.
Is this something we can look at solving through the legal system?

I also was unable to get this to work

tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."

jedpublic said:
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
Click to expand...
Click to collapse
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?

tronoftroy said:
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
Click to expand...
Click to collapse
Yes I did do the 2nd factory reset, which may be significant based on other people's reports...
If I recall correctly, the second time I factory reset, I held Volume Down from the moment I confirmed the restart. Honestly, I was trying so many different things though, so everything kind of blurred together.
One thing to point out is that my Really Blue Pixel was obtained from Google directly, not Verizon.

I've just bought myself a brand new Pixel 1 XL - 128GB Factory Unlocked. Sadly I wasn't aware of all these issues with OEM unlocking via the Developer Menu. Not knowing the drawbacks, I casually breezed through all the upgrades and reached 10.0 (QP1A.191005.007.A3) state. It was then I realised I cocked up...:crying: because no matter what combination of instructions I try in this (and other) threads, I simply cannot get the greyed out menu to budge! I have tried at least a dozen factory resets, countless adb removals, with/without WiFi, with/without SIM, with/without Google sign in, with/without Safe Mode, with/without Guest User Profile delete and so on.... all to no avail:crying:
I am lost at the moment... I'm sure there's other in the same boat as me. I really do hope there is a solution for all of us out there.. any one have any ideas?

For those in previous versions, I can only think of using zero-day exploit with an app such as Qu1ckR00t. But we would need a dev or something to tailor such app for our Pixel. Any other idea is welcome!

I gave up and sold my Pixel 1 XL - thinking of getting a used Pixel 2 instead. I just need this as my backup phone and for travelling. My primary is the Pixel 4 XL.

dfx12345 said:
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Click to expand...
Click to collapse
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018

Taswim said:
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Click to expand...
Click to collapse
My understanding is that you're out of luck with a Verizon Pixel. Mine was a non-Verizon Pixel.

locked bootload, any methods to fix it?

Hi there,
I think I have screwed up my V20.
I have flashed a new rom, met the decryption unsuccessful, format data didn't work.
then I searched a thread, it said lock bootload and then unlock it could help.
then, brick.
I have not entered the new rom and tick on the oem unlock button. and now the phone didn't pass the security check and shutdown automatically.
any methods could help? 9008?
thanks a lot.

magicsword123 said:
Hi there,
I think I have screwed up my V20.
I have flashed a new rom, met the decryption unsuccessful, format data didn't work.
then I searched a thread, it said lock bootload and then unlock it could help.
then, brick.
I have not entered the new rom and tick on the oem unlock button. and now the phone didn't pass the security check and shutdown automatically.
any methods could help? 9008?
thanks a lot.
Click to expand...
Click to collapse
yeah... locking the bootloader has zero to do with encryption/decryption..
If it won't let you back into fastboot mode (volume down+usb connect) and reunlock it.
You might have Download mode/LG UP.... unless you put/left twrp on that. (volume up+usb connect from powered off).
If you don't have either of those and you have an H918 you're screwed.
If you don't have either of those and you have another variant (as long as its not an ARB 1 ls997) it may be possible to reflash using the leaked firehose (which is arb 0 and signed for the other variants besides H918) but I have no experience with

Phoenix591 said:
yeah... locking the bootloader has zero to do with encryption/decryption..
If it won't let you back into fastboot mode (volume down+usb connect) and reunlock it.
You might have Download mode/LG UP.... unless you put/left twrp on that. (volume up+usb connect from powered off).
If you don't have either of those and you have an H918 you're screwed.
If you don't have either of those and you have another variant (as long as its not an ARB 1 ls997) it may be possible to reflash using the leaked firehose (which is arb 0 and signed for the other variants besides H918) but I have no experience with
Click to expand...
Click to collapse
thanks for the reply mate.
i am afraid I have met the worst situation.
1. able to enter fastboot, but not allow wo unlock bootload. (cos I flashed the new rom and didn't even enter it, and tick the oem unlock button )
2. I have used LAF to change the download mode to be TWRP, so no hope here. the tricky thing is, once I lock the bootload, it could not even enter download mode or TWRP, showed not pass the safety check, will not boot. and then an endless boot loop.
3. my V20 is H918.
4. MY V20 is totally screwed........cry face.