Root I thought flashing kernels was suposed to be easy..

[45droid]

..well, relatively anyway.

I'm running UD 3.1.1 and have saved some of ChevyNo1's LV kernals (renamed update.zip) to the root of my SD. Wiped cache and dalvik. Installed update.zip (not update.zip.zip) and with every version I get stuck on the 'M' screen and have to pull battery, boot to recovery and install UD 3.1.1.

Does my Droid not like these kernels or am I missing something? Thanks.

 

[Dark Jedi]

this is a gingerbread rom. you need a gingerbread kernel. froyo kernels wont work

Try petes kernel and see if it will let your phone boot up. http://www.peteralfonso.com/search/label/kernel

 

[skilaufen]

+1 ^^^^ what dark jedi said.

Several additional suggestions. If your using clockwork recovery you do not need to rename your .zip files to update.zip. As long as there are no spaces in the name it will flash in clockwork just fine (SPRecovery requires the renaming). Also you do not need to wipe data or cache prior to flashing a kernel. The last big thing is to make sure you make a ROM backup prior to flashing a kernel so if you go into bootloop you can just restore your working ROM without having to reflash it.

 

[William T Riker]

this is a gingerbread rom. you need a gingerbread kernel. froyo kernels wont work

That isn't true, I've had absolutely no issues running Chevy's ULV 1.2 and I've used it with every revision of GPA including 14 now that Pete has put out. Sounds like either the phone or rom hes using doesnt like the kernel to me..

 

[skilaufen]

That isn't true, I've had absolutely no issues running Chevy's ULV 1.2 and I've used it with every revision of GPA including 14 now that Pete has put out.

Pete's ROMs work with those but I think UD's 3.0 GB ROMs require the gingerbread kernels. I maybe wrong since I haven't run UD 3 yet but I thought that was a requirement for his.

For the OP if it is not that then it may be your phone just wants a different kernel and doesn't agree with the one your trying to flash.

 

[William T Riker]

I figured it might be individual to that rom, I've never used UD, just stock pete builds.

 

[45droid]

this is a gingerbread rom. you need a gingerbread kernel. froyo kernels wont't work

Hm, yes. I saw that people were using Chevy's kernels with UD but failed to notice their ROMs were all froyo versions. I was trying to find some sort of current compatibility info but it seems things move so fast with this stuff that nothing stays current for long. I'll try that link, and I think I'll have better luck just googling "gingerbread roms" in the future. Thanks.

 

[45droid]

+1 ^^^^ what dark jedi said.

Several additional suggestions. If your using clockwork recovery you do not need to rename your .zip files to update.zip. As long as there are no spaces in the name it will flash in clockwork just fine (SPRecovery requires the renaming). Also you do not need to wipe data or cache prior to flashing a kernel. The last big thing is to make sure you make a ROM backup prior to flashing a kernel so if you go into bootloop you can just restore your working ROM without having to reflash it.

I thought that was the case with clockwork as I was sure I read it before and I didn't have to rename UD when I flashed it. Thanks for the info!

 

[icecold]

Hm, yes. I saw that people were using Chevy's kernels with UD but failed to notice their ROMs were all froyo versions. I was trying to find some sort of current compatibility info but it seems things move so fast with this stuff that nothing stays current for long. I'll try that link, and I think I'll have better luck just googling "gingerbread roms" in the future. Thanks.

Which version of Chevy's kernels are you using? It appears the latest ones have a date of 3/9/2011 according to the website...

[Kernels] 3/9/11 - Liquid GB Compatibility - Droid Forum - Verizon Droid & the Motorola Droid Forum

 

[45droid]

Alright I got pete's 1.25GHz up and running. Can definately see a difference when selecting different frequencies (this thing can MOVE!). But since I flashed it I can't get wifi on my device. When I go to wireless settings the wifi selection just says error and has an un-tickable box. This is from his site...

Note:

