PLEASE help me! Google Pixel 2 got stuck in bootloader! - Android Q&A, Help & Troubleshooting

I was testing the "fastboot" command in bootloader mode today and I got stuck in bootloader after I ran the command "fastboot flashing lock".
My device won't boot into system nor will RECOVERY MODE work.
Code:
$ fastboot reboot
Rebooting OKAY [ 0.007s]
Finished. Total time: 0.007s
I tried to unlock OEM or BOOTLOADER and got two "FAILED".
Code:
$ fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
I checked the device info and it returned
Code:
$ fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
Install stock Android also won't work
Code:
$ ./flash-all.sh
Sending 'bootloader_b' (38728 KB) OKAY [ 0.829s]
Writing 'bootloader_b' FAILED (remote: 'Operation is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_b' (60428 KB) OKAY [ 1.566s]
Writing 'radio_b' FAILED (remote: 'Operation is not allowed in Lock State')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.001s
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: HT7B91A03213
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
Checking 'version-baseband' OKAY [ 0.000s]
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
What else can I do? Could anybody PLEASE help me solve this problem, I am so desperate...:crying::crying::crying:

---

@ayewilling
Your phone obviousy runs an Android version that has A/B-system-partition layout, has AVB enabled, and furthermore it seems phone's boot-loader is locked.
My POV: You at 1st thing of all things should become familiar with HOW FASTBOOT WORKS, WHAT YOU CAN MANAGE WITH IT.
Anyway, running the command sequence
Code:
fastboot devices
fastboot reboot
should boot phone in normal mode.

---

jwoegerbauer said:
@ayewilling
Your phone obviousy runs an Android version that has A/B-system-partition layout, has AVB enabled, and furthermore it seems phone's boot-loader is locked.
My POV: You at 1st thing of all things should become familiar with HOW FASTBOOT WORKS, WHAT YOU CAN MANAGE WITH IT.
Anyway, running the command sequence
Code:
fastboot devices
fastboot reboot
should boot phone in normal mode.
Click to expand...
Click to collapse
Thanks for your relpy!
I have tried several fastboot commands, and it dosen't seem work for me.
"fastboot devices" lists my device, however, "fastboot reboot" still boot my device into FASTBOOT MODE, NOT the NORMAL MODE.
Here is the output
Code:
$ fastboot devices
HT7B91A03213 fastboot
$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
I flashed the stock Android 8.1 and it worked fine, until yesterday I locked the OEM and bootloader
The point is WHY my device cannot boot in normal mode, which I guess may have something to do with the lock status of bootloader.

---

@ayewilling
An universal version of Fastboot does not exist: each OEM/Carrier implement a Fastboot that's suitable to the device's chipset. My guess is that the Fastboot driver you use isn't suitable.
The Google Pixel 2 is based on a Qualcomm chipset. My recommendation is to install and use the matching USB drivers ( incl. ADB / Fastboot ):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

jwoegerbauer said:
@ayewilling
An universal version of Fastboot does not exist: each OEM/Carrier implement a Fastboot that's suitable to the device's chipset. My guess is that the Fastboot driver you use isn't suitable.
The Google Pixel 2 is based on a Qualcomm chipset. My recommendation is to install and use the matching USB drivers ( incl. ADB / Fastboot ):
Click to expand...
Click to collapse
Hum! I'll give it a try!
Look forward to good news！

---

0

---

Hello ayewilling your problem is fixed or not ??

---

Seppppx said:
Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google.
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
@ayewilling
On what rom did you lock the bootloader?
If it's a rom like lineageos which uses userdebug builds you can disable AVB by doing
"fastboot oem disable_dm_verity"
The locked bootloader shouldn't be a problem as Pixels support locking the bootloader on unknown signing keys. You should then be able to unlock it in your rom afterwards.
Click to expand...
Click to collapse
Hello seppppx sir I was
Seppppx said:
Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google.
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
@ayewilling
On what rom did you lock the bootloader?
If it's a rom like lineageos which uses userdebug builds you can disable AVB by doing
"fastboot oem disable_dm_verity"
The locked bootloader shouldn't be a problem as Pixels support locking the bootloader on unknown signing keys. You should then be able to unlock it in your rom afterwards.
Click to expand...
Click to collapse
jwoegerbauer said:
@ayewilling
Your phone obviousy runs an Android version that has A/B-system-partition layout, has AVB enabled, and furthermore it seems phone's boot-loader is locked.
My POV: You at 1st thing of all things should become familiar with HOW FASTBOOT WORKS, WHAT YOU CAN MANAGE WITH IT.
Anyway, running the command sequence
Code:
fastboot devices
fastboot reboot
should boot phone in normal mode.
Click to expand...
Click to collapse
Hello sir my device is on same problem how I recover my device Sir plz help me

---

Seppppx said:
Wrong! fastboot/adb is made by google, thus it works on Google phones. And a lot of times you can get fastboot and adb to work with generic drivers from google.
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
@ayewilling
On what rom did you lock the bootloader?
If it's a rom like lineageos which uses userdebug builds you can disable AVB by doing
"fastboot oem disable_dm_verity"
The locked bootloader shouldn't be a problem as Pixels support locking the bootloader on unknown signing keys. You should then be able to unlock it in your rom afterwards.
Click to expand...
Click to collapse
Hello sir my device is on same problem how I fix this plz help me sir