Develop Bugs

[Q] Dead screen

I was running my 3G Slide on Cyanogen 6 Stable (latest) with no problem. Then one day I say artifacts on my screen, I thought there was no problem, as I was playing a game at the time. I assumed it was just a bug in the game. So I kept on using the phone with no problems. About a week later however, the first signs of my current problem surfaced. The face keys died and no longer responded, unless I slided the phone open. The problem just got continually worse from there. It progressed to the point where I could not utilize the touch screen when the phone was open and now it is at a state where the touch screen completely doesn't work either open or closed and the face keys do not work either.
Just to differentiate, the face keys are the home, menu, back, and the google search thing. But the side buttons are all intact.
I've tried rebooting the phone with no success. A memory wipe, resetting Cyanogenmod, failed to solve the problem. I've since then emailed HTC to see if I still have coverage, since I bought it second hand, and reverted back to the original rom, from a thread in the Android Development forum, so I would be covered by warranty.
I at first assumed it was the digitizer, which might still be part of the problem; I still haven't completely ruled it out. But the digitizer alone wouldn't explain the dead keys, would it?
Help? Any suggestions if HTC decides not to repair it or charges a ridiculous price?

I also get the "android.process.acore has stopped unexpectedly" message now once I boot up.

It's most likely the flex cable that connects your screen, front buttons, microphone, etc. (everything on the front panel). That would explain the gradual going-out of the touch screen and the artifacts on the LCD. Send it in to t-mobile, the phone has only been out since last June, less than a year, so it's under warranty. Call for a replacement.

Thanks for the advice, MusicMan. I visited a T-Mobile store today, and its no doubt its under warranty. But here's the problem. I didn't buy the phone from a corporate store or an authorized store, I bought it second hand, and T-Mobile, after a visit and numerous calls of begging and pleading and employing moral responsibility, they said they can't replace the phone because the phone is not registered under my name... blah blah blah. Apparently warranty is through person and not transferrable.
What do I do?

Also, a side note.
In the off chance that I have to deal with HTC for my problem, what is the radio of the stock T-Mobile rom?
Just to make sure my phone is "stock" as ever before I send it in.
As of now I have 7.00.35.04S
I assume that the phone is still rooted even though it is back on the stock rom, will that be a problem if I send it back to HTC?

Leoster121 said:
Also, a side note.
In the off chance that I have to deal with HTC for my problem, what is the radio of the stock T-Mobile rom?
Just to make sure my phone is "stock" as ever before I send it in.
As of now I have 7.00.35.04S
I assume that the phone is still rooted even though it is back on the stock rom, will that be a problem if I send it back to HTC?
Click to expand...
Click to collapse
You could try to get a hold of the guy who sold you it. If he calls T-mobile customer care and puts you as a "authorized user" of the phone you can get it replaced.
However, make sure you are on the latest OTA. Check out this http://forum.xda-developers.com/showthread.php?t=946435 and scroll down to my post for another non over the air update method.
-Current stock ( ota ) radio is 7.09.35.10
- Make sure you don't have superuser. If you replaced your rom with the stock build ( like in the method linked ) you should be fine.

He's currently in Taiwan "for a few months", so I doubt he can help me from there.

Also, I'm pretty sure you have to have proof of purchase when you send it to HTC... So that might be a roadblock as well. Your last option would be to order a new flex cable online and install it yourself. Or you could pay HTC the repair fee to fix it.

MusicMan374 said:
Also, I'm pretty sure you have to have proof of purchase when you send it to HTC... So that might be a roadblock as well. Your last option would be to order a new flex cable online and install it yourself. Or you could pay HTC the repair fee to fix it.
Click to expand...
Click to collapse
Thats why the "owner" of the account calls customer care. They already have the record that he purchased the phone. So if he is put as an "authorized user" of the phone he can send it in. Of course the original owner would have to give t-mobile the shipping address and in sense do it. However it only takes maybe 20 mins? Once his refurbished comes in the mail it comes with either a plastic back or box pre-labeled to send the defective product back in.
Along the lines of have the guy call tmobile.
Hi..my cousin is in the states and is having problems with the tmobile slide..I would like to add him as an authorized user so that he may send it in for a refurbished phone...
tmobile will ask for the # and two other pieces of information...password and something else.
imo worth a shot before you have to spend money!