• The ext modules are quite large, if you do not need support for ext you may remove them from the .zip with no ill effect.
  • Wifi may not work if your ROM does not have enough room to fit all of the modules.

I removed the modules folder before puting the kernel on my SD. Is the 1.25GHz version too much for my droid even though I can select a lower max frequency?

 

[45droid]

Which version of Chevy's kernels are you using? It appears the latest ones have a date of 3/9/2011 according to the website...

[Kernels] 3/9/11 - Liquid GB Compatibility - Droid Forum - Verizon Droid & the Motorola Droid Forum

Yes, this was another of my oversights. I was using his froyo kernels on a GB ROM.

Flashed Chevy's 1.25Ghz ULV and it's working great. 1.25Ghz cranks but gets a little hot and xScope browser can't handle it (crashes). 1.1Ghz has been working fast and cool. The battery is juicing quickly but I'll have to wait for a full charge and more normal usage to get a better idea on that.

*edit* I am still currious about that WiFi issue with pete's kernel though...

I never thought my stock droid was particularly slow before but I would now! Thanks very much for the link.

 

[icecold]

Yes, this was another of my oversights. I was using his froyo kernels on a GB ROM.

Flashed Chevy's 1.25Ghz ULV and it's working great. 1.25Ghz cranks but gets a little hot and xScope browser can't handle it (crashes). 1.1Ghz has been working fast and cool. The battery is juicing quickly but I'll have to wait for a full charge and more normal usage to get a better idea on that.

*edit* I am still currious about that WiFi issue with pete's kernel though...

I never thought my stock droid was particularly slow before but I would now! Thanks very much for the link.

ROMS, kernels, and their combinations are definitely not a one size fits all on the Droid 1. I would play around with the kernels, and or setCPU to play around with the CPU speeds to get the best balance of battery life and performance.

You may even want to try a LV kernel. I know my first droid wouldn't run the higher clock speeds on the ULV. But if things are running cool, then you may have found the right kernel for your phone.

 

[skilaufen]

As has been said, stick with what works. 1.25 ghz is about the max any droid will run and still be stable which means that alot of the droids can't handle he 1.25 ghz. Still that says alot for our Droids though that you can over double the current Verizon stock speed and still run it.

If 1.1 ghz is working well stay at that for a few days and see how it does. Generaly most Droids can handle 1.0 or less with an increasing chance of problems occuring as you approach and pass the 1.2 ghz mark.

 

[teddyearp]

this is a gingerbread rom. you need a gingerbread kernel. froyo kernels wont work

Wrong. There is no such thing as a 'gingerbread' kernel. The kernel is seperate from the overall Android version. With Eclair, we had 2.6.29, when Froyo was released, that was part of the upgrade as well. The kernel got upgraded to 2.6.32 to enable tethering, JIT, and a few other goodies. If anyone remembers, we only got tethering to work on Eclair when the devs were able to pull the parts out of 2.6.32 and put them into 2.6.29 to enable it.

The rom vs kernel compatibility issue was fixed when Koush released his "anykernel" update.zip template file. And most if not all kernel devs are using it. Previously, a kernel dev would package the whole boot.img file with the twilan-drv.ko file, but that meant that the ramdisk (contained within boot.img), etc. HAD to be compatible to your current rom. With Koush's template, the kernel dev would insert the twilan-drv.ko file in the right place and the raw kernel ONLY (zimage) file was put in. Then koush's template file unpacked the current boot.img file into raw kernel, ramdisk, etc., and put the new raw kernel back in.

<snip>Sounds like either the phone or rom hes using doesnt like the kernel to me..

45Droid, the thing about overclocking is not to try and see how fast you can go, that is where most people will ALWAYS run into trouble. I used to run @ 1100 with Eclair, but didn't really see any difference between that and about 800, and now with Froyo, etc., I find my phone to enjoy a 800 mhz kernel even better that trying to go faster. Of course, YMMV and you are more than welcome to push the limit. But I think that is why you're having trouble. Somebody once posted that overclocking is not to see how fast you can go, but how slow you can stand it.

