[Q] Black screen after replacing - Nexus 7 Q&A, Help & Troubleshooting

Hi Guys,
After I "replaced" the screen,it was blank, yet booting and visible to computer,
I decided to recheck - and switched to the old screen. It didn't work either!
So now I have two sceens but non is functional
Any ideas?
Btw, i found this topic
http://forum.xda-developers.com/showthread.php?t=2529791
but there is no solution

ilgeor said:
Hi Guys,
After I "replaced" the screen,it was blank, yet booting and visible to computer,
I decided to recheck - and switched to the old screen. It didn't work either!
So now I have two sceens but non
Any ideas?
Btw, i found this topic
http://forum.xda-developers.com/showthread.php?t=2529791
but there is no solution
Click to expand...
Click to collapse
Got the same problem right now, trying to solve it. Was about to post new topic but saw yours. Can you boot your device into bootloader? Mine seems to be able to do that and I see everything but once it shows the Google logo during normal boot or recovery, the screen goes dark and blank.
Very mysterious indeed, never seen this issue before...
Hoping someone can shed some light on this...
deltatux

Can you remind me of how you did it?
Cause vol up+power\vol down+power won't work for me
What screen have you bought?
Cause I was super anxious about getting original Hydis, now chungwa they now sell everywhere
at first, I would think that I somehow messed uo the cable - but if you are saying, that you are able to boot
mystery!
I guess, we need some experienced service man here

ilgeor said:
Can you remind me of how you did it?
Cause vol up+power\vol down+power won't work for me
What screen have you bought?
Cause I was super anxious about getting original Hydis, now chungwa they now sell everywhere
at first, I would think that I somehow messed uo the cable - but if you are saying, that you are able to boot
mystery!
I guess, we need some experienced service man here
Click to expand...
Click to collapse
Vol down + power. Though upon further reassembly, it seemed to get worse. Now my screen won't even light up or show anything. Try shining a flashlight on the LCD panel. Do you see anything? If you do, it's likely a bad data cable. In which case, you should find one on eBay.
deltatux

It isn't working at all(
But I can't be 100% sure, cause I've so many change cycles
Buying things on ebay means +1 month of waiting, so I'd prefer to know exactly, will the new cable heal me tablet
Anyway, have you decided, what happened to your screen?

ilgeor said:
It isn't working at all(
But I can't be 100% sure, cause I've so many change cycles
Buying things on ebay means +1 month of waiting, so I'd prefer to know exactly, will the new cable heal me tablet
Anyway, have you decided, what happened to your screen?
Click to expand...
Click to collapse
For me since I shone a light and there is something showing underneath and I know that the panel should work since I did see a Google logo and fastboot did properly show up before I reassembled it again 2 times before it completely disappeared, It's likely the data cable, so I repurchased a data cable from eBay.
Have you tried shining a light on to the LCD panel to see if you see anything? If not, it's likely a faulty LCD panel.
deltatux

Related

I need some serious help.

My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.

Black Shroud of Death

FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then it goes to a black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. Playing around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried downgrading to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. laying around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried going down to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
Sorry, this post isn't going to help, but I literally laughed out loud when I saw
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Click to expand...
Click to collapse
in the preview of the post. Lol
Maybe I should delete my original Karma-Killing post as a start.
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
a.mcdear said:
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
Click to expand...
Click to collapse
It might not be software but I can see the recovery screen so I have some reasons to believe it could still be software. Unfortunately, if I try to RMA, they're going to say that I voided the warranty....because I probably did by opening the case AND running a cooked ROM. So, they'll fix it but as a service. I'm not sure it would be worth the cost.
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
yanbo2012 said:
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
Click to expand...
Click to collapse
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Skyeclad said:
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Click to expand...
Click to collapse
Yea, you screwed up by opening it. You might as well upgrade if all else fails. I'd hold off on another transformer for as long as I can though if I were you...already hearing about minor defects in tf300s such as light bleeding.
Then there's always the...iPad...but make sure you update if you get one! Jailbreak that MF first and then you'd be good to go. My dad wants me to jailbreak his iPad 2, but it doesn't help that he's "update happy"
Skyeclad said:
I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
farsight73 said:
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
Click to expand...
Click to collapse
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Skyeclad said:
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Click to expand...
Click to collapse
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
1) NVflash works on B60 and below.. check yours
2) Put it in a freezer for a night
3) Dissemble again and see if anything disconnected or loose since the last time you open it.
4) Smell it and see if anything like burn smell around the motherboard(this could be over voltage from a weak components).
.
.
.
.
.
If all above still yielled the same result..
5) Check and see if your TF101 could survive 2 storey height drop..
Good Luck..
farsight73 said:
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
...
2) Put it in a freezer for a night
...
Good Luck..
Click to expand...
Click to collapse
A lot of LCD screens can be damaged by freezing, unless you know that the TF is safe I would not freeze it.
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Skyeclad said:
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Click to expand...
Click to collapse
Lol, didn't you already take it apart before?
I2IEAILiiTY said:
Lol, didn't you already take it apart before?
Click to expand...
Click to collapse
Yes, but at the time I was looking for a cable that I could loosen, now I'm looking for a cable to tighten. Fml, yes it sounds stupid but I'm at the point where I need to decide if a repair or replacement is the next step. I'm not thrilled with anything out there.
Almost exactly the same problem here...
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
I had the same problem of the backlight being on but no video. It worked over the hdmi but that was it. I had to send in my unit via a RMA to get it fixed.
Thankfully it was under warranty so they fixed it. Did you drop your unit?
MeLikes said:
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
Click to expand...
Click to collapse
Just out of curiosity, why not nvflash your way back to stock? I did because I couldn't find my HDMI mini cable. I haven't opened my tablet again. I'm going to try to RMA it.
try to nvflash stock rom and start over? that would your best chance....
Sent from my Transformer TF101 using xda premium
Well first of all i don't know how to use NVflash, and secondly i have a B70 transformer so i don't know if it will work. Also i need to flash the stock Taiwan firmware because that's the original firmware that came with it and i can't find instructions for that. Just wondering though does flashing the stock rom using NVflash also install the stock recovery?

