• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Dedicated Thread for Fixing Touchscreen

I am by no means giving up completely, but I think I lack the programming knowledge to fix this single-handedly, this thread will serve as a template for anyone attempting to fix this issue though.

The thing that strikes me odd about this issue is it only manifests itself when you:
move > stop > then move again
Samsung Transform Ultra Screen Issue - YouTube

I've tried the same thing on demo units at corporate sprint stores and boost stored and it's identical

I don't know if it's because the object is throwing a switch at the UI that says "float" or maybe the phone is clocked too high and cannot handle the IO
If anyone figures out the clocking speed, the first thing I'd try is undervolting to 800mhz and seeing what that does.

Anybody who has CWM installed could do a test for me if they don't mind their phone being out of commission for a few hours.
Here's what we could try:

To find out if it's related to the kernel or the touchscreen driver (adreno 205)
we can take a phone that uses the same combo and flash a rom from one of those.
Sometimes when you flash an incorrect rom to a phone you get weird pixelated colors but the UI and everything will work, it may soft-brick your phone or put you in a boot loop but with CWM it's easy to recover from.

According to this wikipedia page, these phones use the came CPU/GPU combo, clocked the exact same.
http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)

List of possible phones to find a flashable rom:
Fujitsu Toshiba IS12T, HTC Droid Incredible 2,[20] HTC Evo Design 4G,[21] HTC Thunderbolt, LG Revolution, Motorola Triumph, Pantech Mirach IS11PT, Samsung Conquer 4G,[22] Sharp IS05 (SHI05), Sony Ericsson Xperia Acro (IS11S)

The most popular phone out of all of those would be the Thunderbolt, but the second most available roms would be the Triumph.
I don't want to tell anybody "go and brick your phone" but all things considered, those two phones would be the best match, even with no physical keyboard, some things may not work correctly, but if we got to the home screen, even without fully working screen colors or a working radio, we'd be able to test on homescreen objects.
 
Sure ill flash em if you send em... just don't send me an overclocked one that will fry my phone... I brick my phone often... thanks interpth for cwm!
 
Also it would be nice if some one else can try all the steps in this thread, just incase I messed up or somthing... the more people attempting to fix it the better...

Thank you Andy for your efforts and reserch! ... and imfm too for the exact breakdown of the real problem some months back...
 
I think the most closely related phone (save for the keyboard and screen size) will be the Triumph on Virgin Mobile.. in our own forums here, we have some pretty good roms:

Try FroyoCreamSandwich 1.3
Froyocream_Sandwich_v1.3.zip

or
CM7 TG Reloaded
CM7-TG-Reloaded-2012-02-02.zip

as long as you don't touch the OC settings in CM7 TG Reloaded you should be fine.
Since the GPU is the same the phone should automatically readjust for the screen size in both roms, the radio will probably only half-work but you probably wont get service on it, but I'd say either one of those is a close match.

If you flash one of those roms and the screen works, then I'm pretty confident we can build a custom rom to take care of the screen problem
 
AndyDroidBot said:
I am by no means giving up completely, but I think I lack the programming knowledge to fix this single-handedly, this thread will serve as a template for anyone attempting to fix this issue though.

The thing that strikes me odd about this issue is it only manifests itself when you:
move > stop > then move again
Samsung Transform Ultra Screen Issue - YouTube

I've tried the same thing on demo units at corporate sprint stores and boost stored and it's identical

I don't know if it's because the object is throwing a switch at the UI that says "float" or maybe the phone is clocked too high and cannot handle the IO
If anyone figures out the clocking speed, the first thing I'd try is undervolting to 800mhz and seeing what that does.

Anybody who has CWM installed could do a test for me if they don't mind their phone being out of commission for a few hours.
Here's what we could try:

To find out if it's related to the kernel or the touchscreen driver (adreno 205)
we can take a phone that uses the same combo and flash a rom from one of those.
Sometimes when you flash an incorrect rom to a phone you get weird pixelated colors but the UI and everything will work, it may soft-brick your phone or put you in a boot loop but with CWM it's easy to recover from.

According to this wikipedia page, these phones use the came CPU/GPU combo, clocked the exact same.
http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)

List of possible phones to find a flashable rom:
Fujitsu Toshiba IS12T, HTC Droid Incredible 2,[20] HTC Evo Design 4G,[21] HTC Thunderbolt, LG Revolution, Motorola Triumph, Pantech Mirach IS11PT, Samsung Conquer 4G,[22] Sharp IS05 (SHI05), Sony Ericsson Xperia Acro (IS11S)

The most popular phone out of all of those would be the Thunderbolt, but the second most available roms would be the Triumph.
I don't want to tell anybody "go and brick your phone" but all things considered, those two phones would be the best match, even with no physical keyboard, some things may not work correctly, but if we got to the home screen, even without fully working screen colors or a working radio, we'd be able to test on homescreen objects.
Click to expand...

