Database Info

Nexus 5 won't prompt for decrypt on boot / TWRP fails to decrypt

So I think I am screwed here but was wondering if anyone has run into similar issue. I was running SlimKat and had the data encrypted and I used BootUnlocker to relock the bootloader after I flashed TWRP a few months back. Been working fine for a couple weeks then yesterday I pull my phone out my pocket and it looks like it factory reset prompting to input all my info. So I reboot the phone thinking could be fluke and it doesnt prompt me for decyption password and again boots to setup screen. If you do login you cannot access the internal storage and there is no data connection. So I rebooted into TWRP and it prompts for decryption password only its not working. If I put in wrong password it comes back immediately that it failed. If I try correct password it tries for 30 - 45 seconds then comes back with failed. So tried downloading factory image and flash with fasboot but was complaining about bootloader locked. So I issued fastboot oem unlock and choose yes the screen switches to unlocked but doesnt wipe anything try to flash again and I get FAILED flash write failure. When I reboot to the bootloader it shows as locked again. I think my flash took a crap. Anyone have any ideas?

I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....

since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.

kj2112 said:
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.

simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.

what do you mean doesnt unlock it?

prestonr83 said:
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
Click to expand...
Click to collapse
very odd!
youre device is seen by fastboot(not adb)?

prestonr83 said:
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
Click to expand...
Click to collapse
That's a good point.
I'm afraid that if you cant flash the stock image, and you can't unlock the bootloader to try other methods....you may be at an impass.
You need to either get the stock image back on. Or unlock the bootloader, Then try my link. Not sure what else can be done here.
Sent from my cell phone telephone....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Oh....and again.....you may have driver issues on the pc, and that's why fastboot isn't seeing the phone. That is the first thing that needs to be corrected.
Sent from my cell phone telephone....

Zepius said:
what do you mean doesnt unlock it?
Click to expand...
Click to collapse
I mean i put it in fastboot issue fastboot oem unlock it prompts me on the phone to choose yes or no. I choose yes it then immediately goes back to fastboot screen and shows unlocked. However when trying to flash anything it fails and upon rebooting back into fastboot it again shows as locked.

Your emmc is dead. RMA it
Sent from my Nexus 5 using Tapatalk

simms22 said:
very odd!
youre device is seen by fastboot(not adb)?
Click to expand...
Click to collapse
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.

prestonr83 said:
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
Click to expand...
Click to collapse
have you tried flashing clockworkmod recovery and factory resetting it there?

simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Advice I would really have to disagree with as it is a built in security measure; telling people to avoid using proven security methods is sketchy in itself. I had my Nexus 4 encrypted for the last 4 months and had never had any issues. What issues are you talking about?

Encryption slows the device down... We all know that. Also, if by chance someone forgets their pw (yes... Seen it happen plenty) you lose al your stuff to get back in.
Anyway, to each their own... But I'm not important enough to worry about what's on my phone getting into the wrong hands. ?

Unable to install OTA updates since unlocking bootloader

Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?

ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.

SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.

Can you root without patching or unlocking the bootloader so you don't fail the integrity check?

robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.

I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.

With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete

socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?

smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread

socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)

smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?

socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.

smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.

socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.

You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.

davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?

No resolution. I sent it back to uk for replacement via seller.

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716

davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.

VZN locked, Pixel stuck at bootloader, recovery mode fails -- what now?

Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK

TromboneKenny said:
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
Click to expand...
Click to collapse
Try reflashing the same factory image ur on

If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.

shagbag913 said:
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
Click to expand...
Click to collapse
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA

KittyRgnarok said:
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
Click to expand...
Click to collapse
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
Yeah that's what I'm thinking. OP test this and if anything breaks report back

That's pretty odd that it would just break like that. If he hasn't messed with anything software related it could be a hardware issue

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?

TromboneKenny said:
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
Click to expand...
Click to collapse
I don't think it would be different. This sounds like a hardware issue, not software.

Is this my fault or a hardware issue? (ERROR: Slot Unbootable: Load Error)

Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.

u found any way to unbrick your phone?

yuva_cool said:
u found any way to unbrick your phone?
Click to expand...
Click to collapse
Nope. The RMA was approved and I'm using a new (refurbished) device.

U had an unlocked bootloader and yet your RMA was approved? @computerslayer

yuva_cool said:
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
Click to expand...
Click to collapse
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.

computerslayer said:
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
Click to expand...
Click to collapse
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.

robocuff said:
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
Click to expand...
Click to collapse
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.

computerslayer said:
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
Click to expand...
Click to collapse
If that's the case, it's a certainty that that's the cause of your problem. You have to be completely stock when you relock it. Flashing the factory boot image should take care of that if all you have done is installed Magisk. That said, I'd still flash the factory image and let it do the wipe, just to be sure.

computerslayer said:
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
Click to expand...
Click to collapse
I have this issue and now my pixel 2 cant boot. It stuck. Cant enter fastboot. This is my last experience with pixel series devices. Its expensive phone, but its too sensitive to brick. I dont know why, an update or a flashing stock rom can make your phone totally unuseable. I just cant accept it

I had exactly the same issue. just keep holding the power button with or without the vol- for a good 30~ seconds or so (it will restart several times) but keep holding.
and make sure you are connected to the PC until you hear the ding that the phone got recognized, then the phone will accept fastboot commands.
This worked for me before I was going to throw the phone in the garbage!

Pixel bricked with locked bootloader

Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).

You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.

post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'

This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905

junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.

Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs

junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?

aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.

Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?

post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.

Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks

HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.

Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks