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.

Unbrick RN 8 PRO (China/Global) without Miflash

Hello everyone, This post is about how to unbrick your Redmi Note 8 Pro.
Sorry for my bad English
A couple of months ago, at the start of sales, I bought myself a Redmi Note 8 Pro, deciding to flash it on a global version, I bricked it, at that time no one knew how to fix it, I decided that it couldn’t be fixed anymore, I bought another phone and left Redmi Note 8 Pro on the shelf, and now a couple of weeks ago I decided to turn it on and see if I could fix it and it turned on! first the vibration starts and then highlighted a white Redmi logo, after that the phone showed that it is charging and I decided to go into a fastboot mode and he booted up! I flashed a boot.img and recovery from my Miui version that i was using before bricking phone (in my case it was from miui 10.4.5)and the phone turned on! none of my data was deleted.
So what you need to do:
1. After bricking your phone, do not try to charge it!
Leave somewhere for a 3-5 days to discharge your phone
2. Put your phone in charge after leaving your phone for a 3-5 days, if your phone boot up as usually (No logo and no image, only black screen) then leave it for a couple more days and put it on charge after couple days
3. If your phone discharged to 0% (battery is fully discharged), then redmi logo comes and then phone shows that it is charging like usually.
4. Do not waste your time, after battery icon shows up *photo* Press Volume Down and Power OFF together, then phone will be booted in fastboot mode.
5. Then you need to flash boot.img and recovery, I was using from version Miui 10.4.5, i will put everything below so you can download it
6. After Flashing boot and recovery, your phone will boot up and that's it!
Download links:​boot.img V10.4.5
boot.img V11.0.1.0
recovery V10.4.5
Following this guide might help you to unbrick your phone, no need to use any programs like Miflash or SP FlashTool!
I hope my guide will help you, have a good day

It only works if boot image is not damaged. You can try eg: fastboot flash boot twrp.img and reboot to see.
This will replace your boot image with recovery image, it will completely brick the phone because boot image is no longer working, then prepare to go back to Mi store or $29 for authorised service account.

idog8818 said:
It only works if boot image is not damaged. You can try eg: fastboot flash boot twrp.img and reboot to see.
Click to expand...
Click to collapse
Dude, how could you suggest to try something which will hard brick your device? That's careless and reckless! So guys, don't do that!

That's just example, not suggest someone to do it. Trying to use this example to support my point.
---------- Post added at 11:49 AM ---------- Previous post was at 11:47 AM ----------
Olei said:
Dude, how could you suggest to try something which will hard brick your device? That's careless and reckless! So guys, don't do that!
Click to expand...
Click to collapse
You are using parts of sentence to kill my point.... This is ridiculous.

idog8818 said:
It only works if boot image is not damaged. You can try eg: fastboot flash boot twrp.img and reboot to see.
This will replace your boot image with recovery image, it will completely brick the phone because boot image is no longer working, then prepare to go back to Mi store or $29 for authorised service account.
Click to expand...
Click to collapse
Exactly. If you had flashed custom recovery.img and boot.img and after booting in TWRP the phone became hard brick (only led light works) then the stock boot.img is lost. The method proposed (drain the battery) could be done by opening the phone and disconnecting - connecting the battery.
There is only one solution if boot.img and recovery.img are flashed and afterwards the phone became brick. Either buy an authorized account to use it while in 'sp flash tool' or wait and see if developers create a 'MTK__DA.bin' file or an 'auth_sv.file' in order to use it in 'sp flash tool' and flash the phone. The 'mi flash' program can't work if the pc can't recognize the device. The bricked phone is visible in devices only if you hold vol button.

tornado71 said:
There is only one solution if boot.img and recovery.img are flashed and afterwards the phone became brick. Either buy an authorized account to use it while in 'sp flash tool' or wait and see if developers create a 'MTK__DA.bin' file or an 'auth_sv.file' in order to use it in 'sp flash tool' and flash the phone. The 'mi flash' program can't work if the pc can't recognize the device. The bricked phone is visible in devices only if you hold vol button.
Click to expand...
Click to collapse
https://forum.hovatek.com/thread-23776.html is collecting those above mentioned files. As of now, there's nothing available for the RN8Pro, however, it has already been requested. So there's at least the chance to fetch it from there in the future. I don't know whether the available generic Xiaomi files will work.

Olei said:
https://forum.hovatek.com/thread-23776.html is collecting those above mentioned files. As of now, there's nothing available for the RN8Pro, however, it has already been requested. So there's at least the chance to fetch it from there in the future. I don't know whether the available generic Xiaomi files will work.
Click to expand...
Click to collapse
I tried the generic files. They do not work

