[maybe solved] Touchscreen does not react after flashing an new ROM
Started by
Seb801
, Feb 07 2011 10:45 AM
#21
Posted 14 March 2011 - 02:32 PM
The Dalvik cache is different - try clearing that.
#22
Posted 15 March 2011 - 11:17 PM
#23
Posted 15 March 2011 - 11:26 PM
Dovbush, on Mar 13 2011, 22:26, said:
Hi, I have the same problem:
After the install any ROM (JJR9 or CyanogenMod 2.3) - the touchscreen does not react.
When I downgrade to fuctory setting(2.1) everything works fine.
Upgrade Software is fine -100%. All the same set of installs on another phone - everything works fine.
Please help.
After the install any ROM (JJR9 or CyanogenMod 2.3) - the touchscreen does not react.
When I downgrade to fuctory setting(2.1) everything works fine.
Upgrade Software is fine -100%. All the same set of installs on another phone - everything works fine.
Please help.
Edited by Dovbush, 22 March 2011 - 02:05 AM.
#24
Posted 17 March 2011 - 02:11 AM
Hi, I have the same problem:
After the install any ROM (JJR9 or CyanogenMod 2.3) - the touchscreen does not react.
When I downgrade to fuctory setting(2.1) everything works fine.
Upgrade Software is fine -100%. All the same set of installs on another phone - everything works fine.
After the install any ROM (JJR9 or CyanogenMod 2.3) - the touchscreen does not react.
When I downgrade to fuctory setting(2.1) everything works fine.
Upgrade Software is fine -100%. All the same set of installs on another phone - everything works fine.
Edited by Dovbush, 22 March 2011 - 02:06 AM.
#25
Posted 17 March 2011 - 12:52 PM
Hey guys!
Just bought home my new SF, since the other's speaker dead, and the same issue happened to me.
Got home, tried to put it into download mode (vol+ and pwr) nothing.
Flashed clockwork with Rom manager, flashed new cyanogen nightly, and...pff no touchscreen. Tried with FLB 10b, no touchscreen either. Just found this topic, but im pretty sure that this phone dont have OLED display.
Now i'll try stackbladroid 0.2. But damn with the stock it worked well, any suggestions what can cause this ?
I dont want to miss the new CM builds :S
Just bought home my new SF, since the other's speaker dead, and the same issue happened to me.
Got home, tried to put it into download mode (vol+ and pwr) nothing.
Flashed clockwork with Rom manager, flashed new cyanogen nightly, and...pff no touchscreen. Tried with FLB 10b, no touchscreen either. Just found this topic, but im pretty sure that this phone dont have OLED display.
Now i'll try stackbladroid 0.2. But damn with the stock it worked well, any suggestions what can cause this ?
I dont want to miss the new CM builds :S
#26
Posted 17 March 2011 - 03:35 PM
seems this problem is unknown and as most devs own working models, getting it sorted quickly feels unlikely 
gsf 19
Greetz from Dr.Ezkimo
Greetz from Dr.Ezkimo
#27
Posted 17 March 2011 - 06:39 PM
DrEzkimo, on Mar 17 2011, 16:35, said:
seems this problem is unknown and as most devs own working models, getting it sorted quickly feels unlikely 
Thats very bad news. :S
I mean, i just got my new SF, and no matter what ROM i use (i flashed original TPT too), it doest come to life. :S
With the TPT method i luckily got the recovery back, but damnit, i cant put it into download mode, and i cant use any
custom firmware. So at all, i got a phone, with no digitalizer.
Any suggestions are welcome, what to do, what to try, please.
Thanks in advance
#28
Posted 17 March 2011 - 06:46 PM
I'd like to see the config.gz from one of these new phones, but I gather from the posts above no one can restore their original rom?
#29
Posted 17 March 2011 - 06:48 PM
hecatae, on Mar 17 2011, 19:46, said:
I'd like to see the config.gz from one of these new phones, but I gather from the posts above no one can restore their original rom?
As i got home, i flashed it in no time. :S
Didn't though that will cause these problems, since i have my blade for 3 months, and went thru a way lot of roms, and
no problem occured. Well, until now. >.<
#30
Posted 17 March 2011 - 06:58 PM
Drakedian, on Mar 17 2011, 18:48, said:
As i got home, i flashed it in no time. :S
Didn't though that will cause these problems, since i have my blade for 3 months, and went thru a way lot of roms, and
no problem occured. Well, until now. >.<
Didn't though that will cause these problems, since i have my blade for 3 months, and went thru a way lot of roms, and
no problem occured. Well, until now. >.<
could be a new screen, could be a module missing in the boot.img, what was it running before you flashed it?
#31
Posted 17 March 2011 - 07:03 PM
hecatae, on Mar 17 2011, 19:58, said:
could be a new screen, could be a module missing in the boot.img, what was it running before you flashed it?
Stock 2.1 Tmobile Hungarian, and to be honest, i didnt checked the version.
Well, i think the final of this will be another exchange, maybe at another shop, since i cant get any out of this,
without the official ROM, which i dumbly flashed over .
#32
Posted 17 March 2011 - 07:06 PM
Drakedian, on Mar 17 2011, 19:03, said:
Stock 2.1 Tmobile Hungarian, and to be honest, i didnt checked the version.
Well, i think the final of this will be another exchange, maybe at another shop, since i cant get any out of this,
without the official ROM, which i dumbly flashed over .
Well, i think the final of this will be another exchange, maybe at another shop, since i cant get any out of this,
without the official ROM, which i dumbly flashed over .
have you tried the new software update executable on the T-Mobile Hungarian website?
http://www.t-mobile....29TV1_00_00.zip
#33
Posted 17 March 2011 - 07:56 PM
hecatae, on Mar 17 2011, 20:06, said:
have you tried the new software update executable on the T-Mobile Hungarian website?
http://www.t-mobile....29TV1_00_00.zip
http://www.t-mobile....29TV1_00_00.zip
Just flashed this over, and screen works.
Dont know how they managed to protect it down like this.
But for me, the phone lost its potential with an "anti-modification-layer" added to the protection.
Since i bought the phone, i always used custom roms, i really enjoyed every single bit of it.
Now i'll have to stick with the original enclair rom, which is dumb, this phone is cheap, and for devs, newbies @ android.
Dont really get the advantage of this, over to modding, in the eyes of Tcom. :/
*edit
allright i loled a big, at the time i wrote this message, the phone rebooted itself, and no screen again.
Then it must be some kind of faulty.
Edited by Drakedian, 17 March 2011 - 07:59 PM.
#34
Posted 17 March 2011 - 09:24 PM
Drakedian, on Mar 17 2011, 19:56, said:
Just flashed this over, and screen works.
Dont know how they managed to protect it down like this.
But for me, the phone lost its potential with an "anti-modification-layer" added to the protection.
Since i bought the phone, i always used custom roms, i really enjoyed every single bit of it.
Now i'll have to stick with the original enclair rom, which is dumb, this phone is cheap, and for devs, newbies @ android.
Dont really get the advantage of this, over to modding, in the eyes of Tcom. :/
*edit
allright i loled a big, at the time i wrote this message, the phone rebooted itself, and no screen again.
Then it must be some kind of faulty.
Dont know how they managed to protect it down like this.
But for me, the phone lost its potential with an "anti-modification-layer" added to the protection.
Since i bought the phone, i always used custom roms, i really enjoyed every single bit of it.
Now i'll have to stick with the original enclair rom, which is dumb, this phone is cheap, and for devs, newbies @ android.
Dont really get the advantage of this, over to modding, in the eyes of Tcom. :/
*edit
allright i loled a big, at the time i wrote this message, the phone rebooted itself, and no screen again.
Then it must be some kind of faulty.
definitely a faulty phone, probably a loose cable, I'd get it exchanged
#35
Posted 18 March 2011 - 02:28 AM
hecatae, on Mar 17 2011, 18:46, said:
I'd like to see the config.gz from one of these new phones, but I gather from the posts above no one can restore their original rom?
After the install any ROM (JJR9 or CyanogenMod 2.3) - the touchscreen does not react.
When I downgrade to fuctory setting(2.1) everything works fine.
Upgrade Software is fine -100%. All the same set of installs on another phone - everything works fine.
Please help.
#36
Posted 18 March 2011 - 10:02 AM
hecatae, on Mar 17 2011, 18:46, said:
I'd like to see the config.gz from one of these new phones, but I gather from the posts above no one can restore their original rom?
Hectae, I'm a bit of a noob with android (only just tweaked the builld.prop for the first time yesterday)...
I've got my phone running back on stock Orange B10, so if you let me know what files you need (and whee they are!) then I'll be happy to provide..
#37
Posted 18 March 2011 - 11:11 AM
Allright guys, i got my phone exchanged, maybe we can work out something.
I think this is the same generation of ZTE, since im able to see the digitalizer's dots.
At the last i couldn't see them.
So, how can i make a full TPT of the phone before trying out anything ?
I dont think nandroid is that safe like TPT.
*edit
Baseband version
TM_P729TV1.0.0.B01
Kernel
2.6.29
zte-kernel@Zdroid-SMT
Build
TM_P279TV.1.0.0B03
hope that helps
I think this is the same generation of ZTE, since im able to see the digitalizer's dots.
At the last i couldn't see them.
So, how can i make a full TPT of the phone before trying out anything ?
I dont think nandroid is that safe like TPT.
*edit
Baseband version
TM_P729TV1.0.0.B01
Kernel
2.6.29
zte-kernel@Zdroid-SMT
Build
TM_P279TV.1.0.0B03
hope that helps
Edited by Drakedian, 18 March 2011 - 11:27 AM.
#38
Posted 18 March 2011 - 11:33 AM
HI,
I have the some problem , i have a clockworkMOd Recovery v3.0.0.6 instaled, and install a "flb-Froyo-blade-r10b" in My portuguese San Francisco, and the toushsreen don't work.
Help-me please.....
FFreeconect
I have the some problem , i have a clockworkMOd Recovery v3.0.0.6 instaled, and install a "flb-Froyo-blade-r10b" in My portuguese San Francisco, and the toushsreen don't work.
Help-me please.....
FFreeconect
#39
Posted 18 March 2011 - 12:59 PM
Luis Alonso, on Mar 18 2011, 12:33, said:
HI,
I have the some problem , i have a clockworkMOd Recovery v3.0.0.6 instaled, and install a "flb-Froyo-blade-r10b" in My portuguese San Francisco, and the toushsreen don't work.
Help-me please.....
FFreeconect
I have the some problem , i have a clockworkMOd Recovery v3.0.0.6 instaled, and install a "flb-Froyo-blade-r10b" in My portuguese San Francisco, and the toushsreen don't work.
Help-me please.....
FFreeconect
You know, with that "HELP ME IM LOST" type messages you dont help resolving the problem at all.
Try installing different roms, backflashing your original one, to see if there is any solution.
Maybe you can try flashing OLED only roms, or stock 2.1. I had to take back mine for an exchange tbh, but
some people say that they original 2.1 rom works. Dont know if it help you out or not.
#40
Posted 18 March 2011 - 01:31 PM
One interesting point to note is that although my version is B10, and therefore supposed to be TFT -
The TFT dialler test codes DON'T work, but the OLED dialler test codes DO !
The TFT dialler test codes DON'T work, but the OLED dialler test codes DO !
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users







Sign In
Create Account

Back to top









