Develop Bugs

Bricked?!?

Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.

Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again

And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.

if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all

Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.

So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?

Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked

If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.

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?

Google Pixel 3XL fastboot locked and Recovery not working

Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you

try sideloading the full OTA.
https://developers.google.com/android/ota

robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?

v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.

robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!

Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you

v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable

robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?

sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes

robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.

sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.

robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.

sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer

i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,

Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.

Motorola G6 Play (Boot loop)

I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy

Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately

Thanks for the reply, please can you put a link to your guide?

Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928

Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.

Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops

sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?

Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?

The phone was bought direct from Amazon so in my mind a generic model to take any SIM.

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.

I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it

Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?

ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?

Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it

Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a

ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..

Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted

I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.

Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant

Question Hard Bricked Pixel 6 Pro Android 13

Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.

PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image

DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.

Read this thread if you haven't...

blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.

lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.

Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.

rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.

PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.

DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked

If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.

Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.