[Q][XP] Can't get in to TWRP after kernel flash (CM11) - Sony Xperia P, U, Sola, Go

Hello
I recently wanted to go back to CM11, but i got stuck on to a problem
I had Honoami V8 installed with the Nemises Kernel on a unlocked bootloader.
I wanted to have clean install so I flashed the Stock 4.1.2 with flashtool that went just fine and i had no problems.
until I flashed the CM 11 kernel with TWRP from Percy_g2.
In the instructions it says that i need to hold the power button to get into TWRP when the phone vibrates on boot, but the phone won't vibrate and it justs cuts to black no matter what I do. I tried it with the Stable M8 version and Nightly-16, but it just does the same.
Any help with this?

The kernel used with the Paranoid rom does work with TWRP. It appears only Cyanogen mod kernel does not work

Related

Unable to flash CleanROM 5...

Hi, was planning on flashing my Galaxy S3 i9300 with CleanROM, just to try it out. I have an unlocked bootloader, on ICS firmware (stock), and TWRP as my recovery tool. When I try to install it, all goes well until I reach 10% of the installation, where everything just freezes and then boots me back to TWRP. When I reboot, I'm still on my ICS firmware, like nothing has happened. Any tips?
Oh and I'm trying to flash both CleanROM 5.5.1 and 5.6, neither are working.

[Q] [Help needed] S3 mini wont boot into recovery.

Mid year I decided to root and flash Cm 11 onto my little s3 mini (gt-i8190) and everything went great. Recently I read on the Novafusion website that they recommend using TWRP instead of CWM, searched on Google and saw it was safe to flash over custom recoveries. I used Odin to flash over the TWRP I downloaded from the Novafusion site. When odin completed its process my phone rebooted into TWRP and it all seemed fine, then I proceeded to flash the latest version of the Cm 11 4.4.4 rom. Again everything went great and my phone booted up normally.
I got the zip file for the Android L keyboard and I used Rom manager to reboot into recovery and showed the "Samsung Galaxy sIII mini gt-i8190 screen and just went black for 10 seconds, rebooted and continued going black then rebooting. I pulled the battery out and booted up my phone again then used rom manager to flash CWM again and it worked! I used CWM to flash the keyboard apk and it worked.
I was a little bit worried about the recovery bootloop and decided to make a nandroid backup. I couldnt reboot into recovery, manual way or with Rom manager.
I have used odin to flash CWM and TWRP a few times now without any luck. My phone just reboots normally when odin finishes.
If anyone could shed some light on this issue I would be grateful.
Thank you.

Black Screen after install any rom (stock and custom) except one

Hello,
I have SGS3 i9300 that was installed on it Cyanogenmod 11 for along time and it working great!!
until i did some mistake because i have a problem with the power button and i thought it was the CM that cause this resets.... but now it's too late/
i fix the problem and tried to install CM11 back, but the phone showing black screen after the Samasung s3 logo... and nothing.
the steps that i try is:
1. install recover CWM and install ROMs.
2. install recover TWRP and install ROMs.
3. install Stock Rom from Odin.
4. install CM10 snapshot or CM11 nightly.
5. binary code reset.
6. install throw CM windows installer.
7. install BlissPop.
none of the above works :crying:
the only ROM that i manage to install where "Android Revolution HD 29.0"
PLEASE HELP ME....
thanks
were you running a custom kernel also?
Phantogenic said:
were you running a custom kernel also?
Click to expand...
Click to collapse
i don't know
but i do install Stock Rom
Does it not change to the Stock Kernel?
UP
up please i still get my phone work
i recently install stock rom 4.0.2
and this work but when i do upgrade with Kies or even Odin to new version
i get this problem with the black screen immediately after the Smasung S3 logo :crying:
please help

Phone reboots to recovery after installed built CM13

I finally successfully built CM13 from source for higgs2g, but after install, I rebooted, it stucks on the splash screen 3 seconds, then reboots to recovery.. :/
I think the cause of that is the outdated kernel version (3.10.17, the only available kernel for SM-G350E), but how to build a new version of the kernel?
Thanks in advance

Touch is lost after BL unlock

I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Don't flash a different kernel, just try RR first, boot and make sure it works.
Once that is done, then you can try flashing the kernel and see if everything works. If it doesn't, you have your answer.
Most custom ROMs are also builded just for their kernel so if u flash custom kernel then there is chance that ROM will not work as u expected. Just think about it when you are installing a custom kernel.
Today I did flash lite mode rom . It boots up but touch was not working...nothing was flashed even gapps.
Sometimes the recovery twrp too does not work.,touch lost. Now i suspect something wrong with the hardware.
But no issues with miui roms...Thats what makes me wonder
did you do it on the computer?
sibikallikkat said:
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Click to expand...
Click to collapse
You may want to try installing Radon Kernel. I've got an aftermarket display which also didn't work with a custom rom (Lineage OS), but after flashing Radon Kernel it worked flawlessly. You may want o try Radon 5.0 as I'm having trouble with 5.1.

Categories

Resources