Develop Bugs

Really...really bricked OnePlus 3

Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem

If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.

CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.

dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.

I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.

dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.

Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.

Nexus 5X hard bricked. Is there definitely no way to fix it?

I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.

@gwynlordofcinder: sad for you. But why you ask the same question as 20 others before? Try freezer and/or oven to get back the mainboard-connections. If successfull, you can save your data or go on with a kernel-profile which makes the big core sleep. Use search for details.

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.

Most likely fixable, but with the need of special files.
Search up on QD Loader 9008 on this subforum and read through it.
i'm on the hunt to find a fix for it, hopefully i'll make it. gonna share my findings asap!

Voicebox said:
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.
Click to expand...
Click to collapse
There is no extended warranty in the UK, which is where I purchased the phone.

gwynlordofcinder said:
There is no extended warranty in the UK, which is where I purchased the phone.
Click to expand...
Click to collapse
Since this happened from normal usage and not from you installing a custom ROM or updating the bootloader, or something like that, I think you have the bootloop problem. I normally think of a hard brick being the result of flashing say the incorrect bootloader, or a corrupt file, etc. which can then hopefully be undone by software means to get the right software back on there.
If you have the bootloop, it is a hardware problem. The fact that the phone doesn't bootloop does not mean you don't have the hardware problem. Boot looping was just the most common way to identify it, but many, like mine would just either never even start booting, or would start, then go black.
If you don't figure out any software way to do anything, then try to look for bootloop fixes. Searching for that might get you further. But with a hardware problem, everything except the fix for disabling the big cores (in XDA threads), is temporary unless you are lucky.
Assuming you have a hardware issue, here's some steps to maybe try. I was able to get the rescue fix installed on my phone after using a hair dryer on the motherboard. But that didn't fix anything since my problem was hardware. But if your OTA update was maybe slightly corrupted, maybe it'll help.
https://productforums.google.com/forum/#!topic/nexus/G_0s70PzK_s
To jump right to trying a rescue OTA, go here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/hdrNONCCoNE
If it doesn't react enough to do anything from a computer, you may have to resort to putting it in the freezer for a while first. Which may give a short period where it'll boot and you can maybe adjust the settings so you can try one of the XDA fixes that disable the big cores.
One fix that disables the big cores:
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E

Voicebox said:
which can then hopefully be undone by software means to get the right software back on there.
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E
Click to expand...
Click to collapse
except that the files needed for unbricking corrupt bootloaders/eMMCs' are so hard to find it's incredible.
bought a used 5X that "suddenly died in a pocket", now that you mention all of this, i might try doing the hardware fixes and then apply the big core disabling and hopefully get my phone to work.
the phone did get serviced though, so they might've installed bad firmware since the phone is in QDLoader & in EDL mode (PC recognizes the phone, while fastboot/adb/LGUP doesn't)

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
Can you update driver "QHSUSB_BULK" in device manager by choose driver manually . I have problem like this in Inew V3 (Chaina Phone) and can fix by choose driver manually.

S20 Ultra Bricked (G9880)

Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Date: 2020-10-26
Version: 10
PDA: G9880ZHU2BTJ6
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.

Gerstark said:
Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Version: 10
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.
Click to expand...
Click to collapse
Aorry to hear that.. did tou try vol up and power to go to recovery?

Gerstark said:
Hi guys, i come here searching for help, it was a normal day, i was out with the phone fully working, it was on my pocket, when i get home i see that it's off, tried to turn on and nothing... tried vol- and power to enter download mode and nothing, the screen is always black.
Connected it to my laptop to see if it shows up as a USB device, it sounds like it connected and in "Device Manager" it show as "QUSB_BULK_CID:0412_SN:BA92F870" but ODIN doesn't detect it, so i can't try to install a clean ROM.
I can't take it to samsung as this model is a HONG KONG one and i'm in Chile, they won't apply warranty and legally i had only 3 month in a external shop but i'm on my 5th month, so it's not use to try that way.
A few points about the phone:
Latest firmware: (INSTALLED NATURALLY, I GOT IT FROM SAMSUNG OFFICIALY)
Country/Carrier: Hong Kong
Date: 2020-10-26
Version: 10
PDA: G9880ZHU2BTJ6
CSC :G9880OZS2BTJ6
NEVER EVER tried to install a rom or something on the phone, i was happy with how it works and the battery i got from it.
Now i bought a S20 FE as a momentary replacement because i can't be without a phone for my work... i've read lots and lots of threads on XDA and other places but all of them are about the Note 4, so it's really out of date to try fix it that way, at least 6-8 years old posts.
Anyone here had a similar issue? is it fixable?
Hope someone can help, it really hurts loosing a phone that costs +USD1000
Thanks guys.
Click to expand...
Click to collapse
The device is powering on and off randomly on it's own, correct? This sounds like a hardware issue, you may have a defect somewhere in the power supply chain. If you have a reputable repair agency nearby, not necessarily Samsung, this would be my first step. Not sure why Odin isn't detecting the device. Here's an article which offers common solutions for this problem.
https://rootmygalaxy.net/fix-odin-not-detecting-samsung-android-phone/
Good luck!

myaslioglu said:
Aorry to hear that.. did tou try vol up and power to go to recovery?
Click to expand...
Click to collapse
Yes, but it doesn't work, screen alway stays on black, i know it's not fully dead because it sounds as a USB driver when connected to my laptop
varcor said:
The device is powering on and off randomly on it's own, correct? This sounds like a hardware issue, you may have a defect somewhere in the power supply chain. If you have a reputable repair agency nearby, not necessarily Samsung, this would be my first step. Not sure why Odin isn't detecting the device. Here's an article which offers common solutions for this problem.
https://rootmygalaxy.net/fix-odin-not-detecting-samsung-android-phone/
Good luck!
Click to expand...
Click to collapse
tomorrow i'll try to take it somewhere, thanks for the link, but i already tried all those tips

