Related
Alright so I know that there has been some discussion on this POS model of a phone, but I would love to know before I get the digitizer replaced, if it's a bug or something else.
I guess it started about 8-10 months ago, my brother bought the phone from Mobilicity here in Canada and he let his friend borrow the phone for a call. She dropped it on the cement and the glass cracked. The LCD itself is functioning, but when I got it I had to wipe the device through the recovery menu using Power-X then ALT-L. Anywho every month or so since I got it a few months back for free and long story short it's been glitching out constantly.
Now finally the screen barely works and until I got the "smart" idea to recover it again thinking it would fix but the screen only reads the bottom right side and nothing else. Oh and I'm stuck on that stupid Touch Android to Begin screen. So I'm pretty much SOL'd. Basically my question is this; is it the digitizer, corrupted FW, the phone is just shot or all of the above?
If it's repairable could someone please tell me how to enable usb debugging without the touchscreen or in the very least bypass this Android screen with the keyboard, PC or both? I used Droid Explorer a couple days ago to even control the screen with ScreenCast?
I know of ADB, Input Events, and stuff like that but I really can't figure out what to do. I thought about Clockwork but because the phone has a locked bootloader, I wasn't sure I could even install. Hell I even consider using my other phone to do a NANDROID backup but even that won't work.
So in short what the hell do I do?
Hi everyone,
I'm experiencing really wierd behaviour with my HTC Desire S. I'll try to tell the story as it happened, so you may have the best grasp on what's happening to me. Here's the thing: yesterday, I charged my HTC on the wall plug as almost every night (y'all know how it is with smartphones, always needing to be charged ). When I unplugged it on the morining, the green LED stayed on. Not cool. I can't really remember if it was turned on and stuck or already turned off at that time, but I had to reboot the phone. Okay, that can happen, phones have to reboot sometimes.
And then, it did not boot. Instead, it was stuck on the bootscreen. I looked around on the internets, but people seemed to have boot loops or devices stuck after the "quietly briliant" part. Actually, mine was stuck before that part. It didn't even play the funny sound and show the fancy animation: it was stuck on the blank screen with only the HTC logo.
I tried many things, like praying pagan gods and removing the battery, let it cool for a while, boot and wait to see what happens for more than 30 minutes, boot it while plugged on the wall plug... I think I was about to get to the "I'll have to make a factory reset, then" line when I tried to see what dmesg would tell me if I plugged the phone on my computer. Note to self: always try to plug to computer. It did boot completely. The victory dance was almost completed when I was invited to enter my PIN code. My touchscreen did not respond. Damn.
So I had to reboot. Again had to remove the battery (I don't like that, but what choice do I have?). Now it always boots completely (that's a good start), but my touch screen seems completely unresponsive. I can't access anything, can't enter my PIN code or unlock the phone when there's no SIM.
That's where this forum comes in: I've not given up. You see, my phone has USB debugging activated (yeah I know, the thread's title spoiled all the story). I'm pretty sure this means adb can help me in some way to troubleshoot my device. adb shell gives a nice UNIX-like shell, yay, that is relevant to my interests.
My phone has never been rooted. I've looked into it (that's why USB debuging was activated), but I wasn't 100% confident it would work, so I gave up before ending up bricking my phone (duh, too late, haha). It's running the last Gingerbread version distributed by HTC in Belgium (2.3.5, I think, without any certainty), with the last Sense version related (could it be 3.0.3?).
tl;dr: Unrooted phone with unresponsive touch screen, debugging mode enabled, trying to find what's wrong.
So here's what I'd like to know: is there any way to try to force start my touch screen with the help of adb? Where's the related log, the one that should display the error(s) that occur(s)? Should Bill Murray play in the next Batman? If root is needed, do I have a way to use a temproot exploit in order to fix my phone once and for all?
Any attempt to help will be greatly appreciated. This is my first post here, I hope it's clear enough, and not too nooby for you guys. Also, that I didn't break any rule (I watched/lauged at that video about noobs to xda). Btw, I'm quite confortable with UNIX shells, so don't avoid cli-related answers if that may happen to be helpful. Also, I'm not at home right now, but I'll follow this thread with a lot of interest anyways. I'm back on a regular connection next sunday.
Have a nice day! And sorry for the long post (but believe me, I'm even more sorry to admit I can't investigate further on my own, now that is frustrating).
Okay, I'm back.
It makes no sense. I let my phone on for a few days, then suddenly, probably out of boredom removed the battery, put it back and rebooted. I distractingly tried to unlock it… and it worked.
I have absolutely no single clue on what happened. And I'm still quite concerned, because this means it can happen again without any warning.
I'm gonna give a shot at HTC's support in order to ask them what I can do to locate the problem if there are traces. I'd really, really like to read all the logs (and logcat didn't show anything interesting).
If anyone has a suggestion, feel free to shoot it. I'll try to keep this thread updated in case someone has the same problem.
Duh, just got an anwser from HTC's support. Totally useless, they told me to try to reboot in Safe Mode in order to see if the problem happens again. Well, even in normal mode it has not failed for two days. GJ, guys.
I'm really willing to meddle in my system in order to see what could have gone wrong. I'd especially like to see if there is any way to see whether there are HW faults or not, since I'm suspecting a temporary TS chip failure, which can happen again at any moment. I'll be reading some documentation about Android's system and its logs.
Yeah, I know I'm talking a lot alone, but if someone ever has the same problem, he might be able to see what I've gone through, so I'm documenting as much as possible. =)
adb bugreport
Hi
I think I've killed my phone. I have voided my warranty. Please help/comfort me!
The story so far...flashed stock ROM with ARHD, no problems everything fine. Broke screen in pocket while at work (fuzzy lines across screen), phoned htc to explain problem, they told me to send in for repair but said that the repair would not go ahead if any mods such as custom ROMS had been installed - I told the guy that a custom ROM had been installed (probably my biggest error!). Bought new lcd/digitizer combo from ebay (ukeasybuy), and installed following an online guide (I was very meticulous and followed the guide to the letter with great care). Initially seemed fine but then quickly started doing weird stuff on its own accord, not responding to button/screen touches, would have to press the power button twice to get it to play normal. Yesterday the phone threw a wobbly and crapped out, switched itself off. Tried many times to power on, eventually managed to get into 4ext recovery where I started a restore to earlier nandroid backup, phone switched itself off again after about 20secs through the restore process (battery at this time was at 57%). Now can't seem to power on at all (tried loads of times), no charge light when plugged in, seems bricked.
When installing a custom ROM if you brick your device does it happen instantly or is it something that can develop over time? Only that for a brief period after installation it seemed to be fine, I made sure I had flashed the correct firmware package for the ROM.
I have done some research, but stumped on what to do now...my only thought is that I do have gadget insurance through barclays but wonder if they will just refer me to HTC??
Your thoughts and advice greatly appreciated..
Xenon
Bump
The turning off of the device itself can be a precautionary measure to protect itself. I'm guessing maybe the LCD was installed wrong and is causing a short within the board.
Sent from my HTC Sensation 4G using xda premium
I followed the iFixit guide to install the new screen/digitizer.
As I mentioned I was very careful to follow it carefully, the only extra thing I did was to add some double sided sticky pads inside to stick it back together again as the thin tape supplied was damaged and discarded when taking the phone apart.
Should I try and take the phone apart again and look for any mainboard damage and/or potential areas where shorts may have occurred?
What do you think about the insurance cover, is it worth a shot? what would be the best way to approach the subject?
Many thanks!
Xenon
Maybe you did install it correctly, but there could also be the possibility that the screen is defective. But i would suggest checking the main board for a short.
Good luck
Sent from my HTC Sensation 4G using xda premium
I have taken the device apart again, but no signs of any shorts / problems or anything suspicious. I don't want to spend anymore cash on a new screen without knowing its that that is causing the problem.
Perhaps its one for the scrap heap
talk to whoever supplied you with the screen and tell them you think the screen is defective. say you have installed it to the letter and it is giving you issues. any respectable ebay seller should be willing to hear you out at least. hope youve not left feedback already though as they may think your a chancer :/
Unfortunately feedback was left once I first turned on the phone and the screen lit up. I will give it a try but I won't keep my fingers crossed!
What about the gadget insurance that I have, is it worth trying to get the phone repaired or replaced through them, or will they just send me back to HTC because the phone is less than a year old?
I'm fixing an infuse for a friend who needed the screen replaced simple enough job so I thought as I repair phones and electronics as kind of a hobby. However the replacement screen isn't responding to any kind of touch at all. It displays the puzzle piece lock screen and everything else even shows there's been some missed calls ect. yet will not respond to any kind of touch. I think it's a calibration issue but I can't get passed the lock screen so there's no way to change the setting. Honestly I'm most worried about all the media on the phone most (pics, videos, contacts, ect )
If there is a way I can retrieve that off the internal storage I'll feel better about taking drastic measures. Other things I've noticed is an unusualy long boot up time hanging at the white Samsung letters but this is the first time I've dealt with an infuse so I'm not to sure on that.
Any advice is appreciated.
Thanks,
s1im
There are different versions of screens or maybe it was revisions. At least for the LCD +digitizer assembly. Rev.6.1 and 6.2 and 6.3 if I remember correctly.
Edit....here is a link for reference, also two of the screens were interchangeable but not all three. Sorry I don't remember which ones.
http://item.mobileweb.ebay.com/viewitem?itemId=180914982430&siteId=0&isClassified=false
Edit....my statement regarding interchangeability may not be true. The screen I bought could be used as a replacement for two of the rev numbers. That could mean that it is backward compatible but the other one isn't forward compatible.
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
s1imch4anc3 said:
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
Click to expand...
Click to collapse
Correct mine had a sticker on it.
Bummer I have no idea what kind of screen she had I threw it away as a jumbled mess is there any other way to find out what screen it was... either way thanks for the replies
Wish I could answer that, but here is another screenshot. It shows one for 6.0/6.1 and another for 6.2 so my original numbers were off. Did the new one say what it is?
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
s1imch4anc3 said:
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
Click to expand...
Click to collapse
Just guessing but maybe adb. You could try to edit the title of your thread or start a new one about this question.
Edit..I have an idea but first a few questions , is this phone stock, and would you be comfortable flashing a kernel if it is? This will give you CWM recovery which has mount USB storage as an option in it. All this can be done with the physical buttons, power and volumes.
I found something that may work without having to make software modifications so I'm going to try that first and if not I'll get back to you...
To answer your questions tho the phone is stock and I've rooted /flashed a couple phones with no problems before so I'm OK with giving it a try
Again I'd like to thank you for your continuous help
You should be able to pull everything you need with adb...but the problem is, is adv enabled? And can you pull a whole directory? I doubt you know individual file names for each media file, not to mention that would be a long tedious process as there are likely well over a 100 if not in the 1000s of music/pics/vids
Well..looks like you can pull a whole.directory (sdcard)
this thread may help http://forum.xda-developers.com/showthread.php?t=744454
Btw...you don't have to be rooted to adv pull
Sent from my HTC PH39100 using Tapatalk 2
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
s1imch4anc3 said:
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
Click to expand...
Click to collapse
ADB was the first thing I thought of, but flashing a kernel with custom recovery in Odin should allow you to get into USB storage. I am not familiar with the stock recovery but you could see what options are there. I believe it would be from device powered off hold volume up+volume down+ power buttons then release power at Samsung screen.
Were you able to resolve the screen issue with the different version? I am having the same problem.
I have had extremely bad luck and all sorts of dramas including frying the mainboard of my T-865 while attempting to flash TWRP on my way to get it rooted. I will get my tablet back a few days later after paying 550 bucks for the repair on top of the purchase price of the tablet itself 10 days ago (of course of out warranty since I unlocked the bootloader and tried to install "unauthorized software" according to their warranty terms)
My simple question now is, is there is a way to get the T-865 rooted without having to install a custom recovery (which under no circumstances I will attempt again)? All I need is root, nothing else.
Thanks for the advice
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
jaidev.s said:
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
Click to expand...
Click to collapse
Dearest jaidev.s.. it's quite of a long story (and a surprising one at that) as I have been flashing, testing and even helping build several custom ROMs for Samsung deviced in the past 12 years without ever getting stuck in a truly unforeseen situation.
To make a very long story short, after doing all my homework through all the available threads and feedback I could find on the matter, I ventured to unlock the bootloader, install TWRP custom recovery, required custom kernel and magisc root files for my T865. And yes, I followed precisely the available guides on it from our community. Things all went pretty much as planned and I eventually booted into a successful fully rooted session on my tablet. I tested all of the tablet's native apps and functionality, installed Root Explorer and a few other apps that I had backed-up APKs for. My session was about 30 minutes long, I never connect to any data in stayed always offline, after which I decided to reboot the tablet. And then, meltdown.
The tablet immediately refused to restart again, completely bypassing the initial standard Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. With the help of some other developers we all ventured together if my firmware was actually from another region, all of which I tried without any success. Eventually the tablet got stuck in a state that would not even turn off anymore even if I forced it via the volume down and power button commands. I eventually just waited out until the battery exhausted itself and then that was that.
Upon taking it to Samsung for repair where within seconds they realised that I had unlocked the bootloader and had tried to install a custom recovery, they came back about half an hour later explaining me that the hardware itself would not read or write any data any more despite their efforts, for which they would have to replace the mainboard.
I am yet to try and understand how the the tablet stopped functioning upon a reboot when up to that point everything had been flashed correctly and I had managed to do a session with everything properly configured. This said, I'm facing a $550 repair to what was an $800 tablet purchased just 10 days ago. I will obviously now not venture to try to install custom recovery again. I believe my tablet might have been a one-off with some sort of a preexisting hardware glitch that got ignited by the custom flashing that I did.. I really don't know and it really doesn't matter. At this point as I am about to collect the repaired tablet in a couple of days, the only thing I am interested in doing (a must for me on any device) is to achieve root and let it be. I don't want custom recoveries, kernel overrides or anything else other than having root. Thus my search on what will be be the best venue I have how to get the tablet safely rooted without messing with TWRP again or trying to mod the bootloader. And that's pretty much it..
And let me state, I have received nothing other than truly overwhelming support and help from lots of members of the community on my particular case for which I am extremely thankful and appreciative.
PS - I also have a Note 10 plus, recently purchased to finally replace my daily driver Note 8 that I've had for almost 3 years. Needless to say that I am absolutely dreading about the thought of installing a custom recovery on it as well and achieving root, and having again any kind of bad luck to get myself stuck in another nightmare again. I will first deal with the tablet, and if that eventually goes well, I will try to gain the necessary courage to get myself to flash TWRP and root on it without destroying it next. More than 12 years doing these things with nothing but success on dozens of devices, and suddenly here I am.
Part of me is wondering if Knox's eFuse tripping could have been the reason the board got fired? Perhaps a fault in that. Can't see any other reason reason why modifying software would cause a catastrophic hardware failure.
Anyway, as far as I'm aware the only other way to achieve root is to patch your stock OS in Magisk, then flash the modified file as detailed in this thread...
https://forum.xda-developers.com/galaxy-note-10+/how-to/guide-how-to-root-note-10-t3960031
Which is originally linked from This Thread
I've not tried it myself and it's a process from before TWRP was developed for the Tab S6 - So, you should do further research on it before jumping in to ensure nothing has changed.
Precisely why I am not installing twrp. The threads pages are having so many varied info and people getting bricks following steps, i feel discouraged to try root.
Tab s6 gonna be my first phone in 10 years that m gonna not root. I am using android since éclair and rooting.
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Extreemator said:
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Click to expand...
Click to collapse
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
VeEuzUKY said:
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
Click to expand...
Click to collapse
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
mac231us said:
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
Click to expand...
Click to collapse
Haha, I absolutely agree with you
I'd love a 17" Tablet. Lol. Personally, I don't like any Tablet less than 10" - If I want something small, I'll use my phone.
@VeEuzUKY did you get your Tab rooted?