[Q] Xperia Go st27i - Touchscreen not working after flashed custom rom - Sony Xperia P, U, Sola, Go

Dear xda forumers/developer,
my xperia go touchscreen is not working after flashed the custom rom. ive searched the entire forum for this matter, other than send to service center, there's no suggested solution yet. i respect everyone of you, so please return e a favour.
rom before flash:
stock ics 6.1.1.B.1.1.0
rom which lead to this problem:
http://forum.xda-developers.com/showthread.php?t=2242539
reason:
the stock is quite laggy, so i decided to try other rom
what ive tried so far:
SEUS to restore stock ROM - boots fine, touch screen not working
PC Companion, repair option - boots fine, touch screen still not working
Flashtool, flash stock ics 6.1.1.B.1.1.0 - boots fine, touch screen still not working
Flashtool, flash stock gb 6.0.B.3.184 - boots fine, touch screen still not working
Full restore from CWM backup - boots fine, touch screen still not working
the touchscreen works perfectly fine before flash the custom rom
The device however, boot fine, no boot-loop etc.
Just that since ive flashed the stock rom, recovery (CWM) and root access was gone. plus, i cant do anything to get through the setup screen/first time setup.
since CWM and Root was gone, i have no idea on how to install/put it back. i assuming CWM was gone because i cant seems to access the recovery. any idea?
any help would be much appreciated, thanks in advance!

---

u can try this
flash xperia go ftf
dun switch on
flash wrong ftf (say xperia u)
still dun switch on
flash xperia go ftf
now swtich on
ps - this works after cross flashing of ftf
never tried for cwm flashing leading to touchscreen failure
at maximum ... flashing a wrong ftf will make touchscreen non usable (which u r already having)
so u have nothing to loose
just try it
plz at ur own risk.... dun screw me if something goes bad

---

drsanket_xperia_u said:
u can try this
flash xperia go ftf
dun switch on
flash wrong ftf (say xperia u)
still dun switch on
flash xperia go ftf
now swtich on
ps - this works after cross flashing of ftf
never tried for cwm flashing leading to touchscreen failure
at maximum ... flashing a wrong ftf will make touchscreen non usable (which u r already having)
so u have nothing to loose
just try it
plz at ur own risk.... dun screw me if something goes bad
Click to expand...
Click to collapse
thanks for the reply. the developer has been informed about the non-working touch screen. maybe i should wait for an update.
meanwhile, do you have any idea on how to root & install cwm on stock rom?
currently on ics, with non-working touchscreen, i have basic knowledge about rooting and installing CWM, but have no idea on how to work on it, cant access menu and usb debugging due to touchscreen problems.
can we chat on skype? my skype id "cjoenic" , maybe you can give me some idea.

---

cjoenic said:
thanks for the reply. the developer has been informed about the non-working touch screen. maybe i should wait for an update.
meanwhile, do you have any idea on how to root & install cwm on stock rom?
currently on ics, with non-working touchscreen, i have basic knowledge about rooting and installing CWM, but have no idea on how to work on it, cant access menu and usb debugging due to touchscreen problems.
can we chat on skype? my skype id "cjoenic" , maybe you can give me some idea.
Click to expand...
Click to collapse
Have no skype due to limited data usage
U can't root without touchscreen
Without root u cant install cwm
Bt if u have unlocked bootloader u can install a custom kernel wid autoroot and cwm built in

---

drsanket_xperia_u said:
Have no skype due to limited data usage
U can't root without touchscreen
Without root u cant install cwm
Bt if u have unlocked bootloader u can install a custom kernel wid autoroot and cwm built in
Click to expand...
Click to collapse
about skype, its ok.
about the bootloader, it is locked.

---

cjoenic said:
about skype, its ok.
about the bootloader, it is locked.
Click to expand...
Click to collapse
Since ur touchscreen is damaged now
What r u waiting for?? If flashing a stock rom doesnt solves the issue how can u expect next update of projectgx will???
Why dun u try what I mention in post 2

---

drsanket_xperia_u said:
Since ur touchscreen is damaged now
What r u waiting for?? If flashing a stock rom doesnt solves the issue how can u expect next update of projectgx will???
Why dun u try what I mention in post 2
Click to expand...
Click to collapse
touchscreen damaged? is it on physical or software level?
post 2, about flashing xperia u tft? since i dont have CWM on it anymore. only best bet is ftf.

---

I won't say that to b hardware fault coz many people had the issue who successfully resolved
So no hardware problm
Bt they all flashed wrong ftf files and not cwm flashable Rom

