Database Develop

brick after Lineage 17

Flashed Pixel Expirience without any problems and worked just fine but i didnt like i cant remove date from top of home page
so i done flash of LineageOS 17.1 and worked fine but since i had problems with gaaps (installed but after boot to system nowhere to be found). Flashed Lineage couple more times to flash gaaps
So i installed TWRP 3.3.1 since i got iritated to temporary boot it every time from fastboot
I wipe(and done format ) everything from the phone using installed TWRP but phone still booted LineageOS !!! so i concluded that somehow must be installed on Slot A
Again boot in TWRP and wiped (and done format)Slot A, and again did same with Slot B.
after all this recovery is Lineage OS recovery !!!!!!
Now when i type any command in fastboot i get black screen with "press any key to shutdown"
downloaded stock and tried to force it with MiFlash i also get same "press any key to shutdown" error but sometimes i just get
{
"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"
}
when i forced MiFlash for 50 times it alegedly starts to flash but for eternity
also when i try to change slot with command fastboot set_active (a or b) i get error "Device does not support slots" !!
PS.
Im using USB2.0 and stock cable so USB3.0 is not problem
PPS.
after all this recovery is Lineage OS recovery !!!!!!
BOTTOM LINE:
I got message for whoever came up with slots. Fuk YOU !!

yrakun said:
Flashed Pixel Expirience without any problems and worked just fine but i didnt like i cant remove date from top of home page
so i done flash of LineageOS 17.1 and worked fine but since i had problems with gaaps (installed but after boot to system nowhere to be found). Flashed Lineage couple more times to flash gaaps
So i installed TWRP 3.3.1 since i got iritated to temporary boot it every time from fastboot
I wipe(and done format ) everything from the phone using installed TWRP but phone still booted LineageOS !!! so i concluded that somehow must be installed on Slot A
Again boot in TWRP and wiped (and done format)Slot A, and again did same with Slot B.
after all this recovery is Lineage OS recovery !!!!!!
Now when i type any command in fastboot i get black screen with "press any key to shutdown"
downloaded stock and tried to force it with MiFlash i also get same "press any key to shutdown" error but sometimes i just get
when i forced MiFlash for 50 times it alegedly starts to flash but for eternity
also when i try to change slot with command fastboot set_active (a or b) i get error "Device does not support slots" !!
PS.
Im using USB2.0 and stock cable so USB3.0 is not problem
PPS.
after all this recovery is Lineage OS recovery !!!!!!
BOTTOM LINE:
I got message for whoever came up with slots. Fuk YOU !!
Click to expand...
Click to collapse
search for any tutorial on how to do testpoint and then flash stock in edl
or........ try to flash lineage by using lineage recovery ....then try to enter fastboot
then start over ...
put of a photo of the problem with your fastboot
try something like :
fastboot oem edl
if screen goes black try to flash it in miflash real quick
but now that you have brick convert to wayne ...is A only ... I'm much happier since I converted

KevMetal said:
search for any tutorial on how to do testpoint and then flash stock in edl
Click to expand...
Click to collapse
You mean TO TAKE APART ?!
KevMetal said:
or........ try to flash lineage by using lineage recovery ....then try to enter fastboot
Click to expand...
Click to collapse
Only if i could copy installation zip without twrp
put of a photo of the problem with your fastboot
KevMetal said:
try something like :
fastboot oem edl
Click to expand...
Click to collapse
and i get greetings "press any key to shutdown"
KevMetal said:
but now that you have brick convert to wayne ...is A only ... I'm much happier since I converted
Click to expand...
Click to collapse
I don't understand
PS.
I noticed that in LineageOS recovery i have option ADB sideload
but when i try to do ADB Sideload rom.zip i get message "cannot read rom.zip"

