Develop Bugs

[Q] Am I screwed? Anyway to backup userdata via fastboot?

Hey all,
I just woke up and decided I was going to update to 5.1.1 since the notification kept bugging me to.
Well doing this while half asleep just screwed me. I forgot to open Boot Unlocker beforehand to unlock the bootloader and then proceeded to wipe recovery, boot, system, cache. I then tried to flash the 5.1.1's and got the message that I wasn't unlocked...:highfive::silly:
I was stock kernal and rooted and HAD twrp. I don't do anything special, I just like to root for the added abilities with some apps.
I've tried searching around but have been unable to find any solutions that work.
Any help is appreciated.

FoRealz said:
Hey all,
I just woke up and decided I was going to update to 5.1.1 since the notification kept bugging me to.
Well doing this while half asleep just screwed me. I forgot to open Boot Unlocker beforehand to unlock the bootloader and then proceeded to wipe recovery, boot, system, cache. I then tried to flash the 5.1.1's and got the message that I wasn't unlocked...:highfive::silly:
I was stock kernal and rooted and HAD twrp. I don't do anything special, I just like to root for the added abilities with some apps.
I've tried searching around but have been unable to find any solutions that work.
Any help is appreciated.
Click to expand...
Click to collapse
Did you relock your boot loader AFTER installing TWRP? If so, why would you do that?

SwoRNLeaDejZ said:
Did you relock your boot loader AFTER installing TWRP? If so, why would you do that?
Click to expand...
Click to collapse
I did. I debated about this for a while and researched a lot. The consensus I received was that some people relocked their phones and tablets if they were going to take them in public places to protect their data. Granted, the chance of the thief being savvy enough or caring is pretty slim.

FoRealz said:
I did. I debated about this for a while and researched a lot. The consensus I received was that some people relocked their phones and tablets if they were going to take them in public places to protect their data. Granted, the chance of the thief being savvy enough or caring is pretty slim.
Click to expand...
Click to collapse
Dude, honestly, with the addition of Android Device Manager sometime ago, relocking after you add recovery and root is trivial. If you're that worried about your device, you can encrypt lock and wipe remotely with the device manager.
So how did you go about flashing stock recovery with a locked boot loader, and do you still have TWRP?
Have you tried fastboot oem unlock?

SwoRNLeaDejZ said:
Dude, honestly, with the addition of Android Device Manager sometime ago, relocking after you add recovery and root is trivial. If you're that worried about your device, you can encrypt lock and wipe remotely with the device manager.
So how did you go about flashing stock recovery with a locked boot loader, and do you still have TWRP?
Have you tried fastboot oem unlock?
Click to expand...
Click to collapse
I can't flash anything at the moment. I was however able to format cache, recovery, boot, and system without being unlocked....so TWRP is gone now.
I haven't done fastboot oem unlock because I'm trying to preserve my userdata or back it up before I do that.

Dude you can pull your user data through ADB, but at the end of the day, screw the user data!! Get your tablet working again!

SwoRNLeaDejZ said:
Dude you can pull your user data through ADB, but at the end of the day, screw the user data!! Get your tablet working again!
Click to expand...
Click to collapse
How can i do it through ADB if i can't boot in to enable usb debugging?

FoRealz said:
How can i do it through ADB if i can't boot in to enable usb debugging?
Click to expand...
Click to collapse
Have you checked in stock recovery to check if you have ADB access?

SwoRNLeaDejZ said:
Have you checked in stock recovery to check if you have ADB access?
Click to expand...
Click to collapse
I can't get to recovery since I blew away the recovery partition. I can only get to fastboot/bootloader, but my bootloader is locked so I can't flash or boot from another recovery.
I think I'm out of luck. :crying:

FoRealz said:
I can't get to recovery since I blew away the recovery partition. I can only get to fastboot/bootloader, but my bootloader is locked so I can't flash or boot from another recovery.
I think I'm out of luck. :crying:
Click to expand...
Click to collapse
Dude, screw your data. Run fastboot oem unlock, and see if you can get it unlocked. That's literally your only option.
Moral of the story: Once you unlock bootloader LEAVE IT UNLOCKED. Your data is not at risk. (as is obvious based on this post, only bad things will end up happening)

Stuck on "Google" screen

I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.

This happened to me and Google sent a replacement phone. However the replacement phone is a refurbished phone that suffers from ghost touches Now trying to get a replacement for the replacement.

Ocelot584 said:
I was using my phone like I usually do, and then it suddenly froze. So I held down the power button, forcing it to restart. Ever since, the screen only shows "Google" for a while, then becomes blank; no booting animation. It would restart itself occasionally.
I tried booting into recovery mode by holding Power+VolDown, and selecting "recovery mode". For the first few tries, it would go back to the Google screen, the turn blank. After giving it a break and trying again, I finally got to the "no command" screen, and I wiped the cache partition. Sadly, I'm still having the same problem.
Is this a bootloop? How can I fix this?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
can u boot into bootloader mode?

