So I have been upgrading my ROM without realising I should probably upgrade my Kernel too. Just loaded up Devil Toast 0.7 and it works great, but since installing it I haven't been able to use my wifi. Started getting curious, and I noticed a lot of people have a different kernel than myself, and the last time I probably upgraded mine was when I installed CM7.
So my question is, where/how can I get a more up to date kernel? I did a few searches but I wasn't able to find solid answers. I really just want a nice stable kernel that works with Devil Toast.
are you CDMA or GSM? HTC just released the kernel source code the other day. So now the kernel devs can actually start making good kernels. AFAIK for CDMA the only kernel besides stock is the MAC kernel(see here). There might be a few floating around the Infected forums, but I'm not sure. Best bet right now is to probably run the kernel that comes with the rom, until the devs pump out some better kernels with more features(and more stable). Maybe post your WiFi problems in the DevilToast thread to see if someone has an answer?
netwokz said:
are you CDMA or GSM? HTC just released the kernel source code the other day. So now the kernel devs can actually start making good kernels. AFAIK for CDMA the only kernel besides stock is the MAC kernel(see here). There might be a few floating around the Infected forums, but I'm not sure. Best bet right now is to probably run the kernel that comes with the rom, until the devs pump out some better kernels with more features(and more stable). Maybe post your WiFi problems in the DevilToast thread to see if someone has an answer?
Click to expand...
Click to collapse
I'm CDMA with a kernel version is [email protected], and I've noticed a few of the people in the devil toast thread are running 3.0 versions of a kernel. So I'm guessing those people installed a different kernel than what the ROM carries? I might just do a complete wipe and see what happens, I just hate re-configuring everything. I was going to post on the DT thread but I can't since I haven't made enough posts on the boards. Tricky business.
The kernel in question is right here: https://github.com/htc-mirror/shooteru-ics-crc-3.0.16-e733189 but I have no idea how to go about grabbing it for my phone. I was never big on compiling my own code.
It seems like you are running toascfh's WiMAX build, correct? agrabren has had a 3.0 kernel for a bit now on DevilToast. What version are you running? Try installing the newest one(.7). I would recommend a full wipe though... the latest version has almost everything working sans 3D.
netwokz said:
It seems like you are running toascfh's WiMAX build, correct? agrabren has had a 3.0 kernel for a bit now on DevilToast. What version are you running? Try installing the newest one(.7). I would recommend a full wipe though... the latest version has almost everything working sans 3D.
Click to expand...
Click to collapse
Yeah, that's what I was running before. I just tried a full wipe and reinstalled 0.7 devil toast, but it didn't change my kernel. I'm guessing i'm missing a step or doing something wrong for my particular phone. I've got hboot 1.50 and I have successful root, but I've heard of hboot 1.50 causing fussiness, so maybe it's related.
I've been dropping into TWRP and flashing the ROM from there. Since I've got hboot 1.50, do you think I'll need use adp to push the ROM through? That's how I originally flashed toastcfh's mod, but when I tried to use adp to push CM9, it wasn't cooperating, so I just used TWRP.
Are you S-ON? I know alot of people have been having problems booting DT, one thing that seems to help is using 4ext recovery. You should try changing your recovery, you can always go back if it doesn't help or you don't like it. Just fyi, nandroids are not compatible between the two. Using 4ext, wipe all but SD card, then flash the rom, then wipe data again and you should be good to go.
netwokz said:
Are you S-ON? I know alot of people have been having problems booting DT, one thing that seems to help is using 4ext recovery. You should try changing your recovery, you can always go back if it doesn't help or you don't like it. Just fyi, nandroids are not compatible between the two. Using 4ext, wipe all but SD card, then flash the rom, then wipe data again and you should be good to go.
Click to expand...
Click to collapse
I was S-ON. I finallyyyyy got it working, but it was a hell of a pain. I ended up downgrading to hboot 1.40, which was a majority of the hassle. Then I got it to S-OFF. Once I got that going, I was able to get both the ROM and the Kernel to flash. I get to deal with a new issue, but the original problem of the Kernel not updating is fixed. It's now running 3.0.x very nicely.
Thanks for the help, I finally have my wifi back!
Related
Since upgrading to new version of twrp, I can't lock on a Wifi signal. Any suggestions?
I have removed the wifi device and tried readding it.
You'll shoot your eye out (in 3D)
Have u tried reflashing ur kernel? What hboot u got?
Your kernel got screwed up when you flashed it. Wipe and reflash.
My thoughts exactly.
mugetsu666 said:
My thoughts exactly.
Click to expand...
Click to collapse
Yip known issue if your kernel flash went bad You were right lol.
Yeah I've learned first hand on that especially with this 1.5 hboot
I'm running virus rom with stock kernel. It's 1.4 (preorder. Phone)
You'll shoot your eye out (in 3D)
Just reflash ur kernel and that should solve it.
Where can I find it here stock kernel to flash? Or are you talking about reloading the recovery?
You'll shoot your eye out (in 3D)
babyschmoof said:
Where can I find it here stock kernel to flash? Or are you talking about reloading the recovery?
You'll shoot your eye out (in 3D)
Click to expand...
Click to collapse
On virus's page he has a list of kernels. Or you can check out his website infectedrom.com .
Still having a clarity issue. I'm running the virus rom, with stock evo kernel. I'm not using any custom kernels. I did reflash the older released rom.
You'll shoot your eye out (in 3D)
Ok bro what kernel is in that rom? U should just have to flash the kernel not the whole rom.
Ugh... The kernel is the stock HTC evo 3D kernel. He didn't start adding custom kernels until the 3.0 nightlies. I reflashed the the older rom again. I'm thinking it must be the new twrp recovery. Any thoughts to switching over clockworkmod? Been afraid to make that jump. I miss the rom manager, but the twrp touch screen is cool.
You'll shoot your eye out (in 3D)
I too was having issues with the 2.0 twrp, so I went back to 1.1.1 and haven't had any more issues. Don't get me wrong the whole touch thing was awesome but I was having flash issues. So try the 1.1.1 and see if that helps. I personally have never used cwm
Hey everyone, this is thread is meant to centralize all of the information and questions about the kernels for this phone. I feel as though information about peoples issues, and their "triumphs" with certain kernels are scattered everywhere, so finding useful information can be tedious. I have noticed that most, if not all of the ROM threads specifically say, "No kernel questions". This is what this thread is going to be for. I also thought it would be neat to have some general discussion about kernels. for example, what kernels work best with what ROM, what are some of the issues that people run into, what works, what doesn't work, etc...
I know there is only a few kernel options now, but hopefully that list will grow and as it grows this thread will be become more useful.
there are only a few rules for this thread:
1. No flaming-one of goals for this thread is to help noobs, this thread is meant to de-clutter the ROM threads of kernel questions, (seemingly stupid or intelligent).
2. This thread is for talk of kernels only, there is a "off topic" discussion thread for everything else; and ROM threads to specifically talk about ROMS
So far i only know of three kernel types:
Faux's kernel
Stock kernels
X boarder's kernels, (different variants to go with different ROMS).
From what i understand Faux's kernels work with pretty much all of the ROM's but seem to cause boot loops.
I do not know too much about X's kernels and the issues they cause, so it would be nice if some one filled me in.
Ill start the thread by saying, I have used the stock kernel that shipped with my phone over the quick sense ROM, and the Bullet proof 2.4 ROM. the weird thing with that was, my WIFI worked. its weird because X, and everyone else says to flash one of X's or Faux's kernels or else wifi will not work. I have been apprehensive about flashing kernels because of the boot loop issues people have reportedly been having. however i went ahead and flashed the kernel that was included in the Bullet proof 2.4 ROM. i haven't used the phone all that much so no bootloop yet. the phone is fast and smooth. X's kernels are able to be overclocked and have three governors. i am very curious about Faux's kernel because he did some amazing things on the Mytouch 4g when i had it.
Jms122589 said:
Hey everyone, this is thread is meant to centralize all of the information and questions about the kernels for this phone. I feel as though information about peoples issues, and their "triumphs" with certain kernels are scattered everywhere, so finding useful information can be tedious. I have noticed that most, if not all of the ROM threads specifically say, "No kernel questions". This is what this thread is going to be for. I also thought it would be neat to have some general discussion about kernels. for example, what kernels work best with what ROM, what are some of the issues that people run into, what works, what doesn't work, etc...
I know there is only a few kernel options now, but hopefully that list will grow and as it grows this thread will be become more useful.
there are only a few rules for this thread:
1. No flaming-one of goals for this thread is to help noobs, this thread is meant to de-clutter the ROM threads of kernel questions, (seemingly stupid or intelligent).
2. This thread is for talk of kernels only, there is a "off topic" discussion thread for everything else; and ROM threads to specifically talk about ROMS
So far i only know of three kernel types:
Faux's kernel
Stock kernels
X boarder's kernels, (different variants to go with different ROMS).
From what i understand Faux's kernels work with pretty much all of the ROM's but seem to cause boot loops.
I do not know too much about X's kernels and the issues they cause, so it would be nice if some one filled me in.
Ill start the thread by saying, I have used the stock kernel that shipped with my phone over the quick sense ROM, and the Bullet proof 2.4 ROM. the weird thing with that was, my WIFI worked. its weird because X, and everyone else says to flash one of X's or Faux's kernels or else wifi will not work. I have been apprehensive about flashing kernels because of the boot loop issues people have reportedly been having. however i went ahead and flashed the kernel that was included in the Bullet proof 2.4 ROM. i haven't used the phone all that much so no bootloop yet. the phone is fast and smooth. X's kernels are able to be overclocked and have three governors. i am very curious about Faux's kernel because he did some amazing things on the Mytouch 4g when i had it.
Click to expand...
Click to collapse
so ur sayin we can flash most of these roms & still have the stock htc kernel wrking but wifi might break? so how about NRG's modified stock kernel on the Energy rom,will it wrk on all amaze roms & will wifi not break?? im coming frm a mytouch 4g so this phne is a lil complicated..sorry for actin like a noob lol..i havent used that easy kernel flasher,i been using flash image gui & heard that fauxs new kernels cnt b flashed with it?
cmdmilitia13 said:
so ur sayin we can flash most of these roms & still have the stock htc kernel wrking but wifi might break? so how about NRG's modified stock kernel on the Energy rom,will it wrk on all amaze roms & will wifi not break?? im coming frm a mytouch 4g so this phne is a lil complicated..sorry for actin like a noob lol..i havent used that easy kernel flasher,i been using flash image gui & heard that fauxs new kernels cnt b flashed with it?
Click to expand...
Click to collapse
Idk about the WiFi question, I'm not educated enough on that, but what I've found to be successful is flashing the boot.img from xboarders ROM's .zip file with easy kernel flasher to get the best results. But with Energy ROM, I flash the stock kernel he provided with the stock kernel flasher. That method has worked flawlessly for me. I've never had a random reboot and I've never had a broken WiFi or BT. I've never had to flash a kernel more than once due to failed flash either.
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
Idk about the WiFi question, I'm not educated enough on that, but what I've found to be successful is flashing the boot.img from xboarders ROM's .zip file with easy kernel flasher to get the best results. But with Energy ROM, I flash the stock kernel he provided with the stock kernel flasher. That method has worked flawlessly for me. I've never had a random reboot and I've never had a broken WiFi or BT. I've never had to flash a kernel more than once due to failed flash either.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Thanks for the response.. i just wanted to read up on all this more before i flash another rom..Ive been on Energy rom since i got the phone but at first i had the wifi issue,then i went & dwnloaded his stock kernel & flashed it thru flash image gui..i dnt have access to a computer unless i go to a friend house so i rely alot on flash image gui lol.. thats why im askin if its fine to flash roms without flashin another kernel..
I'm not sure why, but the stock kernel worked just fine On quick sense and on bullet proof. I never had a wifi issues on those but the wifi on the energy rom didn't work. I'm using faux's kernel on bullet proof 2.4. I guess fauxs kernel is included in the bullet proof zip. I have only had 1 reboot in the past week. Also faux's kernel can be over clocked which is nice if your into that. I came from a mytouch 4g also so learning all this stuff can be a pain but once you read over everything its really not that difficult
Sent from my HTC Amaze 4G using xda premium
I finally relocked and forced the RUU (newest official version of our phone software) which puts you on the stock everything (ie kernel), and am running just fine on Energy ROM. Wifi works great, I haven't tried Bluetooth. So a far as I can tell, the stock kernel from TMo RUU 1.43 runs great and wifi is perfect. FYI.
Sent from my HTC_Amaze_4G using XDA App
cmdmilitia13 said:
Thanks for the response.. i just wanted to read up on all this more before i flash another rom..Ive been on Energy rom since i got the phone but at first i had the wifi issue,then i went & dwnloaded his stock kernel & flashed it thru flash image gui....
Click to expand...
Click to collapse
I bet most of the kernel issues in this thread would be from people having issues with flash image GUI. Not a fact, just a strong uneducated hunch
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
I bet most of the kernel issues in this thread would be from people having issues with flash image GUI. Not a fact, just a strong uneducated hunch
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
2 kernels that im aware of is flashable with flash image gui,the amaze stock kernel frm Energy rom & the faux kernel frm fast amaze rom before the new update i guess.. Other than those 2 kernels i heard EKF modules or something like that cnt b used with flash image gui.. People gotta read before flashin things lol
Sent from my HTC_Amaze_4G using xda premium
glacierguy said:
Idk about the WiFi question, I'm not educated enough on that, but what I've found to be successful is flashing the boot.img from xboarders ROM's .zip file with easy kernel flasher to get the best results. But with Energy ROM, I flash the stock kernel he provided with the stock kernel flasher. That method has worked flawlessly for me. I've never had a random reboot and I've never had a broken WiFi or BT. I've never had to flash a kernel more than once due to failed flash either.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I'm probably just educated enough to be way off-base, but it seems to me a kernel with a wifi problem would also have a BT problem. Do people tend to experience those 2 together?
KineticEntropy said:
I'm probably just educated enough to be way off-base, but it seems to me a kernel with a wifi problem would also have a BT problem. Do people tend to experience those 2 together?
Click to expand...
Click to collapse
Yep that's uaully the case
Sent from my HTC Amaze 4G using xda premium
I'm pretty sure it had to do with the official build each rom is based off of. I know the official update to 1.43 changed the kernel around so if people have a stock kernel from an earlier official ruu the wifi and bt break when updating to a build based off 1.43. Most all roms past xboarders beast mod 2.0 are built off 1.43 at least. I think there are some ones newer than 1.43 but I'm not sure if the kernel had any updates in those builds.
Sent from my HTC_Amaze_4G using XDA App
So I have been browsing around and have decided to flash the newest version of Sebastian's overclocked kernel. I am S-Off on the newest HBOOT currently running zhp's Vigor 1.1 on the latest ICS RUU.
I am assuming I just flash the zip provided (kernel) via recovery correct? Also, what programs do you guys use in order to tune the speed of the cpu's? Is it built into the kernel?
I have also been hearing that people get problems flashing the kernel straight up, and that they need to flash the stock kernel before hand then flash Sebastian's over that. Is this true?
Thanks in advance.
Answers
996 said:
So I have been browsing around and have decided to flash the newest version of Sebastian's overclocked kernel. I am S-Off on the newest HBOOT currently running zhp's Vigor 1.1 on the latest ICS RUU.
I am assuming I just flash the zip provided (kernel) via recovery correct? Also, what programs do you guys use in order to tune the speed of the cpu's? Is it built into the kernel?
I have also been hearing that people get problems flashing the kernel straight up, and that they need to flash the stock kernel before hand then flash Sebastian's over that. Is this true?
Thanks in advance.
Click to expand...
Click to collapse
Flash in recovery ( make sure not cwm, our phones dont seem to like that one too much, I would use Amonra for something as serious as a kernel, then switch back TWRP for fun), simple as that, i wipe cache and dalvik but heard that it was unnecessary. You wont lose anything if you do
I use incredicontrol by chad, but sebastians doesn't have fast charge built in. SO that option wont be available.
People get problems because they are s-on flashing it, you dont have to worry, make sure you dont have a ph98img stored on your sd card in case of trouble you can just go to recovery from hboot and flash a different kernel. and make sure u match the kernel with your rom of course, sense 4 , sense 3.6 , aosp , or whatever, i see your rom but i am making sure you understand you cant just slap a kernel that was intended for a different platform.
Changing voltage ABILITY is built in the kernel, but to harness it , you need an app , once again i like incredit kernel, i am hearing issues with setcpu, choose your flavor.
jmichaels1982 said:
Flash in recovery ( make sure not cwm, our phones dont seem to like that one too much, I would use Amonra for something as serious as a kernel, then switch back TWRP for fun), simple as that, i wipe cache and dalvik but heard that it was unnecessary. You wont lose anything if you do
I use incredicontrol by chad, but sebastians doesn't have fast charge built in. SO that option wont be available.
People get problems because they are s-on flashing it, you dont have to worry, make sure you dont have a ph98img stored on your sd card in case of trouble you can just go to recovery from hboot and flash a different kernel. and make sure u match the kernel with your rom of course, sense 4 , sense 3.6 , aosp , or whatever, i see your rom but i am making sure you understand you cant just slap a kernel that was intended for a different platform.
Changing voltage ABILITY is built in the kernel, but to harness it , you need an app , once again i like incredit kernel, i am hearing issues with setcpu, choose your flavor.
Click to expand...
Click to collapse
Thank you for your great response. I think this is for Sense 3.6. I will also try out incredicontrol and get back to you on that.
*EDIT
Where can I find out that this is for 3.6?
Edit:
To add to this it look like it will work on any ROM that has a unsecured boot.img. Now I haven't tested that..
Here you go
Edit : I would listen to zone ... lol he is awesome ...
Ah alright. Are you on this kernel zone?
*edit.
Thanks for the input on which firmware version this has to be run on.
Sent from my ADR6425LVW using xda premium
996 said:
Ah alright. Are you on this kernel zone?
*edit.
Thanks for the input on which firmware version this has to be run on.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes I am. It will run on 3.14 or 4.03 as long as you are flashing over a kernel that it unsecured.
zone23 said:
Yes I am. It will run on 3.14 or 4.03 as long as you are flashing over a kernel that it unsecured.
Click to expand...
Click to collapse
hmm. alright that sounds alright. How can I find out if the kernel is unsercured? I am running the stock kernel which was included with zhp's vigor 360 1.1
*edit.
found out that the kernel on vigor is unsecured.
Thank you for your help!
One more question. What setup are you guys running? ex: voltage levels and cpu levels?
sorry wrote this way too many times
996 said:
One more question. What setup are you guys running? ex: voltage levels and cpu levels?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=31267314&postcount=8
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