Database Info

Cannot Install Custom Kernel

This is a strange problem that I only started to have once I installed Team Nekkid 7.2 RC dated 3/29.
I can flash the ROM no problem, wipe dalvik and fix permissions and I'm good to go without any issues. But if I flash the ROM, then either morfic or faux kernel, then gapps, when I go to wipe dalvik, all I get is a quick screen flash with no option to actually wipe dalvik.
I go back and wipe the overall cache completely, fix permissions, the reboot. I am now stuck at the morfic boot animation until i pull battery.
If i try to install a Faux kernel, same thing happens with dalvik, but gets stuck at the blue LG screen.
Once i battery pull and get back to CWM, i wipe everything, reflash ROM and gapps, wipe dalvik and fix permissions no problem and boot up into whatever ROM i choose.
EDIT: Went back and flashed Bionix 1.4.1 and was able to flash a Faux kernel and wipe dalvik. Booting up this ROM now.
I also have NO problem with ICS ROMS/kernels.

When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!

Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium

mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did all of that. I flashed the kernel before and after gapps but end up with the same result.
I have a feeling there is an issue with the CWM since I am constantly flashing roms/kernels and have never had these problems before. I'm at work so I cant use the Nvidia tool to flash CWM so I have to wait until I get home.

mariuscm said:
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Click to expand...
Click to collapse
I meant I have no problem flashing ICS roms and kernels.

mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
[UPDATE] Ok I got it now. Just read your last message

mariuscm said:
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
Click to expand...
Click to collapse
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.

stevew84 said:
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
Click to expand...
Click to collapse
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.

mariuscm said:
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
Click to expand...
Click to collapse
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.

stevew84 said:
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
Click to expand...
Click to collapse
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!

mariuscm said:
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
Click to expand...
Click to collapse
If the maps shows up and then goes blank, simply close the map and re-open it.

I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.

mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
All the important information will be in the first post of his thread. he doesn't include a change log, though.

mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
Yes, it's 4.0.4 with all of the latest CM9 commits.
Sent from my LG-P999 using xda premium

Degradation

Has anyone experienced degradation over time? I've been using CM10(nightly build for about 3 days and it seems like it has become a little buggy. Yes I know this is a nightly build and I did a search with no clear results. Just curious if anyone is experiencing the same issues? First it was the Wifi and then my cell signal indicator kept greying out. So I decided to try AOKP Evita for the HTC One X and flashed it and the wifi wasn't working at all with that rom. So I flashed back to CM10 and it seems to be working a lot better and faster. So do these mods degrade over time? If so, is there any easy method other then trying another mod because CM10 so far seems to be about the best just from reading and trying the AOKP CM 10 seems to be about the best out there.

RC196 said:
Has anyone experienced degradation over time? I've been using CM10(nightly build for about 3 days and it seems like it has become a little buggy. Yes I know this is a nightly build and I did a search with no clear results. Just curious if anyone is experiencing the same issues? First it was the Wifi and then my cell signal indicator kept greying out. So I decided to try AOKP Evita for the HTC One X and flashed it and the wifi wasn't working at all with that rom. So I flashed back to CM10 and it seems to be working a lot better and faster. So do these mods degrade over time? If so, is there any easy method other then trying another mod because CM10 so far seems to be about the best just from reading and trying the AOKP CM 10 seems to be about the best out there.
Click to expand...
Click to collapse
I haven't experienced degradation. Did you do a full wipe before you flashed?

absolutelygrim said:
I haven't experienced degradation. Did you do a full wipe before you flashed?
Click to expand...
Click to collapse
Yes, I did the factory restore, wiped the cache and the dalvik. Then once I flashed I wiped the cache and dalvik again then flashed Gapps and wiped.

AG is that Viper Rom Jelly Bean that you have as your signature?

RC196 said:
AG is that Viper Rom Jelly Bean that you have as your signature?
Click to expand...
Click to collapse
ICS - its sense based

is it ok to flash stock ics rom when on cm10?

