I'm not really sure I understand and maybe someone can help me to, but the appeal of CWM to me was the ability to flash a ROM without needing a PC. However, most of the ROM's in the dev section say that a kernel flash is required and the utility requires a PC. The appeal of being able to flash a new ROM at any time is lost since I need to wait until I'm at home with my PC. If a kernel flash at the PC is required for most ROM's then why CWM at that point?
I'm realizing as I write this that the answer is likely that it's easier for a noob than adb. I still ask the question in the event there is something else I'm missing.
Also, before I get 30 hypersensitive replies about not appreciating the devs work and I should dev something myself if I don't like it please know that this is not intended to criticize the work of the devs. I'd just like to know if there is something I'm missing or maybe that I'm misunderstanding that a kernel flash is required when I read the releases.
BialyMurzyn said:
I'm not really sure I understand and maybe someone can help me to, but the appeal of CWM to me was the ability to flash a ROM without needing a PC. However, most of the ROM's in the dev section say that a kernel flash is required and the utility requires a PC. The appeal of being able to flash a new ROM at any time is lost since I need to wait until I'm at home with my PC. If a kernel flash at the PC is required for most ROM's then why CWM at that point?
I'm realizing as I write this that the answer is likely that it's easier for a noob than adb. I still ask the question in the event there is something else I'm missing.
Also, before I get 30 hypersensitive replies about not appreciating the devs work and I should dev something myself if I don't like it please know that this is not intended to criticize the work of the devs. I'd just like to know if there is something I'm missing or maybe that I'm misunderstanding that a kernel flash is required when I read the releases.
Click to expand...
Click to collapse
Yes! You missed this thread
All the latest roms are using Faux kernel anyways, Flash once, and then you can use CWM to flash any multiple roms you want
The ONLY time you NEED to flash a seperate kernel is when going to a totally different build. Examples:
Sense 3.0 to Sense 3.5
Sense 3.5 to Sense 3.0
ICS to Sense 3.0
ICS to Sense 3.5
Sense 3.0 to ICS
ICS to Sense 3.5
...etc
Other than that the kernel that you use is still pretty much stock.
rbaruch said:
All the latest roms are using Faux kernel anyways, Flash once, and then you can use CWM to flash any multiple roms you want
Click to expand...
Click to collapse
This is true, but each successive release says that a kernel update is needed. I am assuming that this includes not only those freshly flashing the ROM, but also those flashing from a ROM's previous version. Are they incompatible from version to version? Basically, if I'm bored while out and wanted to flash a ROM then flash the kernel later are there risks?
antiquezip said:
Yes! You missed this thread
Click to expand...
Click to collapse
This looks great! Since T-Mobile just throttled my data for the remainder of my billing cycle I will have to follow the thread and then give it a try later when I have WiFi. Thanks for the link.
Thanks Binary. That makes sense. No pun intended. So then the boot.img a dev includes with the packaged ROM is more or less a suggested kernel to best optimize their ROM and not that there are features of a ROM that will not work?
BialyMurzyn said:
Thanks Binary. That makes sense. No pun intended. So then the boot.img a dev includes with the packaged ROM is more or less a suggested kernel to best optimize their ROM and not that there are features of a ROM that will not work?
Click to expand...
Click to collapse
That depends on the kernel that the developer includes.
If it's a faux edition then there are a few tweaks however it's still stock.
All features should be accessable in the rom as long as you are using an unsecured kernel.
Related
Does his new kernel in GB NOT work in any other non GB ROMs? I hate the look of GB and all the themes are hideous. Am on Sheds Vanilla ROM (LAST RELEASE) and I really wanna try his new kernel. How come he hasn't released it like he normally does in his kernel update thread? :/
You could always just ask him - you know, a PM or something.
If you are eager to put your hands on it, just yank it out of the boot.img from one of the ROMs that claims to have it, and pack up your own boot image with it. If you have S-OFF, you don't even need to make a signed install package; just flash it with fastboot.
I knew I had read this somewhere.
According to this: http://forum.xda-developers.com/showpost.php?p=11286048&postcount=645
The Kernels are different, this rom uses an Unreleased version of Conap's CFS kernel, while Tazz's Froyo rom was using CFSv9... but they are basically the same, the unreleased Kernel has Ext4 abilities as where CFSv9 does not.
Click to expand...
Click to collapse
So that may be why it hasn't been released as a new kernel: it adds one featured that only GB ROMs need. But perhaps I should just let Conap answer...
I had researched and found that pretty much only change in the changelog, as well. From my understanding, the added ability doesn't even really do anything on the Eris...yet. Since we're not using Ext4 for anything, but maybe as you noted, Gingerbread at least requires the ability for whatever reason, if it's not made use of.
I am looking for a ROM that allows overclocking.. currently I just tried Suprarom as it's AOSP with HTC Sense so still very similar to what I am use to without a whole new learning curve. But I hate it when developers developing these ROMS don't unlock them completely Set CPU does not work.. I can not overclock so I need to know what would be the best ROM for me that allows overclocking but not too much of a new learning curve and 3D and that still works.
molitar said:
I am looking for a ROM that allows overclocking.. currently I just tried Suprarom as it's AOSP with HTC Sense so still very similar to what I am use to without a whole new learning curve. But I hate it when developers developing these ROMS don't unlock them completely Set CPU does not work.. I can not overclock so I need to know what would be the best ROM for me that allows overclocking but not too much of a new learning curve and 3D and that still works.
Click to expand...
Click to collapse
Overclocking does not require you to flash a different ROM. Just flash a overclockable kernel on your current ROM and you will be fine.
NOTE: Not all kernels work on every ROM.
mnomaanw said:
Overclocking does not require you to flash a different ROM. Just flash a overclockable kernel on your current ROM and you will be fine.
NOTE: Not all kernels work on every ROM.
Click to expand...
Click to collapse
ok thanks.. so guessing that Anthrax v2 that appears stickied is the one to flash than.
molitar said:
ok thanks.. so guessing that Anthrax v2 that appears stickied is the one to flash than.
Click to expand...
Click to collapse
I do not guarantee this will work on your current ROM or not.
If anything goes wrong like you are stuck on htc screen/broken wifi/4g etc reflash th kernel that came with your rom. Also if you are on hboot 1.50 you will need flash image GUI to change kernel or use fastboot method. I dont know whether these can be overclocked or not. Check their description. What is your current rom based on?
2.08.651.2/.3 or 2.17.651.5 ?vCheck whether those kernels are made for your current version.
Hope this helps.......
http://forum.xda-developers.com/showthread.php?t=1427963
http://forum.xda-developers.com/showthread.php?t=1224659
Search here there might be kernels in some folders
http://www.androidfilehost.com/main/EVO_3D_Developers/
Don't flash this as you already have one from ur ICS ROM! I just did not see any Stock Kernel that is the reason why i made a thread!
Haven't seen a stock ICS 4.0.3 kernel in development section so i m just dropping stock kernel in case some one needs it.
It meant we'll have mod kernel soon? Better battery faster ... everything.
Sent from my AT&T Galaxy Note™ - please forgive any typos
ummm... what?! Is this i717 specific, or just the AOSP 4.0.3 kernel? How did we get this for the i717 without source? Where is it from? So many questions!!!11 lol
If this is for real, someone please throw a bucket of ice water (and/or trout) on Da_G...
I have tried to use this tool http://forum.xda-developers.com/showpost.php?p=20806471&postcount=1 to inject init.d support into the stock kernel but cannot tell if it worked. It worked on the stock ICS kernel for the Asus Transformer according to this post. http://forum.xda-developers.com/showpost.php?p=23005237&postcount=104
Anyone else more familiar with init.d care to try it? It did give me an init.d folder, and the command prompt on PC seemed like it was successful but I can't tell from the file it placed in init.d after first boot if it was successful or not. I tried putting a supercharger script in the init.d folder but it doesn't seem to be working.
edit: Also at the risk of sounding dumb I don't know what set permission as 755 is. I tried to set the permissions of the folder to match the other folders in the directory.
I don't understand why are guys so happy about this ?
This kernel (boot.img) is already in ICS ROMs,
you can just unzip one of those ROMs or the leak and there you have it !
They need kernel SOURCE to do overclock etc.
Sent from my SGH-I717D using Tapatalk 2
Jckpsa said:
I don't understand why are guys so happy about this ?
This kernel (boot.img) is already in ICS ROMs,
you can just unzip one of those ROMs or the leak and there you have it !
They need kernel SOURCE to do overclock etc.
Sent from my SGH-I717D using Tapatalk 2
Click to expand...
Click to collapse
I was assuming this was source... which, as my previous post indicates, wouldn't make sense.
Otherwise, you're right, this isn't anything special. Nice to have separately? Sure, I guess...
so what is a kernal is this a ics leak, im a nubie and pretty stupid.
thanks
Guys, this is STOCK ICS 4.0.3 Kernel. In other words, the kernel that was provided with the leak. It's unmodified.
zer0nine said:
Guys, this is STOCK ICS 4.0.3 Kernel. In other words, the kernel that was provided with the leak. It's unmodified.
Click to expand...
Click to collapse
yes we know this.......which is not that useful for the dev....as they need the source code for the kernel.....without the source code....we can't OC/undervolt and do all the lovely things that we need...
I've been wanting a stock ICS version as there have been a few bugs that I can't get away from with the two mods I've tried... Maybe it's ICS, maybe it's me, but now I can see how the original runs. Thanks!
Surrylic said:
I've been wanting a stock ICS version as there have been a few bugs that I can't get away from with the two mods I've tried... Maybe it's ICS, maybe it's me, but now I can see how the original runs. Thanks!
Click to expand...
Click to collapse
You do know this is just the kernel right? If you flash only this after a full wipe, you're not going to have a booting Android phone.
You sure? I would think it would be more like flashing it to what is already in it, unless, this is not for the i717.
thair7391 said:
You do know this is just the kernel right? If you flash only this after a full wipe, you're not going to have a booting Android phone.
Click to expand...
Click to collapse
C0BRA01 said:
You sure? I would think it would be more like flashing it to what is already in it, unless, this is not for the i717.
Click to expand...
Click to collapse
I think he means if you flash it after a "full" wipe, meaning clearing the system. If you just do a data and cache wipe it should be fine, if of course you are running an ICS ROM.
live4nyy said:
I think he means if you flash it after a "full" wipe, meaning clearing the system. If you just do a data and cache wipe it should be fine, if of course you are running an ICS ROM...
Click to expand...
Click to collapse
...which already has the same kernel, so there would be no point.
If this isn't source, then I don't understand what this is for. Every i717 ICS leak currently available has this kernel already included. Having it on your SD card just in case isn't really going to do anyone any good, since everyone running any of the currently available ICS ROMs is already running this very kernel. If this is acceptable, then I won't be surprised to see others parting out the leak and posting pieces of it in the dev section, when it really belongs in General since it isn't source. Please don't flame me, just trying to make a point.
tonyc0642 said:
If this isn't source, then I don't understand what this is for. Every i717 ICS leak currently available has this kernel already included. Having it on your SD card just in case isn't really going to do anyone any good, since everyone running any of the currently available ICS ROMs is already running this very kernel. If this is acceptable, then I won't be surprised to see others parting out the leak and posting pieces of it in the dev section, when it really belongs in General since it isn't source. Please don't flame me, just trying to make a point.
Click to expand...
Click to collapse
It's pretty useful for noobs who flashed DaG's kernel mistaking it for an ICS kernel.
OP is pretty misleading. There is no reason to flash this at the moment.
Sent from my SAMSUNG-SGH-I717 using xda premium
Actually, I dont understand what the big deal is...
There are stock roms in the development thread aren't there?
Stock Odin recovery image:
http://forum.xda-developers.com/showthread.php?t=1506330
Stock boot & recovery:
http://forum.xda-developers.com/showthread.php?t=1504999
Strange that no one *****ed about these being in Android Development... I dont see what the difference is.
All this is is the stock kernel from the ICS leak taken out and made available for flashing in case you want to flash the stock kernel FROM THE ICS LEAK (so, if you are still on stock GB, this wont be helpful, this is ONLY useful if you are running the stock, unmodified ICS leak and have changed the kernel and want to revert back to the stock ICS kernel from the leaked ICS rom).
The OP is pretty self explanatory, in fact, the title of the thread is pretty self explanatory. I mean, ICS 4.0.3 STOCK KERNEL sounds pretty clear to me.
My only beef is not with the thread or its location but the lack of organization on XDA. There should literally be a category for ROMS, another for mods & themes & apps, and another for stock images. Q&A should be removed and combined with General. Given the limitation of the current choices, this doesnt fit under General, Q&A, Themes and Apps, or Accessories. The next best fit is Android Development. This is of course all my opinion.
Thread moved
Stock kernels belong in General.
littlewierdo said:
All this is is the stock kernel from the ICS leak taken out and made available for flashing in case you want to flash the stock kernel FROM THE ICS LEAK (so, if you are still on stock GB, this wont be helpful, this is ONLY useful if you are running the stock, unmodified ICS leak and have changed the kernel and want to revert back to the stock ICS kernel from the leaked ICS rom)
Click to expand...
Click to collapse
I really didn't want to jump back into this, and it seriously doesn't bother me at all that this was posted... that said, there are NO modified ICS kernels on our Notes right now (we're all on the same kernel at the moment), so this won't become useful until someone modifies one (as appdroid apparently intends to do to add init.d) -- and even then, it will need to be replaced once the official ICS build/source gets released.
Either way, like I said, this thread doesn't bother me at all... appdroid's dev efforts on the Note are much appreciated!
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.
For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?
Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?
Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.
Thanks
I would do it just to be safe and I flashed the new radios and got faster 4g but only slightly faster
Sent from my ViperDNA infected with ViperBlue DNA
devilsaces said:
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.
For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?
Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?
Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.
Thanks
Click to expand...
Click to collapse
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
devilsaces said:
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
Click to expand...
Click to collapse
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
TJMac44 said:
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
Click to expand...
Click to collapse
Yeah, I can't remember a ROM for the thunderbolt that had the same level of customization as Viper. TBolt ROMS went more in the direction of trying to get the latest sense roms, most felt unstable, or to get ASOP. I have my ASOP fix with my Nexus 7 now so I don't mind sticking with just sense based roms.
TJMac44 said:
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
Click to expand...
Click to collapse
I just flashed the new radio, planning on flashing ViperDNA this weekend.
After doing a little more research I came across this post:
http://forum.xda-developers.com/showpost.php?p=37535001&postcount=1
It turns out that there are 2 parts to a kernal, the kernal modules and the boot.img. I guess I DO need to flash the boot.img separately. The modules are already packaged with the ViperDNA Rom. Does this sound correct? When I was flashing ROMs with my TBolt I usually flashed different kernals separately so they were already together.
uppon2 said:
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details.
3. You now need all required kernel files you are planning to use with the ROM you have selected. Now for the Droid DNA at the moment the kernel is broken down in to 2 parts. The first file is kernel modules and the second file is the the boot.img. Now whatever ROM you choose to download and install, it should already be using a specific kernel. When you flash a ROM the kernel modules will already be installed for the specific kernel the ROM is using.
For example If you listened to my advice and are going to use ViperDNA, this ROM already comes with the kernel modules required for the kernel it is using. The only thing that is left for you to do is download the second part of the kernel which is the boot.img file. Every kernel needs both the kernel modules and boot.img files to work 100% without fault, and every kernel has different modules and a boot.img that will only work for that specific kernel.
Each ROM should give you a download link for the required boot.img so just make sure to read the first few posts - If you are planning to use ViperDNA then it can be found on the first page post number 2 of the ViperDNA thread and it is named Stock DSB System Write Boot.img -
* If that wasn't already clear enough I would like to say that if you are download a complete kernel zip separately (which you can do) then you will get both files required. The first is the "already included in the ROM" kernel modules and the second file will be the boot.img - You can find all of the different kernels here - as you can see in this list the kernel included in ViperDNA is the one named "[KERNEL]Droid DNA Cubed Kernel Stock" - Once you have finished installing a ROM then I would recommend having a look at some different kernels if you want. Down the very bottom of this post I have included instructions on how to flash a kernel so please check it out.*
Click to expand...
Click to collapse
I recently picked up a GP 4.2. I immediately got it rooted so now I'm running a 2.3.6 stock rom with root. What's the next step in terms of getting a recovery installed and maybe moving up to an ICS or JB rom? I've kind of poked around a bit but it's some what confusing with all the other types of GPs in the same area. Does anybody have a recovery and rom they'd recommend? Is using rom manager to push CWM feasible?
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
NapalmDawn said:
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
Click to expand...
Click to collapse
you should flash CWM via odin first and then flash the ROM via CWM
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
NapalmDawn said:
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
Click to expand...
Click to collapse
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
Xenphor said:
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
Click to expand...
Click to collapse
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
MetaMav said:
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
Click to expand...
Click to collapse
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Xenphor said:
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Click to expand...
Click to collapse
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
NapalmDawn said:
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
Click to expand...
Click to collapse
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Where could I find a stock kernel?
Xenphor said:
Where could I find a stock kernel?
Click to expand...
Click to collapse
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Ok thank you. However, will this work with YP-GS1?
But about kernels, on the webpage where I downloaded the stock rooted rom http://tau.shadowchild.nl/attn1/?p=166 it says specifically that the Wifi module in system and kernel must MATCH. This is what I'm talking about in regards to kernel compatibility with roms. How do I know if a kernel I'm downloading will have changes applied to it that will work with another rom like with this stock rom/kernel?
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Well I had to flash this kernel http://forum.xda-developers.com/showthread.php?t=2198234 to get CWM on mine. I haven't actually flashed anything with CWM because there doesn't seem to be any good roms for the 3.6 unless CM7 comes out sometime. I used Odin to flash a stock rom from here http://tau.shadowchild.nl/attn1/?p=166
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
NapalmDawn said:
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
Click to expand...
Click to collapse
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
MetaMav said:
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
Click to expand...
Click to collapse
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Xenphor said:
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Click to expand...
Click to collapse
Xen-it seems GPlayer development is still fairly newish. the work you see from devs now are all ground work. For the 4.2 and 3.6, they seem a little less dev populated than the 4 and 5. People will build upon the work of early devs and eventually get kernels that can OC and maybe ICS and JB roms. At this stage, we likely won't see anything like ZOMG earth shattering until people spend time with the devices. Seems Serk is on his way to doing the best he can for 4.2 but I am not sure who is tackling 3.6
It's weird how roms for devices go. I learned this when I had a tbolt and shockingly saw a FUNCTIONAL JB rom for my old Eris while the tbolt was still hanging back in ginger land with not even a really good ICS rom let alone JB. I asked the Tbolt community-why? How is it the dinosaur Eris has JB and not us? It all depends on what the devs can do with the sources provided. Sometimes certain hardware points are sticky. you can have beautiful JB rom for a device that can't talk to the camera if the hardware source isn't made available (reference the HP TP for many years)
For now, flash what you're comfortable with and and learn what you do and don't like. Also learn if you want to play things safe and not experiment or take on potentially beta builds. For the tbolt, tackling an ICS rom was too dicey so I never did. On my new Rezound, I eat up JB roms as they are in much better shape