Develop Bugs

Please help LG-G4-H815 not booting up after a shutdown.

I need help, I've got LG-G4 H815 unlocked purchased from ebay brand new.
I had issue of phone warming up from time to time while charging or when I run waze and at the same time play music in car over Bluetooth.
Yesterday my phone shutdown on its own as it got too warm while I was driving.
After that phone is not restarting, I took off battery - let it cool down and tried charging it fully overnight but still looks like it is not restarting. I tried to do the hard reset and it wont even do that. All I see is the LG logo on screen and as I try to charge it using power cable provided by LG it warms up from time to time. The LG logo keeps coming and going from time to time as if phone is trying to reboot but nothing else happens after that.
Is there a way to fix this thing or I should contact Squaretrade for warranty call ?

Anyone can help with this please ?
I've tried putting in new battery assuming it was battery related issue. But all my phone does is reboots and brings to screen which says Android is starting....
It then tries to optimize different apps for Android. But nothing happens - after 10-15 minutes of optimizing app (at most it reaches count of 15-20 apps out of 84 apps) amd then once again phone reboots. This is going on in loop now.
It wont even allow me to factory reset phone using power button + down button combo. Is there any other way to fix this issue ?
Also I bought this online on ebay brand new, and this is H815 variant of device. So whom should I contact for warranty question ?

Will it go in to download mode? Plug it in to a PC whilst off and holding volume up.

El Presidente81 said:
Will it go in to download mode? Plug it in to a PC whilst off and holding volume up.
Click to expand...
Click to collapse
Okay I will give that a try, if it goes in download mode what does that mean ? Is there a way to reset it after connecting to PC/MAC ?

http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If you can get to download mode, you can use the instructions in above link to reflash the phones software. If it still won't boot after a fresh firmware is installed, it's probably a hardware issue and you'll have to return it.
If you have the IMEI number noted, you can check to see if the software version for your specific handset is available here: http://devtester.ro/projects/lg-firmwares/
Was it bought in the EU? If yes, contrary to popular belief, I'm almost certain the seller is responsible for the return for the first 6 months, but I'll need to double check that.

El Presidente81 said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If you can get to download mode, you can use the instructions in above link to reflash the phones software. If it still won't boot after a fresh firmware is installed, it's probably a hardware issue and you'll have to return it.
If you have the IMEI number noted, you can check to see if the software version for your specific handset is available here: http://devtester.ro/projects/lg-firmwares/
Was it bought in the EU? If yes, contrary to popular belief, I'm almost certain the seller is responsible for the return for the first 6 months, but I'll need to double check that.
Click to expand...
Click to collapse
Thank you I tried using the firmware update to get it back to stock but looks like it is of no avail. Device still keeps rebooting.
I contacted LG for this issue and they wont touch the device because I'm in USA and this is international version of device. I bought this device off of Ebay probably 3 months back. So I don't think if I can contact seller for any exchange.

It might be worth contacting eBay to see what they say.
Did you use PayPal? They might offer some sort of protection.
Not sure what to suggest otherwise, sorry.

El Presidente81 said:
It might be worth contacting eBay to see what they say.
Did you use PayPal? They might offer some sort of protection.
Not sure what to suggest otherwise, sorry.
Click to expand...
Click to collapse
Thanks for your help. I will contact Paypal to see what can be done.
Do you know any other method to HARD reset device back to factory default apart from one in the link ?

Just that method. You're completely reflashing the software on the phone so if it was a software issue, that should have sorted it.

I also have the same problem and when contacted LG US support got the same response, saying its international version only LG UK can support it.
When contacted LG UK, they say they can send repair label only to UK addresses. Not sure what to do, been like this for almost 2months now

S4 Mini i9195 Boot loop - Recovery problem - Download mode working good

Hi to all, After two years of good working S4 mini is giving up. The last time when the problem is occured, the phone was „forced“ swiched off because of low battery. It was put on charger to charge normally and it did it as usual. But, when it was swiched on again it stayed in the boot loop on the Samsung logo over and over again. When I tried to come into recovery, it shows as normally when it starts to go into recovery with text that it has, as last, succesfully loaded CRC and then it shows for a short text: „There is no command“ and immediately reboot and come out of recovery. I went to „Download mode“ and I flashed in Odin, with no problem, the newest S4 mini official ROM but it didn't fix the problem. Any expiriance or sugestions are welcome... Thanks in advance !

If someone knows... Is it possible that some hardware component inside the phone which is responsible for recovery to work, that is burned out or something like that... ? And if so, could it be replaceable ? Thanks in advance !

Someone with a similar problem and some solution, maybe ?
Sent from my GT-N7000 using XDA-Developers mobile app

Boombastical said:
Hi to all, After two years of good working S4 mini is giving up. The last time when the problem is occured, the phone was „forced“ swiched off because of low battery. It was put on charger to charge normally and it did it as usual. But, when it was swiched on again it stayed in the boot loop on the Samsung logo over and over again. When I tried to come into recovery, it shows as normally when it starts to go into recovery with text that it has, as last, succesfully loaded CRC and then it shows for a short text: „There is no command“ and immediately reboot and come out of recovery. I went to „Download mode“ and I flashed in Odin, with no problem, the newest S4 mini official ROM but it didn't fix the problem. Any expiriance or sugestions are welcome... Thanks in advance !
Click to expand...
Click to collapse
Did you solve it? I'm having the same problem