dominoeflux said:
can u boot into bootloader mode?
Click to expand...
Click to collapse
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?

Ocelot584 said:
What's that? Is it the screen that comes up when you hold down Power+VolumeDown and gives you the option to select Start, Power Off, Restart Bootloader, or Recovery?
Click to expand...
Click to collapse
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems

dominoeflux said:
Yes that's the one. If u can get back to that screen you should be able to flash it back stock and re root the phone with out any problems
Click to expand...
Click to collapse
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.

Ocelot584 said:
So are you saying that I should factory reset my phone from the recovery menu, or do I have to use the method that requires the factory image?
My phone wasn't rooted btw, so I can't re-root it.
Click to expand...
Click to collapse
Oh ok I thought it was sorry if I wasn't of any help

dominoeflux said:
Oh ok I thought it was sorry if I wasn't of any help
Click to expand...
Click to collapse
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?

Ocelot584 said:
haha it's ok you tried to.
Rooted or not, do you think factory resetting it will fix the problem as long as I can get to the bootloader menu?
Click to expand...
Click to collapse
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?

dominoeflux said:
In pretty positive that it will, make sure u unlock the Bootloader first before you do anything. Do you know how to unlock it?
Click to expand...
Click to collapse
nope...what's a bootloader anyway?

Ocelot584 said:
nope...what's a bootloader anyway?
Click to expand...
Click to collapse
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it

dominoeflux said:
The bootloader allows the phone to be unlocked to flash custom ROMs on it, without it unlocked you'll brick your phone. Read up about rooting your phone first so you can get the idea of what goes into it before attempting it. Once you get the general idea of unlocking the phone and flashing things on it, it becomes relatively easy. There's even a nexus root toolkit on this forum that you can download on your computer for free as well as "how-to's" for doing it
Click to expand...
Click to collapse
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?

Ocelot584 said:
Wait...what?? So if I choose to factory reset my phone now without unlocking the bootloader, it might become completely useless? Is rooting necessary?
Click to expand...
Click to collapse
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative

dominoeflux said:
No is not necessary, but in order to re flash the factory image to fix the problem the bootloader must be unlocked. You never have to root your device but having a unlocked bootloader is essential to flashing anything on your device other wise like I said, you'll brick your phone. You can even lock it back to full stock once you've re flashed the image.
Edit: there's another way of flashing the factory image but it requires some searching. You might not be able to do it the way I'm explaining to you Because you would have to give it permission to be unlocked in the developers option while the phone is booted up and operative
Click to expand...
Click to collapse
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?

Ocelot584 said:
Oh...I see. So what about the factory reset option in the recovery menu? Would you expect that to fix it too?
Click to expand...
Click to collapse
Of course
Edit: have you tried resetting it in the factory recovery?

dominoeflux said:
Of course
Edit: have you tried resetting it in the factory recovery?
Click to expand...
Click to collapse
Nope...I was waiting to see if I could find a way to recover my data first

Ocelot584 said:
Nope...I was waiting to see if I could find a way to recover my data first
Click to expand...
Click to collapse
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.

dominoeflux said:
When u first bought your phone and it takes you through the set up window, when it asked you to put in your email, that right there backs up all your apps that you previously had in the phone so when you go through the setup again, it's going to ask you if you want to start as a new phone or recover your previous apps. You won't be able to recover all of your data but you should be able to recover all of your apps.
Click to expand...
Click to collapse
Alright, but since all my data won't be recovered, is there a way to get access to files on my phone before I factory reset it?

Ocelot584 said:
Alright, but is there a way to get access to files on my phone before I factory reset it?
Click to expand...
Click to collapse
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way

dominoeflux said:
Sorry bro but I wish there was.... There actually is away, but you would have have to have been rooted with a custom recovery on your phone and since you had neither, there's my other way
Edit: I meant no other way
Click to expand...
Click to collapse
oh... wow.
I'll just suck it up and reset it then. I'll let u know how it goes.

Cant find valid operating system after during update - please help

My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.

sumasage said:
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Can you get to stock recovery for a factory reset?

It doesn't even let me get to recover. Picking recovery from the bootloader screen just make the phone restart like it try to go to recovery but then it come back to the same screen saying it can't find valid operating system.

Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well

trim81 said:
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
Click to expand...
Click to collapse
What did you say Google? Did you tell them it happened while re-locking boot loader? I am on same boat....I tried to relock bootloader and getting Can't find valid operating system

I rma the unit as well.

sumasage said:
I rma the unit as well.
Click to expand...
Click to collapse
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?

ram4ufriends said:
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
Click to expand...
Click to collapse
Tell them exactly that. It no longer boots

As soon as I said there was no valid os the rep proceeded to rma. Seem like it a know issue so they didn't bother to transfer me to tech support.

Not sure if you want to try any of these solutions before you RMA, but here's another thread on the same "No OS ....." with several options, might be worth a try?