tri4life said:
However, make sure you are on the latest OTA. Check out this http://forum.xda-developers.com/showthread.php?t=946435 and scroll down to my post for another non over the air update method.
-Current stock ( ota ) radio is 7.09.35.10
- Make sure you don't have superuser. If you replaced your rom with the stock build ( like in the method linked ) you should be fine.
Click to expand...
Click to collapse
I've installed the esprimg, but how do I install the extraneous files for radio?

Leoster121 said:
I've installed the esprimg, but how do I install the extraneous files for radio?
Click to expand...
Click to collapse
So right now you are unrooted and installed the 1.27.531.1 stock correct? In order to update to the latest OTA make sure you download the zip provided. Both are the same file, but for some reason the one on the google docs worked for me.
-copy the update.zip file to your sd card.
-Turn off your phone then power into fast boot( volume down and the power button)
-go into recovery once fastboot gives you the option.
-Once in recovery just hit "apply update.zip"
-Wait for it to finish installing then reboot.
Edit:
Original Thread for update.zip
http://forums.t-mobile.com/t5/HTC/Manual-Update-for-Mytouch-Slide-Guide/m-p/439800#U439800
Follow the rules in the original thread. Much more detail than I provided!
Enjoy man.
I checked all the settings and anything else that I could think of with a normal never rooted mytouch. All looks perfect...also sent my mytouch back to tmobile doing this. Have yet to hear from them.

What do i do now that HTC has screwed me over?

Just to give you a brief rundown of everything that's happened..
I'm 17 and saved up for a few months to buy a HTC One X. Needless to say, it's probably the most expensive phone i've ever owned, since all my other phones were hand-me-downs and old phones from eBay.
This morning i wake up and go to work as usual. Just to find my phone's display won't switch on. As you can imagine, I'm tirelessly panicking and try the 3 button combo.. to no avail.
Using Fastboot to reboot didn't work either.
This phone turned into a brick overnight, and i have no idea what happened??
Just before i left for work, i did check my phone and it was working alright.. Then five minutes later, it won't display anything.
The thing is, I can't take it back to HTC either because this is my 5th replacement phone!
First one had black glue smudged on the LCD it's self,
Second one had the screen not glued down and wasn't aligned,
Third one didn't even have any glue applied and the case wasn't even attached properly,
Forth one had this problem where the screen's LCD would dilate if i touched it - even lightly,
and this one is my 5th, the antenna wasn't properly connected and now the screen doesn't work.
I've had terrible luck, and i don't know what i can do?
If you can give me any information to get me out of this, it would be much appreciated.
Although i still can receive text's and calls fine, it's just the display..

Since you’re unlocked and running a non-stock kernel and ROM, maybe some of the dev-ish folks can help you resuscitate it if it’s indeed a s/w problem.
If it’s a h/w problem, what to do depends on where you bought the phone and how old it is. If it’s within the remorse/DOA period maybe you can exchange it. It’ll be hard for whoever you bought it from to see you’ve unlocked it if nothing’s showing on the display.
If it’s outside of the exchange period you’ll have to send it in for repair. If you can’t bring it back to life to flash it back to stock you’ll have to throw yourself on the mercy of HTC Asia in getting it fixed unlocked. HTC's different repair centers seem to all have different policies related to warranty coverage for h/w faults on unlocked phones. If it is a dead display maybe you’ll get lucky.
You might want to put a note in with it telling your “I’m 17” story and how devastated you are something you’ve worked so hard for has failed. Repair techs are people too. Good luck.

BarryH_GEG said:
Since you’re unlocked and running a non-stock kernel and ROM, maybe some of the dev-ish folks can help you resuscitate it if it’s indeed a s/w problem.
If it’s a h/w problem, what to do depends on where you bought the phone and how old it is. If it’s within the remorse/DOA period maybe you can exchange it. It’ll be hard for whoever you bought it from to see you’ve unlocked it if nothing’s showing on the display.
If it’s outside of the exchange period you’ll have to send it in for repair. If you can’t bring it back to life to flash it back to stock you’ll have to throw yourself on the mercy of HTC Asia in getting it fixed unlocked. HTC's different repair centers seem to all have different policies related to warranty coverage for h/w faults on unlocked phones. If it is a dead display maybe you’ll get lucky.
You might want to put a note in with it telling your “I’m 17” story and how devastated you are something you’ve worked so hard for has failed. Repair techs are people too. Good luck.
Click to expand...
Click to collapse
I shook the device out of frustration.. and it started working for a few seconds.
What's going on here? Is it a faulty display/connection? Is there a way to possibly just send it to a nearby phone shop and get it fixed?
Sorry about all the questions, I'm shocked, happy, and devastated all at the same time.

