I was trying some of the 1.2 ROM's on my gTablet when the touchscreen function started to fail. At first it was slow to respond and then became totally unresponsive after several reboots. Now I cannot get a touch response from the screen or the side buttons.
I was able to NV Flash and even load other ROM's but the screen still does not respond. I thought it was likely a problem with failed hardware but I noticed that when I was using CWM the home and back buttons were totally responsive so now I am thinking there may be a hidden software issue that I could fix.
I have tried the calibration.ini with no result and I would not be able to run the recalibrate apk as it would require touchscreen response to run it.
I have been reading the threads and have not found any results on fixing a totally locked touchscreen. Can anyone help?
wipe the tablet clean and start from scratch. Most likely it is software based if the buttons work in CWM. Use nvflash to wipe it.
Boot into ClockworkMod.
Go to Advanced
hit key test
Press all the buttons. If you get two numbers for each press, it thinks you have a finger on the unit all the time.
Related
Alright, so here is what's going on. I've flashed my phone a few times now and it's always been successful. I've also installed PointUI in the past on my Touch Pro, along with a few other apps most of which don't do anything significant(S2U2, advanced config, etc.).
Now the problem is, my hard key buttons will simply NOT respond. Only the power key, volume keys, and keyboard keys work. None of the front ones do. My other problem is that when I try to flash a new ROM now, it doesn't take. I've re-flashed my phone to the Sprint stock ROM and have since tried putting NRG's ROM onto it but whenever I flash his ROM and start my phone, it restarts on the HTC loading page(Before the red text shows up).
I've tried doing a hard reset, I've tried flashing back to the original ROM, I've tried all I can think of. Any help would be appreciated! Thanks!
While trying to install a new rom on my droid eris i used rom manager to backup and install from my SD card.
IT said everything went fine, however when the phone rebooted I got stuck in the Nexus boot loaded screen. I do have a past nandroid back up..
but here is the problem. I only have the android system recovery, and my trackball will not allow me to scroll down past "reboot system now" does anyone have any suggestions on how I could possibly fix this?
The trackball issue is probably Independent what you can do is take your eris, put it face down on a piece of paper and move the whole phone rolling it on the trackball do it in figure eights like 10 or 15 times, then see if that fixes the trackball issue.
As far as the phone itself. If you used rom manager, correct me if I am wrong, but that means you used clockwork mod recovery right? Clockwork has had a history of bricking Droid Eris devices. It doesn't sound like its completely dead but it is a definite possibility.
Try the trackball solution and get back to us and let us know if that fixed the scrolling, let us know if the previous nandroid worked. And uh, did you happen to take the next step and go s-off on your bootloader so you have access to fasboot? The way to check that is hold power and volume down when turning it on and it should say in the upper right S-on or S-off.
Edit: Also if the trackball thing doesn't work, people have had success in getting the trackball to move down by lightly pushing a plugged in USB cable toward the back of the device, not too hard, but gentle. In addition if none of this works, but while in H-boot mode (as discussed previously, vol-down + power) you can get the device recognized by your computer, an official RUU, which is an application that runs from your computer that basically rebuilds your phone from scratch to stock. Then start over with rooting and such. And I'd advice you to get the SDK and go it alone from here because honestly, its not difficult and the more intermediary programs you introduce the more issues you open yourself up to.
Let us know, and if I sound condescending at all, please err on the side of positive interpretation, I just had a cruddy night and chipped the heck out of my back tooth and I'm tired, so no offense intended.
Edit 2: Lulz, I just realized that Its been so long since I've used the stock android recovery, but did you try the volume up and volume down buttons to navigate and the send button to select? Either way, if its the stock recovery I don't believe you will be able to load a nandroid backup, so the RUU is probably your only option.
Here's the scoop:
After successfully installing CM 7.1 on my SGS2, I started to do the same on my girlfriend's. The procedure was as follows:
1) The phone was already rooted so I booted into CWM Recovery 5.0.2.3
2) I wiped data/factory reset, cache and dalvik cache
3) I installed the CM 7.1 ROM from the SD card. Everyone is aware of the bug in the CM 7.1 installation so I installed the CM 7.1 ROM again without rebooting as required. There were no errors during the installation.
4) I then rebooted the phone through CWM and it booted to Android OS just fine.
However the big problem is that my touch screen does not accept any input. A few seconds after Android OS starts up, the screen seems to dim and no matter where I tap my finger, my taps are not recognized. The soft buttons (menu, back) and the hard buttons (home, volume up/down, power) all work fine. In fact, they even bring up events in Android OS (eg. holding the menu key brings up a key board, volume key turns up/down the ringer volume). However, the touch screen or digitizer just are not working. Obviously rebooting the phone does not help. I also tried booting back into CWM Recovery and installing the Google Apps. When the phone restarts it asks me to "Touch the Android to begin" but again it does not register any input.
Through ODIN I tried to go back to two stock roms (XXKH3 and XXKI3) but those did not fixed the problem either. Obviously, these were flashed through Odin and prior to flashing them I cleared the data/cache/dalvik through CWM Recovery before hand. I also tried two nightly versions of CM 7.1 (115 & 116) as well as Litening ROM 6.1 and Villain Rom 3.0 but those did not help either.
My feeling is that this is not a hardware problem, rather a corrupted driver through one of the ROM installation processed. While I am fairly well versed when it comes to problem solving technology issues, I am not familiar with the Android OS structure to go any further. For example, are the drivers for the touch screen and digitizer embedded in each ROM or on a secure portion of the physical phone?
Please let me know if you have been in a similar situation or whether you can pass along any tips that I should try. Again, my girlfriend's phone was working perfectly before the ROM upgrades. And I know my upgrade process was correct as my phone that I upgraded just an hour earlier is running CM 7.1 very well.
Any help is appreciated.
Thanks!
UPDATE & Help Still Needed:
This morning I tried the latest nightly build from @codeworkx. The same problem occurred - I could not use the touchscreen at all. Boots into Android perfectly, but does not allow any touch input including unlocking the screen once it times out. While the phone is booting (which is incredibly fast and great), during the CM logo, the screen dims which I think is the first clue that either a power saving setting is kicking in or it is shutting down. I can make it bright again by hitting the home key or one of the haptic keys which all work great.
What are some next steps I can try? I don't think is a hardware problem because I can't think that it would creep up so co-incidentally at the point where I was upgrading the phone (which I have done many times successfully before). Is there a log or something that I can post or review about the start up process to let me know which processes were successfully stated and which ones failed to start?
Thanks again.
Are you sure that the version of your girlfriends phone is I9100 ? That's the only thing I can think of.
I've searched the forum for you, and some people advice to use a .pit file with flashing a stock rom.
Using a .pit file is highly disadvised because it could seriously mess up your phone. It will format your device and if it fails, you could lose download mode and recovery.
If you really can't find an other way, you could give it a try. Make sure that no proces on your pc can interupt the flashing with odin, make sure you use a decend usb cable. Just make sure the flashing does not fail.
Find a stock rom with a .pit file in the package and load the .pit file with all the other files for flashing (DO NOT ONLY FLASH THE .PIT), also check repartition. Any questions?
Make sure you have read about the dangers when using .pit files. I have really no idea if it will actually will fix your problems, but I think it's worth a shot. Use my advice on your own risk of course.
/edit I asked someone to give some advice about the .pit, hold on His advice: It's ok as long as you know what you are doing and are aware of the risks.
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
jje
I have an issue that you may or not be able to help me with, I recently flashed CM10 & used the appropriate gapps and everything seemed fine except that I kept getting a server error while accessing the playstore, also this weird thing occurred, I was able to use the left arrow key at the bottom and also was able to use the internet button , but for some reason the home button on either the display or the n button would not bring me back to the home screen when pressed, I checked settings and nothing worked, I finally gave up and tried to flash CM10 again but still the same issue, I then saw the 10 touch firmware app so I figured that may do the trick but that didn’t work either, I then tried to flash down to CM7 and this time it got worse, the touchscreen stopped working all together, I tried using my fingers and even a stylus but the screen didn’t recognize any touches, I then gave up on that and used the repart image and went back to stock 1.4.2 and everything seemed fine until the set up started, none of my screen presses worked, I tried then to flash up to 1.4.3 and still the same, I even did the master reset trick with power, n & volume key and still the same somehow, whatever I did turned off the touchscreen, volume keys & power button works but my screen doesn’t, is there a fix for that or am going to have to just give up and have BN swap it out, thanks in advance for any help, I have a 16gb NT
You need to reflash the stock 2 touch driver. Once you install the 5/10 touch driver you can't leave cm10 without reflashing the touch driver again. There are several threads in the dev forum telling you what to do to fix this. Any of the cm10 threads should have the information. Search nook tablet touch drivers .
Sent from my CM 10 SD nook tablet. Thanks devs.
SlowCobra96 said:
You need to reflash the stock 2 touch driver. Once you install the 5/10 touch driver you can't leave cm10 without reflashing the touch driver again. There are several threads in the dev forum telling you what to do to fix this. Any of the cm10 threads should have the information. Search nook tablet touch drivers .
Sent from my CM 10 SD nook tablet. Thanks devs.
Click to expand...
Click to collapse
Could you explain what the 5/10 touch driver is on CM10, also I see that you run CM10 off a SD card, do you think the system works as quick running of the SD opposed to running off the emmc, I personally had a nook color that I flashed dual boot stock BN and CM7 off the emmc but I can't seem to find any threads on how to do that without dual booting from SD, and thanks for your help
devious20000 said:
Could you explain what the 5/10 touch driver is on CM10, also I see that you run CM10 off a SD card, do you think the system works as quick running of the SD opposed to running off the emmc, I personally had a nook color that I flashed dual boot stock BN and CM7 off the emmc but I can't seem to find any threads on how to do that without dual booting from SD, and thanks for your help
Click to expand...
Click to collapse
As I said in my first post, all the information about the 5/10 touch driver(firmware) can be found in one of the CM10 posts. It is to allow for 5/10 points of pressure that comes with the Nook HD and HD+ instead of the stock Nook Tablet 2 points of touch. As for flashing the EMMC with a dual boot, no the Nook tablet can not do that thus the reason people are running dual boot from EMMC and SD. I do not notice any speed difference running from an SD card and I still have access to the stock OS with a simple reboot from within CM10.
It doesn't require removing the SD card or any weird stuff people are doing like hopping on one foot while patting their stomachs to get it to work. Recently I have seen a lot of posts by people that either fail to read, fail to understand what they have read, or just go straight to posting the same question that is literally on the same page of the forum because they failed to spend some time searching and reading.
With my current configuration from a completely off state it boots to CM10. If for whatever reason I want to boot into the B&N Rom I hold the power button to get the menu options and choose reboot. After 2 mins or so I am in the stock rom. If I want back to CM10 I shut it off then turn it back on.
I experienced similar problems as you with CM10 and discovered that I was using the 4.2 version of GAPPS instead of the 4.1.2 version. Perhaps that was what you were seeing in the beginning.
My phone (Galaxy S2 i9100) is blocked. I don't know the screen unlock code and at the same time my power button is not working due to water damage. So I cant use the phone.
I attempted to fix the power button/board first with some isopropol treatment but that didn't fix the problem. I then bough a jig from ebay and managed to get into download mode. I flashed a stock rom onto it thinking this would solve the problem, but it rebooted nicely and gave me the same lock screen (and I dont have the password).
I've been trying everything to get this phone restored, but obviously since I dont have access to the software and I cant use the power button to get into recovery mode, I am a bit stuck.
My ideas here are:
- re-partition with odin if I can find the PIT file., would this work?
- find another way to get into recovery mode. (I considered ADK developer tools, but USB debuggin isnt enabled)
- flash another custom rom to override this, would that work/where would I find such a rom?? (cyanogen doesnt have md5 files?)
PLEASE help, I wanted to give this phone to my mom as she needs one, but I am not seeing the light at the end of the tunnel.
Try to open your phone. I mean open the screws at the back part of your phone, then remove the triggers for the buttons. after you remove the triggers. click the buttons many times. then bring back the triggers, and re-assemble it again. And the buttons may/can work again. I also have this kind of issue before. But I did this thing at my own risk.
Just try this thing man, I mean just try or do it at your own risk.
Crazyevilbeef said:
Try to open your phone. I mean open the screws at the back part of your phone, then remove the triggers for the buttons. after you remove the triggers. click the buttons many times. then bring back the triggers, and re-assemble it again. And the buttons may/can work again. I also have this kind of issue before. But I did this thing at my own risk.
Just try this thing man, I mean just try or do it at your own risk.
Click to expand...
Click to collapse
Thank you for your reply. I cant detach the buttons but I got the phone to work ). I still need to replace the power button though.
What I did was I flashed it over and over, I found a PIT file and flashed it, nothing happened. then SOMEHOW it gave me a start screen without the pin lock (as when flashing a new rom). I dont know how this happened, but I think it was a software error. I quickly went through the phone, doing all I could to reset it and remove all pins and passwords and enabling USB debugging, but it wouldn't let me change the pin without entering the old pin. So I downloaded quick boot, hoping to be able to reset into recovery, but I couldnt use that either, because I had lost root access by flashing a stock rom, lol. Long story short, as I was searching for answer, the phone screen timed out and locked on me again, I thought I was going to be sick. I tried rebooting it and it got into a boot loop (you can't make this up)
I then remembered that the one good thing I had done was to enable USB debugging, so the hacking began... .....I rebooted into recovery mode and couldnt do ANYTHING without the power button, lmao... It was like seeing the light at the end of the tunnel and then realizing that it was covered with steel bars. ..BUT... after educating myself and hacking a bit more, I was able to unlock the phone by using the "remove password key" command in adb. It only took me 20 hours of frustration and lots and lots of coffee and sweets. :victory: I hope my mom appreciates it .