Hello, yesterday I was on my phone when it suddenly just seemed to shut off. I have cm10, and want to get rid of it and go back to stock. can i go back to the stock ics rom instead of gingerbread, and be able to do it on cm10 at the time? i can restore to the time i had my phone just rooted and stock ics. i just dont want to go through the trouble of going back to gingerbread stock rom and then updating to ics stock rom through kies. thanks in advance.
side question: is it normal for my phone to randomly shut off on cm10? from what i hear, its the screen of death. it happened to me 2 days after i flashed cm10 and then happened yesterday. (i flashed cm10 last month). if it occurs this often im going back to stock. im fine with the t mobile apps as long as no random reboots occur.

Just restore a backup it will work fine
Sent from my SGH-T769 using Tapatalk 4

so stock ics rom rooted will have no problems right? no random shut-offs? i want to stay out of this risky business.

exo114 said:
so stock ics rom rooted will have no problems right? no random shut-offs? i want to stay out of this risky business.
Click to expand...
Click to collapse
Have you tried the latest cm10 nightly ? The screen of death has not been present in ages.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

flyers00 said:
Have you tried the latest cm10 nightly ? The screen of death has not been present in ages.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.

exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
Sorry to hear but the nightlies are very stable and with use of one of the custom kernels (lz or blue lightning) the phone is stable. If you decide to go back to stock ROM good luck with everything
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

exo114 said:
Hello, yesterday I was on my phone when it suddenly just seemed to shut off. I have cm10, and want to get rid of it and go back to stock. can i go back to the stock ics rom instead of gingerbread, and be able to do it on cm10 at the time? i can restore to the time i had my phone just rooted and stock ics. i just dont want to go through the trouble of going back to gingerbread stock rom and then updating to ics stock rom through kies. thanks in advance.
side question: is it normal for my phone to randomly shut off on cm10? from what i hear, its the screen of death. it happened to me 2 days after i flashed cm10 and then happened yesterday. (i flashed cm10 last month). if it occurs this often im going back to stock. im fine with the t mobile apps as long as no random reboots occur.
Click to expand...
Click to collapse
I too have been experiencing what appears to be the SOD. The bottom "soft buttons" light up and the phone is dead. I have to perform a forced reboot to get it working. I am running CM 10-20130804 but it was happening on nightly builds before this version as well. It happens every few days for me. I keep hoping the next build will make it go away but it always comes back. I even posted the issue in the CM 10 thread but no one had any ideas other than a complete wipe and reinstall and i would rather not do that for CM10. I am waiting for the 10.2.....

mine shut off less frequently than yours. my question is: can i download stock ics rom from sammobile and use that through odin? i dont want to use stock gingerbread rom and then update through kies.

exo114 said:
mine shut off less frequently than yours. my question is: can i download stock ics rom from sammobile and use that through odin? i dont want to use stock gingerbread rom and then update through kies.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1591601
The last post addresses your question...
Sent from atop a BeanStalk

exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
Nightlies are very stable. The listed "stable" has many issues and would pose more of a threat than the nightlies. Try them out sometime . If something happens (which I highly doubt something will) we will be here to help and guide you

xWolf13 said:
Nightlies are very stable. The listed "stable" has many issues and would pose more of a threat than the nightlies. Try them out sometime . If something happens (which I highly doubt something will) we will be here to help and guide you
Click to expand...
Click to collapse
I said the same thing as you last night. With the nightlies and one of the custom kernels ,its a great combo
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

flyers00 said:
I said the same thing as you last night. With the nightlies and one of the custom kernels ,its a great combo
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I agree too. The stable is from 11/13/12, almost a year old, lulz. The nightlies are super stable and very customizable.

Romman0 said:
I agree too. The stable is from 11/13/12, almost a year old, lulz. The nightlies are super stable and very customizable.
Click to expand...
Click to collapse
Truly amazing its almost a year. The cm10.2 ROM and variations are pretty stable for alpha builds. Once the camera is fixed we should be good to go.
I remember being the guinea pig testing a fully functioning rooted ROM stock and cm7. Come a long way lol
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

in the end i just went back to stock ics rom. no need to worry about random shut-offs (used to happen on stock rom rooted, with "shell has been granted superuser permissions"). can i delete the clockworkmod folder and root stuff? i take it i cant go into cwm recovery without root.

bump. final question is what do i need to delete to leave no traces of being rooted before? is it safe to delete the clockworkmod folder in my phone files?