Are HTC refusing then? That seems a bit off/ illegal... Surely under the faulty goods act (I assume the law isn't THAT different in Australia to UK) they have to take it back as it CAN'T be a year old and they can't prove the issue was caused by your mistreatment. It doesn't matter how many phones you've had... Also, where did you buy the phone from? I think you should be able to return it through the shop as THEY sold you the phone, not HTC... They are still under an obligation as they sold you the thing.
Plus, the 'I'm a 17 year old and saved up for ages thing' might work too! I'd try not to get too technical with the law if you go down this route though!
Best of luck sorting this out. It's within your rights to get a replacement (you bought the phone new, I assume?) so I'm sure this will eventually work out. Don't give up! You just need to speak/ write to the right person...
sent from my internet

What rom were you on?
I remember my One X not charging at all while it was turned off completely although it showed Orange charging led.
It could be that you ran out of battery and phone not turning on. Due to no charging effect.

@Op,
Reading your story there's one thing that's crossing my mind.
Could it be possible the battery run dry during the night?
It sounds stupid but those things you forget easy when you're in a hurry or stressed.
I don't read anything in your post you tried to charge.
Atrixx said:
Just to give you a brief rundown of everything that's happened..
I'm 17 and saved up for a few months to buy a HTC One X. Needless to say, it's probably the most expensive phone i've ever owned, since all my other phones were hand-me-downs and old phones from eBay.
This morning i wake up and go to work as usual. Just to find my phone's display won't switch on. As you can imagine, I'm tirelessly panicking and try the 3 button combo.. to no avail.
Using Fastboot to reboot didn't work either.
This phone turned into a brick overnight, and i have no idea what happened??
Just before i left for work, i did check my phone and it was working alright.. Then five minutes later, it won't display anything.
The thing is, I can't take it back to HTC either because this is my 5th replacement phone!
First one had black glue smudged on the LCD it's self,
Second one had the screen not glued down and wasn't aligned,
Third one didn't even have any glue applied and the case wasn't even attached properly,
Forth one had this problem where the screen's LCD would dilate if i touched it - even lightly,
and this one is my 5th, the antenna wasn't properly connected and now the screen doesn't work.
I've had terrible luck, and i don't know what i can do?
If you can give me any information to get me out of this, it would be much appreciated.
Although i still can receive text's and calls fine, it's just the display..
Click to expand...
Click to collapse

privatetrousers said:
Are HTC refusing then?
Click to expand...
Click to collapse
Yes. But not in every region (yet). Do a search. It's been disucssed. Also, it appears Samsung's going down the same path.
http://forum.xda-developers.com/showthread.php?t=1745834

BarryH_GEG said:
Yes. But not in every region (yet). Do a search. It's been disucssed. Also, it appears Samsung's going down the same path.
http://forum.xda-developers.com/showthread.php?t=1745834
Click to expand...
Click to collapse
Aware of the discussion... Using the xda app and didn't pick up that the phone's been 'HTCdev'd (my fault for not reading properly - sorry, folks!). Still not sure HTC/ Samsung can legally 'sign your rights away' though. Still, not a discussion for here...
Hope you got the phone sorted anyway.
sent from my internet

Atrixx said:
I shook the device out of frustration.. and it started working for a few seconds.
What's going on here? Is it a faulty display/connection? Is there a way to possibly just send it to a nearby phone shop and get it fixed?
Sorry about all the questions, I'm shocked, happy, and devastated all at the same time.
Click to expand...
Click to collapse
How or who fixed ur antenna problem, could be related if handset wasnt but back together properly.

Mysterious i9190

Hello everyone! This is my first thread and I know it's the right site to ask this. (sorry for my english)
I bought this "suspicious" i9190 in Budapest 2 years ago. Since then it has been impossible to use it regulary.
Constant rebooting and freezes are part of its daily routine. As well as stopped apps and processes messages in a ridiculous way.
I have tried millions of ROMs, officials and customs, all kind of wipes and restores. I have even tried the eMMC brickbug apps looking for damaged chips or internal memory: Nothing, the phone is perfectly fine.
But here are some facts that may be relevant to find the problem:
- The phone came with the IMEI number scrached in the back of the battery.
- I've been using the phone for hours and hours perfectly fine as long as no update is performed and the Sync option is off.
- Doing the above I have even downloaded and used some little apps with no problems.
- When the major apps are installed, like Facebook and Instagram the phone begins to die, popping more and more "stoppped working" errors.
- The processes that fail the most are the google type but, in general, every single existing process has failed in this 2 years.
- I have noticed that when you start the phone for the first time after a wipe or a new ROM, it is better to create a new google account than using an existing one because the existing one, I think, will start updating everything while the new one will not. Anyway, using a new google account collapses the phone sooner or later.
Sorry for the long post, fellas. But I wanted to give you all the possible info I have about this phone.
Hoping for you can help me fix this issue... Have a good day.
Galaxy S4 mini GT-I9190

I'd guess at a hardware issue in the radio and related circuitry as you seem to get the issues when apps that send/receive data frequently are in use. Though it could be anything. You probably need to get it checked by an authorised Samsung repair centre ......... if your phone is not too "suspicious!"

IronRoo said:
I'd guess at a hardware issue in the radio and related circuitry as you seem to get the issues when apps that send/receive data frequently are in use. Though it could be anything. You probably need to get it checked by an authorised Samsung repair centre ......... if your phone is not too "suspicious!"
Click to expand...
Click to collapse
Thanks for your reply! Do you have an idea why they scratched the IMEI number? Maybe that could take me to where the exact problem is. Here is a photo of the back
http :// imgur. com/Sa0ptSm
Sorry for the link, my account still cannot post outside links

I was going to say they scratched the IMEI number probably because it was stolen so that it could not be tracked, but it is quite easy to see the number so that is probably not the reason. One place I used to work at the test department used to scratch the bar codes on faulty PCB's so that they cannot be scanned back into the system by mistake (if the fault tag comes off, etc) as that computer system did not prevent scrapped boards from being re-entered. So I would guess this may be the case with your phone, but of course we can't know for certain! But based on this and all tests of different ROMs etc you did I suspect it is quite likely the explanation.
What I would do is look for the same model that has a cracked screen on ebay etc so it's cheap to buy then swap the PCB's from the cracked phone to your good screen (swap everything to prevent the possibility of the boards not working due to different revision numbers, as has been reported when replacing the power boards on our phone). You can also buy a repair kit for a few dollars on ebay with screwdrivers, pry tool etc
http://www.ebay.com/itm/10-In1-Repa...et-for-Mobile-Phone-iPhone-6-5s-/281869038536
If the PCB on your phone was scratched to show it was faulty then taking to a repair shop is probably a waste of money, unless then run an assessment for free before they repair it.
Hope you can fix it for a few dollars!

not sure if this helps but that I actually managed read off the IMEI code correctly and it turns out its a turkish registered phone, I can PM you IMEI code if you want, also its not reported stolen (but i am guessing its most likely is), anyways thats all I was here to say, good luck.

Severe brightness issue (screen largely unusable)

Hi all, I have a problem with my stock T-Mobile US S9. A few months ago this weird thing happened where if I turned on my screen immediately after it turned itself off, only the top few lines would be visible. The whole screen would take input, but you could only see a little below the status bar, maybe. If I waited a bit and then turned the screen on, it would work normally, with the whole screen visible and looking fine.
It's gotten progressively worse to the point where this happens most of the time I turn the screen on. However, I've found two workarounds:
1) My Always On Display is set to turn on when I tap the phone. If I do that, the AOD works as normal, and if I then turn on the phone screen the phone screen works fine. This only works when Always on display is set to turn on on tap. It does not work if AOD is set to always be on.
2) If, when my screen is glitching out I hold the screen up to a reeaally bright light (like inches from a lightbulb), the rest of the screen turns on. It's weirdly green tinted and kind of stuttery.
Turning off automatic brightness does not fix this issue. If tried booting in safe mode and even factory resetting the phone. Issue still persists, including on screens like when the phone enters recovery mode.
The fact that I can get the screen working normally using workaround #1 makes me think this is a software issue, but the fact that it happens on the recovery screen makes me think it's pretty low-level. Any ideas? Anyone else had a similar issue?