Olei said:
I tried the generic files. They do not work
Click to expand...
Click to collapse
They work with authorised service account, I've tried. lol.

idog8818 said:
They work with authorised service account, I've tried. lol.
Click to expand...
Click to collapse
Hello my brother, i finished by bricking my RN8PRO while flashing TWRP, no normal boot no fastboot no recovery, just LED lighting when connecting him to PC, PLZ do you know where i can find an Authorized Mi Account, i will donate. Thanks bro :good:

Thread cleaned
XDA-Developers is a platform to discuss and share, but please do not spam your mail or phone numbers to exchange paid unlock services as we do not encourage others to post with the intention to sell something, see our FORUM RULES :good:
Thank you all for your understanding :good:
strongst
Forum Moderator

Phone not booting
my phone is charging but not booting only the notifikation light glows (not blinking)
what does that mean?

documentation android xiaomi
fi4tch said:
Hello everyone, This post is about how to unbrick your Redmi Note 8 Pro.
Sorry for my bad English
A couple of months ago, at the start of sales, I bought myself a Redmi Note 8 Pro, deciding to flash it on a global version, I bricked it, at that time no one knew how to fix it, I decided that it couldn’t be fixed anymore, I bought another phone and left Redmi Note 8 Pro on the shelf, and now a couple of weeks ago I decided to turn it on and see if I could fix it and it turned on! first the vibration starts and then highlighted a white Redmi logo, after that the phone showed that it is charging and I decided to go into a fastboot mode and he booted up! I flashed a boot.img and recovery from my Miui version that i was using before bricking phone (in my case it was from miui 10.4.5)and the phone turned on! none of my data was deleted.
So what you need to do:
1. After bricking your phone, do not try to charge it!
Leave somewhere for a 3-5 days to discharge your phone
2. Put your phone in charge after leaving your phone for a 3-5 days, if your phone boot up as usually (No logo and no image, only black screen) then leave it for a couple more days and put it on charge after couple days
3. If your phone discharged to 0% (battery is fully discharged), then redmi logo comes and then phone shows that it is charging like usually.
4. Do not waste your time, after battery icon shows up *photo* Press Volume Down and Power OFF together, then phone will be booted in fastboot mode.
5. Then you need to flash boot.img and recovery, I was using from version Miui 10.4.5, i will put everything below so you can download it
6. After Flashing boot and recovery, your phone will boot up and that's it!
Download links:​boot.img V10.4.5
boot.img V11.0.1.0
recovery V10.4.5
Following this guide might help you to unbrick your phone, no need to use any programs like Miflash or SP FlashTool!
I hope my guide will help you, have a good day
Click to expand...
Click to collapse
bonjour,
je debute et je cherche une doc systeme android. Peux tu m'aider?
hi,
i'm looking for a system's documentation for Android. Can you help me please?
regards

I only flashed the recovery.img, not the boot. img. Should I try to drain the battery? Also, would disconnecting/reconnecting the battery work instead of waiting for the battery to drain?

lakhdar0104 said:
Hello my brother, i finished by bricking my RN8PRO while flashing TWRP, no normal boot no fastboot no recovery, just LED lighting when connecting him to PC, PLZ do you know where i can find an Authorized Mi Account, i will donate. Thanks bro :good:
Click to expand...
Click to collapse
you must to let the battery drained to 0% or disconecte the battery after this connecte the charger and the phone boot again

How long to wait battery drain? 1 week? 2 week?

Mi A2 Lite-accidentally removed OS,can't install stock or custom roms - help needed

Hello, hoping someone might be able to help me? I installed TWRP 3.3.0-dees_troy on my MI A2 Lite. Somehow whilst trying to update the phone to Android 10, I've managed to remove the OS (Android 9 @ 1.2020 prior to original OTA update to Android 10 which caused a bootloop problem). I have since tried all sorts of methods via videos and instructions on the internet and have not been able to reinstall any OS be it stock or custom. Before doing so I'd unlocked the bootloader, enabled Developer options etc. Would be grateful for any assistance you can offer. Desperately hoping a kind soul on here can help me get my phone up and running.? Thank you and best wishes

I am in the process of writing a detailed guide for custom rom installation. So you can wait 1-2 days about that because I think it will help you out. Regarding your issue, for custom roms you should use offain TWRP
Join Telegram at t.me/XMiA2Lite for additional queries and support

