Xz premium freezing and resetting when i unlock it. Also no volume up, related? - Sony Xperia XZ Premium Questions & Answers

Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!

leemo89 said:
Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!
Click to expand...
Click to collapse
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.

Atrax2010 said:
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.
Click to expand...
Click to collapse
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!

leemo89 said:
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!
Click to expand...
Click to collapse
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.

Atrax2010 said:
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.
Click to expand...
Click to collapse
Thanks very much, I'll give that a go first!
If it fails where and you are close to me (Melbourne Aus) how would you like a project?

I share with you my personal experience.
The phone is amazing, is very fast, efficient, amazing sound, amazing screen.
I have the same problem with the volume up bottom but in my case it was caused for a fall incident, I took it apart and I discovered there is one flex connector that goes from the mother board and is shared with the volume bottoms, the power- fingerprint sensor, the camera bottom, the lower speaker and the lower microphone.
In fact due to that fall I am having problems with the volume up bottom as I wrote, the lower microphone, the lower speaker and sometimes the fingerprint function does not work.
I think is still worth having the cel phone, I`ll search for the flex to fix it up
I think most of the description Zagreb does of your case can be adjusted to the reality of what is happening, I think is necessary a technical checking of the hardware.

I'M sorry, of course I meant buttons and not bottoms!

Freezing, unresponsive ui and volume buttons not working properly.
I've had this same issue for a few weeks tried hard resets safe mode, etc, nothing helped. So after much frustration searching forums to no avail I set to and tried a deeper investigation into my own device, I accessed the dev options and looked at power hungry services. The most hungry was Xperia home so I stopped it and low and behold my phone hasn't locked up since, still volume buttons are mostly not working but I'm not locked out any more.

Same here,
First randomly reboot, after factory reset randomly system UI failed constantly , very annoying.
Indeed button up volume is not working (properly).
Someone found solution for this? I already purchased a new battery.
@Chernob0g : how you disabled/stopped Xperia Home so I in meantime can use my phone.

Replaced battery, looks better now.
Volume up still not working, but freezing looks solved.

Related

Backlight Stuck On Low

I have an HTC One XL (Rogers-Canada) and my back-light is stuck at the lowest setting. This persists all the time from the boot-loader, to recovery to ROM. It seems to persist across Stock ROMs, Custom based on Stock, ICS & JB, AOSP, etc. When I attempt to adjust the brightness in settings the screen stays dim until I slide it to the brightest setting (far right) and then the screen goes completely dark (ie...back-light off). This problem started after upgrading from CleanROM5 to CleanROM6 but it wasn't immediate. It was probably a week or two before the problem cropped up so that may be unrelated.
Since the problem started I've been flashing everything I can get my hands on trying to see if it's software related. I went from unlocked & rooted to Unlocked/Rooted/SuperCID/S-Off but to no avail. I had a glimmer of hope at one point during the process of flashing various ROMs when the phone plugged in at the boot-loader. I had left it for a while (doing something else) and the backlight suddenly came back to full brightness. So, I happily flashed RUU, then unlocked, then rooted and installed CleanROM. Then, after an hour or so of getting the phone setup again it went back to low back-light.
Questions I assume you will ask...
Doesn't this sound like a hardware problem?
Yep, definitely could be. The only reason I think think the back-light isn't broken is that it is still working, just at a really low level. I can tell this because I can see the screen in a dark room reasonably well and the back-light really does turn completely off when I move the brightness slider to max. But, yes, it could be hardware...
What Hboot were you on when you went from CleanROM5 to CleanROM6?
I was boot-loader unlocked + rooted on Hboot 1.11.
Have you tried draining the battery?
I did run the batter down until the phone shut off but I don't think I completely drained it. I seem to recall draining lithium battery to totally empty is actually a bad idea. Any suggestions on this? Is this any different from powering down the phone in terms of resetting some software issue?
Why not just return it to Rogers?
I'm not actually a Rogers customer (Bell). I bought the phone off of someone who changed their mind and went with a different carrier. I have the box and Rogers stickers for service and repair and I'll try that if it comes to it but I doubt it's that simple.
Any help would be appreciated. Are there mods related to brightness on the HOXL I could try? Is there something lower level than an RUU I can flash to try and get everything back to stock? Is it worth trying the JET tool or is that just for real brick situations?
Thanks in advance for any help!
quasi51 said:
Have you tried draining the battery?
I did run the batter down until the phone shut off but I don't think I completely drained it. I seem to recall draining lithium battery to totally empty is actually a bad idea. Any suggestions on this? Is this any different from powering down the phone in terms of resetting some software issue?
Click to expand...
Click to collapse
Draining the battery to shutdown does not actually lower the battery voltage to zero. There are safeguards against that, as draining a Li ion battery to zero (or actually below a certain threshold) would actually render it unable to take a charge.
However, the problem is that the safeguards do not always work in a completely fail safe manner. Most times, running the battery down will not have any negative consequences. But there is a slight possibility that the safeguards will not work completely intended, and the battery voltage will be allowed to drop too low, causing the battery to be unable to charge. Its happened to some folks on this device, and other Android devices. Sometimes, leaving the phone on the wall charger overnight will bring the battery back. Otherwise, it might require a battery meter with a "boost" function, which is normally only available at repair shops.
So the moral to all that, is to avoid draining the battery to shutoff whenever possible. The other point is, that I don't see how draining the battery would help your backlight issue at all. The battery meter calibrations all get wiped whenever you flash a new ROM or RUU. So the backlight issue is not likely related to battery meter calibrations. TO properly calibrate the battery meter after a ROM flash or RUU, its good practice to charge to full, then discharge to 10 or 20%, then repeat a couple times. But again, I don't think this would help or affect your backlight issue.
Since the problem persists through ROM flashes and RUU, it does suggest a hardware issue. But its not certain.
OK, I'm pretty sure it's a hardware fault. I was cleaning off the screen in the middle of troubleshooting and the back-light flickered to life and went back off again. I may have been pushing a little harder than usual out of frustration! I proceeded to gently but firmly push on various part of the screen and was able to get the back-light to come on and off briefly. Now it seems totally dead as I can only barely make out what is on the LCD and being in the dark doesn't help.
I have some experience taking phones apart so I'd like to take a run at replacing whatever is broken. The simplest swap would be the LCD/digitizer assembly but I'm concerned that the problem could lie in the motherboard or power circuitry.
Does anyone have any experience with HOXL back-lights dying and fixing them?
Thanks
quasi51 said:
OK, I'm pretty sure it's a hardware fault. I was cleaning off the screen in the middle of troubleshooting and the back-light flickered to life and went back off again. I may have been pushing a little harder than usual out of frustration! I proceeded to gently but firmly push on various part of the screen and was able to get the back-light to come on and off briefly. Now it seems totally dead as I can only barely make out what is on the LCD and being in the dark doesn't help.
I have some experience taking phones apart so I'd like to take a run at replacing whatever is broken. The simplest swap would be the LCD/digitizer assembly but I'm concerned that the problem could lie in the motherboard or power circuitry.
Does anyone have any experience with HOXL back-lights dying and fixing them?
Thanks
Click to expand...
Click to collapse
Backlight is part of the LCD. You can't replace just the backlight. Seperating digitizer from LCD is very difficult. Most people are ordering LCD and digitizer when either needs to be replaced. HTC has a minimum of 1 year warranty, some countries 2 years. Before ordering new parts, see if you are under warranty. If not try reseating the cables that connect the screen to the MB. If that doesn't work it's time to order new parts. Good luck. You tube has videos showing disassembly and screen replacement. Watch a few first, it will make things easier for you.
Sent from the HOXL dimension of S-OFF
Hi, thanks for the reply. I realize that the light itself is part of the screen assembly but I've read elsewhere that some of the circuitry that drives it is located on the motherboard. I was just wondering if anyone had experience with a back-light that had died and what parts they replaced. I'm happy to take the plunge and get a replacement screen assembly for $75 but it's be a shame if the problem was actually on the board.
You mentioned the HTC warranty...I assumed that HTC would wash their hands of phones that were obtained through carriers. Has anyone replaced/repaired a phone through HTC that was obtained from a carrier initially? Mine came from Rogers but I'm with Bell so I doubt Rogers would help me if I tried to get service for what was originally someone else's phone.
Thanks
Contact HTC directly. If it's under warranty, they will fix it.
Sent from the HOXL dimension of S-OFF

Dropped my phone, won't boot?

Been a watcher on the forums for awhile, now I actually had to sign up and get some help, LOL.
Anyway, dropped my s2 skyrocket, noticed that it kept trying to reboot every now and then when I used it the same day. The next day, I plugged it in in the evening, and shut off, rebooted, but the screen would go black and the phone would vibrate with 2 seconds in between vibrations. It gets to the "Samsung" word, then the screen goes black in the style of an old tube TV (with the thin white line at the end). Then the vibrations start. So far a useless phone. Took it apart and checked connections carefully (I'm used to working with processor boards quite a bit).
What do you guys suggest? Damaged memory? Should I attempt to reflash? Stuck power button (seemed ok, though)? Bad screen?
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
creepyncrawly said:
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
Click to expand...
Click to collapse
Oh, thanks for the heads up. Yeah I just figured out that the i727 isn't in "Top Devices" or "Legacy," so you have to go to all forums. Ugg. Already moved. Thanks to whoever notified mod.
Anyway, yeah, any help would be AWESOME. What physical damage would prevent booting past the "Samsung" screen and default to a black screen that intermittently vibrates?
I'll be honest, if ur asking that question probably something u don't have the current skill set to fix. Try to Odin back stock, but if it started post-drop you may be SOL and in need of a new phone.
Got it into download mode after multiple failed attempts. Each time I would get it into download mode, the screen would shut off after about 5 seconds of being on. I tried several combinations of plugging it in first, then installing the battery, or holding down the button while I plugged it in with no battery, etc. I had just given up after getting it into download mode briefly for the 20th time, when I gave it one more go while rocking the on and off button. Technically that is recovery mode, but I let off right before plugging the phone in and it hit download mode and stuck.
So what I am thinking is the power button got jammed internally. I have heard of it happening on other forums. Even though it looks good and clicks upon external examination, the pressure circuit on the inside might be in contact. Anyway, just one theory.
For future though, I did discover that you don't HAVE to have the USB unplugged prior to getting into download mode. On the contrary, a power source must be present in order to register that the keys are pressed PRIOR to initiating USB input. Thus, you can actually remove the battery, plug in the USB (power source), then hold the volume keys while replacing the battery. Goes into download mode that way, too.
Will keep you guys updated. Might need a bit more help if the phone starts acting up again.
At this point, if the Download mode still holds ok, should I consider CyanogenMod, or is it easier to get back a good ROM from stock?
icenight:
Thanks for the reply. I don't understand much about smart phones or how they work, but trust me when I say I have had AMPLE experience with electronics, circuit boards, hardware, etc., particularly in the computer/laptop world. I code quite a bit of websites, and understand almost all things networking and OS. Just never really got into it with the phones.
Getting super excited to see the sheer amount of modding you can do though. Would love to break into a hardware modding world if it ever comes available. That's where it's at with electronics for me.
Well glad u got it sorted, lucky guy you are lol.
As for boards and the like, if it didn't work I would've suggested replacing the motherboard and/or power daughter board. But for a skyrocket may not be worth the money.
Since you're a hardware guy, maybe mess around with the phone and JTAG? Finding a way to unbrick without it would be very helpful
Since the problems started after a physical damage (fall) , I wonder how would Odin or wipe and flash might work !
Definitely a hardware damage...
Yeah, it kinda puzzled me, too. I believe the power button might have been internally stuck, but that's just one idea. Could have been a loose connection, too.
Can you lose some solid state memory with firmware on it, but the SS memory still be OK to right another copy on?
More than likely it was your power button
Sent from my SAMSUNG-SGH-I727 using xda premium

[Q] No tablet display but HDMI works.

Hi,
Yesterday (08/02/2013) I updated my tf700t, everything seemed to be fine after it rebooted, I was playing a game, the battery was low, and it turned off abruptly. I assumed it automatically shutdown because of the battery, so I put it in the dock and plugged in the charger. Several hours later I tried turning it on and nothing. I held down the power button for 8 seconds felt the double vibration, but no display. I tried various combinations of docked/undocked, power cord plugged in, holding the power button for 30-60 sec. etc. but nothing.
Out of curiosity I connected the HDMI to my computer monitor and sure enough, it was there, I could unlock it and everything seems to be functioning fine, just no display. The digitizer seems to work fine, although guessing where things are at is pretty tough.
I think I tried the cold boot, volume up/down (I tried both) plus power, and it didn't make a difference.
In order to do the update I had to flush the DMC Client and CMClient data and cache, I had been getting errors from DMC Client crashing.
Also I'm not certain this is update related, as the tablet had been acting wierd, which is why I did the update. I would press the power button to turn the screen on and nothing would happen, so I'd hold it down longer and the tablet would reboot and finally the screen would come on, or it would come on a few seconds after I pressed the button. I was getting a lot of reboots etc... I thought the update might resolve this.
I'm not sure if the problem is hardware, firmware, or software related.
I'm wondering if when I flushed the DMC and CM Client cache, maybe I deleted the drivers for the display or something?
My options seem to be:
1.) Factory reset by feeling around the digitizer while connected to HDMI
2.) Factory reset via the pinhole
3.) Install new (old) firmware via usb/computer. (the device is recognized by Windows 7 so I think this is doable.)
4.) Send it off to Asus. (would this be free?)
So my questions are:
1.) is there something else I should try?
2.) what order should I do the above in?
*Note: I'd like to save my data somehow.
*Edit: I forgot to mention I was on 4.2.1, no root or anything. Also I bought this in July of '12 so I'm pretty sure it is out of warranty. Any idea how much it might cost to send it off? Perhaps I could replace the LCD myself? I replaced the digitizer/screen on an ipod touch, although I'm sure this LCD is much more expensive and much harder to replace. This is turning into a nightmare. So much for trying to keep my data, now I hoping to keep this from becomming a paperweight.
Thanks.
A bloke at work had this issue. He let it rundown and left it for 3 days. It worked fine again after that.
zpyatt said:
I'm not sure if the problem is hardware, firmware, or software related.
Click to expand...
Click to collapse
If you don't even see the boot logo, it cannot be software related.
Thanks for the replies.
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
zpyatt said:
I'll try letting it run down. Would putting it in the freeser be helpful/safe?
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL. I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
_that said:
I wouldn't put the tablet into the freezer.
Does the backlight come on? If not, it's definitely a hardware problem. If the bootloader boots fine but doesn't show anything, that also looks like a hardware problem.
Click to expand...
Click to collapse
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
zpyatt said:
I'm not sure about the backlight, I think maybe it does, it is kind of hard to tell. I'll try checking in a dark room tonight. Since the screen is just black I suppose I'm looking for a brighter shade of blackness?
The bootloader is definitely booting fine. That is what I meant in my original post, the HDMI out works, I can see everything there, I can even swipe and tap the digitizer and do stuff, it is just difficult to guess where things are at. Do I need to go back and clarify this in my original post?
Do you think this definitely means it is a hardware problem? I figure I'll try letting the battery run all the way down and let it sit a few days and recharge it as sbdags suggested, in the meantime perhaps I should contact Asus, but I'm not lookinf forward to that.
Click to expand...
Click to collapse
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
sbdags said:
I don't know what is the cause but like I said I saw this with my very own eyes - the same as yours. Double buzz on boot not screen but HDMI worked. Somehow completely draining the battery fixed it ...... So hardware / software? Who knows? If it was hardware why did draining the battery fix it? The device has been absolutely perfect for 3 months since and has never done it again.....
Click to expand...
Click to collapse
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
zpyatt said:
Thanks sbdags, I will definitely try this. I'm not sure if I should hurry and contact Asus though, I bought this thing around July 22 2012 I think so it is barely more than a year old, not sure if they would cut me some slack on the warranty or not.
Do you think I need to let it sit three days or just make sure the battery is good and run down before charging again? Also I've seen some suggestions for charging from a computer vs. wall as it charges slower, do you think that would be better?
I'm getting into panic mode and want to make sure I don't do anything rash that limits my options.
Click to expand...
Click to collapse
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Having the same problem
I am having almost the same problem, except that the tablet screen works when the wall charger is plugged in. THe HDMI display and the digitizer work fine. It is just the tablet's screen dispaly when the charger is unplugged.
sbdags said:
All he did was leave it for 3 days. Our assumption was that the battery had completely drained in that time....... A charge later (he was actually just about to box it to send to Asus) and it surprisingly started as if nothing had happened.
Click to expand...
Click to collapse
So I didn't have any luck letting it run all the way down.
I contacted customer support, the warranty is only 1 year, but fortunately for this there is an extra 3 months, so I just managed to squeak by, although I'm keeping my fingers crossed.
same problem as you both
i have d same problem well until last week the screen displays when conne ted to wall charger now its all blank but iy works via hdmi, digitizer works fine but all blank, this tf201, does anyone know if i change d whole display it will work?
i already bought the tf701
any suggestions is welcomed and did you get youra to work?
zpyatt said:
I guess on the software/firmware it depends on the definition. To me drivers are software, firmware is anything written in VHDL.
Click to expand...
Click to collapse
I have not seen people mentioning VHDL and verilog for a while, hahaha... It sounds like you are a low level or physical layer programmer. Any way, a firmware is in general a low level program that communicating with the hardware and the software or high level program ( level 7).. If you will, a firmware is a management levels (level 2 and 3). A VHDL is a level 1 which generates a 0's and 1's or mapping the transistors in the FPGA chip for example.... Oh well, it is just my definition...
zpyatt said:
I suppose what I'm really wondering is if it is software/firmware vs. hardware, i.e. is the LCD or some other component dead or is the display just not getting written to, initialized or whatever.
Click to expand...
Click to collapse
If you can get the output from the HDMI port, it is more likely you have a hardware problems. I think that the problems are your display related hardware. If you really want to troubleshoot your issues, you can look on the mother board to locate all the electrolytic caps and check to see any abnormal signs of those capacitors. Those caps are the one that will blew up first before any others parts go....Good luck...:fingers-crossed:

Nexus 5 restarting regardless of ROM

So I've tried factory wiping and installing a few different roms and no matter which one I go to I keep getting these random reboots. This is particularly troubling when I restore an older rom that I know I was not having this particular issue on.
It is making my phone pretty close to unusable since it will often go into an "Optimizing apps!" speil draining battery and taking an obnoxiously long time to reboot. Not sure what is up. Any suggestions?
Snow_fox said:
So I've tried factory wiping and installing a few different roms and no matter which one I go to I keep getting these random reboots. This is particularly troubling when I restore an older rom that I know I was not having this particular issue on.
It is making my phone pretty close to unusable since it will often go into an "Optimizing apps!" speil draining battery and taking an obnoxiously long time to reboot. Not sure what is up. Any suggestions?
Click to expand...
Click to collapse
Try with a clean flash (or the factory images) without user data/modifications and see if your RRs are still there.
Is the power button stuck by any chance?
Primokorn said:
Try with a clean flash (or the factory images) without user data/modifications and see if your RRs are still there.
Click to expand...
Click to collapse
I've factory reset a few times and wiped everything except internal storage pretty much. Even tried wiping user data just to see if it would help
dicecuber said:
Is the power button stuck by any chance?
Click to expand...
Click to collapse
I don't think it's getting stuck it still seems to go in and out properly. I even took it out the case just to make sure there wasn't something I couldnt' seee putting pressure on it
Snow_fox said:
I've factory reset a few times and wiped everything except internal storage pretty much. Even tried wiping user data just to see if it would help
I don't think it's getting stuck it still seems to go in and out properly. I even took it out the case just to make sure there wasn't something I couldnt' seee putting pressure on it
Click to expand...
Click to collapse
The button will NOT seem to be stuck, even if it is, as the contact is made internally. My bro´s Nexus had this problem, and by the end it kept rebooting constantly because the button was making contact on its own. I fixed it by tapping vigorously at the area between the power button and the camera and that made it work.
A way to know if it is stuck could be to press the volume down key as soon as it restarts, if it goes into recovery, then there is no doubt the power button is stuck.
Don´t dismiss hardware problems, as many Nexus are affected by the power button issue and you already tried software solutions which didn´t work.
Hope you sort it out. Remember to use an app to avoid pressing the button so much, such as when waking the device. I recommend Gravity Screen, but there are many other options.
simonarturo said:
The button will NOT seem to be stuck, even if it is, as the contact is made internally. My bro´s Nexus had this problem, and by the end it kept rebooting constantly because the button was making contact on its own. I fixed it by tapping vigorously at the area between the power button and the camera and that made it work.
A way to know if it is stuck could be to press the volume down key as soon as it restarts, if it goes into recovery, then there is no doubt the power button is stuck.
Don´t dismiss hardware problems, as many Nexus are affected by the power button issue and you already tried software solutions which didn´t work.
Hope you sort it out. Remember to use an app to avoid pressing the button so much, such as when waking the device. I recommend Gravity Screen, but there are many other options.
Click to expand...
Click to collapse
Holding down volume after one reset actually put me into recovery. Plus it's restarting at times in recovery now :/
I doubt it's under warranty since I got it in feb 2014 x.x
Snow_fox said:
Holding down volume after one reset actually put me into recovery. Plus it's restarting at times in recovery now :/
I doubt it's under warranty since I got it in feb 2014 x.x
Click to expand...
Click to collapse
If you got it directly from Google, I'd try calling them up and asking for a replacement even if you are a few months off the warranty period, I have read some stories of them honoring warranties in order to get rid of stock. That'd be true even now that the new Nexus is supposedly releasing this year. Nothing wrong with trying, you might get a new, shiny phone.
That being said, don't worry, it's perfectly fixable. The part that gets stuck is not the button itself, but the part that goes into the motherboard, so don't bother fiddling with the black button. I managed to fix my brother's button by doing the following:
- Clean the area between the button and phone of debris or any dirt that could be causing it to be stuck. This is just to be on the safe side, as it is unlikely that it is the cause of the malfunction.
- Take the case off the phone if you haven't, and then put it upside down and tap vigorously with your fingers in the area between the camera and the power button. It might not work the first few times, but it eventually will release the part that is stuck.
- As soon as you can get it to turn on without rebooting itself, install Gravity Screen, or any other app that replaces the power button to wake up or turn the screen off. You are looking to use the button as few times as possible.
After doing that, his Nexus went for being unusable due to constant reboots to working fine. It's been almost 6 months since it happened so it is bound to work, just don't lose heart and patiently work at it. Tap a bit harder if it's not working. Let us know whether you managed to fix it.
simonarturo said:
The button will NOT seem to be stuck, even if it is, as the contact is made internally. My bro´s Nexus had this problem, and by the end it kept rebooting constantly because the button was making contact on its own. I fixed it by tapping vigorously at the area between the power button and the camera and that made it work.
A way to know if it is stuck could be to press the volume down key as soon as it restarts, if it goes into recovery, then there is no doubt the power button is stuck.
Don´t dismiss hardware problems, as many Nexus are affected by the power button issue and you already tried software solutions which didn´t work.
Hope you sort it out. Remember to use an app to avoid pressing the button so much, such as when waking the device. I recommend Gravity Screen, but there are many other options.
Click to expand...
Click to collapse
simonarturo said:
If you got it directly from Google, I'd try calling them up and asking for a replacement even if you are a few months off the warranty period, I have read some stories of them honoring warranties in order to get rid of stock. That'd be true even now that the new Nexus is supposedly releasing this year. Nothing wrong with trying, you might get a new, shiny phone.
That being said, don't worry, it's perfectly fixable. The part that gets stuck is not the button itself, but the part that goes into the motherboard, so don't bother fiddling with the black button. I managed to fix my brother's button by doing the following:
- Clean the area between the button and phone of debris or any dirt that could be causing it to be stuck. This is just to be on the safe side, as it is unlikely that it is the cause of the malfunction.
- Take the case off the phone if you haven't, and then put it upside down and tap vigorously with your fingers in the area between the camera and the power button. It might not work the first few times, but it eventually will release the part that is stuck.
- As soon as you can get it to turn on without rebooting itself, install Gravity Screen, or any other app that replaces the power button to wake up or turn the screen off. You are looking to use the button as few times as possible.
After doing that, his Nexus went for being unusable due to constant reboots to working fine. It's been almost 6 months since it happened so it is bound to work, just don't lose heart and patiently work at it. Tap a bit harder if it's not working. Let us know whether you managed to fix it.
Click to expand...
Click to collapse
I'm going to get in contact with google. I tried pushing down on the area between the camera and it didn't help much. It has started working again properly after a really peculiar work around. I just don't want to have to be super cautious of a button for the rest of the time i own my device :/
Snow_fox said:
I'm going to get in contact with google. I tried pushing down on the area between the camera and it didn't help much. It has started working again properly after a really peculiar work around. I just don't want to have to be super cautious of a button for the rest of the time i own my device :/
Click to expand...
Click to collapse
Please detail the peculiar work around you mention...
Sent from my XT1095 using Tapatalk 2
mazubo said:
Please detail the peculiar work around you mention...
Sent from my XT1095 using Tapatalk 2
Click to expand...
Click to collapse
Well someone mentioned maybe trying to clean it out somehow. I tried canned air and that didn't do anything so I formed a seal over the button using my mouth and then proceeded to exhale. It has yet to give me any trouble since then.
Had exactly the same issue, reboots over and over again, couldn't boot to bootloader without reboot...
What helped for me was something I read somewhere else, don't remember where, was knocking on the back cover between camera lense and the power switch, did it 4 days ago and it works since than..
Snow_fox said:
I formed a seal over the button using my mouth and then proceeded to exhale.
Click to expand...
Click to collapse
Sounds sexual
You can take the back cover off, and if you are careful there is no sticker or seal that would tell google you have opened the device. It is difficult to pull all the way off, the vibration motor is attached to the case back and comes off with it so it would seem stuck. You just have to keep pulling.
aaargh777 said:
Had exactly the same issue, reboots over and over again, couldn't boot to bootloader without reboot...
What helped for me was something I read somewhere else, don't remember where, was knocking on the back cover between camera lense and the power switch, did it 4 days ago and it works since than..
Click to expand...
Click to collapse
Pressing on the area between the camera and the on switch seems to help a lot of people it didn't seems ot have much of an effect for me. While my phone hasn't given me issues since shortly after I posted this thread I'm kinda worried I'm one drop away from the issue coming back
dicecuber said:
Sounds sexual
Click to expand...
Click to collapse
No way to avoid it sounding that way I fear.
fwayfarer said:
You can take the back cover off, and if you are careful there is no sticker or seal that would tell google you have opened the device. It is difficult to pull all the way off, the vibration motor is attached to the case back and comes off with it so it would seem stuck. You just have to keep pulling.
Click to expand...
Click to collapse
Would this allow me to repair it?
Yeah but you'd need to unscrew a plastic cover that is inside the phone. Phillips head screws, jewelers screwdriver size. Depends on if its dirt or a broken switch though.
fwayfarer said:
Yeah but you'd need to unscrew a plastic cover that is inside the phone. Phillips head screws, jewelers screwdriver size. Depends on if its dirt or a broken switch though.
Click to expand...
Click to collapse
Sorry to disappoint everyone but this is a widespread problem that google is aware of fro some time now. It's not the power button but it's burried deep in the software and appreas to have popped up right after the Lollipop 5.1 up date. Check out all the posts on Google
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w[376-400]
While it apprears to be confined to the Nexus 5 I have had it happen with my nexus 4 just running stock L 5.1
I hope that casts some light on it
Weirdly enough, my power button works flawlessly on 5 and 5.1. Red 32gb from the google play store. I've opened the case multiple times and put Arctic silver knockoff heat compound in sloppily and without regard, no issues other than sprint screwing up their spark LTE rollout.
Blacksmith5 said:
Sorry to disappoint everyone but this is a widespread problem that google is aware of fro some time now. It's not the power button but it's burried deep in the software and appreas to have popped up right after the Lollipop 5.1 up date. Check out all the posts on Google
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w[376-400]
While it apprears to be confined to the Nexus 5 I have had it happen with my nexus 4 just running stock L 5.1
I hope that casts some light on it
Click to expand...
Click to collapse
Sorry, I disagree. While some instances might be related to software, it has been proven that there is in fact a problem with the physical button getting stuck on Nexus 5 phones. You can check it online and will find lots of hits and even YouTube videos, most of them around the time before lollipop.
Best way to check whether it is software or hardware is to press the volume down key when your phone reboots by itself. If it takes you to the recovery, you can bet your cat that it is not lollipop's fault
So I'm suspecting that I have the wonky power button too but.....
I haven't been able to get it to go to recovery when pressing power down and I've defintely had a few restarts very recently.
More importantly, and something that I haven't seen anyone else post about; more often than not my N5 just shuts down. It's usually when I've doing something with the phone (today was flicking through my GPM library). I'll power it back on and it will boot cleanly and then (more often than not) power down again. Other times it will bootloop, but that's rare. It seems to me that if I let it boot up and then don't touch it for a while, it will stay up but I'm not sure that's consistent.
Anyone else seen or heard of the power button causing a powerdown instead of bootloop?
techinv said:
So I'm suspecting that I have the wonky power button too but.....
I haven't been able to get it to go to recovery when pressing power down and I've defintely had a few restarts very recently.
More importantly, and something that I haven't seen anyone else post about; more often than not my N5 just shuts down. It's usually when I've doing something with the phone (today was flicking through my GPM library). I'll power it back on and it will boot cleanly and then (more often than not) power down again. Other times it will bootloop, but that's rare. It seems to me that if I let it boot up and then don't touch it for a while, it will stay up but I'm not sure that's consistent.
Anyone else seen or heard of the power button causing a powerdown instead of bootloop?
Click to expand...
Click to collapse
You will need to troubleshoot this the old-fashioned way. Have you installed any updates, apps, mods or anything recently?
Best case scenario would be that you flash a stock image without restoring apps, kernel or any mods. Run the phone for some time, couple of days or so, and be on the lookout for power downs or reboots. After that, you can try adding a few apps at a time and keep checking. If the phone reboots even with a clean factory image, then I'd have to say the hardware is faulty. Could be the power button, could be something else.
Try it out and let us know

Nexus 5 water damage - screen's all black - motherboard related?

Hello guys,**
Well few days ago I accidentally dropped my Nexus 5 in a glass of water for just 1 sec. So I immediately switched it off and wait a bit to let dry then restarted it, and all seemed to work fine. But just some days later and up to now the phone boots up all fine as usual to the lock screen, and from there I can pull down the notification bar (and navigate through it, activate/deactivate wifi, etc..) but when I unlock it to get to the home screen it becomes all back and nothing appears on the screen even though the phone is still on.*
It's really confusing and weird. When I call the phone it rings (so no signal or sound problem) but I can't still access the screen to take the call as it's all back and unresponsive.
Following some suggestions I disassembled the phone and cleaned it dry but same results again! So now I think the problem is somehow related to the motherboard, coz as you might notice on some of the pictures attached, it seems that some plastic parts have melt down to cover other smaller parts. Anyway guys,*I'm just wondering if some of you guys had experienced something like that and if you were luckier*to find a solution or any directives that could help. Or you even think that's a motherboard problem like, do you know any ways to fix that o buy a new one somewhere??
PLEASE!!
Sorry apparently, I can't publish links until I get like 10 posts or plus..
But anyway guys, I'd really appreciate your help.
Why did you power it on and short circuit it on purpose for??
Bump
@SekouCheikh
Maybe it's a coincidence that you dropped it in water and this happened a few days later. Once in a blue moon mine does something similar to this (although not usually as start up only after lots of use), but I think it's related to an app or xposed. I only notice it after installing a bunch of crap again. Maybe try a factory reset (do it though the computer) just to see if it is somehow not hardware related? That's what I would try first.
Help please
Ttt
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
-SmOgER said:
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
Click to expand...
Click to collapse
No, I just like to help
Help Op solve the problem please
Ttt

Categories

Resources