I take it you have a Qualcomm cpu? If so you need to install the Qualcomm usb driver, link https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ or a newer version if available. This should solve the problem in regard of pc connection, usb recognition and most of all reading the internal memory. Please use Google search for mor info and the correct procedure as i never used this myself. Good luck.

gee2012 said:
I take it you have a Qualcomm cpu? If so you need to install the Qualcomm usb driver, link https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ or a newer version if available. This should solve the problem in regard of pc connection, usb recognition and most of all reading the internal memory. Please use Google search for mor info and the correct procedure as i never used this myself. Good luck.
Click to expand...
Click to collapse
Anything you can find on google i already tried, installing the drivers didn't help either... thanks tho!

Oh hey, its you! We spoke on reddit a few days ago about this problem, sorry to see you haven't been able to fix it.
Have you tried all your USB ports? Or maybe another computer? Worst case scenario there's a solid chance Samsung will repair it either for free if you're lucky or for a price. Even if you bought it from another country there's a possibility the manufacturer's warrant is intact especially because it sounds like you didn't do anything to the phone at all that would've warranted the sudden failure.
Does ADB see it when it's plugged in? If you don't have ADB installed follow this: https://www.xda-developers.com/install-adb-windows-macos-linux, then once installed run "adb devices" from command prompt.

Mi 10T pro not detected by PC/Mac/Linux. No OTG either

I am using a Mi 10T Pro for the past 10 months and the experience has been good so far. I am on stock ROM( MIUI Global 12.5.1 Stable 12.5.1.0 RJDINXM).
Since last week, my phone no longer gets detected by Mac/PC/Linux and it does not detect any OTG as well. The phone is not getting detected in recovery mode and the fastboot mode by adb and fastboot. Also, there is no notification to select the connection mode when a USB cable is plugged in. There were no OTA updates before it stopped working.
When I searched online, I saw a few posts from xiaomi eu forums reporting the same issue but no one has a proper solution. I have tried setting the default USB mode in developer tools but no effect. Any solutions?

praveesh4u said:
I am using a Mi 10T Pro for the past 10 months and the experience has been good so far. I am on stock ROM( MIUI Global 12.5.1 Stable 12.5.1.0 RJDINXM).
Since last week, my phone no longer gets detected by Mac/PC/Linux and it does not detect any OTG as well. The phone is not getting detected in recovery mode and the fastboot mode by adb and fastboot. Also, there is no notification to select the connection mode when a USB cable is plugged in. There were no OTA updates before it stopped working.
When I searched online, I saw a few posts from xiaomi eu forums reporting the same issue but no one has a proper solution. I have tried setting the default USB mode in developer tools but no effect. Any solutions?
Click to expand...
Click to collapse
Hi,
I also experience such problems from time to time. I connect the phone one time to pc and it's detected. Next time only charging - no mtp.
You can try other usb ports of your pc - preferebly usb 2.0. This works for me.

zaqm said:
Hi,
I also experience such problems from time to time. I connect the phone one time to pc and it's detected. Next time only charging - no mtp.
You can try other usb ports of your pc - preferebly usb 2.0. This works for me.
Click to expand...
Click to collapse
Unfortunately, even on USB 2 ports, the phone is not getting detected. Charging works fine and reverse charging works. I suspect that this is more of a software issue due to the lack of USB connection notifications.

Update: Did a factory reset to make sure whether this was a software issue. Still not getting detected and no response when OTG devices are plugged in.

Actually, I ordered a cheap priced charging port for Mi 10T from Shopee. It is not a original Xiaomi product but an OEM I suppose. It has not arrived yet, but, as soon as I receive it, I will go to a technician and have my stock charging port replaced. Maybe around less than month from now I will get back here and post the result. Cause, this is my last resort in finding solution to this issue...

An update on this issue:
Approached the Xiaomi service center with this issue. They diagnosed that it is a harware issue and the mainboard needs to be replaced. Luckily, the phone is still in warranty and hence I don't have to spend any money on this. The main board price is around 24k INR.

praveesh4u said:
Update: Did a factory reset to make sure whether this was a software issue. Still not getting detected and no response when OTG devices are plugged in.
Click to expand...
Click to collapse
Update: Approached the Xiaomi service center with this issue. They checked the issue and diagnosed that the issue was caused by a faulty mainboard. Now waiting for the mainboard to arrive. Since the phone was under warranty, the repair will be free of cost.

This problem is due to Mainboard (Motherboard) issue. Changing of Charging board won't help. Motherboard is not available in local repair shop in Ranchi Jharkhand so I will have to wait. In service Centre it costs 21 thousands rupees.
Let's see if I can get it cheaper in local market.
I think motherboard issue occurred after Miui 13 Update. Mi Sucks

I also have the same problem on a Windows 10 machine. I was ready to leave my 10T in the service center, but I tested the connection on my wife's laptop with Windows 7. The pop-up menu shows up on the phone when connected to the older OS. Check with different versions of Windows before visiting the service center.

zhekozhekov said:
I also have the same problem on a Windows 10 machine. I was ready to leave my 10T in the service center, but I tested the connection on my wife's laptop with Windows 7. The pop-up menu shows up on the phone when connected to the older OS. Check with different versions of Windows before visiting the service center.
Click to expand...
Click to collapse
Didn't work for me

Question *Urgent Help* Bricked Pixel 6 Pro

I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.

Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.

roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.

Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.

Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!

Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.

2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.

verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.

96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port

Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??

liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try