Well, I have a samsung Galaxy Tab A; Model SM-T580 here. and its display is showing nothing; not even the backlight itself.
Strangely enough, whenever I connect the tablet to a computer, the windows device manager will report that an "Exynos7870" is connected, however I could not do anything else with this.
I had already opened the tablet and reseated most ribbon connectors such as the display and the battery's, and now have it lying in a charger with the idea the battery may be entirely flat instead. Unfortunately, even after half an hour or so, no signs of life appear otherwise.
Are there any other suggestions to diagnose and resolve this issue? Other related threads often point me towards the same solutions, or arbitrary "Press all buttons X seconds" that do not yield any fruitful results.
The tablet hasn't been dropped to my knowledge, at worst a loose charging cable had been used.
Related
So I was donated a Droid 2 as the original owner claimed it wont turn on and so must be dead. I happily took it hoping I may be able to revive it.
Quick rundown:
- No indication of water damage ie the watermark stickers have not changed
- Wont turn on, even when replacing with a Droid 1 battery (they are the same, i checked)
- Does not seem to hold a charge (via usb computer), however I can get the charge "white" light to come on, sometimes this happens, sometimes it doesnt...
- Pressing and holding "X" while powering had no effect
- I do not have an actual wall charger but will order one based on what I discovered below...
-Something interesting happens when I have it plugged to my pc AND I am able to get the white charge light to come on. If I quickly press the power button a few times (not pressing and holding mind you), my computer makes an error tone which it usually makes when it detects hardware improperly. I did it again while I had Device Manager on and sure enough, after the error tone started on the computer the words "OMAP 3630" popped up in my list of devices (under "Other Devices" category) and then disappeared.
This gives me hope that this device is salvageable! I read around and it seems like charging these moto devices with their own motorola wall charger (not usb) seems to help charge the device when its not charging so I went ahead and ordered one online which will arrive next week.
So what are your thoughts? Has anyone gotten OMAP 3630 to show up in their device manager? Am I wasting my time? Is there hope that this device can be resurrected?
Any assistance is appreciated
My nook is rooted. I nearly always use it plugged to the wall outlet to save battery live. I use it mainly to read pdf files using "OfficeSuite". When I start up my nook I activate to the app "Nook refresh" and "Smart Rotator"(to use my OfficeSuite in landscape mode).
Some days ago I installed a screen rotator app (from http://forum.xda-developers.com/showthread.php?t=1678431) and couldn't use it, so I uninstalled it. I do not know if this can have any relation with the problem that I am having with the screen.
Some days ago my Nook screen was perfect, no strange thing.
But one day I noticed a horizontal line (from the usual perspective, with the "nook" button below) that was dark/white (that is when the background is white, the line is black and viceversa). I did not give it much importance.
Another day, while I was reading a pdf file, appeared another horizontal line.
Today, while I was reading a pdf file, appeared another horizontal line.
That is 3 lines for now.
What could it be? Do you have any idea to solve this issue?
Thank you.
If you power off and then power on again, do the lines go away?
I would not recommend using the NST plugged in at all times - I think you will do better to let the battery cycle.
E-ink is attracted to and repelled from the screen by electrostatic charge, as I understand it. So if there's anything like a power surge or other mechanical issue affecting your unit while charging, possibly you could see an artifact in the display?
If you power off and then power on again, do the lines go away?
I did this with the wall outlet disconnect several times, but it does not work. The lines are there.
I would not recommend using the NST plugged in at all times - I think you will do better to let the battery cycle.
Why do you think that? I do it because a read that when the battery is fully charged, the light turns green and not continues charging the battery, so I suppose that direct energy is feeding the use of the device instead of charging my nook.
E-ink is attracted to and repelled from the screen by electrostatic charge, as I understand it. So if there's anything like a power surge or other mechanical issue affecting your unit while charging, possibly you could see an artifact in the display?
No, the only image that appears on the display when I power it on is a SD CARD image informing that there is a sd card.
genoxygen said:
If you power off and then power on again, do the lines go away?
I did this with the wall outlet disconnect several times, but it does not work. The lines are there.
They're probably permanent if after unplugging, powering off all the way, then powering on again they persist. If your device is still under warranty, I'd suggest resetting it to stock and getting a return.
I would not recommend using the NST plugged in at all times - I think you will do better to let the battery cycle.
Why do you think that? I do it because a read that when the battery is fully charged, the light turns green and not continues charging the battery, so I suppose that direct energy is feeding the use of the device instead of charging my nook.
I thought about that a little more. On the NC, if the device is plugged in, the screen tends to behave very strangely - detecting nonexistent touches or accepting input, but then repeating it (fast page flipping through a book, rather than turning one page.)
The charger on the NC and NST is not its strong point (the NC in particular, but I've never liked the fit of the NST chargers much - on both of my devices, they tend to seat at an odd angle and need to be pushed a bit to seat correctly) and I've always wondered how well the rest of the device is actually isolated from current when it's plugged in.
Click to expand...
Click to collapse
I've just had the same happen to my NST. First a single horizontal line, now two.
Did you ever resolve your problem?
Same here. One, two, three and yesterday appeared the fourth line! I have the Nook more than one year. I noticed the lines everytime after charging, so it could be connected. Discharge, charge, reset, nothing helps. When I will buy myself a tablet or a new reader. I will open it and pay with some display connectors.
I ended up returning mine to B&N as it was still under warranty.
But I'd be interested to know what you find if you take yours apart. It kinda sounds like a loose connection somewhere...
I was on my computer when i remembered i has something written in my tablet's notes that was important. I took it out of my bag and noticed it wouldn't turn on, it was out of battery (hadn't touched it for about a week). I just plugged it in the proper asus charger and put it down and went straight back on my computer.
I decide to check on it after 2 hours thinking it would be near or fully charged. I pick it up and noticed it was on a blank back lit screen. I unplugged it and then the screen turned straight off. Wondering if it didn't charge at all i re-plugged it in. There was no google logo (rooted), instead it turn on with a lit black screen and off and repeating a few times and then small thin artifact pixels run across the screen (red, blue and yellowy colours) and then stay at a black lit screen like when i first picked it up. I had just noticed a small buzzing sound while this was happening and still does so when stuck at the screen. I'm pretty sure it was buzzing when i had found it.
I redid what i had done (unplug, replug) and watch to see if it did the same thing. It did. I tried to power it off while it was at the black screen and it did, but then it would turn back on and etc. Same if i tried to enter boot loader or any key combinations.
I've tried disconnecting the battery and reconnecting and same effect (tried it without battery attached also)
I have a feeling it is dead now and i have no other ideas (checked many forums but got nothing).
Any help would be appreciated.
yvgamer94 said:
I have a feeling it is dead now and i have no other ideas (checked many forums but got nothing).
Any help would be appreciated.
Click to expand...
Click to collapse
It's surely hardware failure, have take some humidity or something like that?
Try press power for 60 seconds, if you wont see any Google logo there's some hardware failure you need to RMA ( http://en.wikipedia.org/wiki/Return_merchandise_authorization )
found the fix
I found away to fix my nexus 7. You could be right how it might have a minor hardware fault, live in australia in the high hot tropics (high humidity). I decide just to plug it into my computer usb charger instead of the proper charger since it had a lower max amp output. Against my ear, a much fainter buzzing is still heard but this time, there was nothing. No power, no back lit black screen, just a very faint buzzing. Decided to let it sit just to see what happens. After an hour or so, i decided to press the power button and noticed there was a battery charging signal. To my delight, I'm sure it was in working order now so i powered it on and oh how relieved i was.
I determined that my device might have had a small hardware fault that made it draw to much power from the 2 amp original charger and thus why the tablet could not boot up properly (from battery depletion). Either that or my charger could be bugged to. But the thing is, since it charged to slow from the usb, i plugged in the proper charger and it worked fine. Just have to try not deplete my battery i guess.
Thanks.
I have searched and searched and searched, only finding unhelpful suggestions from people not too qualified to offer said unhelpful suggestions, haha. This bastard Moto X will not charge, regardless of charger/cable used (OEM Turbo and regular), no USB trickle charge, and I caved and got a new battery despite knowing better and it still won't charge. It stays on while plugged in and runs until the percentage reaches 0% (rate of discharge isn't always consistent). I've tried a whole host of dumb tricks like draining battery to 0%, selecting "Power Off" from fastboot, and holding Power/Volume Down for five minutes. Doing the latter seems to be the only thing that allows it to get a charge, but it's kind of wholly impractical to do that every day for who knows how long to make a difference. Also did complete factory reset and fresh reinstall of both factory and cm13 ROM and clearing ALL the caches, still to no avail.
So because it will slightly charge in the constant fastboot/reset process of holding Power/Volume Down, I've come to the conclusion that it's a kernel thing because of a damaged component on the board. Biggest issue is that the battery is reported as "Cold", with a general temperate reported by multiple utilities at -32 degrees. I can't upload screenshots at the moment, but TWRP reports system temp as a massive string that covers 2/3 of the bar up top. So for whatever reason the phone isn't getting a reading from the battery temperature sensor, and it's refusing to allow the battery to charge. I've been searching like crazy to find a way around this, be it editing the kernel to ignore temperature, or finding a schematic to know where to look for related circuitry responsible for this. I DID find a single component that has been broken from the previous owner tearing into it to replace the screen, but it's up near the button connector and just seems like an inefficient place to take anything relating to the Power IC. Regardless, since I can't find any way of identifying exactly what it is and what it does, I'm not sure how to handle this. Any flippin' suggestions?
tl;dr - I had pizza leftovers for breakfast and I regret it.
illitero said:
I have searched and searched and searched, only finding unhelpful suggestions from people not too qualified to offer said unhelpful suggestions, haha. This bastard Moto X will not charge, regardless of charger/cable used (OEM Turbo and regular), no USB trickle charge, and I caved and got a new battery despite knowing better and it still won't charge. It stays on while plugged in and runs until the percentage reaches 0% (rate of discharge isn't always consistent). I've tried a whole host of dumb tricks like draining battery to 0%, selecting "Power Off" from fastboot, and holding Power/Volume Down for five minutes. Doing the latter seems to be the only thing that allows it to get a charge, but it's kind of wholly impractical to do that every day for who knows how long to make a difference. Also did complete factory reset and fresh reinstall of both factory and cm13 ROM and clearing ALL the caches, still to no avail.
So because it will slightly charge in the constant fastboot/reset process of holding Power/Volume Down, I've come to the conclusion that it's a kernel thing because of a damaged component on the board. Biggest issue is that the battery is reported as "Cold", with a general temperate reported by multiple utilities at -32 degrees. I can't upload screenshots at the moment, but TWRP reports system temp as a massive string that covers 2/3 of the bar up top. So for whatever reason the phone isn't getting a reading from the battery temperature sensor, and it's refusing to allow the battery to charge. I've been searching like crazy to find a way around this, be it editing the kernel to ignore temperature, or finding a schematic to know where to look for related circuitry responsible for this. I DID find a single component that has been broken from the previous owner tearing into it to replace the screen, but it's up near the button connector and just seems like an inefficient place to take anything relating to the Power IC. Regardless, since I can't find any way of identifying exactly what it is and what it does, I'm not sure how to handle this. Any flippin' suggestions?
tl;dr - I had pizza leftovers for breakfast and I regret it.
Click to expand...
Click to collapse
DID YOU FIND A SOLUTION? I'm facing the same issues with my moto x pure edition (XT1575) after a screen replacement. Ampere aplication says the battery health is "Cold".
I never did, unfortunately. I tried a different battery in the event that some onboard IC was damaged, but it performed the same way. Whatever component was damaged seemed to be responsible for relaying pertinent information regarding battery temp readings; and without it the phone was getting that -32 reading which was beyond a safe/efficient range to allow charging (presumably). In my research, I think I remember it being possible that fiddling with the kernel itself to bypass battery temperature requirements is possible, but that's beyond my level of knowledge and runs the risk of being potentially unsafe since all it takes is one instance of getting too hot for the whole thing to go up in smoke. As frustrating as it is, it's not worth the potential damage to the device and/or home.
Not to say that your issue is the same as mine concerning cause, but the end result of how to bypass it would more than likely be the same :/
Same issue... Well... On my way to it.
I mean, my XT1575 will only charge if I lift the micro usb cable in a very very specific way. And everyday that passes, it's getting more a more difficult to find the right spot
DiegoMarinDiego said:
Same issue... Well... On my way to it.
I mean, my XT1575 will only charge if I lift the micro usb cable in a very very specific way. And everyday that passes, it's getting more a more difficult to find the right spot
Click to expand...
Click to collapse
I had that exact issue with the included 25W quick charger after a while. Switched to another charger and cable and the problem was solved for me.
Folks,
kids got a T580 tablet which, by this morning, all of a sudden didn't wake up anymore. They've been playing games, apparently the device was at 21% battery. Now I can't enable display anymore. Restarting by holding POWER and one of the Volume buttons pressed doesn't work either. Connecting the device to a Linux laptop via USB however shows me a Samsung MTP device connected. Unfortunately rebooting via adb doesn't work, adb claims the device is unauthorized and (with the display off) I also can't change anything about that. Device is not rooted, running latest OTA update firmware. I'm running out of ideas... any suggestions on how to eventually revive the device? Known behaviour?
Thanks in advance,
Kristian
Known? not to me, but I'm new to the A.
Could it just be dead battery? If wall charger doesn't charge it, try usb port linux box, it's a slow charge that way, very slow, but it does work.
Let us know updates, unusual problem...
AsItLies said:
Could it just be dead battery? If wall charger doesn't charge it, try usb port linux box, it's a slow charge that way, very slow, but it does work.
Click to expand...
Click to collapse
Thanks for your feedback, greatly appreciated. Unfortunately, battery seems out here. More insights: The device has WiFi on and actually also an IP address assigned. Connecting it to the laptop, I see an MTP and a modem device, and the device also shows up in adb devices. Even hard reboot using POWER +VOL-DOWN apparently seems to work, by then (still connected to the laptop) the MTP and modem device will disappear for a few moments to finally reconnect. Just all the time the device stays dark, I can't even do anything with it using adb because I can't get it authorized without a display connected.
Really strange. I have never so far seen something like that. Any more insights welcome. Especially, is there a way to enable something such as screen mirroring (I have a chromecast around) without physical access to the device? It's pretty difficult to do anything right now without being able to interact with that thing...
kr428 said:
Thanks for your feedback, greatly appreciated. Unfortunately, battery seems out here. More insights: The device has WiFi on and actually also an IP address assigned. Connecting it to the laptop, I see an MTP and a modem device, and the device also shows up in adb devices. Even hard reboot using POWER +VOL-DOWN apparently seems to work, by then (still connected to the laptop) the MTP and modem device will disappear for a few moments to finally reconnect. Just all the time the device stays dark, I can't even do anything with it using adb because I can't get it authorized without a display connected.
Really strange. I have never so far seen something like that. Any more insights welcome. Especially, is there a way to enable something such as screen mirroring (I have a chromecast around) without physical access to the device? It's pretty difficult to do anything right now without being able to interact with that thing...
Click to expand...
Click to collapse
Pretty much seems like a screen failure. If it's kids I'd say likely been knocked and probably needs the screen connector/s reseating.
Try to open back cover it's very easy,after that disconnecte all of flix cables (lcd ,battery camera,...etc) and connect them again finally press power button it will work 100% .i did it many times
Sent from my SM-G965F using Tapatalk
Wakeel2014 said:
Try to open back cover it's very easy,after that disconnecte all of flix cables (lcd ,battery camera,...etc) and connect them again finally press power button it will work 100% .i did it many times
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
I will kind of second this. The devices have a tendency to freeze or what we call deep cycle discharge. And many times a simple battery disconnect solves these issues.
We have this issue on the s8 s8+ and pretty much any device it can but more of a pain on a non removable battery
A ittle late and maybe too simple, but my wife's did this and the brightness had somehow gotten turned completely down, to the point of not seeing anything. I fixed it by randomly swiping left to right until I hit the bar.