Hi, I installed the MiniCM-6 v3 custom ROM using xrec and everything seems to be going smoothly, until the new screen which says, "Please touch the android to begin"... and I found that my touchscreen is NOT working. All other buttons work.
I am using Sony Ericsson X10 Mini Pro originally running SE Android 2.1.
Please help? Thanks
a full wipe might help? i didnt have problems with the touch.
I have wiped out the cache, dalvik (sp?) cache, made a factory reset, formatted system/data/cache etc. all through xRecovery to no avail. The touchscreen is still NOT working at all. Any other advice?
remove the multitouch module from /system/lib using ADB
same thing happens to me. touchscreen is not working anymore, i flash stock software back and same problem happening again, maybe hardware problem
Everything works OK whenever I restore my stock Android using xRecovery, so the touchscreen is NOT faulty.
I concur with and like the idea of disabling dualtouch but do not know how to do it... is ADB = Andro File Manager?
btw ruifang & asranash, you both fm KL?? I'm fm SG and coming up sometime next week.
UPDATE
I installed FroyoComb 1.32 and I also have the SAME PROBLEM - No touchscreen. It *must* be the Dualtouch driver...
I learnt that MiniCM6 v5.0 is a Stable Release and installed it. However, the dualtouch died on my phone again after 1 week of use. The dualtouch driver is truly defective and might be the cause of the reboots, hangs and total blackouts reported by others in these forums.
First update to official, then make full wipe, factory reset, clear cache, clear dalvic cache. After flash rom and it will work.
ruifung said:
remove the multitouch module from /system/lib using ADB
Click to expand...
Click to collapse
how to do that plz
name's multitouch module plz
i got a “fix” for those who cannot install the ROM due to faulty dual touch. AFTER downloading “XXX ROM” delete the file cyct8ma_ser.ko (the dual touch module) at the zip file. ii is somewhere the “lib/module” folder.. NO NEED TO UNZIP just delete it.. then install there you have it.
use 7zip or winrar to open those files.
hope someone will FIX our problem with dualtouch.
Related
Hi all...
I just got my first Android phone... is an X10i...
I have version 2.1-update1 on it, and i tried 2 custom roms (2.2) with the install from SDcard.
After installing first rom (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip) the result you can see it here: 220.ro/documentare/MOV01113/AVtgAccdjh/
After this, i instaled the 2nd rom (FreeX10-beta4.zip + gapps_FreeX10.zip); the result was: it work perfectly but after 30 seconds it was rebooting. it never stops.. the phone start again, and after 30 seconds , again reboot... and so on.
I must mention that the phone is SIM locked, and to work in my network i must unlock it... can this be a problem? if not can any one help me to fix this?
Or can anyone tell me where to find a custom rom that can be flashed with x10flasher? because when i install the rom from SDcard, is loading normally untill 50%, but when it reach 50%, he instantly go to 100%
Some info about my phone:
model: x10i
firmware: 2.1-update1
baseband: 2.1.54
kernel: 2.6.29
Can anyone tell me what is the problem and advice me what to do?
Thanks in advance.
SE-X10i said:
Hi all...
I just got my first Android phone... is an X10i...
I have version 2.1-update1 on it, and i tried 2 custom roms (2.2) with the install from SDcard.
After installing first rom (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip) the result you can see it here: 220.ro/documentare/MOV01113/AVtgAccdjh/
After this, i instaled the 2nd rom (FreeX10-beta4.zip + gapps_FreeX10.zip); the result was: it work perfectly but after 30 seconds it was rebooting. it never stops.. the phone start again, and after 30 seconds , again reboot... and so on.
I must mention that the phone is SIM locked, and to work in my network i must unlock it... can this be a problem? if not can any one help me to fix this?
Or can anyone tell me where to find a custom rom that can be flashed with x10flasher? because when i install the rom from SDcard, is loading normally untill 50%, but when it reach 50%, he instantly go to 100%
Some info about my phone:
model: x10i
firmware: 2.1-update1
baseband: 2.1.54
kernel: 2.6.29
Can anyone tell me what is the problem and advice me what to do?
Thanks in advance.
Click to expand...
Click to collapse
For now you can only flash stock 2.1 roms using the flashtool, everything else you have to use xrecovery.
As far as your phone being sim locked, I really don't think that's related to any of the issues you've mentioned.
Here's what I suggest:
- use the flashtool to flash it back to stock 2.1
- root
- install xrecovery
- try Wolfbreak's custom 2.2 rom from here
http://forum.xda-developers.com/showthread.php?t=945264
the instructions on the first post are kinda confusing but let me know if you have any other questions. Make sure to use the thanks button if any of this helps.
To install custom ROMs, your phone needs to be rooted and then install the ROMs via xrecovery.
Also for Trip's Froyo or Gingerbread ROM, it is preferable to on bb49..
GUIDES:
For changing BB: http://forum.xda-developers.com/showthread.php?t=960527
For Trip's 2.2 ROM: http://forum.xda-developers.com/showthread.php?t=1013210
Instruction for Flashtool : http://forum.xda-developers.com/showthread.php?t=928343
thanks to both for fast answer...
***********************************
@Lockon Stratos
this rom is working good, is only rom that installs properly and work without reboot, but SDcard is not working, and when i applyed the hotfix, it enter into a reboot loop
@regencyhood
i tried MIUI... same problem... reboot loop
***********************************
i tried again all roms that i have downloaded until now from here, but unsuccessfully
I do not understand why, but ROMs are not installed correctly (i have root and xrecovery installed, i made factory restore, wipe cache, format cache, wipe dalvik cache).
so i think i will stay on 2.1
I was very enthusiastic when i got it, but i see that is not such a great phone with no official update for 2.2, and is low on internal memory (only 465MB data memory and 280MB RAM).
SE-X10i said:
thanks to both for fast answer...
***********************************
@Lockon Stratos
this rom is working good, is only rom that installs properly and work without reboot, but SDcard is not working, and when i applyed the hotfix, it enter into a reboot loop
@regencyhood
i tried MIUI... same problem... reboot loop
***********************************
i tried again all roms that i have downloaded until now from here, but unsuccessfully
I do not understand why, but ROMs are not installed correctly (i have root and xrecovery installed, i made factory restore, wipe cache, format cache, wipe dalvik cache).
so i think i will stay on 2.1
I was very enthusiastic when i got it, but i see that is not such a great phone with no official update for 2.2, and is low on internal memory (only 465MB data memory and 280MB RAM).
Click to expand...
Click to collapse
Reason for Reboot on MIUI is because you are on baseband 54 (i.e 2.1.54)....
Recommended baseband is 49, either you flash and change your bb or you can apply a patch... all the necessary help regarding bb is given in the link in my above post...
hope i was helpful
So which one do you want to use trip's froyo or Z's froyo? I hate to say this but I have a feeling it's something you're doing in between installs that could be causing the problem. I say pick one that you want to use/test, flash back to stock 2.1 using je flashtool, root, install xrecovery then flash just one of the custom froyo roms using xrecovery.
Sent from my X10i using XDA App
Patch BB 54 or rollback BB 52
Lockon Stratos said:
So which one do you want to use trip's froyo or Z's froyo? I hate to say this but I have a feeling it's something you're doing in between installs that could be causing the problem. I say pick one that you want to use/test, flash back to stock 2.1 using je flashtool, root, install xrecovery then flash just one of the custom froyo roms using xrecovery.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
what i want is a version of froyo that look like official one...
something like the ROM from TripNRaVeR (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip)
sorry for the link from my first post... i hope this is working : youtube.com/watch?v=iV408mrlWqA
this is how is working the Rom from TripNRaVeR (Froyo_2.2.1_xperia_TripNRaVeR-v1.0.zip) on my phone
edited:
regencyhood said:
Reason for Reboot on MIUI is because you are on baseband 54 (i.e 2.1.54)....
Recommended baseband is 49, either you flash and change your bb or you can apply a patch... all the necessary help regarding bb is given in the link in my above post...
hope i was helpful
Click to expand...
Click to collapse
so... if i downgrade baseband to 2.1.49, the rom from TripNRaVeR will work to?
and i want to know if appeared any fix for camera for the rom from TripNRaVeR?
so... if i downgrade baseband to 2.1.49, the rom from TripNRaVeR will work to?
and i want to know if appeared any fix for camera for the rom from TripNRaVeR?[/QUOTE]
Yes, it will work.
Regarding the camera I am using "TripNMiUI FINAL 1.0.63" ROM, and the camera is working a-OK. (Pic and Vid included)
Zoom results in FC for me in the stock and MIUI camera app, because of which I use Vignette....
Was adding another post, but thought it was not helpful..now i dont know how to delete a post
Hi, yesterday I have installed Cyanogen Froyo CM6-Latest (based on MiniCM) - v6.0 from this link http://forum.xda-developers.com/showthread.php?t=1059361
and phone didn't boot. After 15 minutes, when it has black screen and vibrate sometimes, I put out batery.
Why it can not boot to system?
Sorry for my english, I am from Slovakia
you need to wait a litle bit longer tihis is knowing bug and is mentioned in the MiniCM v6.0 thread only read a little and you'll all learned
Ok, but how much time I have to wait?
around 30minutes to 1 hur :/ You must be patient it takes so long only for first boot
Thanks a lot Now I have put same ROM into my mini pro as you have, so I am waiting
I am disappointed About 3 hours from installing ROM FroyoComb v1.6, and nothing happend Only black screen with backlight, no vibrating
Hallooooo, does anybody know what to do with it????? PLEASE HELP!
now you have fixed MiniCM v6.1 and you can install it without problems
Thanks a lot bro Works great!
/edit: THERE IS ONE BIG PROBLEM WITH THIS ROM!!! I CAN NOT INSTALL ANY APP PHONE REBOOTING!!!
Yes is knowing bug like in cyanocomb v 1.2
Go to recovery wipe dalvik cache, partition cache, ful wipe (factory reset) and try.
If stil didnt work backup your sd card and format it
Sent from my U20i using XDA Premium App
Thanks again It is fine now. I can install apps. But when somebody calls me, the slider to recieve and reject call is broken I almost can not see recieve slider.
But I have some more questions: Is it possible to change battery indicator in status bar? How?
yes that need to be fixed:/
for battery you can change it with another theme
look at here
http://forum.xda-developers.com/showthread.php?t=1148635
I have installed the Cyanogen Froyo CM6 v6.01 successfully, but when I try to change sound notifications (from Settings -> Sound or from any app) I get an error saying that the application has stopped unexpectedly.
What should I do? I created the ringtones folder in my microSD and rebooted but still nothing.
Sorry, but I do not know what are you doing bad, because it works for me
Just in case anyone is interested, it was the sound picker. I installed Rings Extended and the problem is solved
Before, make and full wipe factory rester, clear cache, dalvic cache, wipe cache partition, before flashing new rom, try again this method and then flash, i think it 99.3% helps.
The other day i thought it would be agood idea to root m Gf's X10 mini Pro. I had the best intentions and all seeing as how i have an EVO3D with Synergy rom and such. I explained to her that Rooting would be awesome and better battery life and faster speeds etc etc. When i came time to root i Used the one click root method which worked fine and all seeing as how i had recover flashed and all. The problems started when we tried to flash Ginger DX. I Wiped cache and Dalvik then proceeded to flash. I then got endless bootloops no matter what i tried. I tried diff roms but when i flashed an eclair based rom the phone finally booted but GAPPS were missing and market was gone. Well im a seasoned CM7 pro so i just found a GAPPS zip to flash with no luck. I tried to manually replace the vending.apk withing root explorer still not working. So i then used PC Companion to "repair" the device but now market is there but forcecloses. Now her phone is just slow as all get out and i tried explaining it happens but i think she got used to the Speed of my EVO3D. Any Ideas would be greatly appreciated on how to fix this issue without losing all her settings
Use SEUS to flash the phone back to stock and then root and put on cwm.
When installing the rom did you factory reset as I have noticed the most common cause of boot loop's is when people dont do a factory reset after the rom install. Some roms require this some dont.
Sent from my X10 Mini Pro using XDA Premium App
So far so good did all that. Only prob is still Market keeps force closing.
Try removing the market or installing a higher version of the marketplace, their is one for the mini pro somewhere in here but I can't find where it is again sorry
Sent from my X10 Mini Pro using xda premium
Latest market - http://forum.xda-developers.com/showthread.php?t=1232155
Should just install if you open it fine. If not you will have to rename it to Vending.apk and then put it into the system/apps folder and overwrite the old one.
I have asked a few times on the forum if this could be related to the baseband of my device. Basically what happens is in call, he proximity sensor seems to cause the touchscreen to go haywire. I receive what amounts to phantom button presses. Basically voiding the functionality of the proximity sensor to begin with, the calls get put on hold, muted, dropped or whatever. A new symptom has now appeared, the dreaded black screen bug. When a call gets dropped, screen goes black and nothing but a battery pull solves this. Contacts are suddenly missing and I need to resync to get them back
I have tried many different roms, every single kernel. The only solution I personally can think of, is disabling the proximity sensor altogether. Can anyone tell me which line in the build.prop would disable this?
Its my everyday phone, so this is rather urgent, any help would be appreciated
You need to add either of these 2 lines (not sure which, or if it matters):
gsm.proximity.enable=false
gsm.proximity.enable=0
Oh, and apparently MIUI ROMs have that option in the settings.
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Left4DeadMW said:
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Click to expand...
Click to collapse
I usually mount and format /system when i do flash a new rom. Thanks for your reply, but as I stated before, this happens on every rom I have flashed before
I flashed Iced Bean 4.0 on my xperia sk17i and i think my touch screen died because of it, That rom has aroma installer and there was no my device on that list so i chose xperia pro. Installation was successful but touch screen didnt work. I reverted to stock using flashtools and it still doesnt work. Is there any way to fix this problem? i really need to try something so pleas suggest.
Just to be clear i'm not blaming on anybody, it is total my fault. I'm fully aware of risk installing custom roms so pleas help in any way you can
Thanks in advance
Have you tried to flashing a new kernel which was made for the phone? As far as I know drivers areusually stored within it in Linux / Unix systems so it might apply here for the touch screen as well.
i tried using command fastboot flash boot boot.img and generally did not work. I have unlocked bootloader. I had hard time finding guide to do that for my phone. I did revert to stock using flashtools and ftf file.
When you say fastboot didn't work, do you mean it could not connect to the phone? Where you in fastboot mode when you tried it?
I recently put the 4.4.4 AOPK rom (Link) on my phone and had trouble getting into fastboot to flash the required kernel, I think I solved that by using the flashtool.
If flashing the stock kernel doesn't fix the issue, perhaps using a custom one, which works with ICS, will help?
You can find some here: http://forum.xda-developers.com/showpost.php?p=47407355&postcount=3
-edit-
does this thread help you? [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
Fastboot worked fine, but any custom kernel after successful flashing didn’t work. I have installed managed to install xperialegacy cm11 it has custom kernel and it didnt fix touch screen. I will try the link you posted. On the side note i bought another sk17 today, yes i love this phone LOL xD
Yess, million times thank you . I made it using this tutorial
here is what you have to do for fix your Bricked touchscreen.
What you need for that is any custom rom with an aroma installer.
1. Flash suitable firmware with Flashtool ( i flashed .587 Because i used Zellycream rom V4 )
2. Then Install any ics Kernel that you like (I installed messa hybrid kernel v4.3 )
3: Then install Any rom that has Aroma installer in it and does support your device, via Cwm recovery (I installed Zellycream V4)
3. While installing the rom choose ST17i in Aroma instead of SK17i
4. Reboot after installation is completed.
5. Wait until phone is On homescree.Nopw touchscreen should work but h/w keyboard not
5. Reboot again into CWM install "keymap_for_pro_XXXX.zip
Link here For Keymap Mini pro
6. Reboot phone again.. Now keyboard and touchscreen should be working. Also options for h/w keyboard should appear now.
Good luck,
It did worked for me hopefully its also going to work for you.
Notice : At first your Touch might not responce how it was before, but give it a time it will work fine after some hours or day or it might never work like before.Mine touch screen worked normally after 8 hours of installing the rom with this method.
Click to expand...
Click to collapse
Now i have questions. Can for some reason touchscreen die again? and also which rom do you recommend for good battery and camera? i like stock but i find it tedious to root and remove all the unwanted apps only to free up a couple of MB and potential screw something
Update: I see that i need to flash a zip which fixes tochscreen. when installing new rom. Is this hardware or software problem?
It would surprise me if the screen died again from the same issue, as the harmful code should have been overwritten by the fix.
I am not a developer though, just a normal user with some basic linux knowledge.
I'd suggest trying out Real ICS. I think I ran it before I got my new phone (I just recently started using the Mini Pro again) and can't remember having any complaints back then.
Other than that you could just go through the rom list. There are some which claim to be focusing on performance, I haven't tried them myself though.
I currently use AOKP kitkat (with some modifications, see this post) but I cannot yet if I'll stick with it. Maybe gonna try out this one http://forum.xda-developers.com/showthread.php?t=2277199 next.
I think im going to stick to the stock for the now. Camera is the best there
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Bucov said:
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Click to expand...
Click to collapse
I'm confused. Didn't you solve the issue already?
If the damage is permanent, then maybe the touchscreen got damaged by using the wrong rom?
If you really want to have two working phones, you could get a replacent display from ebay. They start at around 30€ these days.