---

drsanket_xperia_u said:
I won't say that to b hardware fault coz many people had the issue who successfully resolved
So no hardware problm
Bt they all flashed wrong ftf files and not cwm flashable Rom
Click to expand...
Click to collapse
ok thanks for confirming that. it really relieved me.
meanwhile waiting for the downloads, i think ill look for OTG cable at the local shop, maybe i can hook my mouse on it so that i can enable usb debugging, perhaps root it and install cwm recovery.

---

I have the same problem with the same ROM... I flashed GB and relocked bootloader. Gonna go to the service and let em check it out.. I hope it's going to be cheap.
*EDIT: Btw , root and CWM won't help you, been there done that.
*EDIT2: The second post didn't help.

---

Dimmay said:
I have the same problem with the same ROM... I flashed GB and relocked bootloader. Gonna go to the service and let em check it out.. I hope it's going to be cheap.
*EDIT: Btw , root and CWM won't help you, been there done that.
Click to expand...
Click to collapse
really? how do you confirm that?
could it be kernel / driver issue?

---

cjoenic said:
really? how do you confirm that?
could it be kernel / driver issue?
Click to expand...
Click to collapse
i confirm it , i used this rom from munjeni http://forum.xda-developers.com/showthread.php?t=1912865 v13 rom (Firmware 6.1.1.B.1.10 ) also i tried flashing the ftf files as mentioned above, now i'm trying to do the same in cmw maby would that help

---

cjoenic said:
really? how do you confirm that?
could it be kernel / driver issue?
Click to expand...
Click to collapse
The fact is, this is my second time going to this soft-brick, but last time I gave it at the mobile service and they fixed it in less than a week.
Sorry about my english.

---

Hmm via cmw it dont work , is thear any way to work on the touscreenfiles after its extracted with ext4 unpacker to replace it on the phone ?

---

dimme12 said:
Hmm via cmw it dont work , is thear any way to work on the touscreenfiles after its extracted with ext4 unpacker to replace it on the phone ?
Click to expand...
Click to collapse
sounds like an idea.
im still looking for another version/region of FTF file for the flashtool. might give it a few shot.

---

cjoenic said:
sounds like an idea.
im still looking for another version/region of FTF file for the flashtool. might give it a few shot.
Click to expand...
Click to collapse
what are you looking for , maby i cant help
and Under system/usr/idc there is a file called synaptics_rmi4_i2c.idc i think it is that file

---

Any idea what to do ?

---

Dimmay said:
Any idea what to do ?
Click to expand...
Click to collapse
I do have an idea and maby two ideas, but if it works I do not know. there is a difference between the two files as you can see, that each can be found in the ROMs after they are unpacked I thought to modify the file and stop, it in the custom rom but I think it makes little difference because the ROM does not yet start with a custom kernel .. I hope the other members know something how we can solve the problem or at least one that the ROM has made​​. otherwise it will go these week to a service center with the standard rom and closed boat lauder ... and let the service guys solve the problem, luckily the phone is in warranty: p but i wait for the time being: p
sorry for my bad english: d

---

dimme12 said:
I do have an idea and maby two ideas, but if it works I do not know. there is a difference between the two files as you can see, that each can be found in the ROMs after they are unpacked I thought to modify the file and stop, it in the custom rom but I think it makes little difference because the ROM does not yet start with a custom kernel .. I hope the other members know something how we can solve the problem or at least one that the ROM has made​​. otherwise it will go these week to a service center with the standard rom and closed boat lauder ... and let the service guys solve the problem, luckily the phone is in warranty: p but i wait for the time being: p
sorry for my bad english: d
Click to expand...
Click to collapse
no offense, but im not quite understand the beginning part.
i really hope for solution now. :crying:

---

cjoenic said:
no offense, but im not quite understand the beginning part.
i really hope for solution now. :crying:
Click to expand...
Click to collapse
lol okay .. you have stock rom for sony experia st27i and if you unzip it with 7 zip you can see that er is a file called (Under system/usr/idc) synaptics_rmi4_i2c.idc if you open that with notepad , you can read it is four the touchscreen.. i think it is that file thats have an problem. becouse in the custom rom , that file is different..
I am a beginner myself so I can not make it, but the one that the ROM has made ​ is going to work today on this ROM to find a solution and if not there someone else know how to solve it .. we need to have some patience
and I use a translator to translate as much as possible: p
the only solution is sony service with stock firmware en locked bootlouder i think