Jump to content

[maybe solved] Touchscreen does not react after flashing an new ROM


Guest Seb801

Recommended Posts

Hi,

i have an B05 OLED SF. Running fine with Seb404s r6 ROM. Now i have tried to flash a newer Version like Seb404s R8 or R9. After flashing the phone boots in the normal way, but the touchscreen does not react. Unlock the screen or SIM input is not possible. The notification-LED is flashing red.

Same issue with FLB-Froyo G2 ROM.

Flashed with Clockwork 2.5.1.8 and both partitions wiped. MD5 sums are correct.

further information:

going back to Seb404s R6 by clockwork the touchscreen function is fine.

Can sombody help?

Thanks Seb.

Edited by Seb801
Link to comment
Share on other sites

Have tried some more ROMs.

Eclair:

Sebastian404's de-orangeated-rom [OLED only] - r4 =>Touchscreen is o.k.

Sebastian404's de-orangeated-rom [OLED only] - r6 =>Touchscreen is o.k.

Sebastian404's de-orangeated-rom [OLED/TFT] - r8 =>Touchscreen unresponsive

Sebastian404's de-orangeated-rom [OLED/TFT] - r9 =>Touchscreen unresponsive

Froyo:

-FLB-Froyo G2 for ZTE Blade (r8a) [OLED/TFT] => Touchscreen unresponsive

-de-crossed (cheque) r0.2 [OLED/TFT] => Touchscreen unresponsive

-Japanese Jellyfish RLS9 [OLED/TFT] => Touchscreen unresponsive

-stackbladroid_v0.2 [OLED only] =>Touchscreen is o.k.

It seems to be a problem with the dual OLED/TFT ROMs, all ROMs only for OLED runnig fine. ROMs for both shows the issue.

Link to comment
Share on other sites

Have foud a first solution, changing the boot.img [flb-froyo-blade-r8a OLED/TFT] with an OLED only version, the touchscreen is usable.

Don't know why the dual version won't work on my SF. :P

Link to comment
Share on other sites

Guest isambard
Have foud a first solution, changing the boot.img [flb-froyo-blade-r8a OLED/TFT] with an OLED only version, the touchscreen is usable.

Don't know why the dual version won't work on my SF. :P

nice sleuthing!

Link to comment
Share on other sites

O.k. back to my old r6 ROM. With the changed OLED boot.img WIFI is not working.

Is ist possible to build an actual Froyo boot.img with OLED support only? I'm wondering no one other has this problem.

Link to comment
Share on other sites

Guest Simon O

Must be a problem with your phone as my phone is OLED and the touchscreen is fine.

Yes you could use an older boot.img but you'll be using old bug filled kernels which cause the screen freeze issues.

Honestly if there were problems with OLED I'd be seeing them myself.

Link to comment
Share on other sites

Must be a problem with your phone as my phone is OLED and the touchscreen is fine.

Yes you could use an older boot.img but you'll be using old bug filled kernels which cause the screen freeze issues.

Honestly if there were problems with OLED I'd be seeing them myself.

Thanks for your answer, any idea how i can locate the problem?

Link to comment
Share on other sites

Guest Simon O
Thanks for your answer, any idea how i can locate the problem?

Not too sure if it's hardware issue. Do you ever get screen freezes using older roms?

BTW you can use the boot img from FLB r6 with r8. Just replace the file in the rom zip and flash it. You'll lose the backlit lights and auto brightness may not function but at least it'll give you a mostly working phone.

Link to comment
Share on other sites

Not too sure if it's hardware issue. Do you ever get screen freezes using older roms?

No, no such issues on any rom. Phone works "perfect".

BTW you can use the boot img from FLB r6 with r8. Just replace the file in the rom zip and flash it. You'll lose the backlit lights and auto brightness may not function but at least it'll give you a mostly working phone.

I will try it. :P

Link to comment
Share on other sites

Hi, exchange the boot.img with the one from FLB r6 dont work => phone stuck @ green android. Maybe you have misunderstood, i was going back to my old eclair ROM (Sebastian404's de-orangeated-rom- r6). Not your FLB r6 :D

Flashing your origin FLB r6 same issue, no touchscreen working. (FLB r6 is also an OLED/TFT version). :P

Link to comment
Share on other sites

Guest Simon O
Hi, exchange the boot.img with the one from FLB r6 dont work => phone stuck @ green android. Maybe you have misunderstood, i was going back to my old eclair ROM (Sebastian404's de-orangeated-rom- r6). Not your FLB r6 :D

Flashing your origin FLB r6 same issue, no touchscreen working. (FLB r6 is also an OLED/TFT version). :P

Sorry.. r5a and lower. You can get the boot.img from this zip

Link to comment
Share on other sites

Guest gremlinman
Have tried some more ROMs.

Eclair:

Sebastian404's de-orangeated-rom [OLED only] - r4 =>Touchscreen is o.k.

Sebastian404's de-orangeated-rom [OLED only] - r6 =>Touchscreen is o.k.

Sebastian404's de-orangeated-rom [OLED/TFT] - r8 =>Touchscreen unresponsive

Sebastian404's de-orangeated-rom [OLED/TFT] - r9 =>Touchscreen unresponsive

Froyo:

-FLB-Froyo G2 for ZTE Blade (r8a) [OLED/TFT] => Touchscreen unresponsive

-de-crossed (cheque) r0.2 [OLED/TFT] => Touchscreen unresponsive

-Japanese Jellyfish RLS9 [OLED/TFT] => Touchscreen unresponsive

-stackbladroid_v0.2 [OLED only] =>Touchscreen is o.k.

It seems to be a problem with the dual OLED/TFT ROMs, all ROMs only for OLED runnig fine. ROMs for both shows the issue.

Looks to me like roms capable of OLED an TFT dont work for some wierd reason on yuor phone

Try using ROMS capable of Just OLED

Link to comment
Share on other sites

  • 1 month later...
Guest SpringNBreeze
Looks to me like roms capable of OLED an TFT dont work for some wierd reason on yuor phone

Try using ROMS capable of Just OLED

Hi,

I have the same problem with jellyfish R8 or R9.. please help.

Thanks

Link to comment
Share on other sites

Guest Rotmann
Have tried some more ROMs.

Eclair:

Sebastian404's de-orangeated-rom [OLED only] - r4 =>Touchscreen is o.k.

Sebastian404's de-orangeated-rom [OLED only] - r6 =>Touchscreen is o.k.

Sebastian404's de-orangeated-rom [OLED/TFT] - r8 =>Touchscreen unresponsive

Sebastian404's de-orangeated-rom [OLED/TFT] - r9 =>Touchscreen unresponsive

Froyo:

-FLB-Froyo G2 for ZTE Blade (r8a) [OLED/TFT] => Touchscreen unresponsive

-de-crossed (cheque) r0.2 [OLED/TFT] => Touchscreen unresponsive

-Japanese Jellyfish RLS9 [OLED/TFT] => Touchscreen unresponsive

-stackbladroid_v0.2 [OLED only] =>Touchscreen is o.k.

It seems to be a problem with the dual OLED/TFT ROMs, all ROMs only for OLED runnig fine. ROMs for both shows the issue.

Could you try CM7 RC2 or N15? A guy on IRC has the same problems, but he has the BASE Lutea (german ZTE Blade).

Link to comment
Share on other sites

Guest Dovbush

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.

Link to comment
Share on other sites

Guest Dovbush
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.

.....................

Edited by Dovbush
Link to comment
Share on other sites

Guest Dovbush

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.

Edited by Dovbush
Link to comment
Share on other sites

Guest Drakedian

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

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.