I currently have a phone running PAC man ROM and the stock kernel it came with. Im looking for ANY kernel to run on this ROM that increases battery life and overclocks but everytime I install a kernel, they always successfully install but my phone boots up without the boot animation and leads to a blank screen. The lights work and I can hear the volume controls and notifications, but nothing ever comes on the screen. I did this for 3 different kernels with the same result. I usually just reflash the PACman rom and all is good. What could the problem be?
Knucklez09 said:
I currently have a phone running PAC man ROM and the stock kernel it came with. Im looking for ANY kernel to run on this ROM that increases battery life and overclocks but everytime I install a kernel, they always successfully install but my phone boots up without the boot animation and leads to a blank screen. The lights work and I can hear the volume controls and notifications, but nothing ever comes on the screen. I did this for 3 different kernels with the same result. I usually just reflash the PACman rom and all is good. What could the problem be?
Click to expand...
Click to collapse
You could be installing the wrong kernel for your ROM. For example, the BMS kernel has a 3.0.x version and a 3.4.x version. With the PACman ROM, the 3.4.x version only works on the latest (4.3) nightlies, and the 3.0.x only works on the latest stable or 4.2 builds. That's the first thing I would check. Next, make sure you're flashing the correct kernel for your carrier (eg., d2spr, d2vzw, d2att, etc). But other than that, I don't know what could be causing your problems.
pirogoeth said:
You could be installing the wrong kernel for your ROM. For example, the BMS kernel has a 3.0.x version and a 3.4.x version. With the PACman ROM, the 3.4.x version only works on the latest (4.3) nightlies, and the 3.0.x only works on the latest stable or 4.2 builds. That's the first thing I would check. Next, make sure you're flashing the correct kernel for your carrier (eg., d2spr, d2vzw, d2att, etc). But other than that, I don't know what could be causing your problems.
Click to expand...
Click to collapse
thats kind of confusing. I have the latest PACman rom but its 4.2.2 and I was using dkp Kernel which had a 4.2x and a 4.3x.. So you're saying I should use the 4.3x and not the 4.2x one Ive been trying? Thanks
Knucklez09 said:
thats kind of confusing. I have the latest PACman rom but its 4.2.2 and I was using dkp Kernel which had a 4.2x and a 4.3x.. So you're saying I should use the 4.3x and not the 4.2x one Ive been trying? Thanks
Click to expand...
Click to collapse
If you're using a 4.2.2 AOSP ROM, this is version of dkp you wanna flash: http://d-h.st/uYG
If you're using a 4.3 AOSP ROM, this is the version of dkp you wanna flash: http://d-h.st/05V
Hope that helps...
davelikestacos said:
If you're using a 4.2.2 AOSP ROM, this is version of dkp you wanna flash: http://d-h.st/uYG
If you're using a 4.3 AOSP ROM, this is the version of dkp you wanna flash: http://d-h.st/05V
Hope that helps...
Click to expand...
Click to collapse
When I try the kernel, the boot animation disappears and I still get the blank screen while the phone is on.
Knucklez09 said:
When I try the kernel, the boot animation disappears and I still get the blank screen while the phone is on.
Click to expand...
Click to collapse
Try a different kernel? I don't know what else to recommend.
davelikestacos said:
Try a different kernel? I don't know what else to recommend.
Click to expand...
Click to collapse
So I figured out my phone needed a bootloader update to make everything work smoothly. Thanks for the help.
Knucklez09 said:
So I figured out my phone needed a bootloader update to make everything work smoothly. Thanks for the help.
Click to expand...
Click to collapse
Damn I was gonna say that. I had the same problem.. I had a JTAG done cuz I goofed and I was on the LEN bootloader.
In case anyone doesn't know how to check:
Open terminal emulator
Type: su
Type: getprop ro.bootloader
the last three are your radio
eg. L710VMD4
This is the best way to check because sometimes(like my problem) under settings>about phone my baseband said md4 but my boot loader actually was LEN so when I tried flashing I got the same blank screen.
Sent from my SPH-L710 using xda app-developers app
Related
Hi guys,
I'm running stock 4.1.2 Jelly Bean on my d2tmo Galaxy S3. When I look up kernels and whatnot, they are labelled many different ways. Some have JB in the name, some with AOSP in the name. I'm wondering: what types of kernels can I flash if I'm running a rooted stock ROM? I don't want to flash any custom ROMs because I'm a musichead and I like the stock music player
Thank you!
First of all you can get then stock music player with a custom rom
Second you can only run aosp kernels with an aosp rom. Aosp stands for android open source project. Aosp is not stock.
You can only use kernels labeled stock or touchwiz if you are using stock based rom
Sent from my SGH-T999 using Tapatalk 2
3rd of all, what in the heck do you want? Haha, you say you are running a 4.1.2 rom (only aosp available on TMO) so AOSP... but you want a kernel for stock (4.1.1) touchwiz rom? The stock music apk is great and works on all stock touchwiz based roms, and in my resource guide I have a huge list of what is available and what is what, if the kernel says 4.1.1 TouchWiz then it is for 4.1.1 TouchWiz. if it says 4.2 AOSP it is for 4.2 AOSP, if it says 4.1 AOSP then it is for 4.1 AOSP... Look in my resource bible in my signature, or in the dev sections for [kernel].
See, that's where I get confused. Sorry for the noob questions. I've been looking around but can't find clear, precise answers.
I'm running the stock TouchWiz, out of the box, 4.1.1 Jelly Bean (updated while not rooted to 4.1.2). That stock ROM is not the same as an AOSP ROM or an AOKP ROM, is it? I have another Android device that runs CM10.1 so I know a bit here and a bit there about ROMs and whatnot, but I'm not so confident when it comes to my S3.
Simply put, I want to keep that stock ROM, but get a custom kernel, because the stock kernel SUCKS. I need to know what kernels I can flash, and clninja already said I can only flash kernels labelled stock or TW. Am I correct, so far?
Thank you!
Well here's a Kernel that is supposed to be supported for STOCK rooted : http://forum.xda-developers.com/showthread.php?t=1785466 :highfive: But seriously you should get a custom ROM, the performance improvement is incredible and power management too ! :laugh:
There is a 4.1.2 stock ota ROM?!? I suck lol.
Sent from my SGH-T999 using xda premium
kruse1944 said:
Well here's a Kernel that is supposed to be supported for STOCK rooted : http://forum.xda-developers.com/showthread.php?t=1785466 :highfive: But seriously you should get a custom ROM, the performance improvement is incredible and power management too ! :laugh:
Click to expand...
Click to collapse
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
seokhun said:
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
There are a couple of touchwiz kernal's around, Ktoonsez is one that I would recommend, http://forum.xda-developers.com/showthread.php?t=1871946
Usually the general rule of thumb with upgrading custom rom is full wipe and flash, but some users has dirty flashed and had no problems so it depends whether your phone likes you or not.
mt3g said:
There is a 4.1.2 stock ota ROM?!? I suck lol.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I see what you did there. :highfive:
seokhun said:
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
Most of the times when you flash a ROM that is built off itself, you can "dirty flash". Example--> That means if you are already on a RootBox Nightly 2/17 with a clean install and RootBox 3/6 comes out, all you have to do is wipe /cache and /dalvik-cache and then flash the new version of the ROM. If any bugs creep up, then if you dirty flashed, chances are that is why.
If you are going to go from a TWiz ROM to an AOSP/AOKP ROM then I suggest a full factory reset and wipe accordingly. That way you have a clean install.
Read the OPs of the ROMs
TieDye21 said:
Usually the general rule of thumb with upgrading custom rom is full wipe and flash, but some users has dirty flashed and had no problems so it depends whether your phone likes you or not.
Click to expand...
Click to collapse
Yup. Thankfully my phone likes me, plus I kind of know what I am doing with regards to diagnosis.
@OP Can you please post exactly what your Build Number says in Settings>About Phone?
seokhun said:
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
You could install the update, but seriously I never do updates. I manual flash the whole new ROM. ( and I never had any accidents or bugs)
For the kernel, its was a example kernel chose the one you prefert ( THAT SUPPORT TOUCHWIZ STOCK ROM ) or just flash a new ROM with build-in kernel like the ParanoidKANGdroid 10.2 ROM !
I flashed the FrostyJellybean ROM with Xone kernel and it's been good so far. I'm a religious person when it comes to battery, but so far it's about the same as the normal drainage on the stock ROM, no noticeable improvements.
Another question (whoop): if I run a Nandroid backup, does that backup include the ROM itself? In other words, if I'm running the Frosty ROM, and there's a ROM I want to test, will creating a Nandroid include the Frosty, or will it just backup the system image excluding the ROM itself? I'm asking this because I have wanted to restore my Nandroids but didn't know if that backup may overwrite my existing ROM with the previous ROM.
Thank you guys for taking your time to help me out, I really appreciate it!
Woody said:
@OP Can you please post exactly what your Build Number says in Settings>About Phone?
Click to expand...
Click to collapse
I have flashed a new ROM, so I no longer have the stock Build Number. It now says FrostyJellybean v11.6. I can tell you for a fact that I was previously running 4.1.1 rooted but without any customization or mod whatsoever outside the phone's original settings, so as stock as you can get.
A Nandroid is essentially a snapshot of your ROM at that point in time. You can back it up, try a new ROM and if you don't like it, then restore your Nandroid. A Nandroid should be done before you flash anything. You don't necessarily have to keep them all except your latest, but at least have one for when you try something out.
You can flash and restore just fine from ROM to ROM. Only thing is, you can't restore across platforms. Meaning, if you are on JB 4.1.1, you couldn't restore to ICS 4.0.4. Likewise you can restore a JB 4.1.1 if you are on a JB 4.2.2 ROM because of the file structure. There are ways to do it, but I won't go into that right now. Moral of that story is you can flash and restore laterally as far as builds go, but you cannot restore across different base builds.
*************
I just wanted to see your Settings>About Phone>Build Number because in your OP, you stated that you were running "stock 4.1.2 Jelly Bean". We don't have a stock 4.1.2 ROM, so I was making sure you didn't have another phone. Sure, could be a T999 but there are Canadian versions out there that require different things.
Oh, about the Android version, yes, it's 4.1.1. I wrote 4.1.2 because I thought there was some stuff going on, like wireless and whatnot, and had previously read somewhere that 4.1.2 was rolling out and my phone was doing the "Android is upgrading" thing when it booted up and I didn't check the version before writing that. No worries, it was the stock 4.1.1.
Thank you so much for answering my questions, you guys are awesome!
The title says it all. Can this be done?
re: random rom
androidiphonehacker said:
The title says it all. Can this be done?
Click to expand...
Click to collapse
There is no such thing as a "random aosp rom".
If you really need help, please include as much specific information as you can as to what you want to achieve.
Good luck!
Well, I have a ROM on my m919 Samsung Galaxy s4 called "Google edition s4". Here's the link to the ROM development:
http://forum.xda-developers.com/showthread.php?t=2341026
So, when I installed the ROM, it also installed an i9505 kernal and replaced it from the "SGH-M919" kernal.
What I want to do, (because of a number of reasons) is install the Cyanogenmod 10--i9505 kernal onto my Phone, (NOT THE ROM!) just the kernal from it (Through ODIN).
Can this be possible, or would this potentially mess up my phone, by installing a different ROM's kernal onto another ROM?
androidiphonehacker said:
Well, I have a ROM on my m919 Samsung Galaxy s4 called "Google edition s4". Here's the link to the ROM development:
http://forum.xda-developers.com/showthread.php?t=2341026
So, when I installed the ROM, it also installed an i9505 kernal and replaced it from the "SGH-M919" kernal.
What I want to do, (because of a number of reasons) is install the Cyanogenmod 10--i9505 kernal onto my Phone, (NOT THE ROM!) just the kernal from it (Through ODIN).
Can this be possible, or would this potentially mess up my phone, by installing a different ROM's kernal onto another ROM?
Click to expand...
Click to collapse
A Google Edition ROM in looks like pure AOSP, but in fact it's kernel is touchwiz, if you flash a as you refer "CM10 kernel" by what I assume you mean AOSP kernel, then you'd probably either brick or soft brick your phone. so...be careful!
NinoBrown1911 said:
A Google Edition ROM in looks like pure AOSP, but in fact it's kernel is touchwiz, if you flash a as you refer "CM10 kernel" by what I assume you mean AOSP kernel, then you'd probably either brick or soft brick your phone. so...be careful!
Click to expand...
Click to collapse
Yeah, the first time I flashed a GPe ROM I mistakenly flashed an AOSP custom kernel. It'll just hang the phone on the SGS4 until a TW kernel is flashed.
Toleraen said:
Yeah, the first time I flashed a GPe ROM I mistakenly flashed an AOSP custom kernel. It'll just hang the phone on the SGS4 until a TW kernel is flashed.
Click to expand...
Click to collapse
So then, I should install my TW kernal.
More specifically on what I am doing...
I want to edit the drivers on (apparently a TW kernal) to where I can connect a Wireless adapter to use with Ubuntu chroot to do (what's in the picture). How do I edit the driver configuration on this kernal? (LINK)
https://docs.google.com/file/d/0B1rJR1viXH_BaUdaUGVUMEUzY1E/edit?usp=docslist_api
Hey guys. So, I've been reading and reading and flashing and everything.
Got an S4. It was running 4.3 and I was having Wifi issues.
I had read it was a software issue and welp, I've always liked Cyanogen Mod so I installed that.
It installed the nightly build which was WAY too buggy (I use my camera a lot and it kept failing) edit: but the WiFi worked perfectly!
I got back to 4.2.2 now but now the WiFi is Totally not working now and i'm getting that message about
Kernel is not Seandroid enforcing
set warranty bit : kernel
and it takes forever to reboot.
Since I was on 4.3 do i need to flash that stock rom to get my stock kernel back?
Or can I install deoxed version??
I still need to put custom recovery too!
I know this is a lot of questions and i'm not much of a n00b.
Any help would be greatly appreciated.
Thanks in advance.
re: wifi not working
djphooka said:
Hey guys. So, I've been reading and reading and flashing and everything.
Got an S4. It was running 4.3 and I was having Wifi issues.
I had read it was a software issue and welp, I've always liked Cyanogen Mod so I installed that.
It installed the nightly build which was WAY too buggy (I use my camera a lot and it kept failing) edit: but the WiFi worked perfectly!
I got back to 4.2.2 now but now the WiFi is Totally not working now and i'm getting that message about
Kernel is not Seandroid enforcing
set warranty bit : kernel
and it takes forever to reboot.
Since I was on 4.3 do i need to flash that stock rom to get my stock kernel back?
Or can I install deoxed version??
I still need to put custom recovery too!
I know this is a lot of questions and i'm not much of a n00b.
Any help would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
If you are using any Cyanogen/AOSP/AOKP/GE/KiKat roms then please ignore the following.
If you are using a M919 Tmobile Samsung S4 Jellybean Touchwiz 4.2.2 based rom then here is
the way to fix your wifi issue.
Here is the download link for Ktoonsez's custom kernel:
http://ktoonsez.jonathanjsimon.com/sgs4/TW/KT-SGS4-JB4.2-TW-TMO-12.12.2013.zip
Download it and flash it using cwm/twrp recovery and the wifi will work for you again.
Good luck!
I'm running the stock rom but it seems like somehow it didn't overwrite the Cyanogen kernel.
re: kernel
djphooka said:
I'm running the stock rom but it seems like somehow it didn't overwrite the Cyanogen kernel.
Click to expand...
Click to collapse
That means that this kernel is for you..... "IF you are really running the stock rom".
If your rom was REALLY stock, I mean if you "ODIN" flashed the stock rom using the
official Samsung M919 4.2.2 Jellybean Touchwiz firmware from http://SamMobile.com
or other sources then whatever kernel you had the stock rom would have over-written it.
If you are sure that it's not over written that means that you have NOT ODIN flashed the
official 4.2.2 M919 MDL firmware.
Good luck!
I have two questions about N3 KK Kernal.
1) Which kernal for KK is the best to use
2) Which kernal provides regular charging when it powered down, IE not showing kernal not seadriod or hangs when the battery animation starts
One other inquiry, if installing KK on clean IE full wipe and install kernal and keeps on rebooting at samsung logo, any suggestions
nofroyo said:
I have two questions about N3 KK Kernal.
1) Which kernal for KK is the best to use
2) Which kernal provides regular charging when it powered down, IE not showing kernal not seadriod or hangs when the battery animation starts
One other inquiry, if installing KK on clean IE full wipe and install kernal and keeps on rebooting at samsung logo, any suggestions
Click to expand...
Click to collapse
1. That depends on what you want. I know a lot of people like lean kernel. I am using CivZ and have no issues, but I have yet to really start messing with it.
2. Someone with better knowledge will have to answer.
3. Your phone probably does not like that kernel, that or you got a bad download. Thus the bootloop.
SM-N900T: Powered by X-Note V13/CivZ-SnapKat 2.1
FFTony said:
1. That depends on what you want. I know a lot of people like lean kernel. I am using CivZ and have no issues, but I have yet to really start messing with it.
2. Someone with better knowledge will have to answer.
3. Your phone probably does not like that kernel, that or you got a bad download. Thus the bootloop.
SM-N900T: Powered by X-Note V13/CivZ-SnapKat 2.1
Click to expand...
Click to collapse
Yea hopefully someone can provide some insight
anyone experience this on 4.3 bootloader and on kitkat rom?
nofroyo said:
anyone experience this on 4.3 bootloader and on kitkat rom?
Click to expand...
Click to collapse
They are not compatible... Most 4.4.2 kernels have to be on that bootloader. .. It's not recommended to use 4.4.2 kernel or rom on a 4.3 bootloader anyway. ..
Sent from my SM-N900T using XDA Premium 4 mobile app
Hey all, I am runnig a rooted stock LS980, with TWRP, I just got an OTA push tonight, and I am not going to flash it, but I hate the notification so I guess I am going to flash a custom rom instead of waiting until I get home. Which rom do you all recommend?
I am thinking pac-rom, but the most recent nightly was 7/10, but there is a build called pac_ls980-dev-20140730 can anyone tell me what this is?
Also I cannot find the Gapps to pacrom?
Do you recommend cyanogenmod or AOKP and why? which version should I flash and Gapps???
Thank you!
eddytheyeti2 said:
Hey all, I am runnig a rooted stock LS980, with TWRP, I just got an OTA push tonight, and I am not going to flash it, but I hate the notification so I guess I am going to flash a custom rom instead of waiting until I get home. Which rom do you all recommend?
I am thinking pac-rom, but the most recent nightly was 7/10, but there is a build called pac_ls980-dev-20140730 can anyone tell me what this is?
Also I cannot find the Gapps to pacrom?
Do you recommend cyanogenmod or AOKP and why? which version should I flash and Gapps???
Thank you!
Click to expand...
Click to collapse
You dont have to swap roms to lose the notification. Just swipe down and click and hold the notification, open the app info and select the notification check mark off.
Personally I enjoyed the Liquid Smooth rom, it was very fast. And any standard gapps file for your version of android should be fine. Just remember to flash the ZV8 radio if you are going with an AOSP rom. Or flash dr87s kernel. And not to sure what that build of pac-rom is. And I enjoyed Cyanogen for a bit, they are always working on new things, you know that there's going to be a fix to any problems that arise. And I love the blue look. But everyone uses roms for different things, I mainly use stock, rooted with xposed framework.
Why not try them all?
Tannereed said:
You dont have to swap roms to lose the notification. Just swipe down and click and hold the notification, open the app info and select the notification check mark off.
Personally I enjoyed the Liquid Smooth rom, it was very fast. And any standard gapps file for your version of android should be fine. Just remember to flash the ZV8 radio if you are going with an AOSP rom. Or flash dr87s kernel. And not to sure what that build of pac-rom is. And I enjoyed Cyanogen for a bit, they are always working on new things, you know that there's going to be a fix to any problems that arise. And I love the blue look. But everyone uses roms for different things, I mainly use stock, rooted with xposed framework.
Why not try them all?
Click to expand...
Click to collapse
I am pretty comfy with cyanogenmod, I have used it since I got my HP touchpad two years ago, however I prefer pac-rom.
can I get the ZV8 radio link please? what is the dr87s kernel? good or bad? I am running kernel 3.4., but i believe to be a JDI kerel, and not LGD because I flashed the white lines fix.
CM11 is a great ROM, but I will warn you, if you're in an area with Spark (B26 of B41), ZV8 radio wont connect to those automatically. If you're wanting to keep Spark enabled, I'd recommend Slim or Mahdi until CM11 updates their kernel to support the newer modems.
Also, newest Mahdi/Slim will auto detect your display during installation so you will not need to worry about having a JDI panel.
EDIT: Here's Mahdi's Thread and here's SlimKat's Thread. They both use Dr87's kernel which is boss.
What Ascertion said is spot on, but here is the link for a zv8 radio. It also contains a lot of useful information. http://forum.xda-developers.com/showthread.php?t=2627765
Ascertion said:
CM11 is a great ROM, but I will warn you, if you're in an area with Spark (B26 of B41), ZV8 radio wont connect to those automatically. If you're wanting to keep Spark enabled, I'd recommend Slim or Mahdi until CM11 updates their kernel to support the newer modems.
Also, newest Mahdi/Slim will auto detect your display during installation so you will not need to worry about having a JDI panel.
EDIT: Here's Mahdi's Thread and here's SlimKat's Thread. They both use Dr87's kernel which is boss.
Click to expand...
Click to collapse
Tannereed said:
What Ascertion said is spot on, but here is the link for a zv8 radio. It also contains a lot of useful information. http://forum.xda-developers.com/showthread.php?t=2627765
Click to expand...
Click to collapse
So, If I were to flash Slimrom, and the Gapps, do I have to flash the dr87 kernel as well as the ZV8 radio?
in the install directions it says to wipe everything, however i was told not to wipe system before when flashing a rom... should I or shouldn't I?
Super g2 is the best
eddytheyeti2 said:
Hey all, I am runnig a rooted stock LS980, with TWRP, I just got an OTA push tonight, and I am not going to flash it, but I hate the notification so I guess I am going to flash a custom rom instead of waiting until I get home. Which rom do you all recommend?
I am thinking pac-rom, but the most recent nightly was 7/10, but there is a build called pac_ls980-dev-20140730 can anyone tell me what this is?
Also I cannot find the Gapps to pacrom?
Do you recommend cyanogenmod or AOKP and why? which version should I flash and Gapps???
Thank you!
Click to expand...
Click to collapse
Super g2 is the best by FAR