Database Info

Questions

So I got my XT720 a few days ago and am loving it. Two things though:
1) I've had to do a quick reset (take out battery) about 4-5 times in the same amount of days. What happens is sometimes the screen will go blank (or when I press the on button all that will happen is the 4 buttons at bottom of phone will light up). Screen/phone becomes unresponsive and only way to get back to normal is to take out battery. I'm pretty sure that every time this has happened has been right (or shortly) after me downloading something on my phone (i.e. putting on a new wallpaper, or a song). Anyone have this happen to them?
2) I don't want to root or put on Dexter's ROM just yet. The reason for this is because a) I just got my phone and I don't want to void the warranty until I know everything works with no issues b) I'd rather wait for the complete/fully polished version of the ROM - I'm in no hurry right now, this phone is a big big upgrade from my previous phone even without 2.2.
Anyways, the point is, I'm pretty sure my phone isn't running with the 720MHz update right now and is running at 550. I want to put on that update to make my phone faster while I wait to root. However, whenever I go to - about phone - check for system updates - and click on that, it always tells me "Server unavailable. Try again later.". Been trying for the past few days and no luck. How can I get the 720MHz update (without rooting - at this point)?
Thanks

If the screen doesn't come on when you turn on the phone, you may have a defective one. My first XT720 was a dud right out of the box. I had to take it back to the Cincinnati Bell store and get it exchanged. I've heard of other people having similar experiences with the phone not turning on. Take it back. If they give you any crap about it, just tell them that the Motorola tech from their forums told you to take it back. This adds a bit of validity to the problem and may make it an easier transaction.

Nah, it works fine for the most part. Turns on and off and runs just fine normally. But my issue is I've just had it basically freeze up 4-5 times in the past week (noticing a possible connection to me downloading things).

I would think your phone is running at 720mhz. I believe the European / Asian versions were originally 550mhz & had an ota udate to the 720 level. You could download Android System Info or Elixer to check it out though.
I would also agree with reverendkjr, it the phone is acting funky take it back & get a replacement.

The XT720 from Wind is 720mhz with stock firmware, the only 550mhz was Korean version AFAIK, maybe some Euro versions.
As for the screen, you may want to try doing a factory reset on your phone. If it persists after that take it back to Wind for a replacement, had my wife's XT720 replaced due to a microphone problem.

