Develop Bugs

Help required, possibly bricked?

Hi all,
Hopefully you can help me, i have just installed the latest radio and Modaco ROM (this isn't the first time i've did this).
After installation i got what looked like an image of a drive and an arrow, i assume this meant it couldnt find the boot image. I then tried a couple of times to reboot holding the home key but now i cant even switch it back on... even on charge the light isn't coming on
Any help would be gratefully appreciated
Thanks
GF

When the arrow and drive comes up, you're meant to leave your phone well alone, it means it's flashing something (usually something important!)
If your phone doesn't turn on, sounds like you've made a full hard brick, nothing you can do but see if you can get it repaired.

Gutted, cheers

Can you pull the battery and get into fastboot?

Breakthecycle2 said:
Can you pull the battery and get into fastboot?
Click to expand...
Click to collapse
Not sure what that is? I've tried the various power+key sequences
Thanks

GaelForce said:
Not sure what that is? I've tried the various power+key sequences
Thanks
Click to expand...
Click to collapse
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.

docsamsom said:
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
Click to expand...
Click to collapse
Worked a treat, got a doorstep exchange today
Thanks

hard bricked my phone

Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.

Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.

If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.

brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.

Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux

republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?

If you can't get the phone to turn on you're out of luck.

Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.

thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.

kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots

You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800

lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?

kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/

Call Google and get it replaced. They are very good about that stuff.

kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!

Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.

Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.

kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?

That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!

Nexus 5x won't turn on

Last night my phone went dead. When I plugged it in. I saw the Goggle words on the screen, like when the phone is booting up from being off power. this stayed on for several seconds, then it flashed off and nothing all night. The led light was flashing on and off for a bit, but nothing. I couldn't turn it on then.
Then this morning, I was able to hold the power button and then the Google showed up for a few seconds, then nothing. I have tried holding down the power button for 10 sec to no avail, holding the power and vol down, nothing. Is there any other way to reset this or is the battery or something else on it dead and it needs to be returned to Google. Any and all help is welcomed.
Right now I have it plugged into the google cord and plug, not seeing the led light.

Good news: You're not the only one this is happening to.
Bad News: Not really a good solution yet.
Android Authority is covering it. There's some discussion in their comments.
I tried going into recovery and factory reset/wipe cache and that did nothing. Apparently some people have had luck flashing an older release, but I wasn't able to get anywhere close to that. I ended up calling calling the Google Hardware Warranty Center and they're sending me a replacement.

If bootloader is unlocked, I will be able flash factory image to fix this?

I haven't rooted the phone. It is just the basic android. I'm on with Google support right now. They are going through all the things that I have already done.

I can't get to the bootloader. The phone is off / dead right now. Once it turned off last night, I haven't been able to get it to power up again.

Google wanted me to put it on their cord and charge for an hour to see if anything changed. Hoping it works. I have to travel this weekend, and he was saying it could take up to 7 business days to get a new phone.

No power after 2 1/2 hours on the google cord. Guess to get a replacement.

hope you have a backup phone to use.

I have an iphone 5 I use for Ipod. Would it be too much work to use this until I get the other one, or will it probably not have the right sim card?

I'm in the same boat too. Google sent me out a warranty replacement. Mine just crashed when making a call and it would no longer power on after that. The only thing it would show when plugged in to my computer was Qualcomm downloader for USB.

When I updated to Nougat, I now get the screen that says Firmware Update with a message telling me to keep it plugged in. It's been at 0% for a few hours. Rebooting the phone results in the same thing. Phone's not rooted or anything. Guess I have a brick now.

90s
Sent from my Nexus 7 using XDA-Developers mobile app

There are lots of reports that nexus5x die after the nougat update

I got it to boot up last night, and I was able to get it to recovery mode, then tried to reboot, but nothing else. I'm contacting Google again to get the warranty started.

Just ordered a replacement, bummer that it is a refurb, not new, but sometimes the refub units are tested more than new. Is there any way that I can ensure that the data on the phone won't wind up in the wrong hands after it is fixed by Google and sent out, or is it just a roll of the dice?

They said they were sending me a refurb but its was a brand new one. It came in a retail box. Wondering if they ran out of refurbs with all the people having issues.

So I have the refurb unit at home. It is asking to update to nougat. Are the software updates safe enough to put on the phone. Mine is just stock not rooted.
Can't wait. I've been limping by on the iPhone 5.
Sent from my iPhone using Tapatalk

Mine died, LG told me to send it to them for repair, but only have me a FedEx ground, would have liked more like Air delivery for faster processing

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.

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