yrakun said:
You mean TO TAKE APART ?!
*NO, to unscrew the screws and open the back cover of the phone
Only if i could copy installation zip without twrp
*boot to lineage recovery , then connect the usb and transfer the rom zip to the phone using file manager on pc
put of a photo of the problem with your fastboot
*yes, upload photos of the errors and what's happening
and i get greetings "press any key to shutdown"
* are you sure you are in fastboot ?
I don't understand
*what don't you understand
PS.
I noticed that in LineageOS recovery i have option ADB sideload
but when i try to do ADB Sideload rom.zip i get message "cannot read rom.zip"
Click to expand...
Click to collapse
* do you know how to use sideload ?
**put the rom in the folder of adb
***connect usb cable to phone and recovery activate sideload
**** on pc open cmd window in adb folder
***** use command :
adb sideload rom.zip
#make sure the name of the rom is rom.zip or call it update.zip
#make sure to use the lineage rom that goes with the recovery on the phone
##lastly "Wayne" or Mi X6 is the same phone as A2 or "jasmine" it just uses A only partition and comes with miui not android 1 and you can convert your phone to have A only partition by flashing miui of mi x6 on the phone which is what i did then your phone won't be a A/B device

Yes i know how to use sideload as i already wroted
"adb sideload rom. zip" get message "cannot read rom.zip"
but i made it. I needed newer version
turned on ADB in LineageOS recovery and tried to
flash stock, flashing started and stuck at 47% with some error
flashed newer stock and stuck at 47% with some error
flashed PixelExpirience and stuck at 47% with some error
flashed newer PixelExpirience and stuck at 47% with some error
flashed new Lineage and stuck on 47% with some error
flashed older Lineage and stuck on 47% with some error
flashed EvolutionX and SUCCESS
thank you Evolution, i will try to live with date at top of home screen

