[Question] MTK6589 1:1 Real GT-I9500 touch screen works up whenever lower part is touched

[daniel.pakulski]

Hi all,

I was able to flash ROM from : [Only registered and activated users can see links Click here to register]
but I have a problem with touchscreen which works upside down. When I press screen on top it actually shows that I pressed at bottom of screen. I was looking for solution many days and have learned a lot from many sites and different forum threads, but surprisingly non of the solution works for me. I am not able to reach proper file to change proper property to change this behaviour. Most probably i need to set somewhere: ctp_revert_y_flag = 1 as described here: [Only registered and activated users can see links Click here to register] , but I am not able to find nor edit script.bin on my phone, here I found some info:
[Only registered and activated users can see links Click here to register] and also here is very interesting info about partitions: [Only registered and activated users can see links Click here to register] but I can't find this script.bin on my phone. any ideas?

My phone is chaina phone 1:1 Real MTL 6589 GT-I9500, I was able to flash several ROM's using SP Flash tool from [Only registered and activated users can see links Click here to register], I know how to do this, but no matter which ROM I flash no matter which recovery image I flash this touch screen behavior is still upside down as described. Ideas:
1. set ctp_revert_y_flag = 1 in script.bin on my phone - I can't mount proper partition, don't know which partition should I mount, can't find this file
2. set ctp_revert_y_flag = 1 in script.bin on ROM file before flashing - don't know where to look for this file and don't know how to edit ROM before flashing.

What I know: how to root my phone, how to get to it using adb, how to use android-sdk, how to flash using SP flash tools, how to use recovery mode, clean user data, how to use SP Flash tool, how to switch on developer mode, switch on USB debuging, switch on "show touches". I spent 2 weeks reading many different forum threads and looking for proper solution, so please do not give simple dummy replay: "google it", I know how to google it. If you are expeirenced android user, please help with some hints or proper, relevant forum threads.

Thanks in advance!

[JayVernz]

Hi daniel.pakulski,

Did you manage to fix this? i am having the same problem with my phone.

[daniel.pakulski]

no, i have bought another phone, this broken one is in my drawer and I don't use it.

[WuddaWaste]

Hi Daniel.

I'm sorry this didn't get answered. Your post was the most detailed description and solution I've yet seen to this problem, so thank you for that. Hopefully this steers everyone in the right direction.

You're a more advanced user than I, so I apologize in advance of this sounds novice. However, in my Googling, I found that perhaps you're looking for the wrong file. That is, you were looking for "script.bin" but I believe that the file you need put that switch into is called "init.rc" (an Android initialization file).

The init.rc file itself is in the root directory on a device and in the source tree it is kept under system/core/rootfs. You cannot edit init.rc directly on a device. It's apparently more involved than that. Unfortunately, this is where I get lost in the jargon. To me, it reads like you need to unpack a file, edit init.rc, repack the file, then push stuff to the phone (or maybe flash the ROM with the repacked file). Here's the link I found:
[Only registered and activated users can see links Click here to register]

I know you've already moved on, but if you find the time to hunt this problem again perhaps this will be a step in the right direction. Good luck! And thanks again for your original post.

[daniel.pakulski]

Hi WuddaWaste

I am happy to hear that someone is using information I have shared. Thanks for your remarks. It is indeed a bit of info I was looking for a while ago. When I have a while I will fish out this phone from my drawer and play a bit again with it. I'll share the results certainly. You may be right that I was looking for wrong file. Should be not very difficult to repack IMG file and flash it again with information from your links. I am not convinced however that It'll solve the problem.

Besides I am really curious what is real cause such strange phone behaviour. So, just for curiosity stay in touch. Nice to have somebody trying to deal with the problem shoulder to shoulder - good luck, and share please if you solve!

[WuddaWaste]

Thanks @daniel.pakulski !

For future reference, I'll be alerted on this forum if you either:
1. Quote me (like you did above) or
2. Tag my name using the @ symbol (like I did above)

Doing either of those things should make sure I see your post in the future. I'll try my best to try to keep up with this post and others like it.

This problem is one I've seen repeatedly with several users here. Maybe one of those users will have the time, motivation, and knowledge to put this data to good use and test it out for us. Ultimately, it'd be nice just to see this solved for the greater good of the entire community.

Really, thanks again for doing so much of the digging and leg-work on this. I'm perhaps naively optimistic that we are heading in the right direction on this one.

Cheers!

[Athos]

Hi, I got curious about this and tried looking into it. Here are a few things I found out.

The script.bin file is in the NAND storage. You have to mount the file system and extract script.bin, then make a copy. (/mnt/tmp is just an example. You can mount it anywhere you want)

Code:

adb shell mkdir /mnt/tmp
adb shell mount -t vfat /dev/block/nanda /mnt/tmp
adb pull /mnt/tmp/script.bin

You then need to convert the bin file to a fex so you can edit it.
You need these tools [Only registered and activated users can see links Click here to register]
download and extract the zip file to your desktop. Traverse to that folder.

Code:

sudo apt-get install libusb-1.0-0-dev
make

Use bin2fex to convert the script.bin to fex.
Then you can edit the touch panel settings you mentioned, ctp_revert_y_flag.

Convert the fex file back to bin using fex2bin, then put it back with adb push.
You have to save it as both script.bin and script0.bin (this is a backup file)

unmount mnt/tmp

I apologize, though. This is all just research, I have not tried this. Hope it helps.

[JayVernz]

Hi Athos,

I want to try your researched method to my phone that also has inverted screen touch, but it is MT6572 Note 3 clone. Is it possible?

[Athos]

Hi Athos,

I want to try your researched method to my phone that also has inverted screen touch, but it is MT6572 Note 3 clone. Is it possible?

Hi, JayVernz. Even for Daniel's case, I am not sure. A10 is the well documented SoC. My research is for A10 (I forgot to note this in my post, I'm sorry). But I checked the manuals for both A10 and A20, and they are very similar.
I think the hardest part will be determining which partition of the Nand script.bin is stored in, for A20 (mt6572 included) SoCs. I read somewhere that in more recent SoCs it is found in nandb, not nanda. But nandb cannot be mounted in the same manner. However, if you do find the script file, you could try editing it with the sunxi tools.

Have you read WuddaWaste's suggestion in post#4?
You might want to look into that, too.

[BotezanAlexandru]

Hello. I have a umi x3 mtk6592 the same problem my touch screen I revert just touch screen but not lcd. is there someone who managed