Develop Bugs

[Q] Sudden Hardbrick

My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!

goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight

U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all

Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.

sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.

[Q] Hard bricked, but...

Hi there, I hard bricked my Tab S 8.4. No reaction to anything I did (key combinations, let it charge for hours, stuff like that). Don't know how it happened but it just crashed to death shortly after installing an inofficial Lolloipop build from here. I don't think a ROM can make a device not turn on at all. My money is on hardware failure.
Anyway, brought it in for repairs (willing to pay since I knowingly voided the warranty). Got the call yesterday. They said the software had been tampered with and they can't repair it. I objected that the software won't break the hardware but no dice. They won't even do it for cold hard cash.
BUT: To see the 'illegal' software they HAD to get the thing to turn on . And if they got it to turn on somehow, so can I. Or... am I completely wrong there and they have some magic fairy dust?
Any ideas on how I could accomplish what the repair guys could obviously do? There is no important data or anything on it so I'd be happy with Odin mode, CWM or whatever.

dancress said:
Hi there, I hard bricked my Tab S 8.4. No reaction to anything I did (key combinations, let it charge for hours, stuff like that). Don't know how it happened but it just crashed to death shortly after installing an inofficial Lolloipop build from here. I don't think a ROM can make a device not turn on at all. My money is on hardware failure.
Anyway, brought it in for repairs (willing to pay since I knowingly voided the warranty). Got the call yesterday. They said the software had been tampered with and they can't repair it. I objected that the software won't break the hardware but no dice. They won't even do it for cold hard cash.
BUT: To see the 'illegal' software they HAD to get the thing to turn on . And if they got it to turn on somehow, so can I. Or... am I completely wrong there and they have some magic fairy dust?
Any ideas on how I could accomplish what the repair guys could obviously do? There is no important data or anything on it so I'd be happy with Odin mode, CWM or whatever.
Click to expand...
Click to collapse
I kindof had the same problem, but got mine repaired.
May I ask where you send it to for repairs? Was it Samsung or a local repair shop that told you they could not fix it?
And did they send it back to you? Kindof weird they won't fix your device after you say you are willing to pay for it.
Depending on where you live, Samsung covers a lot of 'problems' in the first year of the standaard warranty.
As for turning on the device..
What options have you tried yet?
If you connect the tablet with usb to your pc and turn it on, does it get recognized?
And if so, as what?
But if your screen doesn't turn on, you're probably going to need repairs anyway.

shifter7 said:
I kindof had the same problem, but got mine repaired.
May I ask where you send it to for repairs? Was it Samsung or a local repair shop that told you they could not fix it?
And did they send it back to you? Kindof weird they won't fix your device after you say you are willing to pay for it.
Depending on where you live, Samsung covers a lot of 'problems' in the first year of the standaard warranty.
As for turning on the device..
What options have you tried yet?
If you connect the tablet with usb to your pc and turn it on, does it get recognized?
And if so, as what?
But if your screen doesn't turn on, you're probably going to need repairs anyway.
Click to expand...
Click to collapse
Over here you bring it back to the shop where you bought it. They will try the simplest solutions in house but usually send it back to the manufacturer. I think the information came from Samsung directly. Another theory I have is a simple lie. They tried it in house, nothing came up, some clever guy screamed 'CYANOGEN!' and they all high fived (I have a vivid imagination )
As for turning it on: tried everything. It's not only the screen, it did nothing at all. No signs of life whatsoever. Of course the PC wouldn't recognize it since it was turned off.
I'll pick it up tonight. Maybe whatever they did to see the software tampering stuck and it will at least go into Odin mode. I can work from there.

dancress said:
Over here you bring it back to the shop where you bought it. They will try the simplest solutions in house but usually send it back to the manufacturer. I think the information came from Samsung directly. Another theory I have is a simple lie. They tried it in house, nothing came up, some clever guy screamed 'CYANOGEN!' and they all high fived (I have a vivid imagination )
Click to expand...
Click to collapse
I lolled
But it you think it came from Samsung directly, then I would advise you to contact Samsung.
Here is a link from an article where it states that Samsung covers bricked devices, but only the first time. (Dutch article, GTranslated english)
I have no idea if this also counts for where you live though.
https://translate.google.com/transl...er-garantie-repareren.html&edit-text=&act=url
dancress said:
As for turning it on: tried everything. It's not only the screen, it did nothing at all. No signs of life whatsoever. Of course the PC wouldn't recognize it since it was turned off.
I'll pick it up tonight. Maybe whatever they did to see the software tampering stuck and it will at least go into Odin mode. I can work from there.
Click to expand...
Click to collapse
Okay.. well.. that sucks.
Don't forget to ask for some of that magic dust they used

shifter7 said:
I lolled
But it you think it came from Samsung directly, then I would advise you to contact Samsung.
Here is a link from an article where it states that Samsung covers bricked devices, but only the first time. (Dutch article, GTranslated english)
I have no idea if this also counts for where you live though.
https://translate.google.com/transl...er-garantie-repareren.html&edit-text=&act=url
Okay.. well.. that sucks.
Don't forget to ask for some of that magic dust they used
Click to expand...
Click to collapse
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.

