Develop Bugs

[Q] Bananacakes kernel on InsertCoin ROM?

Hi all,
Has anyone tried the new bananacakes kernel 0.4 based on the official kernel source?
I tried installing it but my phone randomly resets every now and then. I've gone back to a Nandroid backup for now but I'd really like to use the new kernel.
Can someone who has successfully updated their InsertCoin ROM with the new kernel post some tips?
Thanks.

TBH, if you have problems with a kernel or any other file you flash or install, you're better off not using it anyway. Just "suffer" with what you've got.
You could always try a different ROM with a kernel (if compatible) or try a different kernel with the existing ROM.
Have you tried reflashing/installing the ROM and kernel from new after full wipe? Sometimes you can get issues with a file and undoing then re-flashing/installing can sort this most of the time (providing the file is stable). Are there any instability notes with the ROM/kernel? If so you may want to wait until stable versions are posted.

I updated the kernel without doing a full wipe, didn't want to lose all my settings.
Oh well, I'll do a full wipe and give it a try.
Thanks.

Resetting Between Custom Kernel Flashes on JB

Is there a normal procedure people follow when flashing new kernels on JB in order to ensure they are removing any scripts or tweaks left behind by previous custom kernels?
On ICS, I used to wipe cache/dalvik and flash faux's reset kernel just to be sure, but faux hasn't released a kernel like that for JB yet.
I understand the faux reset kernel replaces the boot.img(?) but I was just curious if there is standard procedure most people follow to make sure new kernel flashes are starting from scratch.

PeterGunz said:
Is there a normal procedure people follow when flashing new kernels on JB in order to ensure they are removing any scripts or tweaks left behind by previous custom kernels?
On ICS, I used to wipe cache/dalvik and flash faux's reset kernel just to be sure, but faux hasn't released a kernel like that for JB yet.
I understand the faux reset kernel replaces the boot.img(?) but I was just curious if there is standard procedure most people follow to make sure new kernel flashes are starting from scratch.
Click to expand...
Click to collapse
bro, most of the time, i just follow the authors instruction on how to install the kernel. i don't do wipes when installing kernel ever since gingerbread and i never encountered any problem.

crazybone21 said:
bro, most of the time, i just follow the authors instruction on how to install the kernel. i don't do wipes when installing kernel ever since gingerbread and i never encountered any problem.
Click to expand...
Click to collapse
Thanks. I noticed some people having trouble with scripts sticking around after flashing new kernels, so I was just double checking,

Cannot get wifi to turn on on multiple ICS ROMS for R800x

I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!

fuhrl said:
I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
Click to expand...
Click to collapse
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.

Xperia Player said:
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Click to expand...
Click to collapse
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?

fuhrl said:
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
Click to expand...
Click to collapse
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium

DubleJayJ said:
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
Click to expand...
Click to collapse
ok. thanks. Just as a clarification to the first part of the original response, I am installing the original stock kernel after i flash back to the stock ROM?

well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.

fuhrl said:
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
Click to expand...
Click to collapse
What version of FXP are you using, and what are the wifi zips called that you're using?

lightningdude said:
What version of FXP are you using, and what are the wifi zips called that you're using?
Click to expand...
Click to collapse
i used FXP 132. I know it's not the latest but I'm sure that it was when I downloaded it a month ago. The zips were cleverly named wififix2, WiFi_FiX_LuPuSv3 and the other was CDMA_mega_fix_v2_by_Leraeniesh. The last one had a WiFi fix in it by Atarii or someone like that.

had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.

nyvang101 said:
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
Click to expand...
Click to collapse
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?

Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.

Xperia Player said:
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Click to expand...
Click to collapse
i think you have to flash doomlords wifi modules in recovery. it's what worked for me when i was using that rom.
http://forum.xda-developers.com/showthread.php?t=1579388

fuhrl said:
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Click to expand...
Click to collapse
The ftf has the stock kernel in it.
Sent from my SCH-I500

here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.

nyvang101 said:
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
Click to expand...
Click to collapse
did this work? i have the latest PACman JB rom for the r800x and im using the lupus v5 kernel that came with it. for some reason all the other roms have working wifi except cyanogenmod based roms....... why is this?

[Q] PA 3.00 doesn't boot

Hi everyone,
I wasn't used to consider myself a too-much-noob anymore, but now I've plenty of doubts.
So, here's my problem: I've decided to give the latest ParanoidAndroid release a try and my maguro was "oem locked". Then, I've run the command "fastboot oem unlock" and copied all files I needed (PA rom, GlaDos v2.2 and latest GApps) into my /sdcard folder (usual job). I've rebooted into recovery (latest touch CWM), formatted /system, /data, /cache (usual full wipe), searched for the files and flashed them.
When it was time to reboot, the phone got stuck at the first screen (black, with the white "Google" and the white opened padlock). In other words, the bootanimation didn't even start.
Then, I've re-downloaded the stuff, double-checked all Md5 sums, re-copied everything in the sdcard but the result didn't change.
I've tried to re-flash the stock unrooted rom, then repeating the steps without formatting /system. I've also tried to not flash the kernel. No way the rom could even boot.
Now I'm seriously wondering what's wrong with what I've done . For completeness, my bootloader version is LC03 and the radio is XXLJ1 (same as the fully stock android bundle that can be found here)
I've also checked (maybe too much quickly, I may admit) the threads for PA and GlaDos, but I haven't seen anyone complaining about the same problem...
Could you guys please help me?

