Related
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.
Hi everyone,
I recently have a problem on my (old) TF201. The touch screen works fine, except the right and left edge. When I turn on Developer options and enable 'Show touches' i clearly see that when I move my finger to the right or left it sort of 'snaps' to the edge. So there a small stroke (left and right) that doesn't respond to input. Very frustrating when trying to point out something on the very right or left of the screen
I've opened my TF201 to see it wasn't a loose cable; but everything is in place. No difference.
Anyone an idea?
I did replace the factory ROM with a custom recovery (TWRP) and used
http://forum.xda-developers.com/devdb/project/dl/?id=6853 to install once a CROMBi-kk ROM for TF300t. Maybe this generates this screen edge fault? If so; how do I revert back to TF201? My TF201 thinks it's a TF300 now.
Thanks for reading this problem.
Hi,
Same problem here. It looks like it started after installing KatKiss. I was previously using Cyanogenmod without any problem. I thought that this could be caused by the new bootloader, but the problem persisted even after reverting back to the stock BL and ROM.
I even tried to replace the touch screen, no luck.
Have you been able to fix the issue?
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
[email protected] said:
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
Click to expand...
Click to collapse
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
altya said:
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
Click to expand...
Click to collapse
I am not sure exactly which kernel it was. But as I explained, I first installed Androwook AiryBean 2.31.
Then I used the "Androwook airyBean 2.31 Kernel Installer" to reinstall the default Androwook kernel, meaning the default kernel shipped with the kernel installer. That probably not Grimlock lite 5.1... See this page to download the kernel installer (and the Androwook ROM): http://forum.xda-developers.com/showthread.php?t=2407248
Maybe I should clarify a bit:
1. I completely wiped the tablet and did a clean installation of Androwook, following the instructions to the letter, including the 30 to 60 minutes wait "for the system to cache itself", followed by a restart. At that point, I still had the issue with the screen edges.
2. I then re-installed the kernel, again following the instructions to the letter. After the final reboot, the problem was gone.
3. And I finally re-installed KatKiss (v26). Since then I enjoyed my TF201 without any issues.
The reason why I tried to re-install the default kernel is because of the following quote:
HairyBean 2.31 Kernel Installer will allow you to try different kernel options without re-flashing the rom. It will also clean up bits left behind by the previous kernel before installing a new one
Click to expand...
Click to collapse
I am not sure that this is what solved the problem, but this is definitely a software issue. And since wiping the tablet multiple time, downgrading to stock and trying various ROMs didn't do anything, this was my last hope. It worked for me, and I hope that it will work for you too...
I can confirm that this is a software issue. After installing the reverse axis kernel of Hairy bean, the unresponsive areas in the touch screen was also reversed! I tried the solution provided above, unfortunately without success. Is it right to assume that everyone got this issue after installing Katkiss version after V26?
jan3586 said:
Is it right to assume that everyone got this issue after installing Katkiss version after V26?
Click to expand...
Click to collapse
I don't think so. I got the problem with an earlier version of KatKiss, and I believe (but may be mistaken) from the research I did in the past that a few people ran into this problem with other custom ROMs.
Thanks, are you using ver 2 of the kernel installer?
Sent from my Nexus 4 using XDA Free mobile app
jan3586 said:
Thanks, are you using ver 2 of the kernel installer?
Click to expand...
Click to collapse
Yes, it was version 2 that I used.
After migrating to a custom ROM (i tried both CM13 and Resurrection Remix) I seem to have corrupted some stock files that i can't reset. I can get back to TWRP no problem, but despite wiping every partition and installing a stock ROM--i still get crashes whenever i open the "Lock Screen Settings" in the Setting App I get the "unfortunately lock screen settings has stopped". All the stock restore files i seem to find are for MM, i just want to get back to LP.
The link from the other thread: http://forum.xda-developers.com/tmobile-lg-v10/help/trying-to-revert-to-stock-t3276181 looks like it might solve my issue, but it doesn't work for me. https://www.androidfilehost.com/?fid=24269982086988331
Will happily bestow "Thanks!" on anyone who can help me get this resolved or for that matter tries. Thanks in advance for helping a wayward noob.
jaysonic88 said:
After migrating to a custom ROM (i tried both CM13 and Resurrection Remix) I seem to have corrupted some stock files that i can't reset. I can get back to TWRP no problem, but despite wiping every partition and installing a stock ROM--i still get crashes whenever i open the "Lock Screen Settings" in the Setting App I get the "unfortunately lock screen settings has stopped". All the stock restore files i seem to find are for MM, i just want to get back to LP.
The link from the other thread: http://forum.xda-developers.com/tmobile-lg-v10/help/trying-to-revert-to-stock-t3276181 looks like it might solve my issue, but it doesn't work for me. https://www.androidfilehost.com/?fid=24269982086988331
Will happily bestow "Thanks!" on anyone who can help me get this resolved or for that matter tries. Thanks in advance for helping a wayward noob.
Click to expand...
Click to collapse
Since all the "stock" ROMs i found continued to have the problem, i ended up taking the plunge and using the method described here http://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240 to migrate to Marshmallow with root. Worked like a charm! Only issue is it seems to have broke my Wifi Calling as i now get REG99 error. Overall a small price to pay, but if anyone has any thoughts would love to hear them.
jaysonic88 said:
Since all the "stock" ROMs i found continued to have the problem, i ended up taking the plunge and using the method described here http://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240 to migrate to Marshmallow with root. Worked like a charm! Only issue is it seems to have broke my Wifi Calling as i now get REG99 error. Overall a small price to pay, but if anyone has any thoughts would love to hear them.
Click to expand...
Click to collapse
Which Part 2 did you flash?
Double0EK said:
Which Part 2 did you flash?
Click to expand...
Click to collapse
I believe i used the newer of the part 2's---V10_H901_V20E_Stock_MM_P2-3.zip
Now that you brought it up i googled it and it looks like there's some known issues there. Is **P2-2.zip the correct one to use then? Can i go reload part 1 and the new part 2 in TWRP? The latest thread is like 50 pages so reading through it now. Sorry if this question is redundant.
jaysonic88 said:
I believe i used the newer of the part 2's---V10_H901_V20E_Stock_MM_P2-3.zip
Now that you brought it up i googled it and it looks like there's some known issues there. Is **P2-2.zip the correct one to use then? Can i go reload part 1 and the new part 2 in TWRP? The latest thread is like 50 pages so reading through it now. Sorry if this question is redundant.
Click to expand...
Click to collapse
Re-read the OP, looks like there's been some changes. I'll reflash the new part2 and see how that works. thanks!
jaysonic88 said:
Re-read the OP, looks like there's been some changes. I'll reflash the new part2 and see how that works. thanks!
Click to expand...
Click to collapse
That fixed it! Also like the Android boot image/graphic better than the white Tmo screen.
Thanks Double0EK!
jaysonic88 said:
That fixed it! Also like the Android boot image/graphic better than the white Tmo screen.
Thanks Double0EK!
Click to expand...
Click to collapse
Uhhh..I didnt do much. But you're welcome.
My Kindle Fire HDX 7'' got hammered (literally). I fixed the dents, un-bent the chassis, replaced the lcd+digitizer and it's working again, but the accelerometer seems to be dead so I can't rotate the display. I tried with several "sensors test" apps, and they don't detect the chip (InvenSense ). I think maybe some contact broke because of the mainboard getting bended and it need to be resoldered, but I'm unable to locate the chip on the board.
Do you know where the chip is?
ttortuga123 said:
My Kindle Fire HDX 7'' got hammered (literally). I fixed the dents, un-bent the chassis, replaced the lcd+digitizer and it's working again, but the accelerometer seems to be dead so I can't rotate the display. I tried with several "sensors test" apps, and they don't detect the chip (InvenSense ). I think maybe some contact broke because of the mainboard getting bended and it need to be resoldered, but I'm unable to locate the chip on the board.
Do you know where the chip is?
Click to expand...
Click to collapse
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Syuriy said:
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Click to expand...
Click to collapse
I had the same problem but after I reflashed my rom it started working again. Try that if u can, or maybe if on stock downgrade to 3.2.8 then update back that might have the same effect
Syuriy said:
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Click to expand...
Click to collapse
CocoBun said:
I had the same problem but after I reflashed my rom it started working again. Try that if u can, or maybe if on stock downgrade to 3.2.8 then update back that might have the same effect
Click to expand...
Click to collapse
Same. Flashed LinOS 14.1 on known good device and rotation stopped working. Tried common solutions but issue persisted. Wiped and flashed CM 13 (rotation started working again) then LinOS 14.1 with full wipes. No issues with rotation since. No logical explanation but 'ROM hopping' (for lack of better term) has reported worked for others experiencing rotation issues. Sounds nutty.
I tried to install all TWRP flashable firmware Nexus, Stock, CM 11 12 13 14, LOS with wipe and format data. No result!!!
Syuriy said:
I tried to install all TWRP flashable firmware Nexus, Stock, CM 11 12 13 14, LOS with wipe and format data. No result!!!
Click to expand...
Click to collapse
Out of ideas. Indeed may be a hardware problem. Hopefully you can find an app that supports reasonably convenient orientation selection (common UX places controls in a permanent notification).
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
I suggest you to flash the latest version of MIUI latest china dev, then from fastboot flash twrp, then clean flash rom + kernel. It takes about 30 minutes if you know what you're doing.
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
ginohabibi said:
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
Click to expand...
Click to collapse
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
ufoshop said:
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
Click to expand...
Click to collapse
Try method in my signature.. it should work for you
khajiit said:
Try method in my signature.. it should work for you
Click to expand...
Click to collapse
Where do i find that method?
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Alright, im going to try that method and i will report my results here.
Followed all the steps within your guide, but that guide didnt work and has nothing to do with our slowboot issue.
Hardware related then
ginohabibi said:
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
Click to expand...
Click to collapse
Didnt you change recently some parts of the phone? Like display/baterry and so...?
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
So you say there is no solution to run the official rom without waiting 4-5 mins on boot, I have the phone from fastcardtech and maybe is a refurbished unit because they have very low prices compared to other resellers...the phone came in sealed box...
Dwnld links plzz..
Hay anybody here ...is there any other kernal for andriold n ROMs...
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
Mine to, it 2 time I had to replace screen. I'll give a test right now and report back.
Im not using the device anymore, but i think i had to replace the screen like 3-4 times, its very fragile, even a drop from small height makes it crack. Also without case its very slippy device, but none of that matters. From the 4 displays i used, which all have been touchscreen + lcd + the frame (as i dont like to glue the display, i pay 10 dollars more and its better) had that exact same problem, which is very long waiting for the device to boot. The custom kernel solved it, but another (probably better quality) display does solve it too.