[Q] LCD not working, screen and digitizer fine, what could be the problem?

Hello all!
I would like your opinions/knowledge on how likely you think it is that my problem is a simple disconnected cable, and if it would be worth it to take apart my phone (I've never done it before.. but I'm careful) to see if I can just reconnect it.
I woke up one morning and my screen would not turn on =( I did not drop it or get water on it, although it had been very humid. The screen is not cracked and it is still responsive to touch (vibrates when touched on the soft keys on the bottom) but it is completely black, no flickers, no faint images, no nothing. I also have not seen the LED light up since this has happened, when charging or plugged into my computer or anything. My computer DOES recognize the phone, and I have used the Motorola utility to update my phone since this has happened, but that did not fix it. I have tried all of the key combinations and I have successfully rebooted it (I can hear the droid start up noise, the camera sound when I hold power and down volume at the same time, and it sounded like I almost accidentally made a call when messing with it last night).
I have not yet been able to factory restore it or anything like that from recovery, as I am flying blind, but I'm thinking this is a hardware problem with the LCD?
The phone is not rooted and boot loader is not unlocked. It's only a few months old but I bought it used online so there's no returning it or anything like that.
I just don't know enough about any of this to know how to proceed next. Any help would be appreciated! Thank you for your time!
SunLilac said:
Hello all!
I would like your opinions/knowledge on how likely you think it is that my problem is a simple disconnected cable, and if it would be worth it to take apart my phone (I've never done it before.. but I'm careful) to see if I can just reconnect it.
I woke up one morning and my screen would not turn on =( I did not drop it or get water on it, although it had been very humid. The screen is not cracked and it is still responsive to touch (vibrates when touched on the soft keys on the bottom) but it is completely black, no flickers, no faint images, no nothing. I also have not seen the LED light up since this has happened, when charging or plugged into my computer or anything. My computer DOES recognize the phone, and I have used the Motorola utility to update my phone since this has happened, but that did not fix it. I have tried all of the key combinations and I have successfully rebooted it (I can hear the droid start up noise, the camera sound when I hold power and down volume at the same time, and it sounded like I almost accidentally made a call when messing with it last night).
I have not yet been able to factory restore it or anything like that from recovery, as I am flying blind, but I'm thinking this is a hardware problem with the LCD?
The phone is not rooted and boot loader is not unlocked. It's only a few months old but I bought it used online so there's no returning it or anything like that.
I just don't know enough about any of this to know how to proceed next. Any help would be appreciated! Thank you for your time!
Click to expand...
Click to collapse
it would still be under warranty by motorola - especially if you accepted the OTA recently (May 2013).
otherwise, I would try leaving it plugged in for awhile (30-60 minutes), then try rebooting it (hold down all 3 buttons)
Thank you for replying!
jco23 said:
otherwise, I would try leaving it plugged in for awhile (30-60 minutes), then try rebooting it (hold down all 3 buttons)
Click to expand...
Click to collapse
I have tried this.. I can hear it booting up but still no screen =(
it would still be under warranty by motorola - especially if you accepted the OTA recently (May 2013).
Click to expand...
Click to collapse
How do I go about collecting the warranty on a phone that I bought used? And what would happen if it showed water damage? I swear I have not gotten any water/liquids on it, but this did happen after it was very humid out for a while, and I have read that high humidity is enough to spread the red dye (regardless of whether or not high humidity actually caused the problem)
SunLilac said:
Thank you for replying!
I have tried this.. I can hear it booting up but still no screen =(
How do I go about collecting the warranty on a phone that I bought used? And what would happen if it showed water damage? I swear I have not gotten any water/liquids on it, but this did happen after it was very humid out for a while, and I have read that high humidity is enough to spread the red dye (regardless of whether or not high humidity actually caused the problem)
Click to expand...
Click to collapse
call motorola (or go to their website and bring up a chat session in their online support section)
Try tapping it somehat hard with your finger all around the phone to see if it flashes the screen.
scottocs said:
Try tapping it somehat hard with your finger all around the phone to see if it flashes the screen.
Click to expand...
Click to collapse
No luck =( I've already tried "pinching" the phone somewhat hard all over too... Thank you for the input though!

[Q]Thin blue line on screen

Today morning wokeup with a bright day,
I saw my phone working normal
I have mahdi rom on my phone..
But theres no issue with rom or any mod is what im sure about..
I looked at my phone..
And im having a very thin blue line on the right of the screen which is probably a hardware issue as it doesnt get captured in the screenshots..
And my power button doesnt work anymore any better.. After fighting with it and has been same since 6 months.. It works..
And the line came from today morning..
When i boot the phone its in red at google logo and fades away n when completes the boot.. It comes from start with blue everywhere on screen..
I have been using the phone like 2 years and so please help me with the problem if anyone else may have came across
Do a factory reset and report back! ?
it does appear even on the twrp,bootloader and even on boot logo of circles too,
so will a factory reset solve it?
sid21 said:
it does appear even on the twrp,bootloader and even on boot logo of circles too,
so will a factory reset solve it?
Click to expand...
Click to collapse
I don't think so, it is probably a hardware issue. Maybe you can check the inner parts of the phone or send it to a repair service. It seems like the connector between the motherboard and the screen is the reponsible.
TheDeathlord said:
I don't think so, it is probably a hardware issue. Maybe you can check the inner parts of the phone or send it to a repair service. It seems like the connector between the motherboard and the screen is the reponsible.
Click to expand...
Click to collapse
Thank you for the reply,
Hope its just a connection problem cause i cant afford screen right now.. I have used my phone with soo much care and yet this happening is very sad for me..

s4 19505 r.i.p??

hi guys
i dont really think anybody can help but its the only chance i have left.
iv been running this rom for a couple of weeks with out mainy problems......only a slight lag.
http://forum.xda-developers.com/galaxy-s4/i9505-develop/touchwiz-lollipop-leaked-rom-i9505-t3027063
one member said
Hi,
For those who have problem with lag:
From Stweaks, change default gov to Lionheart, gpu gov to simple, I/O to fiops, disable android logger, enable zram, reboot.
These settings also give me great batt life
Click to expand...
Click to collapse
so i made the changes and it did make a big difference. i shut the phone down 2 hours after to charge it,, and thats when a odd thing happened.
its dead.
no life at all. even when its connected to my pc. if i plug the charger in it just gets hot.....thats it.
can i assume its bricked for some odd reason??
what happens if you pull the battery, plug it back in and try and reboot into recovery/download mode?
DSA said:
what happens if you pull the battery, plug it back in and try and reboot into recovery/download mode?
Click to expand...
Click to collapse
nothing
try changing the battery
it might be a hardware problem
DSA said:
try changing the battery
it might be a hardware problem
Click to expand...
Click to collapse
i did that + charger,and lead.
no responce and all. if i plug in the charger the top half of the phone gets quite hot in the main board area.
im sure some people come on hear with problems with out telling the full storey ( dropping it down the toilet,or just dropping it) but i literally shut it down to charge it quicker.
im still scratching my head over this.
if all else fails i may look into buying one with a smashed screen on ebay and replace the main board as my phone is in great condition,....gutted.
it does sound like a hardware issue - can you take it back to a samsung service center?
DSA said:
it does sound like a hardware issue - can you take it back to a samsung service center?
Click to expand...
Click to collapse
i could...... but it would cost much more than its worth.
iv had it from new, such a shame.
If you tried another working battery, tried connecting to a computer and cant get into Download Mode.... I say your phone is dead and it sounds like a hardware fault. I have seen soft bricked and hard bricked phones, they still show some form of life like the led turning on, pixel salad, black screen (as you can see the screen light up), white screen, cant get into recovery but can get into Download mode and etc.
Sounds like its dead but I am sure its got nothing to do with what you did and its just a coincident that it died.
Z-Blade said:
If you tried another working battery, tried connecting to a computer and cant get into Download Mode.... I say your phone is dead and it sounds like a hardware fault. I have seen soft bricked and hard bricked phones, they still show some form of life like the led turning on, pixel salad, black screen (as you can see the screen light up), white screen, cant get into recovery but can get into Download mode and etc.
Sounds like its dead but I am sure its got nothing to do with what you did and its just a coincident that it died.
Click to expand...
Click to collapse
yes i totally agree.
i think ill put another main board in it and sell it on.
two years old so it may be a good opportunity to upgrade..........may be a s5.
many thank guys.
I'm back with with my s4, reserected from the ash's with a replacement main board ?
Sent from my GT-I9505 using Tapatalk

Categories

Resources