:/ tried to flash several roms for the phones you listed using CWM, but no luck. Kept getting installation aborted status 7. I also tried replacing the input drivers you posted above, but even using the shell I couldn't get them on the phone. Kept getting File exists or directory doesn't exist errors.

I had an idea though which I would be willing to experiment with if someone with more advanced knowledge of Android would be willing to help. If someone could write a script to install the drivers with CWM, we could probably get them on the phone. I was poking around in the files for the Overclocking Kernel Wifi fix released by BobZhome (http://androidforums.com/transform-.../495512-over-clocking-kernel-sph-m930bst.html) and it looks like it would be relatively simple for someone who knew what they were doing to write a script compatible with CWM to copy those files. The Wifi fix just replaces a few files in the System folder, but I can't make sense of exactly how it works.
 
AndyDroidBot said:
I think the most closely related phone (save for the keyboard and screen size) will be the Triumph on Virgin Mobile.. in our own forums here, we have some pretty good roms:

Try FroyoCreamSandwich 1.3
Froyocream_Sandwich_v1.3.zip

or
CM7 TG Reloaded
CM7-TG-Reloaded-2012-02-02.zip

as long as you don't touch the OC settings in CM7 TG Reloaded you should be fine.
Since the GPU is the same the phone should automatically readjust for the screen size in both roms, the radio will probably only half-work but you probably wont get service on it, but I'd say either one of those is a close match.

If you flash one of those roms and the screen works, then I'm pretty confident we can build a custom rom to take care of the screen problem
Click to expand...

FroyoCreamSandwich 1.3 - Blank screen, notification LED on, appears to have completely bricked the phone. Shit.
 
I can't test on my phone until tonight (must be able to take calls for work)...
I will try to copy the system files over one of my backups and make a new md5 and do an advanced restor and try to restore system by it self.
 
in these two threads they say how to fix installation errors
it has to do with HBoot

http://androidforums.com/evo-4g-all...mod6-error-status-7-installation-aborted.html

Please help (problems installing rom-First timer) - CyanogenMod Forum

In order for you to use CynaogenMod 6.0, you need to what is called "downgrade" your Bootloader. (From my understanding, 0.79.0000 is your bootloader when you upgrade to FroYo and CyanogenMod 6 won't install because of that so your bootloader needs to be 0.76.0000) very easy process but can also brick your phone, I did it and my EVO is still good and I use the NightlyBuilds. I attached the file for you so you can change it and I will explain to you how to do it.

1. Put PC36IMG.zip on the root of your SDCard.
2. Boot into Bootloader (Hold Power + Volume Down)
3. It will search for a series of files on your SD card and the PC36IMG.zip should be selected, it should ask you if you want to Apply it. Hit Volume Up when prompt to update.
4. Reboot.

Presto, you should be able to apply the CynaogenMod 6.0 in Recovery and Make sure you:
Click to expand...
 
If your phone turns on it should still be able to go into emergency mode

If you have Kies or Odin you can reflash your phone to stock and save it

but first take out the battery for a few minutes and restart to see what happens that rom shouldn't have overwritten your boot partition
 
The phone won't do anything without the battery in. With the battery in, the LED comes on but it wont do anything else. Strangely, if I play the phone into my computer, windows installs the following drivers:

SAMSUNG USB Composite Device
SAMSUNG Mobile Modem
SAMSUNG Mobile Modem Diagnostic Serial Port

Nevertheless, adb can't see the phone and I can't seem to get anything else to happen.
 
AndyDroidBot said:
If your phone turns on it should still be able to go into emergency mode

If you have Kies or Odin you can reflash your phone to stock and save it

but first take out the battery for a few minutes and restart to see what happens that rom shouldn't have overwritten your boot partition
Click to expand...

OK. I will try those. How do I get into emergency mode?
 
it must have over wrote recovery and boot... (not that it helps now)

gots to get interpth to the rescue... he can fix the phone (hope)
 
AndyDroidBot said:
Odin Multi Downloader v4.03.exe

here is a link to a new-ish version of ODIN multi downloader
i dont know if anyone has extracted an ODIN file from the TU already, but if not the steps are a little more complicated from the phone dump available at opensource.samsung.com


this lifehacker post is a pretty good explanation
How Do I Fix My Bricked Android Phone?
Click to expand...


how to extract an ODIN file from the TU?
tell me and i will follow... gots to get imfm's phone back on:)
 
AndyDroidBot said:
Odin Multi Downloader v4.03.exe

here is a link to a new-ish version of ODIN multi downloader
i dont know if anyone has extracted an ODIN file from the TU already, but if not the steps are a little more complicated from the phone dump available at opensource.samsung.com


this lifehacker post is a pretty good explanation
How Do I Fix My Bricked Android Phone?
Click to expand...

Thanks for you help guys. No luck with Kies, getting back into clockworkmod, or the links above. Looks like ODIN may be my only hope.

Obviously I don't know too much about all of this, but it seems odd that CWM was able to overwrite itself.
 
You must log in or register to reply here.
Back
Top Bottom