Hi Danaidh, Sorry but not at all. I have spoken with some smartphone repairing technician and he told me that it is a hardware problem and that he has to solder some chip and to replace it with a new one. Because it was all happening abroad (Central East Europe), I thought that I will find some software solution here on XDA. Here where I live (West Europe) I didn't try to bring my smartphone to some smartphone repairing centar because they will simply swap a motherboard and they will charge me a full price what means is much better to buy a new smartphone then repairing this one. Even worst, after five months my phone doesn't charge any more and doesn't start at all and all this „smelt“ now on the real hardbrick. I have regulary charged a baterry to keep my S4 mini i9195 in life, but it could be also that it has swiched on it self during transport in my bag and that I didn't notice this and that it has used all battery power by swichining on and off in the infinite loop... But I will check it later if it will be visable on my PC without battery... If you find some other solution send me a message, please... Thanks in advance... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app

I just checked if it will be „seen“ on my PC and it has installed drivers and it's seen as „Qualcomm HS-USB QDLoader 9008“ on COM6 port... So it means that battery died...
But fortunatelly it means there is still hope for this „little bug“(S4 mini)...
Sent from my GT-N7000 using XDA-Developers mobile app

Same problem here.. Did they say at least which chip should be replaced?

Same problem here.

Same problem, any resolution?

Gianasy, he didn't say which chip particularly should be replaced, but he mentioned the one who's responsible for recovery ... Or something like that... So, if you have some news on it, it will be nice to share it with us later on... Thanks !
Sent from my GT-N7000 using XDA-Developers mobile app

Similar problem here
Boombastical said:
Someone with a similar problem and some solution, maybe ?
Sent from my GT-N7000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Similar problem here but still no solution :/
Link to thread here

Boombastical said:
Hi Danaidh, Sorry but not at all. I have spoken with some smartphone repairing technician and he told me that it is a hardware problem and that he has to solder some chip and to replace it with a new one. Because it was all happening abroad (Central East Europe), I thought that I will find some software solution here on XDA. Here where I live (West Europe) I didn't try to bring my smartphone to some smartphone repairing centar because they will simply swap a motherboard and they will charge me a full price what means is much better to buy a new smartphone then repairing this one.
Click to expand...
Click to collapse
Interesting. I have the very same problem like you (and two friends of mine have the same problem with their s4 mini). I went to a phone repair shop and he told me, that it is "a known problem of the s4 mini" and some part of the motherboard has to be "reparied"/replaced, but he has to send it somewhere and this will take about ten days.

I have ordered a second hand (used - refurbished) mainboard for S4 Mini from China for € 22 - so I'll write here and update you what is going on in about three - four weeks from now... Till then... Cheers !

Boombastical said:
I have ordered a second hand (used - refurbished) mainboard for S4 Mini from China for € 22 - so I'll write here and update you what is going on in about three - four weeks from now... Till then... Cheers !
Click to expand...
Click to collapse
Where did you buy it? I'm searching for a shop selling mainbords for the i9192 version of the S4 Mini.

I have a phone with the same problem.
Do you think i can use adb's pull to extract something from the phone? So far nothing worked.
In order to use adb I should be able to put the phone in recovery

Birtieddu said:
Do you think i can use adb's pull to extract something from the phone? So far nothing worked.
In order to use adb I should be able to put the phone in recovery
Click to expand...
Click to collapse
If you had installed some cyanogenmod, maybe you can use adb while the phone is in recharge mode (=off). I've written a guide, how to extract your data, here.

sumeruter said:
If you had installed some cyanogenmod, maybe you can use adb while the phone is in recharge mode (=off). I've written a guide, how to extract your data, here.
Click to expand...
Click to collapse
No cyanogenmod, it's all stock.
I've tried your guide but as soon as I connect the phone (off), it turns on and keep booting (loop).

Birtieddu said:
No cyanogenmod, it's all stock.
I've tried your guide but as soon as I connect the phone (off), it turns on and keep booting (loop).
Click to expand...
Click to collapse
Interesting, it shouldn't start just by plugging the charge cable in. Someone in another thread mentioned that a defective power button might cause similar symptoms. Have you tried just holding menu and vol-up or -down while it keeps restarting?
When in windows cmd, type
Code:
adb wait-for-device
and plug in the cable then. Does it wait forever or does the command come back?

sumeruter said:
Interesting, it shouldn't start just by plugging the charge cable in. Someone in another thread mentioned that a defective power button might cause similar symptoms. Have you tried just holding menu and vol-up or -down while it keeps restarting?
When in windows cmd, type
Code:
adb wait-for-device
and plug in the cable then. Does it wait forever or does the command come back?
Click to expand...
Click to collapse
Same story, unfortunately.
I made a little video. So you can better see what's going on.
After I plug the cable the phone starts and never stop until I remove the battery.
Here the video: vid .me/9hCh (remove the space after vid)

sumeruter said:
Where did you buy it? I'm searching for a shop selling mainbords for the i9192 version of the S4 Mini.
Click to expand...
Click to collapse
Update: So, after more then one month and half of waiting, I have finaly recieved my 'secondhand' (used - at least so is stated by the seller) ordered mainboard for i9195 lte Europe S4 mini and I swapped it and it works perfect.
Site where I bought it is: Aliexpress.com - Search under: „100% work EU version i9195 unlocked motherboard full function logic board“ Succes !!!
Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app

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.

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