I flashed Cyanogenmod 12 on my GPe 5.0.1 converted XT1033 using Phillz Touch Recovery and then flashed Donkey kernel.One of my sims is working and all other features are also working but "WIFI is not TURNING ON".It gets stuck on "TURNING ON" and doesn't open.I have tried reflashing CM12 as well as DOnkeyKang kernel but doesn't work.
Please Help.
modifan14 said:
I flashed Cyanogenmod 12 on my GPe 5.0.1 converted XT1033 using Phillz Touch Recovery and then flashed Donkey kernel.One of my sims is working and all other features are also working but "WIFI is not TURNING ON".It gets stuck on "TURNING ON" and doesn't open.I have tried reflashing CM12 as well as DOnkeyKang kernel but doesn't work.
Please Help.
Click to expand...
Click to collapse
1). There is a Q&A subforum where this question should have been posted. No offense.
2). The size and colors, just, why? You have a problem with your eyes or something? (< this is a serious question)
And, this is because CyanogenMod has changed the way the kernels are built, kernel modules are now built into the kernel; DonkeyKang (and almost any custom kernel) loads the kernel modules from files. Which, in my opinion, is the stupidest change ever made in CM.
And the Wi-Fi support on the kernel was provided by a kernel module; from which CM12 has disabled the "loadable modules support" and has been now integrated into the kernel.
In short: You will have to wait until the kernel author corrects this, or use a older CM12 version, older than 08/01/2015. On that, you will be able to install your custom kernel.
Okay Thanks!!
That's all I wanted to know...I'll install a Nightly released before 8th Jan.
Related
Hi,
I have a issue that im not used to... i recently got a Nexus 5, and first thing i did was to unlock, root and install aokp rom(nightly)
Then i wanted to install Franco Kernel, using Francos own app to try flash... the device reboots, and are stuck on the google logo.
Have no other choice to enter fastboot mode, and reflash rom(to have it overwrite the kernel), and it starts up again.
Then tried to download kernel zip and flash it in TWRP instead, but with the same result. Also tried changeing to CWM but it doesnt work with encrypted devices.
I have always used AOKP + Franco Kernel on my older devices, but now it seems impossible.
I dont know why it doesnt work, but i have some ideas, and hope someone can put me in the right direction.
1. My device is encrypted and that makes it fail.
2. AOKP lastest nightly rom is not compatible with Franco Kernel or vice versa.
3. Something is broken...
Regards
Ranarn
aokp is cm based(CAF) i believe, which would make it incompatible with any aosp kernels.
simms22 said:
aokp is cm based(CAF) i believe, which would make it incompatible with any aosp kernels.
Click to expand...
Click to collapse
Ah that makes sense, but i guess something have changed then, since i have AOKP + Franco running on 2 older devices.
ranarn said:
Ah that makes sense, but i guess something have changed then, since i have AOKP + Franco running on 2 older devices.
Click to expand...
Click to collapse
yea, just last week cm source went back to CAF.
I know chaos kernel is CAF supported, I would give that a shot. I am still running 9.1 and it works the way I want it to for me (before they went CAF).
mistahseller said:
I know chaos kernel is CAF supported, I would give that a shot. I am still running 9.1 and it works the way I want it to for me (before they went CAF).
Click to expand...
Click to collapse
Ah thanks alot for the answers... not i know what kernels i can look for...
I bought the FKU app and I've been using it with the kernel updates for a good amount of time, but now I installed AOKP and used the app to auto-flash r34 and I got stuck at the the Google with the open lock screen. I thought it was a corrupt download or something, so wiped it and installed r33 from franco's archives. Same thing. r32, same thing. I even installed CM11 and retried and got the same result.
If anyone is having the same problem let me know!
Franco's kernel does not work with CM11 anymore, it's written all over Franco's kernel thread.
I'm not sure about AOKP, but if it's based on CM11, or if they went the same road as CM, that will not work as well.
I recently installed franco.Kernel R15 on my stock OPO with TWRP and I noticed when I plugged in my headphones, there is a full second delay of it being detected (this was also present on R14). Is this normal? This occurred on several other kernels on my OPO as well such as stock Mahdi's, stock CM11 M9/nightlies, and so on. I've tested these combinations and are without the aforementioned problem, PA stock, Franco R13 on all the ROMs I've tested with (PA, DroidKang, Mahdi, CM11S), CM11S stock.
This issue is definitely related to the kernel and I have tried to flash the official recovery image and same results after flashing franco kernel R15. And I would inquire about this in his thread but as of now, I'm not eligible to do so.
Thanks for the help! Cheers!
No one?
Whenever I flash a custom kernel (So far I've tried Donkey Kang and XPerience) on my moto g (xt1032), the wifi doesn't turn on. Its stuck on the "Turning Wifi On" screen in settings. Mobile Data works though. Right now I'm running Euphoria ROM(Which is based off of CM12) with its stock kernel. I'm just wondering if this is a CM 12 limitation, as it didn't work for any other cm12 based ROMs I flashed, including the original nightly from the cyanogenmod website. Thanks in advance!
Hello,
I searched for this issue but couldn't find the exact problem being experienced by others, so I'm asking about it now.
So I'm using the latest MultiROM and Lollipop firmware (the 02/09 one). I simply can't get any Lollipop ROM to stop bootlooping with a recent kernel. Boeffla, AK, Tyr, etc. all bootloop with every LP ROM I've tried, regardless if they're set as primary or secondary in recovery.
The only way I can get a ROM to boot is with a kernel meant for CM11/S, like AK r77 and Sensei r77, though I can't get the radios to work with these. But newer kernels simply won't work, period.
Am I missing something here? I thought the latest firmware and a recent kernel with kexec-hardboot was all I needed.
Edit: Also seems to happen with a fresh install of the latest CM nightly. Using the default kernel that comes with CM, too. There must be something that I am missing here...