I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Hey everyone, I'm new to android and tried something just to install a custom ROM. I flashed the kernel and tried to install a new one and I thought it was going well when I heard the woman talking through the phone, but apparently not... Now when the logo shows as it starts but it never makes it pass there.
It shows something like TV static and then reboots again and again.
It hasnt stopped since... I really feel bad cause i feel like a failure and thats the only good phone i have ever gotten...
Ive also tried the recovery mode, that doesnt work. The logo at startup gets brighter then reboots agaain ans again... Please help me.. Please asap so i can use it finally... Thanks alot
Oh sorry i forgot to state the phone specs , im new here...
Samsung Galaxy S 4G
2.2
Couldnt get it updated to 2.3
Thanks again guys.
StrugglaREP said:
It shows something like TV static and then reboots again and again.
Click to expand...
Click to collapse
As the cobwebs clear, that sounds like problems with bootloaders going from Froyo to Gingerbread. I vaguely remember something about "rainbow" screens if you didn't follow the right steps in the transition.
I think your best bet is getting the Heimdall "one-click" approach to work for you. If you don't have a custom recovery running, there aren't a lot of choices.
@lumin30 wrote up a great set of instructions that I would follow carefully.
It's pretty hard to hard-brick an SGS4G, so breath easier...
I'll give it a try, thanks!
jeffsf said:
As the cobwebs clear, that sounds like problems with bootloaders going from Froyo to Gingerbread. I vaguely remember something about "rainbow" screens if you didn't follow the right steps in the transition.
I think your best bet is getting the Heimdall "one-click" approach to work for you. If you don't have a custom recovery running, there aren't a lot of choices.
@lumin30 wrote up a great set of instructions that I would follow carefully.
It's pretty hard to hard-brick an SGS4G, so breath easier...
Click to expand...
Click to collapse
Thanks for answering so quickly, I'll be sure to go and try it out right now and see what happens. I really hope th phone connects to the computer atleast cause it keeps restarting itself... as I said I'm really new to Android I was just trying to update the kernel toget the ROM able to update so I can put on a custom one and get the apps that I really need that wouldn't work on 2.2
But Thank you very much , I'll get right on it and see what happens and say whether it worked or not
So I had a rooted Galaxy Tab 4 10.1 that I didn't have any backups for and I stupidly changed the DPI of the screen and rebooted the device and it started up in bootloop and I tried recovering it and nothing would work. So I finally settled on the wipe and factory reset, and now it starts up VERY SLOWLY, and the start of the set up for the device shows up but constantly I'm being bombarbed by TOUCHWIZUI has stopped working and 3 other things keep popping up saying they have stopped working. The touch screen barely works.
I have no idea what to do. I have no backups. I am not that familiar with android. I am downloading the stock firmware and am going to try to put it on with odin but I doubt it's going to work.
Can someone give me some advice on what to do? I would REALLY appreciate it.
Sincerely,
SalvelinuxFontinalix
BTW. The tab is the SM-T530NU Canadian (Wifi) version. The firmware I am downloading is the T530NUUEU1ANI1_T530NUXAC1ANI1...
Can I use ODIN to flash this firmware from my PC onto the device or will it be a huge problem if the tablet has been wiped and factory reset and is missing all sorts of information?
Your gonna need to flash the stock rom for the device.
Thank you for your guidance!
zelendel said:
Your gonna need to flash the stock rom for the device.
Click to expand...
Click to collapse
Thank you so much I did what you said. I found the stock rom and "flashed it" I got it back to exactly how it was when I got the tablet! I was unsure how to do it but I learned a bit on my own form the search feature of XDA. I found the stock rom out of a list of many different ones and I found the correct ROM for my country and area and flashed it on with ODIN using my PC and it rebooted and was brand new. I re-rooted it and decided not to alter the DPI of the screen. It's nice enough as is.
Thanks Again! Zelendel! You are a life safer! Oh and BTW...is using ODIN to transfer the stock ROM onto the device considered "flashing"? Or is there some other way people flash devices?
Thanks again I'm so thrilled I don't have a broken device haha. THANKS!!!
Sincerely,
SalvelinuxFontinalix
SalvelinuxFontinalis said:
Thank you so much I did what you said. I found the stock rom and "flashed it" I got it back to exactly how it was when I got the tablet! I was unsure how to do it but I learned a bit on my own form the search feature of XDA. I found the stock rom out of a list of many different ones and I found the correct ROM for my country and area and flashed it on with ODIN using my PC and it rebooted and was brand new. I re-rooted it and decided not to alter the DPI of the screen. It's nice enough as is.
Thanks Again! Zelendel! You are a life safer! Oh and BTW...is using ODIN to transfer the stock ROM onto the device considered "flashing"? Or is there some other way people flash devices?
Thanks again I'm so thrilled I don't have a broken device haha. THANKS!!!
Sincerely,
SalvelinuxFontinalix
Click to expand...
Click to collapse
Yes it is. There are other ways with custom recoveries but that is only for custom rom flashs
Hello. Today I tried to downgrade my phone I don't know what was I thinking, but I installed lost of custom ROMs before and stock firmwares too with Odin, so i kinda know how flashing works so I never thought it will be a problem. But after odin successfully flashed my 4.4.4 firmware onto my A5 i restarted the phone, and it wont power up, go into recovery or download mode, or EVEN CHARGE!! it's practically completely dead. Can someone tell me what should I do considering the fact that this is a unibody phone so very hard to cut the power off AND not very much development for it, i can't find debrick images or anything. Somebody knows what should I do? Thank you very much. Oh, and I can't get it to service because of the fact that the screen glass it's a bit shattered its out of warranty so I can't tell them its not my fault and tell them to replace the device. Thanks again.
Mrelenschi said:
Hello. Today I tried to downgrade my phone I don't know what was I thinking, but I installed lost of custom ROMs before and stock firmwares too with Odin, so i kinda know how flashing works so I never thought it will be a problem. But after odin successfully flashed my 4.4.4 firmware onto my A5 i restarted the phone, and it wont power up, go into recovery or download mode, or EVEN CHARGE!! it's practically completely dead. Can someone tell me what should I do considering the fact that this is a unibody phone so very hard to cut the power off AND not very much development for it, i can't find debrick images or anything. Somebody knows what should I do? Thank you very much. Oh, and I can't get it to service because of the fact that the screen glass it's a bit shattered its out of warranty so I can't tell them its not my fault and tell them to replace the device. Thanks again.
Click to expand...
Click to collapse
Hi
thank you for using XDA assist
Im really sorry to hear that OP,
Cant see any relevant for your device here at XDA but i can route you over here for your questions about your device..
http://forum.xda-developers.com/android/help
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
elboobio said:
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
Click to expand...
Click to collapse
flash a custom recovery, and install this, https://builds.unlegacy-android.org/aosp-4.4/espresso/ua_espresso-4.4.4-20171105172717.zip
Thanks for the reply. I have attempted to flash a recovery, however every one I've tried fails and tells me 'NAND write failed'. I tried the TWRP recovery and philztouch. You don't have a link to a recovery you think might work? I'm pretty sure I've been using recoveries that should work, but you never know.