I gave Samsung tech support a call and the level 1 tech I spoke with seemed to think that it was a software issue and that I should bring it in to be looked at by a technician. I'm in Maine at the moment and there's no Samsung or UBreakIFix stores within two hours, so she suggested taking it to Best Buy to look at. Not amazingly helpful or surprising.
If it's a software issue though... I mean this is my fourth Android phone and I've rooted and flashed ROMs on all the previous phones anyway. I don't want to lose Samsung Pay, so I'd rather not unlock the bootloader, but is there a way to flash the stock operating system or something? The exact model number is SM-G960U

It's a firmware or hardware issue not software as a reload* would have fixed it.
The firmware has been corrupted (needs reflashed) or there's been a hardware failure.
Best to send it in for repair or take it the a Samsung Experience Center as they can reflash the stock rom and have advanced diagnostic tools.
*make sure all system apks are running on factory load and have not been updated after the reload.
Updates, destroyers of worlds...

blackhawk said:
It's a firmware or hardware issue not software as a reload* would have fixed it.
The firmware has been corrupted (needs reflashed) or there's been a hardware failure.
Best to send it in for repair or take it the a Samsung Experience Center as they can reflash the stock rom and have advanced diagnostic tools.
Click to expand...
Click to collapse
If that’s really necessary I’ll do it. But the closest place is out of state and when I called them said it would take 4 hours just to do a diagnostic. That plus the round trip... if there’s a way I can save some time, I’d like to.
For example, if one possibility is a stock firmware reflash, that’s something I’ve never done before on a Samsung device, but not very different from things I feel comfortable doing. I've flashed roms and rooted many android devices in the past. From a preliminary search , it looks like there's even a leaked tool online to do so from Samsung called Odin and that I just need to find the latest SM-G960U image with the right "csc" code for my carrier (I think TMB for T Mobile US). What would be even better is if one of those diagnostic tools you mentioned leaked the same way that Odin did.
Any recommendations on either diagnostic software or firmware reflashing? Or would you strongly advise leaving that kind of thing alone? I would like to still use things like Samsung Pay at the end of all this.

