Related
I don't know if this has been asked about, sorry if it has, couldn't find it via searching.
Randomly while using the Fuze, and sometimes not for weeks at a time, my screen will fade to black. It won't shut off, the image will just fade to solid black, but the screen itself will remain on. Sometimes if I remove the battery and turn the phone on over and over again, the picture will return. The screen always turns on as you can see the backlight, but there is no image. Is this a hardware or software problem? Is this likely something covered under the AT&T warranty? or would I need to file an insurance claim and pay the 120$ish deductible?
I have tried hard/soft resetting, trying to enter bootloader, etc. and I can't get an image. I'm assuming this is a hard ware or graphics driver issue (if software).... does anyone have any info on this at all or a link/search string they might recommend? Thank you in advance.
I know no one has replied to this thread in a while and don't know if you still need help but try turning your screen off....where the phone is on but the screen is black and the back light is off (I know the screen is black but you should be able to see if the back light is on or not. Now try, not too hard though, to squeeze the phone screen and pad a bit. This works on my phone...sometimes. Then hit the power button to turn the screen back on and see if you can see your menu. I think the Fuze has a short...maybe from keeping it in your pocket or someplace where it is compressed. Hope that helps.
Hardware fault - send it back for repair!
In bootloader only the bootloader is running - so no software to cause a problem ∴ must be hardware.
So today my phone fell into some garbage. I dont think there was any water, but after doing some googling, it seems that is one of the causes. After i pulled the battery out, the little circle is pure white but i do see a very little spot of red. Can anyone give me any tips? If its ruined, can i easily replace it? I just got this from ausurion a few months back. I dont really want to have to shed out another 200 for another phone. I put it in rice for the time being just in case.
I can turn it on, and it vibrates normally, and it vibrates when things happen. The bottom icon lights also turn on. So, just imagine your phone working, you just cant see anything.
EDIT: Also, i cant get into fastboot, recovery, etc because it is only blank. Should i be looking into a new screen?
If there's water damage, it might be a lost cause, but if it's not, replacing the screen would be a much cheaper option than shelling out $200.
It isn't anything to do with water my phone did the same thing. You damaged the wires going to the screen. Touch still works right. Do you have insurence?
Zinsko said:
It isn't anything to do with water my phone did the same thing. You damaged the wires going to the screen. Touch still works right. Do you have insurence?
Click to expand...
Click to collapse
There are many different causes of problems. You can't be positive that it isn't a certain cause.
My Nexus 5 is 6 months old, it hasn't fallen hard, doesn't have a scratch on it, but today the auto-rotate feature was not working. I didn't gave it much thought, but next time I picked up my phone, the whole screen was upside down (see picture attached) and had huge lines all over it, making it very hard to figure out or read anything, and the place were all the buttons should have been were OK, instead of following the change-upside down, so to write a 'A', I have to press 'L' and so on, for everything. Basically impossible to do.
I did a hard reboot to factory settings, and even on the recovery screen everything was upside down, and nothing changed after it.
I have been searching for people with the same issue and I found nearly none or no answers to that thread.
Has anyone experienced the same issue, and what was it in the end?
My phone is under warranty from LG still, but Im afraid if I send it for repair, they will just say is a broken screen, therefore making me pay for it (around 150). If anyone thinks otherwise please say so.
I have found the same issue for other phones (older) and some people say is a broken or faulty Flex Cable. Can this be possible? (I could repair that myself)
Any thoughts on this?
Thanks!
valentinitag said:
My Nexus 5 is 6 months old, it hasn't fallen hard, doesn't have a scratch on it, but today the auto-rotate feature was not working. I didn't gave it much thought, but next time I picked up my phone, the whole screen was upside down (see picture attached) and had huge lines all over it, making it very hard to figure out or read anything, and the place were all the buttons should have been were OK, instead of following the change-upside down, so to write a 'A', I have to press 'L' and so on, for everything. Basically impossible to do.
I did a hard reboot to factory settings, and even on the recovery screen everything was upside down, and nothing changed after it.
I have been searching for people with the same issue and I found nearly none or no answers to that thread.
Has anyone experienced the same issue, and what was it in the end?
My phone is under warranty from LG still, but Im afraid if I send it for repair, they will just say is a broken screen, therefore making me pay for it (around 150). If anyone thinks otherwise please say so.
I have found the same issue for other phones (older) and some people say is a broken or faulty Flex Cable. Can this be possible? (I could repair that myself)
Any thoughts on this?
Thanks!
Click to expand...
Click to collapse
If you have warranty take it to LG.
It will be an expensive way to find out what is fauilty, the motherboard or the screen.
Hey y'all, so I'm not sure how well hardware related questions go down on here usually, but not sure where else to ask. So I have about 2.5 Samsung Galaxy s6's. All were given to me at different stages slash periods of time and none of them exactly work fully. Where I am at now is sort of realizing that either: 1. I have to faulty digitizers, or 2. the one battery I have between them is completely shots, or 3. a combination of one and two as well as some other s*** going on.
So what I have for parts AR, two motherboards two digitizers, three bodies, and one battery. I get kind of the same issue switching between the motherboards which is this: I will plug the phones in to my computer and it will read them and say something like SM and then the numbers that represent the s6, and I'll have a either red l LED for a while which will then turn green after a while charging, or a blue LED from the get-go which I believe just stays blue the entire time. Now, the weird thing is that neither of the phones will turn on, however, whenever I push the home button with either digitizer or either motherboard, it will cause the LED to turn off, but will not cause the phone to stop being recognized by the computer. When I say recognized by the computer I don't mean it shows up in the my PC folder, like where I can access the files and such, it just shows up in the device manager, thus giving me the impression that it never actually turns on. This also happens if I end a press up on the volume at any point in time. Also worth noting whenever I unplug it from the computer or just from the charger, the phone will power off completely as in not be recognized by the computer. So, any ideas? I'm thinking of just selling the phones as is maybe for a 150 total for everything but I'd like to fix that myself if it's just something as small as a battery issue. the volume up button and the home button turn the phones off though, is what really perplexes me. Thanks for any insight, much appreciated for the read and have a good Thanksgiving.
DeepPuddles666 said:
Hey y'all, so I'm not sure how well hardware related questions go down on here usually, but not sure where else to ask. So I have about 2.5 Samsung Galaxy s6's. All were given to me at different stages slash periods of time and none of them exactly work fully. Where I am at now is sort of realizing that either: 1. I have to faulty digitizers, or 2. the one battery I have between them is completely shots, or 3. a combination of one and two as well as some other s*** going on.
So what I have for parts AR, two motherboards two digitizers, three bodies, and one battery. I get kind of the same issue switching between the motherboards which is this: I will plug the phones in to my computer and it will read them and say something like SM and then the numbers that represent the s6, and I'll have a either red l LED for a while which will then turn green after a while charging, or a blue LED from the get-go which I believe just stays blue the entire time. Now, the weird thing is that neither of the phones will turn on, however, whenever I push the home button with either digitizer or either motherboard, it will cause the LED to turn off, but will not cause the phone to stop being recognized by the computer. When I say recognized by the computer I don't mean it shows up in the my PC folder, like where I can access the files and such, it just shows up in the device manager, thus giving me the impression that it never actually turns on. This also happens if I end a press up on the volume at any point in time. Also worth noting whenever I unplug it from the computer or just from the charger, the phone will power off completely as in not be recognized by the computer. So, any ideas? I'm thinking of just selling the phones as is maybe for a 150 total for everything but I'd like to fix that myself if it's just something as small as a battery issue. the volume up button and the home button turn the phones off though, is what really perplexes me. Thanks for any insight, much appreciated for the read and have a good Thanksgiving.
Click to expand...
Click to collapse
dang man, id just sell em unless you want a winter project. I just bought a Sunfire sub that has some issues for a winter project, but thats because im a dork and i like that kind of stuff. Anyways, my opinion is just to sell it and get something else that works. I had a buddy offer me a HUGE pile of phones and their respective parts to fix them for like $200 and i gave a hard no.
Damn never heard of such an issue? I'd had hoped that the volume up key as well as the home button both restarting (or, turning the LED off for about ten seconds at least) would have been some kind of dead giveaway, if not just a straight up common occurrence, haha. I even got ANOTHER S6 last night from a homie (asked her if I could borrow the battery lol, she just gives me the whole broken phone) to try and switch out parts, which I'm gonna give a quick shot at tonight at least. But man, no responses other than hours has me quite discouraged :') lol thanks for the time to read at least tho my dude ?
Sometimes, I go to turn on the phone, and the screen will stay black, or, more frequently than the former, I am using the phone and the screen goes blank out of the blue. Sometimes when this happen, I see white-greenish flickering on the top of the screen, as if it was trying to stay on but it couldn't, we're talking about short lived, dim flashes of horizontal bands on the very top of the screen that die off after a short while.
After that, I usually have to "knock" violently on the screen, like you would knock on a door, and it comes back up. If I'm lucky it happens right away, otherwise there's quite some spanking involved until I see an image.
I have to suppose the warranty has ended (the invoice the previous owner gave me with the phone, which he says has been given to him by the previous-previous owner, is clearly a fake one, pointing to a nonn existing seller, still I got the whole package with the box and accessories so the source is legit -"legit"- albeit unknown to me).
Does any of you have experience of this? I mean, I know it's going to get worse and at some point it will get so bad that I will need to buy another phone since I use it for work, and even if it seldom happens when I'm fiddling with the calendar in front of a client, punching the screen to get it back working wouldn't be acceptable in a professional scenario... anywho, suggestions, tips, tricks, whatever? Which doesn't involve having it professionally repaired out of warranty since I suppose it wouldn't make sense economically.
ephestione said:
Sometimes, I go to turn on the phone, and the screen will stay black, or, more frequently than the former, I am using the phone and the screen goes blank out of the blue. Sometimes when this happen, I see white-greenish flickering on the top of the screen, as if it was trying to stay on but it couldn't, we're talking about short lived, dim flashes of horizontal bands on the very top of the screen that die off after a short while.
After that, I usually have to "knock" violently on the screen, like you would knock on a door, and it comes back up. If I'm lucky it happens right away, otherwise there's quite some spanking involved until I see an image.
I have to suppose the warranty has ended (the invoice the previous owner gave me with the phone, which he says has been given to him by the previous-previous owner, is clearly a fake one, pointing to a nonn existing seller, still I got the whole package with the box and accessories so the source is legit -"legit"- albeit unknown to me).
Does any of you have experience of this? I mean, I know it's going to get worse and at some point it will get so bad that I will need to buy another phone since I use it for work, and even if it seldom happens when I'm fiddling with the calendar in front of a client, punching the screen to get it back working wouldn't be acceptable in a professional scenario... anywho, suggestions, tips, tricks, whatever? Which doesn't involve having it professionally repaired out of warranty since I suppose it wouldn't make sense economically.
Click to expand...
Click to collapse
sounds like a bad connection between screen and mobo, does it still happen even when you set the brightness to a high/medium value?
Didn't notice anything about brightness, but as a good measure I just pumped it to the maximum to see if anything changes.
Seeing though as the screen is REALLY dark and I can see no image whatsoever, I'm thinking it actually a problematic connection with the mobo, even if I don't feel confident enough to just open it up.