R-D said:
The XT720 from Wind is 720mhz with stock firmware, the only 550mhz was Korean version AFAIK, maybe some Euro versions.
Click to expand...
Click to collapse
Oh? I figured it might be at 550 since going back to homescreen - it reloads pretty often (thought 720 wouldn't do that), though it does run snappy enough in all other areas.
As for the screen, you may want to try doing a factory reset on your phone. If it persists after that take it back to Wind for a replacement, had my wife's XT720 replaced due to a microphone problem.
Click to expand...
Click to collapse
Be a bit of a pain to factory reset at this point. The problem isn't terribly disruptive at this point. Doesn't happen often enough to really bother me and restarting is quick. If it does continue and become frustrating I may consider factory reset. I just was wondering if anyone else experienced this.
WIND would give me a replacement at any time (within the year) if I told them about this issue? (Kind of hard to prove since it happens at it's own whim. Don't want to seek a replacement just yet anyways - not unless it continues and is an annoyance)

Just put a call into support so they have a record of the problems, explain to them you cant reproduce the problem, but it is a brand new phone and should not be doing this regardless.
They will suggest the reset to see if the issue persists, but you can decline at this time and at least get the issue logged so you have a better chance of replacement in the future.
Keep in mind though, within 14 days they will replace with a new phone, beyond that you may get a used one.

I can't imagine just ignoring a problem with a new phone like that. Especially since you have the ability to have it replaced for free.
Heck, I took a phone back once because it had ONE dead pixel on the screen. When the girl looked at me and said "Really?" I said "Hell yes, I just bought this damn thing and I want it to be PERFECT!"

you need to setup the APN to connect to 3G to get your 720 upgrade from OTA (if purchased unlocked Euro or Asia models)
if it's a Wind XT720 it should already be on 720

reverendkjr said:
I can't imagine just ignoring a problem with a new phone like that. Especially since you have the ability to have it replaced for free.
Heck, I took a phone back once because it had ONE dead pixel on the screen. When the girl looked at me and said "Really?" I said "Hell yes, I just bought this damn thing and I want it to be PERFECT!"
Click to expand...
Click to collapse
Yeah, I suppose that's true. If it happens again I'll look into getting it replaced.
Thanks for the help guys.

my XT711 has done the "blank screen a few times also and I have to remove the battery to reset it. Very strange thing, but I have had the phone for only a few days so im gonna see what its gonna do first cause sending it back to china is a pain in th butt.

[Q] Frustrating One S sensors locked?

Greetings all. I'm not convinced my problem is specifically related to the One S, and I certainly haven't got anywhere near rooting yet, but you Guys are expert at nosing round in the bowels of this phone & the OS, and I'm getting totally flummoxed as to where I've gone wrong.
I've owned this phone since June and it was originally locked to O2, was unlocked and used on Giffgaff, an O2 offshoot - probably irrelevant. One of the apps I particularly wanted to use was Google Sky Map, duly installed and run successfully for a day or so. Other apps installed, as one does, but when I came back to Sky Map, the app was frozen, as were seemingly all compass function apps.
Various uninstalls & reinstalls later, a system reset and a factory reset and this function still was inactive. Returned to HTC for fixing. No better - all worked OK for a short while then stopped. Returned again and this time internals were swapped ,but now the microphone wouldn't work. Third return and an unlocked sim-free handset was returned.
As soon as I loaded my profile from Google, initially it worked, but later most of the sensors again seemed to fail. I've tried the full factory reboot then logged in with a totally new Gmail account, but no change. Phone Tester app shows only readings from proximity and light sensors - no gyroscope,compass, mag. field or accelerometer. Accelerometer did show one set of readings this morning, but nothing since. Lookout AV has always been installed. Incidentally, almost exactly the same profile worked perfectly well on my previous phone, a Wildfire S.
Should I shoot myself or the phone? I admit I'm not any sort of phone expert, but I don't think I'm that dense as to so consistently screw this thing up.
Any ideas people please, in (moderately) simple terminology?

Ok maybe you could shoot google, maybe its a fault by them.
If I helped in anyway please hit thanks

Thank you for the oh-so-helpful response.
Just in case one of the myriad readers of this thread should have just a quiver of interest ................. I believe I've found the answer.
It's always been difficult to pinpoint the problem, and certainly HTC haven't twigged what's happening, as before I sent the phone back to them I TOOK THE FLIP CASE OFF!
That's why it would work for a short while after return, until I replaced the case. I can only guess there's something like Carbon Black in the plastic back shell, and that's what's been interfering with the sensors.
It may also be relevant to the big Home Button problem, with the screen flipping between Home & Helicopter views. Has anyone investigated whether there could be sufficient signal degradation to trigger this problem caused by the use of a case?
Sweetness and light to all.

I spoke to an HTC rep, and he said they would not give an unbranded handset back. If that's the case, I want my phone unbranded. I'll take it to them and hopefully get an unbranded one.

Well good for your HTC rep. They can't go giving out unbranded sets like that. What is the World coming to?
Notwithstanding - the previous clutter of O2 apps was pleasantly noticeable by its absence as was the O2 splash screen.
What a lucky little customer I am and it's only taken 4 months to sort out.

[Q] Screen flickering/shifting/cycling up

For 6 months, my Nexus 5 have been the best thing that happened to my life. But after the 4.4.3 update around Jun13, this display issue appears. Display keeps shifting upward in a continuous manner. For example, the keyboard is now in the middle, and the top part is below, it keeps flickering and moving. So I thought it may be a software bug since it coincided with the update (and no, I did not drop it). I tried all (factory reset, turn auto settings off, Developer options settings) to no avail. I contacted Google support and after a few emails, they told me to contact Japan support team. I don't know anyone from Japan. (Actually I do, but when he called them, the Google person couldn't speak English and my friend can't speak sufficient Japanese). (Note: A friend of another friend bought this phone from Google Store Japan)
So I thought, wth, let's open the back, maybe there're loose connections, like the battery or something. But now the adhesive is tampered with, a small dent in the case (due to the very strong adhesive) and the back does not pop completely back. One corner is a bit loose, so there's no fooling them that I have opened it.
I updated to 4.4.4 and new issue, the display is gone, just backlight. I managed to fix this eventually. Now I'm back to 4.4.2, and the display is still shifting. During bootup, Google logo is stable, but the next animation is shifting. Bootloader is stable, but sometimes it moves up a grid after I press a button. So I assume that the display moves when the system processes something.
So my conclusion now is that this is probably hardware/GPU issue. Or is it? My warranty is as good as void already since I can't communicate with Japanese, and since I opened the back, it really is void already. I have 2 immediate plans of attack: 1) flash a custom rom, if software issue; 2) buy a triwing screwdriver to check the back, if loose hardware.
Any thoughts?

You have answered your questions already m8.. If I were you, I would find someone who can speak Japanese and tell them to contact Google support and act as a interpreter.. I'm sure you will find someone in your workplace.
Since you've opened up the back and damaged the device to a point where it doesn't pop back, the warranty is gone most probably. But I would still contact Google first and then go-ahead with tampering the hardware.
- Sent from an IceCold Hammerhead!

tsuwariwarirap said:
For 6 months, my Nexus 5 have been the best thing that happened to my life. But after the 4.4.3 update around Jun13, this display issue appears. Display keeps shifting upward in a continuous manner. For example, the keyboard is now in the middle, and the top part is below, it keeps flickering and moving. So I thought it may be a software bug since it coincided with the update (and no, I did not drop it). I tried all (factory reset, turn auto settings off, Developer options settings) to no avail. I contacted Google support and after a few emails, they told me to contact Japan support team. I don't know anyone from Japan. (Actually I do, but when he called them, the Google person couldn't speak English and my friend can't speak sufficient Japanese). (Note: A friend of another friend bought this phone from Google Store Japan)
So I thought, wth, let's open the back, maybe there're loose connections, like the battery or something. But now the adhesive is tampered with, a small dent in the case (due to the very strong adhesive) and the back does not pop completely back. One corner is a bit loose, so there's no fooling them that I have opened it.
I updated to 4.4.4 and new issue, the display is gone, just backlight. I managed to fix this eventually. Now I'm back to 4.4.2, and the display is still shifting. During bootup, Google logo is stable, but the next animation is shifting. Bootloader is stable, but sometimes it moves up a grid after I press a button. So I assume that the display moves when the system processes something.
So my conclusion now is that this is probably hardware/GPU issue. Or is it? My warranty is as good as void already since I can't communicate with Japanese, and since I opened the back, it really is void already. I have 2 immediate plans of attack: 1) flash a custom rom, if software issue; 2) buy a triwing screwdriver to check the back, if loose hardware.
Any thoughts?
Click to expand...
Click to collapse
It is incredible, i have exactly the same problem and i did the same as tsuwariwarirap did. So if it is the same issue could be a kind of software problem? Or maybe all the nexus5 hardware will have issues with 4.4.3 or 4.4.4 ?

shevaperu said:
It is incredible, i have exactly the same problem and i did the same as tsuwariwarirap did. So if it is the same issue could be a kind of software problem? Or maybe all the nexus5 hardware will have issues with 4.4.3 or 4.4.4 ?
Click to expand...
Click to collapse
It's a hardware issue. A software update can't cause the flex cable or the display to go bad like that. If you have flashed back to fully stock and still have these issues, your only option is to replace the damaged parts.

Hi, do you mean this kind of issue
How did you solve this?!

[Q] "Retroactive Bricking" or "spontaneous" hardware fault?

PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.

*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!

Question Screen weirdness on me the other day.

My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .

Anyone ?

Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.

jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.

EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?

Hmmm

jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.

Hardware hmm and not software?

Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.

Roblox with my nephew

Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements

Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea

I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?

Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.

V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev

Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!