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:
Related
Hi everyone, I'm have an issue with my Nexus 5 and hoping someone here can tell me whats going on.
It started off with the sound always cutting out, and I have to press the back part near the "S" logo for it to return.
Eventually the screen would go black but I can clearly see a back light is on. Now not only does the sound cut out, and screen goes blank.
It has become very sluggish to reboot it. I hold the power button until the phone reboots "Google" logo appears and the android animation. Now during this time the phone will be so slow to the point of being crippled out and i have to reboot it again and again until it is normal speed returns. Often it will black out during this time.
I'm just trying to understand what is failing. I tried safe-mode and it still has the issue. I cleared cache, reset the phone everything, nothing appears to fix the issue at all.
edit: I forgot to add, when I'm on YT or listening to music or browsing the web, even though the screen is blank with just the back light on, the sound is still going (when it works). I get text/call notifications still during this time.
My Phone Details.
Nexus 5
Android version, 6.0.1 (MOB30Y)
no ROOT
No replies at all, I guess I may have to garbage the phone. Idk what else to do with this device to fix it.
Please don't throw it away.
You said that pushing at a specific spot fixes the problem (or improves the audio situation). This means that it's a hardware problem. I have disassembled it many times and I know the layout. Behind the 'S' of NEXUS is actually the motherboard cover, and under it are 2 connectors; one for the battery and one for an extra 'board' that is located right underneath the LG logo on your back cover. On that 'board' is your screen connector, and also the speaker rests on there, as well as the primary microphone, 3G and 4G antennas and of course the USB port. The connector for this extra board is actually located a bit to the left on the 'S' (when you look at your phone from the back, it's more below the camera).
Now I have to note this: While using my phone, I have experienced some UI hiccups. At random times (very rarely) everything would just freeze for a few minutes, though music would still play. The power button was useless apart from the hard reset, it was so badly stuck. This was a software problem, although it appeared MOST at one point when my motherboard was faulty. Since I got a new device, it happened again but only once. I'm not sure that this is what you are experiencing. If this is the case, then it's a software fault. Never happened on CM so you can give it a try.
But since it's probably a hardware problem, you can always check it out yourself. Obviously if you have warranty you are covered. Otherwise, you can try disassembling it, at least take the back cover and the motherboard cover off, it's ridiculously easy, there is a disassembly guide from ifixit (I think) online, just be careful not to break the clips of the back cover (xp talking). If you open it, keep away metal things and the first thing you do after you remove the motherboard cover is remove the battery (xp talking again). Obviously turn off the phone properly before you attempt anything. Everything is sensitive in there so be careful. What you should look for is the long connector that connects the extra board that is located at the bottom of the phone with the motherboard. That's what you are pushing so if it's not sitting correctly, then that's your problem.
Plus, everything in there, apart from the motherboard, is cheap and can be found on eBay so don't worry if something is broken (unless it's the motherboard, then no hope ).
I hope I helped.
Firstly thanks for the reply. I did manage to remove the back and get to the connector you were saying. I reseated this and noticed the phone was working much better. I noticed the following still.
When it starts acting slow/crippled pressing this connector fixes the issue. However once the screen goes black with just a backlight this method is rendered useless. Also sometimes when I plug in the wire to charge it will cripple and or go black. So I wondering if the board is shot as you suggested to order a new one, or is it the connector strip ?
Again thank you for the response.
It seems like this board is causing everything. First, check the connector on the motherboard. Make sure that nothing is wrong on the motherboard. Then you can remove the bottom black plastic thing that has the speaker on it and 2 antennas. Then, inspect this board. Check the connector of the display. There is only one big connector on it. This board is glued on the frame of the phone. You can remove it but do it carefully. Do it slowly so that you don't break it. First, remove the antennas extension cables from either this board or the motherboard, and then pull it out.
This board is definately responsible for the black screens and audio issues (unless your display is faulty, check its connector), but I'm not sure about the phone being sluggish. Since this board offers input to the motherboard, I suppose that it could be its fault.
Remove it and inspect everything. Then, if you want, you can order a new one. If you come across D820 and D821 models, I don't think that this part of the phone has anything to do with it so don't worry.
I will take a further look into this for sure, and report back. If you can provide which motherboard is required for my device, so I can also read into this and so that I may order it right-away. Is there any model number or something that indicates which board to order once it is open?
Thanks again!
omega59 said:
I will take a further look into this for sure, and report back. If you can provide which motherboard is required for my device, so I can also read into this and so that I may order it right-away. Is there any model number or something that indicates which board to order once it is open?
Thanks again!
Click to expand...
Click to collapse
You don't need to change the motherboard, not to mention it's very expensive and hard to find. What you need to replace is probably the flex cable that goes below the battery. For example this.
This is not model specific, you can use it with all available Nexus 5 models (D820/D821, 16/32GB) so it doesn't matter what device you have.
FYI, if you think that you should replace your motherboard (you probably shouldn't), you need to take into account the storage (16/32GB) and the network differences (D820 or D821, the only difference is about the 4G networking, the american version has some bands enabled and some others disabled, and vice versa)
Okay, I just ordered the replacement flex cable. It is going to take about a month before it arrives from HK , I hope it fixes the issues. I will respond to this post once it is here and installed. Thanks again.
http://www.ebay.com/itm/271660361300?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
omega59 said:
Okay, I just ordered the replacement flex cable. It is going to take about a month before it arrives from HK , I hope it fixes the issues. I will respond to this post once it is here and installed. Thanks again.
http://www.ebay.com/itm/271660361300?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
Click to expand...
Click to collapse
in the meantime, pray it isn´t a motherboard issue, the conector can go bad and lose a few solder joints
I have exactly the same problem... I unmounted motherboard and clean everything but didn't help to much... did you find any solution ??
Siamer no solution just waiting for my delivery of the part. However it is getting worse with the blackscreens and crippled lag.
omega59 said:
Siamer no solution just waiting for my delivery of the part. However it is getting worse with the blackscreens and crippled lag.
Click to expand...
Click to collapse
my is the same. sometimes is working for few hours without any problems and than starting again, on the biggining it was power button problem but not I don't even touch that button (I use vol button to turn on) and sometimes screen getting black (with backlight on) and can't do anything so have to reboot... it's so anoying! Hope that parts will fix it, please let me know if you will find some solution. Today I will open phone and clean all connections etc...
Thanks,
siamer
I believe the part may fix it. I noticed if i run my finger along the strip the phone may uncripple itself or just turn black all together. I'm hoping it fixes it. I will report asap but this HK shipping is so slow it will be a month. Also there is no tracking
ATM i'am just trying to becareful with it trying not to trigger the issue. I just did an OTA update using FlashFire (6.0.1 (MOB31E) i wish v.7 will be available for my Nexus 5 ha ha!
Also if the Nexus 7p arrives I may just buy it to replace this Nexus5.
omega59 said:
I believe the part may fix it. I noticed if i run my finger along the strip the phone may uncripple itself or just turn black all together. I'm hoping it fixes it. I will report asap but this HK shipping is so slow it will be a month. Also there is no tracking
ATM i'am just trying to becareful with it trying not to trigger the issue. I just did an OTA update using FlashFire (6.0.1 (MOB31E) i wish v.7 will be available for my Nexus 5 ha ha!
Also if the Nexus 7p arrives I may just buy it to replace this Nexus5.
Click to expand...
Click to collapse
Hi Omega59.
Today I bought air compressed can(name: air dust) and open my nexus 5 as much as I could. I clean everything, every connector, every cable etc. and last few hours is working fine... even power button is working ok. I will let you know in next few hours how it will be, hope will be still ok
Good luck!
siamer
[edit]
there is still same problem, working better than before, black screen not showing so often but still showing... I think tomorrow I will order oneplus3... Would be nice wait to see new nexus but how... :/
Yeah I'm not sure when the Nexus 7p will arrive, they not even advertised much. I will assume next year?
OnePlus 3 looks nice, but compared to Galaxy 7 it's a bit better slightly. You should check out comparison charts
Maybe they are making a OnePlus 4 soon.
oneplus 3 already ordered. I don't like samsung. I would say nexus "7p" or "pixel xl" will be launch october as always prabaly 4th of october - leaks saing that... next oneplus will be launch around july next year as I know. the only phone that I was thinking about was oneplus, htc10 or new nexus but can't wait to see nexus...
today by excident I broke screen in my nexus 5, got a little bit angry
Regards,
siamer
omega59 said:
Siamer no solution just waiting for my delivery of the part. However it is getting worse with the blackscreens and crippled lag.
Click to expand...
Click to collapse
You probably don't want to hear this, but if it's getting worse, it's probably because of the pressure you apply to it, you make it worse. Be careful when you apply pressure around the motherboard since it's very sensitive. You REALLY don't want to break the motherboard. So if you find yourself pushing on the motherboard too often, you might want to leave it and wait for the replacement part so you won't ruin it.
Waiting for your news...
My part arrived yesterday. I put it in was pretty easy, however the first attempt i had to redo the top connector bc it was still black screen and no audio. After I disconnected the top connector ran some alcohol over it, re-put the top part things are working okay.
Just a note, the little USB connector (charger slot) seems to be very tight compared to the old one. Maybe bc it's new and not as worn down. But even just to put the wire in, requires more of a push, same with removing it.
I will see how it goes before I can really say that was the issue. I will report after a few days about it.
siamer said:
oneplus 3 already ordered. I don't like samsung. I would say nexus "7p" or "pixel xl" will be launch october as always prabaly 4th of october - leaks saing that... next oneplus will be launch around july next year as I know. the only phone that I was thinking about was oneplus, htc10 or new nexus but can't wait to see nexus...
today by excident I broke screen in my nexus 5, got a little bit angry
Regards,
siamer
Click to expand...
Click to collapse
I don't think N7P will be out this year, they have not advertised anything and we are almost in Oct. Right now they are all rumors.
omega59 said:
My part arrived yesterday. I put it in was pretty easy, however the first attempt i had to redo the top connector bc it was still black screen and no audio. After I disconnected the top connector ran some alcohol over it, re-put the top part things are working okay.
Just a note, the little USB connector (charger slot) seems to be very tight compared to the old one. Maybe bc it's new and not as worn down. But even just to put the wire in, requires more of a push, same with removing it.
I will see how it goes before I can really say that was the issue. I will report after a few days about it.
Click to expand...
Click to collapse
When I changed my screen and housing it was difficult to slide the USB connector in too. Just make sure that everything is in place, there is a rubber think for the microphone, maybe that's what's in the way. Don't stress the connector too much.
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.
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.
To give some context, my S10e (Verizon SM-G970U) decided to boot loop out of nowhere. Since this happened, I have factory reset the phone, no success. I brought it to a local repair shop who said they couldn't fix it. Now I have flashed the phone with Odin and despite the phone being flashed it STILL is boot looping. At this point, I'm assuming something went wrong with the hardware but I don't even know where to start with that. If anyone has any suggestions I would greatly appreciate them.
Firmware used :
Download Samsung Galaxy S10e SM-G970U VZW USA (Verizon) G970USQU5GUBH firmware
Fast download latest Samsung Galaxy S10e firmware SM-G970U from USA (Verizon) with G970USQU5GUBH and Android version 11
www.sammobile.com
Vivala8955 said:
... it STILL is boot looping...
Click to expand...
Click to collapse
If it is a hardware issue (which sounds likely), there's an old electronics trick you might try: Power it off, put it in the refridgerator awhile, take it back out and power it on. This has work'd for me with stereo components, for example, as well as a phone. It once revived a hard disk drive long enough for me to capture important data. Oh, but the phone this has brought back for me, an S10e BTW, works only while still cold and has issues with charging while its temperature is low. Still may be worth a try.
MrGoodtunes said:
If it is a hardware issue (which sounds likely), there's an old electronics trick you might try: Power it off, put it in the refridgerator awhile, take it back out and power it on. This has work'd for me with stereo components, for example, as well as a phone. It once revived a hard disk drive long enough for me to capture important data. Oh, but the phone this has brought back for me, an S10e BTW, works only while still cold and has issues with charging while its temperature is low. Still may be worth a try.
Click to expand...
Click to collapse
Wow, I just did this and to my surprise it worked! Prior to this, I wasn't able to get past the Google sign in page on start up (on good attempts) but now I was able to get it all the way to the homescreen and even install some apps before my battery died. Any idea of what this could mean for the actual hardware? I.e. this means the battery needs to be replaced etc
Vivala8955 said:
Wow, I just did this and to my surprise it worked! Prior to this, I wasn't able to get past the Google sign in page on start up (on good attempts) but now I was able to get it all the way to the homescreen and even install some apps before my battery died. Any idea of what this could mean for the actual hardware? I.e. this means the battery needs to be replaced etc
Click to expand...
Click to collapse
Great; glad it work'd. Did you attempt to charge it while it was working? Mine actually took charging after warming up only a short time, once. Got it back all the way to 100% charged. But then it quit with dead black screen, and now revives only for a minute or two.
In the old days of individual transistors, we used to turn on a non-working electronic device and blast a shot of freeze spray on various components until the device started working; even with IC (integrated circuit) chips that have lots of transistors. This way, we knew which part needed replacement. But with today's phones, you replace the entire circuit board because the soldering is done by machines; it's too finely detail'd to replace one chip.
MrGoodtunes said:
Great; glad it work'd. Did you attempt to charge it while it was working? Mine actually took charging after warming up only a short time, once. Got it back all the way to 100% charged. But then it quit with dead black screen, and now revives only for a minute or two.
In the old days of individual transistors, we used to turn on a non-working electronic device and blast a shot of freeze spray on various components until the device started working; even with IC (integrated circuit) chips that have lots of transistors. This way, we knew which part needed replacement. But with today's phones, you replace the entire circuit board because the soldering is done by machines; it's too finely detail'd to replace one chip.
Click to expand...
Click to collapse
I haven't tried charging the phone when it's on. Only when it's off and has returned to room temperature. Seems to me that about an hour in the fridge equals about 5 minutes of screen on time until the phone heats up again.
As for the internal component's you bring up a good point. Even if I were to determine what is causing the issue, I don't have the will/technical know how to buy the parts and do it myself. Outside of just replacing everything, in which I'd just buy a new phone haha.
Vivala8955 said:
... I'd just buy a new phone ...
Click to expand...
Click to collapse
That's what I did. Look'd at lots of possibilities, ended up buying another S10e.
Hello.
For maybe the 5th time I just took apart my old 3a that my son's been using. I was going to replace the battery, but turned out the battery I'd ordered (OEM and fresh from the wrapper) was bad (puffing up). Needless to say, I didn't replace the battery just now. The old one was managing ok, so definitely wasn't dead. I removed it carefully, so figured I could just reinstall it until I got a better one.
Having put the phone all back together (unfortunately, breaking the cable for the fingerprint sensor along the way, but AFAIK, that would have nothing to do with my problem), I found the phone was bootlooping. Not just that, but once I took it back apart, I found that as soon as I plugged in the battery to the motherboard, it started to boot. Holding any combination of buttons didn't stop the bootlooping. I'm just seeing the start screen (it's rooted) and maybe a flash of the Google logo, then back again. I can't turn it off without unplugging the battery.
So now I don't know what to do with the thing. I thought I'd just put it back together and let it limp along for a while, but suddenly it's hosed. Has anyone else experienced this kind of behavior and found any fix?
Thanks
JimDandy68 said:
Hello.
(…) as soon as I plugged in the battery to the motherboard, it started to boot. Holding any combination of buttons didn't stop the bootlooping. I'm just seeing the start screen (it's rooted) and maybe a flash of the Google logo, then back again. I can't turn it off without unplugging the battery. (…)
Click to expand...
Click to collapse
Never took my Pixel 3a apart, but first thing I'd check would be power button - it might be stuck (always pressed), might be "shorted".
Tamsta_T said:
Never took my Pixel 3a apart, but first thing I'd check would be power button - it might be stuck (always pressed), might be "shorted".
Click to expand...
Click to collapse
Thanks, @Tamsta_T
I didn't want to complicate the story, but I did also replace the entire power switch. No matter, it does the same thing with the old power switch, the new power switch, everything connected to the motherboard, or nothing connected at all except the battery. Also, whether or not it's plugged in. IIRC, the battery had over 60% charge when I started this morning, and it's been keeping the phone going for a whole day. I feel like something must be up with the motherboard itself, but don't really know.
Could the touch sensor being broken actually cause this problem? That's the only thing that's different. I don't even know how that cable got broken, as I tried to carefully remove it from the motherboard. But it's done, and to test that theory, I'd have to buy another.
JimDandy68 said:
Could the touch sensor being broken actually cause this problem? That's the only thing that's different. I don't even know how that cable got broken, as I tried to carefully remove it from the motherboard. But it's done, and to test that theory, I'd have to buy another.
Click to expand...
Click to collapse
JimDandy68 said:
I didn't want to complicate the story, but I did also replace the entire power switch.
Click to expand...
Click to collapse
how is power switch connected to the motherboard? Is that connection 100% intact nor damaged? By the way, if fingerprint cable is broken, maybe that connector is damaged too and is causing short circuit?
And can you enter fastboot or recovery mode?
Sorry, this might have gotten buried in my last reply:
it does the same thing with the old power switch, the new power switch, everything connected to the motherboard, or nothing connected at all except the battery
Click to expand...
Click to collapse
I don't have the broken fingerprint sensor cable attached at all. Tried it once, but figured that was pointless if not counter-productive.
I've also cleaned all the accessory contacts, including the one for the power switch, using 91% isopropyl. The only thing I haven't done, and the last thing I can think to try, is to really hit the motherboard with compressed air, especially the contact for the power/volume switches. I just know it worked fine after taking it apart multiple times, before this last time.
If it's not some damage to or debris in the power-switch connector, at this point I'm thinking the motherboard's gone bad in some other way.
Asked over in iFixIt, and was informed that it may well be that not having the fingerprint sensor attached could cause POST to fail, so I'm going to try a new one and see if that helps.
JimDandy68 said:
Asked over in iFixIt, and was informed that it may well be that not having the fingerprint sensor attached could cause POST to fail, so I'm going to try a new one and see if that helps.
Click to expand...
Click to collapse
New fingerprint sensor, per this recommendation. Phone still endlessly bootloops. Seems to be permanently powered on, cannot stay in bootloader/fastboot mode for more than about 2 seconds. The buttons all register -- e.g., if I hold down all 3, the phone goes black, but only until I release them. There seems to be no way to intervene in the problem. I think I may have to give up on this, unless anyone has further suggestions (beyond a new motherboard, since I've already invested too much time and money in it).