I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.

megernic said:
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...l-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
Click to expand...
Click to collapse
Did you check or uncheck OEM unlocking in Developer Options before doing this?

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!

Question Hard bricked - help needed

Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !

Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)

foobar66 said:
Try: https://pixelrepair.withgoogle.com/carrier_selection
(I've never personally used this)
Click to expand...
Click to collapse
Unfortunately the phone is supposed to have a working bootloader

Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Ouch ...

Thibale said:
Unfortunately the phone is supposed to have a working bootloader
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
Also doesn't work?

Morgrain said:
Android Flash Tool
flash.android.com
Also doesn't work?
Click to expand...
Click to collapse
Nope...

Thibale said:
Nope...
Click to expand...
Click to collapse
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)

Morgrain said:
Can you still access Fastboot Mode?
(pressing and holding both Power and Volume Down simultaneously. You should see a green android on his back)
Click to expand...
Click to collapse
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.

yes but you need to be able to communicate with your phone from your pc.....if you cant access fastboot then how will you change partition?

Thibale said:
No that's the problem.
But there are 2 bootloader slots (a and b) and I'm pretty sure there is way to switch from one to another with a special tool or button sequence.
I've already tried many button combinaison with no luck.
This kind of error is so stupid that I hope there is a way to force a rescue bootloader or something on boot.
Click to expand...
Click to collapse
The only special tools we have are either the pixel repair tool or the android flash tool. If both can't get you fastboot / firmware flashing, that's it. Hardbrick. Google Pixels don't have "special" hardbrick solving tools, like older OnePlus had. You need to contact Google.

Ok I'll get in touch with my local reseller on Monday then...

Thibale said:
Ok I'll get in touch with my local reseller on Monday then...
Click to expand...
Click to collapse
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!

Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…

Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
WOW. So even holding volume down and power until you see the fastboot screen wont work? sometimes you have to hold it for a while. I say that because when the December firmware came out I accidentally flashed the wrong region but was able to access bootloader and so was able to rescue myself. So sorry dude. That really sucks.

Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
Yes worst case we'll have for repair but they could have implemented a simple device id check on their script prior flashing anything, especially for the bootloader.
Anyway, I'm alive, in a good health and it's just a phone

niko26 said:
Do you remember what went wrong?
EDIT: Uh, never mind. So you accidentally used the P5 fw. Why on hell would the device accept the P5 fw at all?!
Click to expand...
Click to collapse
You can flash gobbledygook to your phone if you're not careful. You can flash a non-Google phone's image. Flashing just flashes what you tell it to flash.
Psfanboy88 said:
Same problem here: downloaded from a blog the latest firmware. They have linked the pixel 5 firmware and named it as Pixel 6 pro full firmware. Just flashed without looking and now the phone wont boot. No reaction at all, no fast boot or whatsoever. Have filled in a repair request in my google account, because I’ve bought it directly in their store.
Do you think they have a way to find out what went wrong? I meant the phone is not giving any signal, regardless of which button combination I press. Worst case: I have to pay for the repair…
Click to expand...
Click to collapse
That sucks. I'm sure you know now, always go straight to the source for everything if possible, firmware, platform tools, drivers, BIOS / UEFI (for computer).
SDK Platform Tools
Get the Google USB Driver
Pixel 6 Pro Factory Images
You can also Google for official pixel firmware and the top search result is what the want. I know it doesn't help you now. Good luck with your phone!
Morgrain said:
After having played around with the January patch (came from December Europe A4 firmware that was pulled), it seems that the FP scanner got even faster and more reliable, even though it's not stated in the patchnotes. Maybe it's just placebo.
Click to expand...
Click to collapse
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.

roirraW edor ehT said:
So many folks have reported the exact same thing, I'm really, really curious just how much faster it will seem when I get around to updating.
Click to expand...
Click to collapse
I noticed how faster it was before I saw everyone else posting about it, so at least no placebo on my end. Hope you find the same.

I know that you tried to get into Fastboot. Pixel 6/6P also has a Recovery mode. I can get to it from a working phone.
I would think that there is someway to boot into Recovery mode from a dead phone via button combos.

Thibale said:
Hello,
In the rush of flashing the january update I've flashed by mistake the Pixel 5 image bootloader (my wife's phone)
Yest that's stupid, I've done this every months for years with several Pixel phones, but I was listening to music at the same time and did dl the wrong image...
Anyway my phone is now hard bricked but I'm sure there must be a way to enter the other bootlader slot and/or entering a special recovery tool.
I cannot enter bootloader anymore
Requesting some help as I'd avoid to send it for a reflash...
Thanks !
Click to expand...
Click to collapse
Hy, how did you flashed? Via adb sideload or?

vrda08 said:
Hy, how did you flashed? Via adb sideload or?
Click to expand...
Click to collapse
factory image with modified flash-all.bat
I'll do the exact same process when I'll get my phone back but this time I'll check the image name at least 3 times