LinkBoi said:
I am in the process of writing a detailed guide for custom rom installation. So you can wait 1-2 days about that because I think it will help you out. Regarding your issue, for custom roms you should use offain TWRP
Join Telegram at t.me/XMiA2Lite for additional queries and support
Click to expand...
Click to collapse
Thank you, I'll take a look @ twrp-daisy-3.3.0-0-offain.img now. Will wait to hear from you regarding a detailed guide for custom rom installation. I'd prefer to reinstall stock android but if I have to first install a custom rom first, I'm happy to do this. A lot of the guides out there seem to me to be done for people that are familiar with installing custom rom, modifying and or manually flashing their handsets etc. I haven't done this for years as I have a MI A2 which I bought because it came with stock android. Before that I had a Samsung Galaxy Note 2 which I'd messed around with installing custom Roms and messing with developer options and bootloader t get rid of bloatware but went back to Samsung supplied rom. With the Mi A2 lite, completely my fault, I'd tried to update it using mi flash and TOOL ALL IN ONE, neither worked. Installed TWRP 3.3.0-dees_troy on my MI A2 Lite via TOOL ALL IN ONE. Thought it was straight forward to use. Big mistake. Ended up removing the OS which would not update OTA. Mi A2 lite came with a bootloop problem following 1/2.2020 initial update to android 10. I solved this via switching partitions via fastboot. Got complacent thinking modding and flashing was straight forward. Have paid the price. any help you can afford me will be greatly appreciated.

There is a flash reset script for using with adb. Try searching for unbrick Mi A2 Lite. It's a German thread. With that you can even go back from 10 to 9 without any errors or problems. Works 100%, did this multiple times.

Thanks but I no longer have android 10 or 9 on my phone. Accidentally removed operating system with TWRP. Absolutely lost now as to what to do next

dropmail said:
Thanks but I no longer have android 10 or 9 on my phone. Accidentally removed operating system with TWRP. Absolutely lost now as to what to do next
Click to expand...
Click to collapse
Doesn't matter. Even with no OS it will work. Give it a try.

dropmail said:
Somehow whilst trying to update the phone to Android 10, I've managed to remove the OS
Click to expand...
Click to collapse
Can you still get to fastboot?
Using the stock fastboot ROMs should be able to recover, or MiFlash if you prefer.
Assuming that by "removed the os" you don't mean broke the partition table. In which case you probably need edl.

dropmail said:
Thank you, I'll take a look @ twrp-daisy-3.3.0-0-offain.img now. Will wait to hear from you regarding a detailed guide for custom rom installation. I'd prefer to reinstall stock android but if I have to first install a custom rom first, I'm happy to do this. A lot of the guides out there seem to me to be done for people that are familiar with installing custom rom, modifying and or manually flashing their handsets etc. I haven't done this for years as I have a MI A2 which I bought because it came with stock android. Before that I had a Samsung Galaxy Note 2 which I'd messed around with installing custom Roms and messing with developer options and bootloader t get rid of bloatware but went back to Samsung supplied rom. With the Mi A2 lite, completely my fault, I'd tried to update it using mi flash and TOOL ALL IN ONE, neither worked. Installed TWRP 3.3.0-dees_troy on my MI A2 Lite via TOOL ALL IN ONE. Thought it was straight forward to use. Big mistake. Ended up removing the OS which would not update OTA. Mi A2 lite came with a bootloop problem following 1/2.2020 initial update to android 10. I solved this via switching partitions via fastboot. Got complacent thinking modding and flashing was straight forward. Have paid the price. any help you can afford me will be greatly appreciated.
Click to expand...
Click to collapse
no worries pal, I hope I helped

https://forum.xda-developers.com/mi-a2-lite/how-to/detailed-installation-guide-custom-roms-t4142637 Check this thread

a1291762 said:
Can you still get to fastboot?
Using the stock fastboot ROMs should be able to recover, or MiFlash if you prefer.
Assuming that by "removed the os" you don't mean broke the partition table. In which case you probably need edl.
Click to expand...
Click to collapse
Hello, thank you for your time, i can go into fast boot via volume down and power button. I think I wiped everything using TWRP. I've no idea what edl is? or what you meany by breaking the partition table? I've tried misflash, fastboot and tool all on one
https://sourceforge.net/projects/tool-all-in-one/
I'm not too techy but can follow instructions if they are complete. the phone was originally stuck on a bootloop, I sorted that via a video on youtube i.e. switching from slot to slop b via ADB and fastboot.
In spite of extensive (several hours of searching) and trying ,several roms both fast boot and non fast boot, nothing has worked.
Very frustrating as if I can actually find a video or website with simple and complete (that doesn't suppose the user knows tech jargon or is familiar with the or similar procedures, I'm confident I can sort the problem)