First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
- Based on stock Android kernel Jelly Bean 4.1.1 JRO03C
Click to expand...
Click to collapse

Pirateghost said:
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
Click to expand...
Click to collapse
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki

Endriu90 said:
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Click to expand...
Click to collapse
i have been looking forward to a new GladOS...thanks for the link
in recovery, all you have to do is factory reset then flash the rom. thats it
EDIT:
which version of PA 3.0 are you trying to install

Pirateghost said:
which version of PA 3.0 are you trying to install
Click to expand...
Click to collapse
I've tried with all releases which can be found here

Flash Kernel too
Hi,
When the new PA version was uploaded (20 Feb), this was the warning posted by the developer:
WARNING
As I didn't have so much time, I couldn't make it booting with default kernel (Need to update prebuilt kernel). So if you're gonna use it BE SURE YOU FLASH A CUSTOM 4.2.2 KERNEL!
Click to expand...
Click to collapse
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Hope this helps.
Regards,
Neeraj

neerajvd said:
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Click to expand...
Click to collapse
Thank you guys, I've solved (I've tried just with the factory reset as said by pirateghost, but I was used to format /system, /data and /cache when it was time to flash roms like AOKP and everything used to work properly) (I was used to do the same with the Nexus S).
Now I'm running the 15feb release with the stock android kernel (which comes with the stock 4.2.2 factory bundle) and everything just works as expected.
Anyway, I still can't get the reason why GlaDOS shouldn't work with the 20feb release. I mean, it's a custom kernel and it should work as well as AK or franco kernels, shouldn't it? If I'm wrong, could you briefly tell me why? (sorry, I won't move to other kernels, as I personally love GlaDOS and it provides my GNex with the optimal equilibrium performances/battery life)
EDIT:
alongside the 15feb release, I've tried to flash GlaDOS (just factory-resetting before flashing), but nothing boots. Restored the backup, now I'm still running PA with the stock kernel

[Q] StockMOD Custom ROM 4.3 RLS2.1 Question

am I able to flash this StockMOD Custom ROM 4.3 RLS2.1 for att or tmobile, over my existing stock 4.4.2, my modem as of now is i747UCUFNE4 but the rom description says to flash the 4.3 modem or it wont get data? someone help me out
heres the rom url http://forum.xda-developers.com/showthread.php?t=2504903

do not flash the older modem. just flash the rom and youll be good to go.

DocHoliday77 said:
do not flash the older modem. just flash the rom and youll be good to go.
Click to expand...
Click to collapse
since im coming from stock 4.4.2 do I only wipe cache n dalvik before flashing

You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.

one more question
DocHoliday77 said:
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
Click to expand...
Click to collapse
Thank You I tried wiping cache n dalvik, it hung but I went back in to twrp n wiped cache n dalvik again after install, worked like a charm!!!!!
hank you very much but can you answer me one question is there anyway you or another could port the revolutionary s5 v3 to the i747 it looks so amazing they only have it for the s3 i9300 not the s3 i747

Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....

DocHoliday77 said:
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
Click to expand...
Click to collapse
well thank you very much for responding you've been a very patient n helping hand if you could maybe you could pass it around to some of the other developers you are in contact with I know of about 30 people personally that would love to have that on there i747 not counting the people ive seen on here asking for a rom from the s5 but no big deal THANKS AGAIN

I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.

plastic_green_head said:
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
Click to expand...
Click to collapse
if you flashed it without wiping cache n dalvik- dirty flash then it should have worked unless u came from another 4.4.2 rom mine is working fine
correct me if im wrong

If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.

DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all

DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
Why exactly will it not work to flash a MJB kernel?
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.

Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
Are you using this rom along with the included kernel? Or something different?
plastic_green_head said:
Why exactly will it not work to flash a MJB kernel?
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Click to expand...
Click to collapse
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)

DocHoliday77 said:
Are you using this rom along with the included kernel? Or something different?
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
Click to expand...
Click to collapse
whatever kernel that was built into the rom is what im on I listed it in my reply before, I haven't flashed anything else ONLY THE ROM, mine booted right up n works great,

The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.

DocHoliday77 said:
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
Click to expand...
Click to collapse
well I have a twrp backup of it on my phone if you have some way of opening it, maybe somehow I could send it to you n whatever you find may be a tremendous help to you in how to fix the wifi n not having to flash the other kernels

I dont think there would be anything in a nandroid backup that would help. But tbh, right now I have no intention of digging into it any further. First because we already do have a pretty simple solution, and second because im already swamped with other projects and problems I've promised others I would work on.