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.
Related
Hi!
I have a huge problem. Sometimes the touchscreen is dont work, but its doesnt matter now. So i want to bring back i heard they fix it in warrantly.
But I rooted, run gingerbread rom, with changed kernel, and radio... so i dont want to break the warrantly (but i heard sometimes they dont care with this but its risky)
Today i started to reset the phone, i want to downgrade it but when i started to install the RUU it says: customer id error...
Whats the problem? please help i want to over the way as soon as possible
thanks.
Extract ROM.zip and try manual flashing using hboot.
tenke said:
Hi!
I have a huge problem. Sometimes the touchscreen is dont work, but its doesnt matter now. So i want to bring back i heard they fix it in warrantly.
But I rooted, run gingerbread rom, with changed kernel, and radio... so i dont want to break the warrantly (but i heard sometimes they dont care with this but its risky)
Today i started to reset the phone, i want to downgrade it but when i started to install the RUU it says: customer id error...
Whats the problem? please help i want to over the way as soon as possible
thanks.
Click to expand...
Click to collapse
Hi
Had the same problem when I installed cronos gingerbread with jumping screens and keyboard buttons not working , same thing happened when flashed other roms
It just unrooted by unstall the new official rom from the htc website.. updated it with the 2.1 ota and was good to go no more screen problems.
also try pressing down the screen a bit on the edges that helped as well
I have ADB installed so unrooting was a breeze
Have install Elelinux's gingerbread and is super smooth now
tfn said:
Hi
Had the same problem when I installed cronos gingerbread with jumping screens and keyboard buttons not working , same thing happened when flashed other roms
It just unrooted by unstall the new official rom from the htc website.. updated it with the 2.1 ota and was good to go no more screen problems.
also try pressing down the screen a bit on the edges that helped as well
I have ADB installed so unrooting was a breeze
Have install Elelinux's gingerbread and is super smooth now
Click to expand...
Click to collapse
"also try pressing down the screen a bit on the edges that helped as well" if it works, that means its a hardwer fault. i downloaded an untouched rom, with radio, flashed it, and i play with radiant, and another games, ,and facebook for two hour and no problem...
otherwise... Super one click works with hero? i have offical rom, and offical radio. i only have to unroot the device, and they dont realise it at the service.
edit: another interesting thing: after the touchscreen problem the touchscreen is stoped working, i restart the phone, and after when it starts the phone was felt my fingers from 3-4 centimeters! iam stunned! now the touchscreen is working correct with the original rom/radio
Solved
tenke said:
Hi!
I have a huge problem. Sometimes the touchscreen is dont work, but its doesnt matter now. So i want to bring back i heard they fix it in warrantly.
But I rooted, run gingerbread rom, with changed kernel, and radio... so i dont want to break the warrantly (but i heard sometimes they dont care with this but its risky)
Today i started to reset the phone, i want to downgrade it but when i started to install the RUU it says: customer id error...
Whats the problem? please help i want to over the way as soon as possible
thanks.
Click to expand...
Click to collapse
so i format my sd card with my computer (no quick format) and the problem is solved! thx all
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
after updating my ray to ics 4.0.4 wifi and bluetooth not working. when trying to turn on it shows turning on for 10 seconds but it doesn't. please help
hello there
i will try and help you but i have to ask you something
1.which android 4.0.4 were you trying to flash the unofficial one or the official one
2.this is a development section not q and a
for me wifi and Bluetooth is working fine.i will need more detail in order to help you.
i installed ice cream sony ka19.1 after that blutooth and wifi not turning on .
Please, make sure you do full wipe before flashing...
and reflash you rom.
i didn't find any problem with KA rom
i wiped every thing and tried to install several roms. but same problem all the roms...
well try two things
1.try changing kernels could be kernel issue than the rom.
2.flash official android 4.0.4 then root it with cwm(by flashing kernel) then install the rom.
i tried several roms and kernels . but the bluetooth and wifi is not turning on . what should i do?
Then just flash the official kernel with offical 4.0.4 rom as normal
Please update...i have the same problem. With me the phon turns itself off once the screen is locked. (
yeah, me too, i have same problem
not only in 4.0.4, but also 4.0.3, i flash my ray to 4.0.4 and 4.0.3 and do a full wipe, but wifi and bluetooth still not working
i don't know what happened with my phone, but suddenly at morning, my phone was already like this, i'm not installing something at my phone
please, help me, someone
there is a Help thread in this section, so please post your queries there
now, there's something wrong with what you did (your process)...
I've been flashing roms for the past 3 months without any issues (aside from the bugs on the roms themselves)
better clean up your phone first before doing mods...
sometimes people do not read instructions and do their own research
i have the same problem too...
please help..!!!
please update soon...
I think all the most popular custom kernels have the necessary modules embedded – so it’s unlikely to be a software problem.
For some rom/kernel/mod combinations I find that wifi doesn’t work on the first boot – I just reboot and it works.
These issues aside the only problems I have with custom kernels/roms/mods will be because I have conducted a lazy install (i.e. I’ve not followed instructions to the letter, or I haven’t flashed the stock ftf first).
The best way to trouble shoot is to start again and just re-flash the stock ftf – if your phone is not working properly after this it is 99% likely that your issue is hardware related - this might your phone, but the faulty hardware might also be your USB cable or the USB port – so swap the port/cable or even use a different computer and test again. The last thing to remember is that your file might be bad – so if what I’ve said already fails download the files again and try once more.
Similarly, if you constantly flash custom roms, without reverting to stock before hand – it is my perception that eventually your device will start to misbehave. You can get away with flashing JJ’s Hybrid and then Ice Cream Pureness, but this may not be the case with all kernel/rom combinations.
The best way to achieve clean installs of customs roms is to do it over a clean install of the stock ftf – if you’ve backed up this is a minor inconvenience that only adds 5 minutes to the installation time. If you’re lazy you may have bootloops or soft bricks or an unstable system (lots of fc’s or things not working e.g. wifi) – these will inconvenience you much more.
Finally I’ve had some hairy moments where I thought I’d permanently damaged my phone – but what every noob must remember is that you can always just re-flash stock and start again.
Folks
I've unlocked the bootloader, rooted phone, installed all different ROMs possible - and also ran the overheating fix as is prescribed.
Which is, running the touchpanel.sh through script me or Gscript lite tools from play store.
The script works (I am assuming it does because my phone shut down when I ran it under root) - but the phone overheat problem does not go away
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
I run the same touchpanel script with all possible ROMS and it just wouldnt work - what is it that can be done if anyone knows please?
thanks
Dhruv
dhruvraj said:
Folks
I've unlocked the bootloader, rooted phone, installed all different ROMs possible - and also ran the overheating fix as is prescribed.
Which is, running the touchpanel.sh through script me or Gscript lite tools from play store.
The script works (I am assuming it does because my phone shut down when I ran it under root) - but the phone overheat problem does not go away
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
I run the same touchpanel script with all possible ROMS and it just wouldnt work - what is it that can be done if anyone knows please?
thanks
Dhruv
Click to expand...
Click to collapse
Flash stock firmware, i seriusly doubt that it can solve your problem, but give it a try..
dhruvraj said:
I first tried CM10, latest FXP (146), and it didnt fix. Then I tried CM9 also, and that didnt fix it either.
Click to expand...
Click to collapse
You'll need an older stock GB rom that has a utility called "cyttsp_fwloader" included for touchpanel.sh script to work; CM9 or 10 dont include it.
ideopath said:
You'll need an older stock GB rom that has a utility called "cyttsp_fwloader" included for touchpanel.sh script to work; CM9 or 10 dont include it.
Click to expand...
Click to collapse
Thanks a lotttttt man. You've just made my phone usable again. Owe you half a dozen beers at least
dhruvraj said:
Thanks a lotttttt man. You've just made my phone usable again. Owe you half a dozen beers at least
Click to expand...
Click to collapse
Its a pleasure @dhruvraj, i remember how good it felt when i fixed it, so HTH.
I run that script so many times when I was on stock (rooted) rom, before switching to FXP.. sadly never solved my problem (its still here).
BTW, don't try to move the cyttsp_fwloader in CM10/FXP and run it there... it broke my touchscreen instantly, I had to flash the stock rom back again to repair it.
cosmacol said:
I run that script so many times when I was on stock (rooted) rom, before switching to FXP.. sadly never solved my problem (its still here).
Click to expand...
Click to collapse
Actually the script didnt work for me either - i opened an adb shell, su'd to root and did this as a one-liner
Code:
cyttsp_fwloader -dev /sys/devices/platform/spi_qsd.0/spi0.0 -fw /system/etc/firmware/touch_smultron_sony.hex -verify_only
BTW, don't try to move the cyttsp_fwloader in CM10/FXP and run it there... it broke my touchscreen instantly, I had to flash the stock rom back again to repair it.
Click to expand...
Click to collapse
Thanks for the headsup, i was thinking this was a possibility if the problem comes back on a future rom!
how do u think about this?
my touch didnt work on bottom screen area (see attchment).
it happen when ive use phone for long time or when my phone become warmed.
yes, i sent from my phone using Xda Premium, so what?
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.