Database Info

Can't unlock the bootloader nor start the phone

Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.

There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though

KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.

hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that

Google Pixel Verizon bootloop, Lock bootloader

I lock bootloader on Verizon Google Pixel when my device have TWRP and i have brick! Device Loading up to logo Google on 1 sec and reboot. Fastboot work, but i don't unlock bootloader. In recovery is don't enter. Please help me!

https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.

kkjb said:
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
Click to expand...
Click to collapse
There is still no solution to this problem? ((

Unlock again.

lafester said:
Unlock again.
Click to expand...
Click to collapse
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"

Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
Put the phone in fastboot mode, then run `fastboot flashing unlock` from a PC. If it says unlocking not allowed, you're out of luck, it's a brick now. Never lock your phone without being 100% stock on both slots

Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.

lafester said:
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
Click to expand...
Click to collapse
In this topic https://forum.xda-developers.com/pi...bootloader-t3540772/post77016940#post77016940 man has unbrick Pixel XL, but i think that method will work on Pixel.

Unable to unlock bootloader (OEM unlocking disabled)

Hello,
I couldn't unlock the bootloader as the OEM unlocking's disabled and i can't access system! Everything's erased!
Any help????

A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.

junglism93 said:
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
Click to expand...
Click to collapse
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!

eldeen said:
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
Click to expand...
Click to collapse
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.

junglism93 said:
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
Click to expand...
Click to collapse
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!

eldeen said:
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
Click to expand...
Click to collapse
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots

AndroidNazi said:
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
Click to expand...
Click to collapse
Thanks for help, but could you please show me how to do that?

eldeen said:
Thanks for help, but could you please show me how to do that?
Click to expand...
Click to collapse
Make sure you have the latest fastboot. On the bootloader your phone will either say "slot a" or "slot b" and you should type "fastboot --set-active=b" if you are on slot a or "fastboot --set-active=a" if you are on slot b

still didn't fix the problem... any probable solutions please?

Bricked completely, need advice if it is possible to recover.

Hi everyone, to add some background I am fairly familiar with flashing this device as I have had it for 3 years and have done a lot of tinkering with it. However this does not mean I am good, and I have definitely soft bricked this phone a lot over the years, but today I think I finally hard bricked it.
Basically, I was using stock MIUI but with TWRP recovery and wanted to add my card to Google Pay, however it said my device was not secure (or something) so I thought it must be because I don't have fully stock MIUI. So I decided to see some way to return the stock recovery, and after doing 5 minutes of research I saw that I could flash the stock ROM and then through fastboot run "fastboot oem lock" which would reset it to stock. However I definitely did something wrong because after rebooting into recovery it says "The system has been destroyed, Press power button to shutdown", and the phone will not boot normally anymore.
You might now suggest that I should unlock my bootloader again through Mi account, but the problem is that I wasn't logged into my Mi account, so I think this is impossible. I have tried running "fastboot oem unlock", but that obviously returns an error when I tried.
Is there any hope to recover this device or is it gone forever? I would appreciate any advice. If you need more info please just ask.
Thanks!

futiiile said:
Hi everyone, to add some background I am fairly familiar with flashing this device as I have had it for 3 years and have done a lot of tinkering with it. However this does not mean I am good, and I have definitely soft bricked this phone a lot over the years, but today I think I finally hard bricked it.
Basically, I was using stock MIUI but with TWRP recovery and wanted to add my card to Google Pay, however it said my device was not secure (or something) so I thought it must be because I don't have fully stock MIUI. So I decided to see some way to return the stock recovery, and after doing 5 minutes of research I saw that I could flash the stock ROM and then through fastboot run "fastboot oem lock" which would reset it to stock. However I definitely did something wrong because after rebooting into recovery it says "The system has been destroyed, Press power button to shutdown", and the phone will not boot normally anymore.
You might now suggest that I should unlock my bootloader again through Mi account, but the problem is that I wasn't logged into my Mi account, so I think this is impossible. I have tried running "fastboot oem unlock", but that obviously returns an error when I tried.
Is there any hope to recover this device or is it gone forever? I would appreciate any advice. If you need more info please just ask.
Thanks!
Click to expand...
Click to collapse
hi, u can try to unlock again over mi unlock tool not over fastboot command. if u unlocked before your account is maybe still binded with that phone. so u can try unlock first..
Do u have stock mi recovery on it?

Dadovvv said:
hi, u can try to unlock again over mi unlock tool not over fastboot command. if u unlocked before your account is maybe still binded with that phone. so u can try unlock first..
Do u have stock mi recovery on it?
Click to expand...
Click to collapse
Thanks for responding, I will try this as soon as I can get a different phone to receive the SMS for the Mi account. As for the recovery, I'm not really sure what exactly it is because as I said, when I try to boot recovery it just says, "The system has been destroyed".

Hi, I've found that tutorial, but for other Redmi model, still maybe helpful:

Derenk said:
Hi, I've found that tutorial, but for other Redmi model, still maybe helpful:
Click to expand...
Click to collapse
this is not helpful since u have locked bootloader, video is fake, it is just flashing fastboot rom by cmd nothing else.

Had this same problem a few months ago, just try to unlock the phone again using mi unlock. After unlocking quickly install a custom recovery and you should be good.

Thanks for the suggestions guys, I'm in the process of trying to unlock with mi unlock however it says my account is suspended when I try to log in, I will be trying to recover it but I hope it will not cause any issues with unlocking the phone if I change the phone number as part of the recovery process.

Hello again, it would seem that I will not be able to unlock the Mi account that I used to unlock the device originally so I think I am out of options unfortunately. I will look into buying a new phone.

futiiile said:
Hello again, it would seem that I will not be able to unlock the Mi account that I used to unlock the device originally so I think I am out of options unfortunately. I will look into buying a new phone.
Click to expand...
Click to collapse
u can try to open your phone there are pins which u can use to unlock by bridgeing them by wire or something metal then u can try to flash normally dont know if your phone got that option try to find graphics or videos for your phone maby u wll need service account for miflash with more options for flashing

Hi everyone, I got it unlocked by some guys on Telegram as recommended by @NOSS8!

Question brick phone

help the brick to return to a living state!
I flashed the Indian version, it seemed to work, I blocked the bootloader and that's it. The phone on the key combination always reboots and shows the same thing:
the current image(boot/recovery) have been destroyed and cannot boot
It only reacts to clamping the volume + and - in the off state, appears in the device manager for a couple of seconds "Device with a USB serial interface" and then reboots again and again "the current image (boot / recovery) have been destroyed and cannot boot"
Mtk client does not work: handshake error - read them on the git that the device does not support or the exploit does not work.
What to do, how to unbrick now?

siryx said:
help the brick to return to a living state!
I flashed the Indian version, it seemed to work, I blocked the bootloader and that's it. The phone on the key combination always reboots and shows the same thing:
the current image(boot/recovery) have been destroyed and cannot boot
It only reacts to clamping the volume + and - in the off state, appears in the device manager for a couple of seconds "Device with a USB serial interface" and then reboots again and again "the current image (boot / recovery) have been destroyed and cannot boot"
Mtk client does not work: handshake error - read them on the git that the device does not support or the exploit does not work.
What to do, how to unbrick now?
Click to expand...
Click to collapse
Hello Friend I was asking the same in other forum. Actually I am on the Indian firmware running OK but I want to relock bootloader. I want to be sure about the correct steps to do it and don't make any mistakes with my phone.

Got my phone fixed after locking the bootloader. Since I can't have it fixed on the service center, I looked for someone that can fix it remotely.
It's a paid service though.

ajcayetano92 said:
Got my phone fixed after locking the bootloader. Since I can't have it fixed on the service center, I looked for someone that can fix it remotely.
It's a paid service though.
Click to expand...
Click to collapse
Hi, i have the save problem after locking bootloader, who helped you to fix? Tell me please how to do it ir somebody who can, thanks!

dekkerKOSS said:
Hi, i have the save problem after locking bootloader, who helped you to fix? Tell me please how to do it ir somebody who can, thanks!
Click to expand...
Click to collapse
These are some of the ones I have contacted to fix the unit.
You messages them using whatsapp

ajcayetano92 said:
These are some of the ones I have contacted to fix the unit.
You messages them using whatsapp
Click to expand...
Click to collapse
Were you able to resolve the issue remotely?

siryx said:
Were you able to resolve the issue remotely?
Click to expand...
Click to collapse
Yes. I'm already using it.

ajcayetano92 said:
Yes. I'm already using it.
Click to expand...
Click to collapse
I wrote to the number from the screenshot, but he does not answer me.

did you manage to solve it?

dekkerKOSS said:
Hi, i have the save problem after locking bootloader, who helped you to fix? Tell me please how to do it ir somebody who can, thanks!
Click to expand...
Click to collapse
It's most likely a scam
He says the phone is being repaired remotely, while it can't even connect to a PC, if I understand the phone's behavior after relocking the bootloader well. Then he mentions that it's paid. All these + you can contact them through WhatsApp is more than suspicious.
I saw a few less well-intentioned users on GT Neo 3's forum. Mostly simple liars, but listening to their comments might lead you to trouble, like when one of them claimed it's safe to relock the bootloader after installing the global ROM, he did it, and his phone works as before. I doubt that he has a GT Neo 3.