dancress said:
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
Click to expand...
Click to collapse
I'm laughing so hard right now :laugh::laugh::laugh::laugh::laugh::laugh:

dancress said:
Magic dust it was. Got it back, dead. Came home a minute ago, put it on the charger. Lo and behold, the battery appears. Device turns on too, boots Lollipop goodness. 0 per cent battery but hey. Whatever they did, they obviously did NOT realize they solved the whole problem with just their diagnostic :laugh:
Thread can be locked if the PTB deem it necessary.
Click to expand...
Click to collapse
It simply reset itself after the battery completely died. Black screen and no response doesn't mean the device is off.
As soon as they switched it on they would have seen knox had been tripped.
Sort of did you a favour by telling you it wasn't bricked.

I had the same sort of problem i connected my tab to my laptop and used the recovery mode key combination then my tab came back to life
---------- Post added at 04:29 PM ---------- Previous post was at 04:29 PM ----------
Sorry download mode not recovery mode

Comforts me while ROM developing that the only reported case of a hardbrick was here - and the battery just died.

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.

Help! Hard-bricked Galaxy S9

Hi,
I got my daughter a new phone and planned to send in her s9 as AT&T was offering $800 for trade in... She got her new phone set up, then, somehow, her S9 that's been going strong for years, hard bricked itself. I've been all over the internet trying to dig up a solution, but no luck yet....
**Symptoms**
No blinking LEDs
Power + Volume Up: Nothing
Power + Volume Down + Bixby: Nothing (Boot menu screen never comes up)
Plug into computer:
Hear windows USB connect sound
See device in device manager under "Other Devices":"qusb_bulk_cid:0402..."
Unplug from computer:
Hear windows USB disconnect sound
While plugged into comuter:
Power + Vol Down + Bixby: Usb Disconnect / Reconnect Sound, device disappears / reappears from Device Manager (no boot menu)
**What I've tried so far...
FixPpo for Android: Wasted $40. Does not fix hard-bricked phone. If you can't get to the screen you can't get the firmware image onto the phone.
ODIN 3: Does not see the phone in the ID:COM field. Iinstalled the Qualcomm HS-USB drivers and restarted w/ Driver unsigned mode. Phone shows up under Ports (COM & LPT) but ODIN still doesn't see it.
QPST: Can see the phone, but that's all I could seem to do with it.
QFIL: This started out promising, until I needed "Programmer Path" and "Content XML" files, which I can't seem to find for the galaxy S9 (Or perhaps there's a generic Qualcomm one I can't find)
If someone's out there, anywhere, that's been able to resolve this I'd really appreciate some additionl info / links to the right files for QFIL. Or am I SoL if the screen doesn't come up? I feel like we would have seen some symptoms earlier if the screen was starting to burn out vs. just never coming up again...
Thanks in advance,
Steve in Massachusetts, USA

Display dead or software dead

Thanks for the reply...
That's a good question.... I think it's just the software. The phone has been working fine for years, with no degradation or dead pixels, and it wasn't abused or dropped. I've had no luck qith QFIL... was going to attempt Octoplus next, but I don't want to drop $50 for a license if I'm still going to end up bricked. I think QFIL could work if I could get it into download mode, but with no screen that's proving difficult.

stevenlmas said:
Thanks for the reply...
That's a good question.... I think it's just the software. The phone has been working fine for years, with no degradation or dead pixels, and it wasn't abused or dropped. I've had no luck qith QFIL... was going to attempt Octoplus next, but I don't want to drop $50 for a license if I'm still going to end up bricked. I think QFIL could work if I could get it into download mode, but with no screen that's proving difficult.
Click to expand...
Click to collapse
Hey, you need download software for you model s9 if you want flash again

oli231 said:
Hey, you need download software for you model s9 if you want flash again
Click to expand...
Click to collapse
Thanks - I did download QFIL, Odin and QPST, but b/c I can't get PC to see it as a modem, Odin doesn't work. I can't get QFIL to work b/c I can't get into download mode. I just blew $50 on Octoplus, but am still waiting for my license key...
I've put $150 into a dead phone... I probably could have got a used one for that if I looked hard enough.

stevenlmas said:
Thanks - I did download QFIL, Odin and QPST, but b/c I can't get PC to see it as a modem, Odin doesn't work. I can't get QFIL to work b/c I can't get into download mode. I just blew $50 on Octoplus, but am still waiting for my license key...
I've put $150 into a dead phone... I probably could have got a used one for that if I looked hard enough.
Click to expand...
Click to collapse
For my eye motherboard is dead

My S9+ died similarly. Was watching a video and suddenly it crashed and stopped working. Came back to life 2 days later just to die again after an hour. Turns out it was old liquid damage from a month prior swim. Popped it open and cleaned it with isopropyl alcohol and it's working now. If you're feeling confident you can try to open it and see if it's liquid damage or anything that a simple fix such as an alcohol clean might fix. But most likely it's a hardware not a software problem. Good Luck.

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