jptiger said:
If that’s really necessary I’ll do it. But the closest place is out of state and when I called them said it would take 4 hours just to do a diagnostic. That plus the round trip... if there’s a way I can save some time, I’d like to.
For example, if one possibility is a stock firmware reflash, that’s something I’ve never done before on a Samsung device, but not very different from things I feel comfortable doing. I've flashed roms and rooted many android devices in the past. From a preliminary search , it looks like there's even a leaked tool online to do so from Samsung called Odin and that I just need to find the latest SM-G960U image with the right "csc" code for my carrier (I think TMB for T Mobile US). What would be even better is if one of those diagnostic tools you mentioned leaked the same way that Odin did.
Any recommendations on either diagnostic software or firmware reflashing? Or would you strongly advise leaving that kind of thing alone? I would like to still use things like Samsung Pay at the end of all this.
Click to expand...
Click to collapse
If it's under warranty let Samsung deal with it. A good tech with experience is invaluable.
Rather then waste time the extra ride might end up being the easiest solution. You could also next or 2nd day it to the center and back, make sure it's insured and packaged well.

blackhawk said:
If it's under warranty let Samsung deal with it. A good tech with experience is invaluable.
Rather then waste time the extra ride might end up being the easiest solution. You could also next or 2nd day it to the center and back, make sure it's insured and packaged well.
Click to expand...
Click to collapse
That makes complete sense for something under warranty, but unfortunately my phone isn't. The S9 is about three years old now, and the Samsung rep was quick to tell me that the device was no longer covered. It looks like a mail-in repair service would cost about $175, which I'm theoretically willing to pay, but not if I can just handle on my own for free.

jptiger said:
That makes complete sense for something under warranty, but unfortunately my phone isn't. The S9 is about three years old now, and the Samsung rep was quick to tell me that the device was no longer covered. It looks like a mail-in repair service would cost about $175, which I'm theoretically willing to pay, but not if I can just handle on my own for free.
Click to expand...
Click to collapse
In that case you have nothing to lose by reflashing it. Hopefully that gets it.
Otherwise it be hardware... probably a good chance this actually the cause.
The good news is the 9's are available for a couple hundred in good condition if need be.
I was considering getting the 9 as a second phone (have the 10+) as the 10+'s haven't come down much in price.
Samsung current lineup sucks.

