To preface:
I have owned this tablet for well over a year now, and while it has had mild issues with load speed and such, I have never encountered this particular issue in conjunction with the paragraph below before.
Occasionally and seemingly at random, when picking up the tablet from a resting position and turning it at a certain angle, the screen would suddenly be filled with a single solid color, with a single black line at the very far left of the screen (landscape mode). A quick reboot and all was well.
Last night however, having retrieved my tablet and it's charger, I encountered the above described error, and upon attempting to reboot I found it was stuck at the logo, and did not boot even after sitting all night. It also appears to no longer recognize the charger (no vibration feedback), yet it still gains power when plugged in.
I shall be frank here; how buggered am I?
EDIT: Managed to get into CM Recov; now how do I fix the boot error?
Related
Hi guys
I have this strange behavior going on in my Sentation.
Out of nowhere my phone started to have strange screen behavior... Didn't light up after pressing the power button (had to phone my self in order to get screen on).
The next thing was that suddenly the screen goes to maximum brightness or goes to minimum without any explanation (tried both auto brightness or manual).
After that I noticed that the screen went off when I was using it but when I pressed the left side of it it lighted up and off again... making me think of some kind of bad contact underneath. As I already had changed a broken touch screen for t3 times, and let the phone fall for several times I thought it had to do with some plug out of line...
I disassembled the phone completely and mounted up back again. The thing is that the phone started to freeze every 5 minutes (screen on but completely freezed. I have to pul out battery). Sometimes it freezes even in the recovery menu. I've tried several rom's with full wipe and not installing anything and its all the same.
Some times I still not that the screen goes off during the freeze but when I touch the left side it goes on again, but that doesn't change the freezed state even that I let down the phone for several minutes.
I disassemble the phone again, tried different back cover and different battery (one stock and other extra strength) I tried also all the suggestion related to the small pin in the back not connecting well with the back cover (adding an aluminium foil, pulling the pin out, etc..)
Nothing seams to resolve anything so I have clearly an hardware problem... but I don't know what to replace or where to look the damage!!!
Can anybody help me please?!
Update
I have an update on my problem:
I noticed that when I leave the phone on top of some kind of metal part and don't touch it it works all day without any problem but, as soon as I start to touch the phone, it freezes within minutes!
Could it be some kind of static electrical problem? How to resolve it?
I would apreciate any help
Thanks
I encountered my first problems with my Nexus 5, which i am very happy with, about 1-2 weeks ago. After about 11 months of happy, problem free use, without dropping it or anything else, it started misbehaving (about a month with Android L so far). It crashed and wouldn't start up farther than the 'android' screen most of the times. Rarely it would fully boot, but the seemed to go into the lock screen and crash after a max. time of about 1 Minute of normal use. After going through this a few times I checked some forums and found a solution suggesting to repeatitly press the lock screen button while it boots. This solution worked quite good, even though i had go through the process multiple time the following days.
Last thursday evening (today is saturday) though my phone crashed fully once more (just after checking and having an 80% charged battery) , but now the quick hits on the Power button did not work at all. Instead my phone wouldn't react at all. Neither pressing the volume rockers alone or together with the power button would work either. Having plugged in the Nexus though acheived it to at least reach a state which seems to be a more common problem. It has been discussed and solved for many (seemingly everyone) in another thread called '[Q] Nexus 5 constantly rebooting at 'Google' ' (Link to this at bottom). Long explanations and videos of the situation have been given here, depicting my exact situation along with two solutions:
1. Using magnets near the power button (to apparently loosen two magnets used when pressing the power button)
2. Two flick and quickly press the button (for some this had to be done many minutes)
After seeing many (surprisingly) positive reactions to both methods, I tried them myself. I began with the magnet method and without having it connected to a charger it would boot to the google screen twice (note: As said, without a charger nothing happened). First once about as long as when connected to power and once very briefly. This method didn't prevail more than once and i couldn't start it up any diffrently than before.
So next I tried the flicking method and (maybe because of the magnets) it booted al the way to the 4 colored dots flying around. I let go and it crashed once more. I fooled around with the magnets again and tried the flicking method again, without stopping, as other users mentioned a long time needed (15-30 Min.) and after about 20 Minutes I stopped. My Nexus did not crash, but it is now 'stuck' at the colored Dots. I have tried connecting it to a power outlet, my PC and again started pressing the power button and volume rockers, without effect. It has been so for about an hour if not more. I will try to drain the battery and then continue, but if any other solutions are known Please help, thank you!
Link to other Question: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-constantly-rebooting-google-t2809617
Update
After having drained the battery completely and then charging it again, the normal 'charging battery' icon popped up. Trying to start the phone, however resulted in getting into the flying dots loop again... I am able to go into fastboot mode, but neither start or Power Off help the situation. Should I go into recovery mode? I would strongly dislike losing all my data....
(Update)
I tried going into recovery mode, but the only thing that happened was that a little android figure, lying down with a red exclamation mark showed up (which should be normal as I recall going into recovery mode before my problems), and a text saying 'no command' above it. What now? I'm all out of ideas and back up plans, except calling google as it should still be under my warranty. But I don't want to give up my data as I haven't saved anything and I don't want to give up my phone either.
My friend smashed the screen on his nexus 5 and gave it to some shady repair shop. They replaced his screen (with a white one, on a black phone btw, now it has a white dot on top) and he paid a lot of money for it, but now his display won't work, so he gave it to me to fix, as I have some experience with fixing phones and he has no money left. The repair shop refused to take it back and he doesn't want to start a legal battle. As far as I've tested, the phone shows three behaviours. The first is that the phone boots normally, but without displaying anything. I can still hear it getting notifications and can connect it to a computer, it's just not displaying anything. The second behaviour is identical to the first, except instead of a black screen the phone shows colorful static which seems to correspond to screen-on time (when I lock the phone it goes black and vice versa). The third behaviour, which is the weirdest, is that the display works, but everything displayed is glitching. The google logo maybe has the top 20% moved down a bit, the boot animation may be choppy or distorted, the recovery menu may be divided into blocks which are moved around a bit. In this 'mode', I have never gotten it past the boot animation. The reason I wrote 'may' is because it's different every time, but eventually it always just goes black and stops responding until i disconnect and reconnect the battery.
I opened the phone and fiddled with the connectors a bit and found out that pressing the usb board connector to the mainboard seems to cause the phone to switch between these behaviours. I took a small piece of paper, folded it over a few times and put it on top of the connector and then screwed the cover back on to hold the connector firmly in place. That seemed to put the phone into constant behaviour 3 (graphical glitching).
What could be the problem? I know that the static indicates that the usb board or more probably its connector is faulty, but I'm more concerned about the glitching. It seems to me that the graphical processor is malfunctioning, but I have very little knowledge about graphical processing and displaying so I really don't know. Any help would be greatly appreciated.
UPDATE: the phone just did something weird, when I turned it on it displayed static, but then it started drawing the boot animation slowly from top to bottom. And then proceeded with behaviour 3 as usual, the animation ran at about 3fps and just went blank after 10s.
Okay, I have located the exact location of the fault, the USB board ribbon cable that goes over the battery was bent at a sharp angle and then apparently straightened again. If I press it in that point, the screen switches between static and nothing. I have not been able to recreate the glitching since I cleaned all the parts of the phone with isopropyl alcohol. Still, I'm interested in an explanation to avoid further problems with glitching
now it's behaving even more strangely. When I turn it on, it slowly fades from grey to bright white screen and then goes black and starts blinking a red light. What does this mean? Please help
anyone?
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here
Hi guys,
I am experiencing the wierdest thing on my brother's Xperia Z3.
2 days ago, the phone randomly stopped showing images on the screen, but the backlight would still switch on and off as normal when pressing the power button. If the phone is restarted in this state by using key combos, the Sony logo won't even show up. This problem started intermittently, but now it does this for a much longer period. The issue would usually occur after the phone being locked, or if it were being used, the screen would show horrible distortion on the bottom half and become non-responsive until the screen switched off and any attempt to switch it on would be make the phone behave as described earlier.
I used to be able to make the image work by plugging in the USB cable, but this method seems to have stopped working, or at the very least has a really low success rate. I have tried all the soft reset methods: Power+VolUp, yellow button in the sim tray, none of those work for me.
I have just stopped short of reflashing the phone with Flash Tools.
Has anyone had this problem before? It is really confusing me as to whether this is a software or hardware issue.
Any suggestions?
I reflashed the phone using Flash Tools and the phone is still behaving the same way; just the backlight is turning on. Besides that, the phone seems to be making the correct noises and responding to the USB cable. Anyone have any ideas? Could it be the screen itself? I'm worried that it may be the motherboard.
Ok, I found something that works. If I hit the device with my hand on the back or the screen a few times, it seems to bring the phone back. My suspicion is either a loose screen connector or something on the motherboard. I'm not really comfortable with opening the phone up, so this is going to be my go-to solution. Hope this is able to help someone.