I installed agni kernel 10.7 on lavender with hellas rom and after installation it doesn't boot to system. Instead it boots back to recovery. I tried installing stock backup rom and same prob occurs. I tried format data and problem still persists. Any help?
Related
Hello,
my phone was working like a charm with cm 7.1 , Siyah Kernel, clockworkmod recovery mod 5.0.2.
I decided to upgrade my Siyah Kernel from 2.0 beta 8 to v2.
I used the QR code from Xda forum. Phone downloaded kernel, then once download finished, opened Rom Manager app, then invite me to install the new .zip file.
I usually do it manually, in rebooting in recovery and installing the .zip file in recovery mod, but I wanted to try this way.
Now my phone doesn't boot, hanf on on Samsung logo. No recovery mod available, only download mod.
Tried to reinstall ClockworkMode recovery 5 with Odin, but nothing happens. The yelow box stays yellow, and message hans on at Setup connection.
I alos tried to flash P-SBL.tar with odin, but it failed.
So, what can I do??
EDIT : Issue solved. Retried with Odin and ClockworkMod. This time I booted in recovery, phone booted in it and installed new kernel, and the booted in cm 7.1. I do think this issue came from Rom Manager.
So far as i know, using rom manager with the S2 is a mistake.
The S2 dosnt like rom manager much, and it can end up in a lot of problems up to a semi bricked phone.
Glad you solved it , but i recommend to avoid rom manager for now
Ive run into a problem and need some help.
im running stock 5.0 with multi-boot and have autodroid 1.2 as a secondary rom for nethunter.
all was running well untill i used the "flash image gui" while booted into autodroid to flash the m4xx3dout .img
now my internal 5.0 rom will not boot it just loops at the circular-wavy-dots lol, i can still boot autdroid however. so still have access to storage and all my data (thanks multi-boot). autodroid rom is still showing as kangaroo kernel.
ive tried flashing the kexec_50_final zip in the "flash img gui app as well as in multiboot recovery to no avail.
any ideas?
No one?
I have a Galaxy note 4 SM- N910V, i just recently updated my bootloader to the CPD1. I rooted, installed TWRP, and CyanogenMod 13 beta. It works flawlessly, but ive always had an issue with bluetooth sound that was fixed when i installed a custom kernel on BPA1. Now that i am updated to CPD1, i installed CyanogenMod13, and the emotion kernel, But now my Phone wont boot pass the CyanogenMod logo at the beginning. I did wipe cache and dalvik after in installed the Kernel. Any help is greatly apprecieted.
Thanks,
Deershoot3r
EDIT: Also i forgot to mention, i did a clean restore in odin, rooted, reflashed twrp. But this time i installed the Emotion Kernel first, THEN installed CyanogenMod/Gapps, and it booted perfectly BUT in settings my kernel doesnt say emotion it says "3.10.40-ga6f06c0 [email protected] #1"
When you flashed the kernel, then the ROM, the ROM overwrote (not sure what you think you installed the kernel to if the OS wasn't there?) the kernel, is my guess.
In any case, it simply sounds like you don't have a compatible kernel for the ROM. Ensure you have a kernel that's compatible with the ROM and your hardware.
Alright, so I'm thinking my problem was that i initially had supersu installed when attempting to install this kernel, and thus causing that bootloop.
Can anyone provide insight as to whether this is true. I had a nandroid backup of my stock rom and even though I "restored" it, it was still stuck in bootloop regardless :/. I don't want to keep restarting and reinstalling everything over and over without knowing what the problem is.
I currently run Resurrection Remix with xposed. I'm fearing if I make another nandroid backup for this and try to flash the rom again, it won't work and I have to start again.
FYI: I was on RR when I attempted the kernel install.
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
billamin said:
Try downloading the kernel again and dirty flash it. If that doesn't work try dirty flashing some other kernel. And if that doesn't work dirty flash your rr rom. And if still not working then restore your backup
Click to expand...
Click to collapse
well what i did was following:
round 1. RR rom already installed
wipe cache and delvik, install kernal, bootloop
attempt to restore nandroid., still bootloop,
attempt 2:
wipe everything and install RR, SU, Gapps
did setup
installed franko r25
attempt 3.
wipe and factory reset
restore nandroid
bootloop
attempt 4
DONT install franco and install ak. after everything
works
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
feis said:
Franco kernel needs to be installed twice to work. flash kernel, dont restart, just flash again
Click to expand...
Click to collapse
omg thanks! that worked perfectly. Now a new problem is specifically when I'm using tugapower, while typing on my swiftkey into the xda forum. I'm noticing a lag. I've made it so then both apps are operating on performance with franco. Not sure what's causing the lag. Is it possibly the theme?
Dunno whats the problem, but im pretty sure if you just flashed franco, didnt change anything and used those apps, they wouldnt lag
didn't figure out what caused the lag but its gone now
Hello,
So basically, I got an OTA update today for my EvolutionX custom rom and I've installed it. Afterwards I got a boot loop.
Turns out, that for some reason, no matter what recovery I use, after the flash is done and recovery states "Updating partition details..."
I get a bunch of errors:
Error opening: '/sth/sth' (Operation not permitted)
Same thing happens if I try to wipe Cache or Dalvik through the recovery.
I've found some threads related to the issue, such as this one, but nothing helps.
I've tried several different versions of both TWRP and OrangeFox, no avail.
I can't roll back to previous ROM version because apparently it disappeared from EvoX website (it was EvolutionX 5.8, this one)
Any clue?
As far as i kniw newest evox is 7.3 and uses 4.19 kernel. It needs special recovery handle 4.19
matthias1976 said:
As far as i kniw newest evox is 7.3 and uses 4.19 kernel. It needs special recovery handle 4.19
Click to expand...
Click to collapse
Could you link me the aforementioned recovery handle? I can't seem to find anything
If you mean the one included in the EvoX zip then it doesn't work.
Update: Flashing the old ROM did not work.
Update2: I've managed to restore the OS by wiping data completely...does not fix the encryption issue in recovery however.