exo114 said:
i'd prefer not to, i feel nightlies pose more of a risk than the stable. I think i'll just go back to my backup.
Click to expand...
Click to collapse
boulos said:
I too have been experiencing what appears to be the SOD. The bottom "soft buttons" light up and the phone is dead. I have to perform a forced reboot to get it working. I am running CM 10-20130804 but it was happening on nightly builds before this version as well. It happens every few days for me. I keep hoping the next build will make it go away but it always comes back. I even posted the issue in the CM 10 thread but no one had any ideas other than a complete wipe and reinstall and i would rather not do that for CM10. I am waiting for the 10.2.....
Click to expand...
Click to collapse
The quote-unquote "Stable" build was not stable at all. It was captured before it was supposed to. Something like 2 or 3 nightly builds after that they incorporated the SOD fix into the kernel.
The latest nightly for CM10 is 100% stable as far as SOD, reboots, crashes, etc. I didn't ever have any problems with it up until I flashed beanstalk. I encourage you to give the latest nightly a chance before you go back to 4.0.4, but it's ultimately your choice

Agreed with above
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

4.4 Kit/kat rom

I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.

mefistofel666 said:
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
Click to expand...
Click to collapse
nope those 3 build threads are it

I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)

SSPENCER10 is working very well for me. Everything he is putting out is stable and appears to be having fewer issues than KitKang. It is even working just as well with ART as it was with Dalvik. The 11-23 build also has the new CM11 boot animation.

markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
You realize they are all based on exactly the same code right?
And you realize that if one makes 'progress' they all make 'progress' because they use the same code right?

[ROM][4.3.1][Official][OSE Rom][d2vzw]
I'm using this one and so far so good.
It has nightlies that have 4.4

I'd recommend KitKang. It's been extremely stable and has really good battery life. ART works very well.
Sent from my SCH-I535 using Tapatalk

KitKang!!
Second that!!
Sent from my SCH-I535 using xda app-developers app

markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
Summary: I don't think KitKang is recognizing my SIM card, and is causing "Phone" to crash every second or two.
Hey guys, I tried flashing the latest KitKang ROM last night, but ran into a big issue. I wiped system, cache, dalvik cache, etc. I then reflashed the MF1 firmware (it was already flashed, but for some reason I always feel better re-flashing it every time.) Then I flashed the latest KitKang D2VZW nightly linked above, and flashed the GApps mentioned in that thread too. However, upon rebooting, every second or so it would say "phone has forced closed" (or something along those lines. Also, there was no signal. I got through the setup process after a VERY long time of pressing "okay" to that error and setting up my CM and Google accounts with one key in between each error. I thought I would be able to go into Mobile Networks and change the settings, which fixed certain early issues with CM10.1 or 10.2, but to no avail. I then tried reflashing (after wiping clean) CM10.2 again to get certain files for the phone to work, then flashing CM11 over that, and it seemed to work up until it freezes after getting to the home screen. Any thoughts on what the issue may be and/or how to fix it?
Thanks!
Sent from my SCH-I535 using xda app-developers app

[Q] [KERNEL] Newbie here, some direction needed

Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!

e_poch145 said:
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
Click to expand...
Click to collapse
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.

One other thing to note, is AOSP kernels are not compatible with TouchWiz roms, and TW kernels are not compatible with AOSP roms.
Make sure you get the right one, if the developer offers both options.
Sent from my SCH-I535 using XDA Premium 4 mobile app

buhohitr said:
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
Click to expand...
Click to collapse
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4

Thanks Guys!
SlimSnoopOS said:
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Much appreciated guys! I decided to go with [4.3/4.4][AOSP] ¤ BMS ¤ d2vzw / d2usc 3.4.y (link below). So far so good, flashed easily and no problems at this point. Ill report back and see how the performance gains are.
http://forum.xda-developers.com/showthread.php?t=2133550
Thanks again for all of your advice!

I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk

wont connect to wifi for me
twistedillutions said:
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol

e_poch145 said:
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
Click to expand...
Click to collapse
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4

versions im running
SlimSnoopOS said:
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Liquid Smooth 2.37 from 11/06/2013
KT747-AOSP-JB-MR2-3.4-VZW-11-04-2013
BMS_3.4_d2_2014-01-27

U need an older version of BMS thoss new version from dec till now are for 4.4 roms and liquid 2.37 is a 4.3 thats the reason why ur having issues
Sent from my unknown using Tapatalk