good luck

 

[Dark Jedi]

Wrong. There is no such thing as a 'gingerbread' kernel. The kernel is seperate from the overall Android version. With Eclair, we had 2.6.29, when Froyo was released, that was part of the upgrade as well. The kernel got upgraded to 2.6.32 to enable tethering, JIT, and a few other goodies. If anyone remembers, we only got tethering to work on Eclair when the devs were able to pull the parts out of 2.6.32 and put them into 2.6.29 to enable it.

The rom vs kernel compatibility issue was fixed when Koush released his "anykernel" update.zip template file. And most if not all kernel devs are using it. Previously, a kernel dev would package the whole boot.img file with the twilan-drv.ko file, but that meant that the ramdisk (contained within boot.img), etc. HAD to be compatible to your current rom. With Koush's template, the kernel dev would insert the twilan-drv.ko file in the right place and the raw kernel ONLY (zimage) file was put in. Then koush's template file unpacked the current boot.img file into raw kernel, ramdisk, etc., and put the new raw kernel back in.



45Droid, the thing about overclocking is not to try and see how fast you can go, that is where most people will ALWAYS run into trouble. I used to run @ 1100 with Eclair, but didn't really see any difference between that and about 800, and now with Froyo, etc., I find my phone to enjoy a 800 mhz kernel even better that trying to go faster. Of course, YMMV and you are more than welcome to push the limit. But I think that is why you're having trouble. Somebody once posted that overclocking is not to see how fast you can go, but how slow you can stand it.

good luck

If that was the case then why did pete make a kernel to work with his GB rom and many others have to? If froyo kernels works fine then no one would be making the GB ones and people like the OP wouldnt be having boot loop problems. Then fix them by using a GB kernel .

 

[teddyearp]

The people that are getting boot loop problems _might_ be trying to overclock too fast for their phone. The reason that Pete is 'making' GB kernels is one of two reasons. The way he packages his kernels, i.e. not using koush's 'anykernel' template and/or to keep his fan base up, since they are so used to his twitter feed style of constant updates. I'm not bashing Pete, BTW, I remember when he first got started over at the old alldroid.org with some cut and paste nandroid backup style roms when we were on 2.0.1. I am very familiar with his work.

As a further argument there are probably just as many if not more kernels that will work on both Froyo and Gingerbread. I am using one of Prime's that worked fine on my Froyo and now on my Gingerbread rom. P3Droid's are another set I know of from personal experience.

 

[Dark Jedi]

I would agree with the OC for the boot loop, but in his original post he installed the kernel and then the phone was in the boot loop. So he never had a chance to OC the phone and was why I suggested the petes kernel for GB to see if it was the kernel or not.

 

[twistedlim]

I think wiping messed you up. No need to wipe. Just install and if you are using setcpu I would recommend going though the setup again to recognize the phone and new kernel. You can leave your settings the same.

 

[45droid]

Well after a week running UD 3.1.1 with Chevy's 1.25Ghz ULV kernel (set at 1.1Ghz) everything's still going fine. The battery takes a little more of a hit than UD's stock kernel, but I doubt I'll be trying any others until I start checking out other ROMs.

As far as the debate about compatability, after searching through and looking into various kernels, I agree with teddyearp that there are not necessarily GB or froyo kernels. Having said that, there are ROMs and kernels that obviously don't work together. Icecold provided a link for some of Chevy's kernels that worked for me. I think that's all that most here are really looking for, regardless of specific terminology.

 

[Rodeojones]

this is a gingerbread rom. you need a gingerbread kernel. froyo kernels wont work

Try petes kernel and see if it will let your phone boot up. Peter Alfonso

100% untrue! I can and have run kernels originally made for Froyo ROMs (like those made by Slayher, P3Droid or ChevyNo1). In fact, my current kernel (by Raidzero) was created before any Gingerbread ROMs were released. So it's also "technically" a Froyo kernel.