Huh. Well, before reflashing, I tried something I found other people suggesting for a related problem: https://eu.community.samsung.com/t5...t-bars-black-screen-issue/td-p/1745470/page/7
It's an app called OLED Saver. It's not perfect, the screen still has an odd green tint to it unless I use one of the tricks I was describing above. But I no longer have the issue where most of the screen isn't visible.
I might try reflashing anyway, will post results if I do.

Yeah, no joy. Reflashed by downloading the latest firmware using Frija for SM-G960U with TMB as the CSC, and flashed using Odin v3.13.3. If anything the problem is slightly worse now, but OLED Saver still mostly seems to fix it. I guess it's just a hardware issue with a weird software workaround...

Same type of brightness problem here as you describe, on my new S9 (G960U) - - Model starqltesq - CSS XAA
The product is under guarantee, but as it is imported from Hongkong to France, I don't have accesss to the Samsung local representatives and have probably to send it back to Hongkong ...
I will keep you updated if I learn something about the problem and the solution ....

Wiping the cache partition stopped this happening for me for around 24 hours but it came back this morning. On the Note9 forums someone posted that setting animations to .5 in dev options fixes this. I will try it.

Bhonka said:
Wiping the cache partition stopped this happening for me for around 24 hours but it came back this morning. On the Note9 forums someone posted that setting animations to .5 in dev options fixes this. I will try it.
Click to expand...
Click to collapse
Disable animations instead. It wastes resources. Personally I like seeing a fast, snappy OS do it's thing with no middle man needed. Lol, you end up waiting for the animations rather than the OS.

I've heard of people flashing custom roms and that resolved the issue permenetly, but can't find anyone willing to give some real feedback. I posted a topic asking this question, but haven't gotten any replies..

Not very helpful, but a work around could be to use Screen Filter

I temporary fixing my S9+ green screen issue by uninstalling the NFC module.
Unfortunately, this option make us cant charging the phone.
Maybe some one expert in hardware mod can do better.

Eve&Me said:
I temporary fixing my S9+ green screen issue by uninstalling the NFC module.
Unfortunately, this option make us cant charging the phone.
Maybe some one expert in hardware mod can do better.
Click to expand...
Click to collapse
Hey could you explain what exactly did you uninstall and how?
After uninstalling it wireless charing stopped working or what did you mean by cant charge the phone?
Did it fully resolve the green screen issue?

Some people noticed that problem after upgrade Android 9 to 10.
At this moment we have some facts:
1) OLED saver temporary solves problem
2) disconnect NFC module solves problem, some people on xda and on the yt confirm that
3) heating back cover using heat gun can help - I Discovered that some weeks ago
Interesting comment from the yt:
Sour Words
Sorry to say this, but green screen issue is a hardware fault not something an update can fix. One of the updates from Samsung is causing the CPU to over heat and in return permanently damaging the oled screen. Not only that but also compromising the battery as well. The only fix is the replacement of both the oled screen and battery. This repair is entirely the fault of Samsung due to a faulty update that over works the CPU capacity. Therefore my advice is for you to return your device back to Samsung and lodge an assessment request. They charge a small fee for the assessment, but the entire repair should be compensated by Samsung. Be firm and keep the pressure via emailing them to insist on Samsung covering the repair costs. My Note 9 is almost 3 years old when green screen issue happened. They fixed the entire thing free of charge. But I kept firm and didn't let them bully me into charging me for the repairs, which was their fault in the first place. I must admit, my phone despite its age, is in perfect condition. Not a scratch on it. Which I know contributed winning my argument for the repairs. So if you have psychical damage, I doubt you will have a chance. Good luck to all who will give this successful method a go.
Click to expand...
Click to collapse

mreminemfan4ewver said:
Hey could you explain what exactly did you uninstall and how?
After uninstalling it wireless charing stopped working or what did you mean by cant charge the phone?
Did it fully resolve the green screen issue?
Click to expand...
Click to collapse
When we disassembly NFC Module, the phone will give LOW TEMPERATURE warning. And make us cant charge the phone

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