paying 5$ to whom ever can help me.. [ZTE BLADE]

[Guest Udyr]

Hello there Modaco Hackers! :)
I really ADMIRE your work you've done in the past few years for our antique ZTE BLADE little fellow :).

I've got a slight problem i'm afraid. My touchscreen does not react after flashing Eco CM7 or Eco CM9 ROM's. (it only works for 0.5sec after i turn on/off the lock button) it is NOT a hardware issue, as my phone works dandy with standard Cyanogen cm7 Nightly, or Swedish snow RLS7. (i havent tried newer generation ROM's such as Zeelog's)
I too wish to have a stable fast snappy build, with low battery drainage, such as any of these two mentioned!
I have spent countless hours trying to get these to work on my machine (touchscreen that is) but in vain. I'm afraid only jventura himself, or someone with knowledge of editing kernels can help me :(.

I shall quote a guy who managed to somehow fix this issue, but he doesn't replies to my PM, nor does anyone on forum topics seems to read my cries. His forum name is leromarinvit.
Here it goes:

Quote

I finally figured out what the problem is (on my device, at least): for some reason, the touchscreen controller is in the wrong mode (bootloader mode, due to configuration CRC failure) when booting. A reset fixes it for me.
BUT: This is not an exact copy of what the ZTE kernel does, since I haven't been able to find their changes. It's possible that they actually configure something and my kernel doesn't work for everybody. So please test it and report whether or not it works for you!

Note: The initramfs is from Swedish Spring RLS4b and I haven't tried it with anything else. But if it does indeed fix the problem reliably, the same kernel changes will work for every custom ROM....

 

As far as i understood he somehow edited kernel to not have dual AMOLED / TFT but only one type of touchscreen enabled. Maybe you can understand what he did there, coz i sure as hell cant :(.

i'm looking forward for any kind of help or reply here, and i'm even willing to reward a brave soul who invests some of their time in fixing my issue!
ivanGrozni

::Source material::
topic where they fixed it: http://www.modaco.com/forums/topic/331696-maybe-solved-touchscreen-does-not-react-after-flashing-an-new-rom/?page=7
Eco CM9 ROM: http://www.mediafire.com/download/8ze7wtt27c6wxt8/Eco-CM9-20130723-stable-blade.zip

Eco CM7 ROM: https://www.dropbox.com/s/kfcgg3izlp1cjks/Eco-CM7-20130722-stable-blade.zip
 

QUESTION goes: Can anyone help me editing Eco's Kernel (either cm7 or cm9), so that my touchscreen starts working after flashing it?

Edited January 20, 2016 by Udyr
quoting was badly done :D

[Guest Udyr]

ah damn it.. 111 views and not a single reply..
At least say something.. Like "i cannot do this, it is too much overdo".. something something.

I have tried extracting boot.img using "cygwin64 terminal" (under windows 7), but no success.. I couldn't unpack :(. My plan was to unpack both nightly, and eco's boot.img, compare differences, and try finding the source of touchscreen problem (probably oled/tft support).

[Guest vampirefo]

ah damn it.. 111 views and not a single reply..

At least say something.. Like "i cannot do this, it is too much overdo".. something something.

I have tried extracting boot.img using "cygwin64 terminal" (under windows 7), but no success.. I couldn't unpack :(. My plan was to unpack both nightly, and eco's boot.img, compare differences, and try finding the source of touchscreen problem (probably oled/tft support).

So what is your question?

[Guest Udyr]

You got the point :)
I've edited the 1st post, where i clearly stated what do i need:

QUESTION goes: Can anyone help me editing Eco's Kernel (either cm7 or cm9), so that my touchscreen starts working after flashing it?

[Guest vampirefo]

You got the point :)

I've edited the 1st post, where i clearly stated what do i need:

QUESTION goes: Can anyone help me editing Eco's Kernel (either cm7 or cm9), so that my touchscreen starts working after flashing it?

The post sounds like nonsense basically you unpack the boot.img and comment out all ts drivers except the ones need for your device, then repack boot.img.

Clearly sounds like the poster is totally clueless, most likely he used a boot.img that contained a kernel that wasn't stock kernel for his device, and on top of that didn't use correct files from stock rom /system/usr which are ts files.

[Guest Udyr]

12 hours ago, vampirefo said:

 

The post sounds like nonsense basically you unpack the boot.img and comment out all ts drivers except the ones need for your device, then repack boot.img.

Clearly sounds like the poster is totally clueless, most likely he used a boot.img that contained a kernel that wasn't stock kernel for his device, and on top of that didn't use correct files from stock rom /system/usr which are ts files.

You sound like it's something easy to do! Well, i dont even know how to start (unpacking boot.img). I fail.. And yes, i'm clueless, that is why im here to try and get some help. Obviously, in vain..

[Guest vampirefo]

12 hours ago, vampirefo said:  

The post sounds like nonsense basically you unpack the boot.img and comment out all ts drivers except the ones need for your device, then repack boot.img.

Clearly sounds like the poster is totally clueless, most likely he used a boot.img that contained a kernel that wasn't stock kernel for his device, and on top of that didn't use correct files from stock rom /system/usr which are ts files.

You sound like it's something easy to do! Well, i dont even know how to start (unpacking boot.img). I fail.. And yes, i'm clueless, that is why im here to try and get some help. Obviously, in vain..

Unpacking repacking boot.img is easy, trying to determine what drivers your device is using without having the device in hand is almost impossible.

If you can't unpack and repack boot.img, I doubt you know what drivers your device uses.

dmesg and logcat logs are needed to determine what drivers are being loaded, and used by touch device cross reference with modprobe to see what models are loaded.

[Guest vampirefo]

12 hours ago, vampirefo said:  

The post sounds like nonsense basically you unpack the boot.img and comment out all ts drivers except the ones need for your device, then repack boot.img.

Clearly sounds like the poster is totally clueless, most likely he used a boot.img that contained a kernel that wasn't stock kernel for his device, and on top of that didn't use correct files from stock rom /system/usr which are ts files.

You sound like it's something easy to do! Well, i dont even know how to start (unpacking boot.img). I fail.. And yes, i'm clueless, that is why im here to try and get some help. Obviously, in vain..

Unpacking repacking boot.img is easy, trying to determine what drivers your device is using without having the device in hand is almost impossible.

If you can't unpack and repack boot.img, I doubt you know what drivers your device uses.

dmesg and logcat logs are needed to determine what drivers are being loaded, and used by touch drivers cross referenced with modprobe to see what modules are loaded.