Hi all.
Generally speaking, I know how to flash ROMs, kernels, and my device bootloader is unlocked, TWRP Recovery in place, and I have a Nexus 5. The problem I have is trying to flash a custom kernel on AOKP ROMs or the few ROMs based on AOKP. After flashing, where normally I would reboot and start up the system fine, with AOKP it just hangs after it powers on where it says "Google" and does nothing more. And frankly, I can't figure out why AOKP, am I not wiping something correctly. Typically I would guess to wipe Dalvik and cache but from my most recent recollection, that still did not help. Yes, yes, there is not anything wrong with AOKPs kernels, but I am both obsessive over this new kernel in particular, and also I want to find the answer why or how to fix for my own personal knowledge. Does anyone have any suggestions? I try to Google search it but I'm not finding anything. *Worth noting here, this also has happened flashing a kernel on a couple Cyanogen based ROMs, but then other Cyanogen based ROMs do fine with custom kernels, so what gives? Any knowledge is appreciated!*
This is bugging the life of me because I love the AOKP Roms, but is it I can't have my cake and eat it to?
Related
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?
I don't get what all the hype is surround Philz-CWM6 kernel anything that is even remotely related to it doesn't seem to work. His 4.00B21+22 just don't seem to boot at all, I have to go back into recovery and flash another kernel before it does anything.
Siyah 6.0b4 will boot but doesn't seem to have a working home button.
I can't seem to find the latest CM10.1 Kernel for 4.2.1 roms. I've currently got LS8 modem.
I have no problems with DorimanX I just don't find it a very good Kernel, not very power efficient, don't get me wrong it's fast, but I want my battery to last.
Okay, so what is your question? You name a couple of kernels that don't work for you without telling which rom(s) you run. If all these kernels seem to fail in almost everything I think you'll have to start thinking about you yourself do something wrong, because of course nobody would use and praise a kernel if it doesn't boot.
Sent from the Matrix
I have tried a few roms, I was a long term fan of Rootbox until they removed the DPI Changer, I had tried 3.2 & 3.5, I've also tried stock CM10.1, Paranoid Android 2.99 and a few others that I now can't remember.
My question should have been more to the point, what the bloody hell am I doing wrong? I've been testing a few roms because I'd like to find one that I'm happy with for performance, customizability and battery life, I know it's never going to be a perfect balance, but that's why I'm testing so much.
I've been doing clean installs for all of them, factory reset, wipe cache, wipe dalvik, format system, install rom, install gapps, kernel cleaning script, new kernel, boot.
Ironically after stating in my OP that I couldn't find the CM10.1 kernel, I have just come across one, I just find that they have the best performance, I don't like the stupid complexity of Siyah 6+ and DorimanX, there's too many options that I have no idea what they do and I feel just aren't needed.
Oh yes. Siyah & Dorimanx are stupid because some n00b in Q&A says so You crap on about how much you want to customise, yet you want to run a 'vanilla' CM kernel which offers nothing of the sort compared to those two.
But, eh, whatever works for you.
Edit - Donnie, don't waste your time. OP obviously knows best.
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida
Hello. I used to have cm13+radon kernel. For some time after, I flashed a newer version of cm13, then when speaking on the phone, I experience call drops. I call someone, it accepts the call, but after some seconds (sometimes it's 2 secs and sometimes it's 30 secs) the call drops. But
Then I flashed an older version of cm13 + flashed radon again. But same thing! Then I flashed the rom again (no custom kernel this time) and no problem with calls. Fast forward, yesterday I flashed RR 5.8.0 + agni kernel+cam libs. Same thing happened again. I tried some cm14 firmware, but nothing changed. (actually I bricked the phone.)
Anyway now I am on RR 5.7.4 (nougat roms are buggy without kernels) and no custom kernel. What might be the problem? I can't flash custom kernels.
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
goofball2k said:
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
Click to expand...
Click to collapse
Without flashing kernel, there wont be a problem i guess because, right now I dont have the issue. (rr 5.7.4 no custom kernel). It shouldnt be kernel end, because i havent heard anyone beside me experiences this.