my 2 cents, if that's the only one working and you had it installed before they probly changed something on the default partition layout (which causes all others to fail).
your only way out of the mess is probably to flash the stock rom with miflash (which currently doesnt work because you're trying to flash the pie tgz - since xiaomi are too lazy to release a tgz for android 10). once they releases the 10 that one should let you reset the phone to stock.

Trying to boot my Huawei P9 inot TWRP, stock rom always overwrites even if I boot into recovery correctly

As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screen
{
"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"
}
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23

Catnip202X said:
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screenView attachment 5281583
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Click to expand...
Click to collapse
TWRP must be flashed with the command:
fastboot flash recovery_ramdisk ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help

zgfg said:
TWRP must be flashed with the command:
fastboot flash recovery ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
Click to expand...
Click to collapse
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.

Catnip202X said:
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Click to expand...
Click to collapse
Yes, sorry, you are right, typo.
But I wanted to point that you must use fastboot flash command (not FLASHBOOT or whatever you used in your post #1)
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
But also READ the P9 LOS thread - it clearly describes that LOS must bi flashed from fastboot, not from TWRP and it actually asks users not to use TWRP
See here and better ask there to get the answers directly from developer:
[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9
This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches. It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera...
forum.xda-developers.com

zgfg said:
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
Click to expand...
Click to collapse
I have indeed tried this route, but as I have stated before, trying to boot into recovery mode right after flashing TWRP and pressing key combo still boots me into the error screen where it says that I need to update something. On the bottom of the screen will also show errors such as Function11 not found and error 2 no image etc. I’ll try to replicate it and send you a picture of the error screen when I get home from work tonight.

Phone stuck at black Mi logo

Hello, I never experienced this before so here I am trying to find some explanation, hopefully it's the right place... I have a Xiaomi Mi 5 Pro, few years old, sometimes slow but otherwise perfect, I changed the battery couple times.
Today I noticed it was at around 20% charge, I plug it to the wall, and leave it on the bed (turned on). After a few hours I go back to check on it and found the 100% indicator, but the phone was turned off.
I obviously try to turn it back on, but it gets stuck at the Mi logo (black screen with "unlocked" text below). I have installed a MIUI.eu rom ver. 11, twrp 3.2.3-0 recovery, and everything has been fine for years. I tried several times, still Mi logo (it's not bootloop, it's just stuck).
Suprised, I try to boot into recovery, and there I noticed that all the partitions are marked empty 0 bytes. I tried several things like backup, switching file format, restoring file system, etc., but it just won't work. It's like it has all been wiped and can't be mounted again.
I connected it to my desktop, MTP enabled from twrp, device recognized, storage completely empty. I remember I could see files there just the other day...
I tried all possible wipes, they won't work, either can't mount the partitions or other errors.
I already asked for suggestions elsewhere, which pointed me to fastboot flash using the adb/fastboot tools on Windows.
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Also if I boot in recovery, I can see it detected in the adb/fastboot tools screen, the scary part is that there it says "Bootloader: locked" (but it has been unlocked for years, and it even says unlocked in the black Mi screen!)
I'm lost, I never had anything like this, any suggestions to save the device? I would be really grateful

ZexDC said:
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Click to expand...
Click to collapse
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.

Indie Zex said:
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.
Click to expand...
Click to collapse
Thanks it was the driver stopping the fastboot.
Now I still cannot flash anything though, I get the following error:
{
"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"
}
Tried different roms, different MiFlash, from terminal, but same error.
From recovery I still see empty not mounted partitions.
Any other suggestions?

Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.

Indie Zex said:
Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.
Click to expand...
Click to collapse
Yes that was the first thing I tried unfortunately that's where I found out something was off... I can't wipe any partition, I can't mount any partition, I tried to switch filesystem but no luck.
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...

ZexDC said:
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...
Click to expand...
Click to collapse
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...

Indie Zex said:
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...
Click to expand...
Click to collapse
It's very weird, I've been flashing lots of stuff in the past but I've never been locked out like this.
And the joke is that the black Mi logo screen still says "unlocked" as it should be... no idea, maybe it is programmed to just give up after some years.

Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.

Indie Zex said:
Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.
Click to expand...
Click to collapse
I tried that, it gives the following error:
I noticed that even from MiFlash the device id sometimes disappears, not sure if that's the no link error

I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)

Indie Zex said:
I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)
Click to expand...
Click to collapse
Thanks for trying I really appreciate. I did follow the tutorial, same error.
It's like the internal storage got fried or something? I have no clue

Redmi 10C can't use fastboot nor recovery but OS works

Hi. I got a Xiaomi Redmi 10C (fog/rain) and wanted to install another system because I dislike MIUI. I decided on LineageOS 19.1 since it's based on Android 12 like the default OS MIUI 13. It's not an official ROM, but it worked alright until I decided to try another ROM, PixelExperience. This one is an official ROM, but after I tried flashing their recovery ROM, I can no longer access recovery mode and I can't use fastboot mode either, it is not detected. The phone still boots into LineageOS, and it works, but now I can't flash anything else anymore.
Flashing LineageOS
I followed several tutorials and guides for flashing custom ROMs on the Redmi 10C. In particular, this one has a link to the unofficial LineageOS ROM in question: https://www.getdroidtips.com/lineage-os-19-1-redmi-10c/. I unlocked the bootloader, installed the USB drivers, and then used flashed TWRP Recovery using fastboot mode. I will call this fastboot mode the "normal" fastboot, since it's the one that comes with the device. It's a black screen with the word FASTBOOT written in orange in the center (see the photo below).
{
"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"
}
At this point, everything worked, normal fastboot was detected and I could boot into it with either `adb reboot bootloader` or `adb reboot fastboot`. I could also boot into the TWRP recovery mode with `adb reboot recovery`, so I continued on and flashed the LineageOS ROM. Now the phone would boot normally into LineageOS, no problem except a minor detail: TWRP recovery was replaced by LineageOS recovery (which is expected), and that came with LineageOS fastboot as well (see photos below). Both modes have an option to switch to the other.
The issue with this is that LineageOS fastboot was now detected by the USB drivers, but the normal fastboot was not anymore. Just to make it clear: at this point I could choose to boot into either LineageOS recovery (`adb reboot recovery`), LineageOS fastboot (`adb reboot fastboot`), or normal fastboot (`adb reboot bootloader`). When in LineageOS recovery, the adb tool would work. When in LineageOS fastboot, the fastboot tool would work. But when in normal fastboot, the fastboot tool would not see any device, as if the phone was not connected.
Flashing PixelExperience
The issue with the normal fastboot mode not being detected was not a problem until it became one, when I decided to flash a PixelExperience ROM (this time official) that you can find here: https://download.pixelexperience.org/fog/. I followed the instructions in their Install Guide (https://wiki.pixelexperience.org/devices/fog/install/) with the exception of the "flashing the vendor boot partition" part. I skipped it for two reasons. First, the guide says "Download this vendor_boot.img file", where "this" is a link to the guide instead of a file download link (so basically a broken link). Second, I didn't need to flash the vendor boot partition to install TWRP, so I thought it would be ok, and if anything went wrong I would still have fastboot mode to flash TWRP again, right?... Well, I flashed the PixelExperience recovery ROM (since they say that "other recoveries may not work"), and that obviously didn't work because now I can no longer boot into recovery mode. Whatever I do, it just boots into the OS instead. Only the command `adb reboot bootloader` (or holding volume down when booting) gives me the normal fastboot mode, but it is still not detected! As a result, I have no recovery mode and my fastboot mode is useless.
I still have a working LineageOS, but it's not even rooted, so anything I try fails. I had no idea I could end up in a situation like this where the device isn't bricked but is still mostly useless...
Is there any way I can get back to a working recovery or fastboot? I asked on the Telegram channels of both LineageOS and PixelExperience but no luck so far.

Fixed by downloading the Mi UnlockTool, running MiUsbDriver.exe, and connecting the phone while on the fastboot screen. No clue why this worked. I guess it's a different version of the driver, or maybe it's the act or reinstalling the driver... Whatever.

Question Stuck in FastBoot Mode loop , recovery and rescue mode give boot failure, bricked?

Hi!
I got this new Pixel 7 2 weeks ago, yesterday the battery went completly discharged and now the phone starts into Fastboot mode, with the Enter Reason being boot failure. Recovery mode and rescue mode both fail to load, and just send me back to the Fastboot Mode. I alredy tried a bunch of stuff to fix it, but the phone its still OEM lock so flashing via the Google flash tool its imposible, does anyone has any idea of what can i do to save it?

Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection

t-ryder said:
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
{
"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"
}
yes, Rescue Mode fails to load, so it gives me Unable to connect the Phone

There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
No, i am going to give it a go and update on results

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
It failed, it gives me "Bootloader is locked, can't flash." and trying to unluck the bootloader with the fastboot commands gives me FAILED (remote: 'flashing unlock is not allowed')

And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?

t-ryder said:
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
Click to expand...
Click to collapse
adb its disabled and entering recovery mode also fails, the phone its pretty much new, so i didn't have time do much with it.

I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...

Lughnasadh said:
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Click to expand...
Click to collapse
Even trying to get into recovery mode with Pixel Flasher fails.. looks like my only option its asking for warranty and i wanted to avoid that.

Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.

41rw4lk said:
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
Click to expand...
Click to collapse
Unfortunately their bootloader is locked so they won't be able to switch slots via fastboot commands. Even if they were able to switch slots they would then have to flash the OS to that slot before being able to boot into that slot since you can only boot into the slot where the OS was last flashed in this circumstance.

I can't get over the fact that you can't just flash an official image on a locked bootloader. I used to be a Moto fan and that was always the good thing about them, as long as it was officially signed, locked or not you could flash the same or updated firmware. Plus if it was qualcomm, when you bricked it would go into edl mode and you could blankflash your way back.
Yet a Google device, who also develops android, you're up a creek unless you unlock your bootloader.