dropmail said:
Hello, thank you for your time, i can go into fast boot via volume down and power button. I think I wiped everything using TWRP. I've no idea what edl is? or what you meany by breaking the partition table? I've tried misflash, fastboot and tool all on one
https://sourceforge.net/projects/tool-all-in-one/
I'm not too techy but can follow instructions if they are complete. the phone was originally stuck on a bootloop, I sorted that via a video on youtube i.e. switching from slot to slop b via ADB and fastboot.
In spite of extensive (several hours of searching) and trying ,several roms both fast boot and non fast boot, nothing has worked.
Very frustrating as if I can actually find a video or website with simple and complete (that doesn't suppose the user knows tech jargon or is familiar with the or similar procedures, I'm confident I can sort the problem)
Click to expand...
Click to collapse
If you boot to fastboot, try the script I was talking about. It will help you! No. 3, ADB method.

Thanks ever so much, the link is exactly what I needed
LinkBoi said:
https://forum.xda-developers.com/mi-a2-lite/how-to/detailed-installation-guide-custom-roms-t4142637 Check this thread
Click to expand...
Click to collapse
Thanks ever so much, the link is exactly what I needed, I downloaded everything, followed all but the final instruction (14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots) I disconnected my phone from PC, and it got stuck in a bootloop. Repeated the process for a second time whilst keeping my phone connected to PC via usb cable, held power button down for 10 seconds and it worked and installed android 9 version 1.8.2019. Managed to update to android 10 OTA. Just relocked the boot loader via TOOL ALL IN ONE https://forum.xda-developers.com/oneplus-3/how-to/tool-tool-one-driversunlocktwrpfactory-t3398993. Unfortunately, ths did lock the bootloader but also reset the phone. Just need to reinstall everything now. Thank you again for your time. Really appreciate it. Best wishes

vinylmeister said:
If you boot to fastboot, try the script I was talking about. It will help you! No. 3, ADB method.
Click to expand...
Click to collapse
Thanks ever so much for your time. I used the instructions on the link below. /i was going to try and uses yours after but someone esle posted a link which saved me searching for the German thread you were referring to
https://forum.xda-developers.com/mi-a2-lite/how-to/detailed-installation-guide-custom-roms-t4142637
the link was exactly what I needed, I downloaded everything, followed all but the final instruction (14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots) I disconnected my phone from PC, and it got stuck in a bootloop. Repeated the process for a second time whilst keeping my phone connected to PC via usb cable, held power button down for 10 seconds and it worked and installed android 9 version 1.8.2019. Managed to update to android 10 OTA. Just relocked the boot loader via TOOL ALL IN ONE https://forum.xda-developers.com/one...ctory-t3398993. Unfortunately, ths did lock the bootloader but also reset the phone. Just need to reinstall everything now. Thank you again for your time. Really appreciate it. Best wishes

dropmail said:
Thanks ever so much, the link is exactly what I needed, I downloaded everything, followed all but the final instruction (14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots) I disconnected my phone from PC, and it got stuck in a bootloop. Repeated the process for a second time whilst keeping my phone connected to PC via usb cable, held power button down for 10 seconds and it worked and installed android 9 version 1.8.2019. Managed to update to android 10 OTA. Just relocked the boot loader via TOOL ALL IN ONE https://forum.xda-developers.com/oneplus-3/how-to/tool-tool-one-driversunlocktwrpfactory-t3398993. Unfortunately, ths did lock the bootloader but also reset the phone. Just need to reinstall everything now. Thank you again for your time. Really appreciate it. Best wishes
Click to expand...
Click to collapse
You can always try custom ROMs too. They offer a much better experience than stock in my opinion. For relocking the bootloader, you could also have clicked the "clean all and lock" option in miflash. Anyways, I'm glad I helped ^^

LinkBoi said:
You can always try custom ROMs too. They offer a much better experience than stock in my opinion...
Click to expand...
Click to collapse
Except battery backup

vinylmeister said:
Except battery backup
Click to expand...
Click to collapse
Newer Q custom ROMs with new 4.9 kernels offer great battery backup too.

vinylmeister said:
Except battery backup
Click to expand...
Click to collapse
Thanks again, do you know is there any way to clear some of the system?
I've a 32GB 3GB Ram version of the MIA2 Lite. tthe rom I installed as per the link you sent me was around 3GB in size. Having updated to the latest Android 10, storage confirms the system is using 9.4 GB of space. I've disabled as much as I can i.e. apps I dont use.

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

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.