[Q] Non responsive recovery screen - Xperia SP Q&A, Help & Troubleshooting

i am on archxperia 1.2.1 and when i try to install any android 5.1 based rom like cm 12.1, rr milestone 1, aicp, or vanir, or the tangerine kernel, the twrp recovery is not responding to touch. almost as if the touchscreen isn't working. but the power button works. earlier i had no problems but these problems started after i flashed these drivers http://forum.xda-developers.com/crossdevice-dev/sony/testing-flashable-adreno-300-series-t2901176 they are for kitkat but i flashed them and it worked. i felt the gaming performance was improved so was the antutu score. is it because of the drivers? because even after i did wipe the whole system with the twrp recovery using williams kernel for stock 4.3, the twrp from tangerine was still not working.

I have the same problem, Im on stock with cm12.1, and had to use cwm to flash, twrp doesnt work, but try this, let the phone cool by switching it off for a couple of hours and restart immediately into recovery and it somehow works, I guess my touch is damaged ?
had it replaced once and I can see the reaper hovering man...

Related

Camera stops working often after cwm 6.0.4.8 on aosp roms

I'm not sure if I'm the only one experiencing this but every time I try to flash a custom kernel on CM11 and PA4 with cwm 6...4.8 camera app freezes like usual but then freezes again after 5 secs which is not usual.
Not only does this happen on custom kernals but stock CM11 and PA as well e.g. when I was in the science museum using PA taking pics everything was working well, then phone froze so I did a reboot in fact 5 reboots and camera displayed same symptoms as explained above. Also on CM11 stock kernal I did a regular reboot to apply full theme and bam camera stopped working all AF a sudden.
To fix I had to reflash ROM. I even did a full wipe( including format system) and still had same symptoms.
Pimped kernal just breaks camera straight from reboot no matter how many times I reboot it doesn't fix the problem. Only fix seems to reflash ROM (no need to wipe). Restoring stock/original ROM kernel fixes it but WiFi does not work.
Any way to get custom kernels to work without breaking camera?
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
eclyptos said:
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
Click to expand...
Click to collapse
Thanks for the reply. I have no option but to use cwm cause all my back ups where done on cwm.
As for the problem I found the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=2505973
yup owns Z1 and stuff.

Can't enter recovery, everything else works (sort of)

Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
samcool55 said:
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
Click to expand...
Click to collapse
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
rog_star said:
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
Click to expand...
Click to collapse
Tried that, but UKF says device unsupported, don't know why... I have used it before and it worked then.
Any other options?
I got it fixed. But tbh i still don't understand how. I flashed JB stock with odin and when it rebooted, i got automaticly into CWM weirdly enough... Wasn't going to waste my maybe only chance so i flashed the custom rom, wiped everything again, reboot, went again automaticly into CWM. anyway i was third time lucky and it booted as it should. Everything is working now! Anyway thanks for trying to help.

[Q] how to get rid of this ....

need help
i don't know what i
should do.
So my Problem is I'm getting a wrong recovery when I reboot to it. It's
not the one I had before. My previos recovery was twrp . i flashed the
newest validus Rom for xperia z and it worked( lollipop). But i noticed a bug so i
wanted to get back but it didn't worked because the recovery was
gone. So i tried to install one via some apps .it didn't worked . I only got
a recovery with stock options nothing else. Then I flashed back to
stock 4.4.2 and from that to cm 11 with lightning kernel ( lightning
kernel has twrp which is the one which used before).It worked out fine
but then i tried to flash the resurretion remix it worked but as i wanted
to Boot into twrp to flash Google apps i couldn't because this
cyanogen mod recovery was there again, out oft nowhere . i searched
for hours but couldn't find a solution. How do i get rid oft this recovery
and can get the Team win recovery back on lollipop.
Help would be very appreciated.( sorry for gramma errors, english is
not my mothertongue,i know it's anoying to read that all the time )

[Q] Cannot get rid of CM recovery

Hi!
Today I wanted to try a CM12 nightly on my Xperia Z1. There was also flashed an
own recovery, the Cyanogen Recovery. I was not glad with CM12, so I wanted to
reflashed Slimkat stable. But now I cannot reach the recovery, I only get a black
screen when trying to enter. But I am able to boot Slim. I tried several boot.img
with fastboot. With some, suddenly the CM recovery appeared. I also tried the
boot.img from CM11 stable to get CWM. No chance, black screen.
What can I do?

Stuck on boot animation screen (jumping balls/ waves) regardless of which ROM I use.

Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.
Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.
Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.
I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good:

Categories

Resources