Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether. I looked around and found a thread that has patch to enable it for the DI28 system. It is a zimage file 4.3 mb, there is also a zimage in the rom of 5.5 mb (located in /kernel/update/) Would it be possible to replace the 5.5 with the 4.3? Or would there be a problem because the smaller file was from a DI28 vs a DK28
warlar12 said:
Or would there be a problem because the smaller file was from a DI28 vs a DK28
Click to expand...
Click to collapse
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Koadic said:
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Click to expand...
Click to collapse
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
warlar12 said:
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
Click to expand...
Click to collapse
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Kcarpenter said:
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ive been staring at my computer screen and getting more and more confused...I can not find a program or a way to decompress the file. But apparently it is compressed by a zip program. And on the phone it decompresses it once you flash the rom. Other then that I have decided to call it a night on trying to find a way, (I am sure there is a way.) It is giving me a major headache lol.
The main problem so far is that the source has not been released. However I think it has in a way because it is on the rom, which means there is a way to get it off and mess with it. Just hasnt been discovered yet.
Its packaged by cpio I believe... Ill find something on it tomorrow for you...theres a dev thread that talks about it somewhere...but its probably not for the weak of heart or someone without a bit of kernel knowledge. Not sure how vast your skill set is.
Sent from my SPH-D700 using XDA App
warlar12 said:
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether.
Click to expand...
Click to collapse
I haven't tried any of the Froyo leaks so I can't comment on whether the Froyo kernel has RNDIS support out-of-the-box or not. Once the Epic Froyo kernel sources are released I'll patch in proper RNDIS support if necessary.
Meanwhile, if it's the case that RNDIS can't be enabled in the stock Froyo kernel, then I'm afraid that nothing can be done to fix that without the kernel source code.
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes. So once I get some more knowledge I'll be able to compile my own.
Sent from my SPH-D700 using XDA App
warlar12 said:
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes.
Click to expand...
Click to collapse
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
warlar12 said:
So once I get some more knowledge I'll be able to compile my own.
Click to expand...
Click to collapse
A kernel can't be compiled without the source code, that's what we're all waiting for.
mkasick said:
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
A kernel can't be compiled without the source code, that's what we're all waiting for.
Click to expand...
Click to collapse
Ahh so really there is not a way to change it besides building a new one from source
Related
Well for those of you who want it, here is stock 1.5 from the MR2 with the following changes:
Superuser
Bash/Nano
BusyBox
Deodexed
Zipaligned
Rooted Android 1.5 v1
http://www.multiupload.com/2MX3IUX3G4
Now does anyone know how to OC 1.5? Every kernel I tried kills the touchscreen and everything else.
Change Log:
v1:
Initial Release
Not working:
Overclock (hopefully this is possible)
s10onn2o is looking into it for me, and I'm trying some things myself.
Well, 1.5 used a 2.6.27 kernel. I don't believe anyone ever made an OC version of .27. If you've tried OC'd .29 kernels and they didn't work... I would think that the only option is to either just not have an OC kernel or make a .27 one. Here's one of the best posts I've ever read on just about anything. Read that. Read it again. I've read it at least 3 times, and I feel the need to read it again. Heck, I don't know. The patches might even work on the old kernel source. Someone with more knowledge than me might know. Or you could just try it.
http://forum.xda-developers.com/showthread.php?t=679102
I'd love for someone to take the time to OC the .27 kernel, and I'd use it in Retro1.
gnarlyc said:
Well, 1.5 used a 2.6.27 kernel. I don't believe anyone ever made an OC version of .27. If you've tried OC'd .29 kernels and they didn't work... I would think that the only option is to either just not have an OC kernel or make a .27 one. Here's one of the best posts I've ever read on just about anything. Read that. Read it again. I've read it at least 3 times, and I feel the need to read it again. Heck, I don't know. The patches might even work on the old kernel source. Someone with more knowledge than me might know. Or you could just try it.
http://forum.xda-developers.com/showthread.php?t=679102
I'd love for someone to take the time to OC the .27 kernel, and I'd use it in Retro1.
Click to expand...
Click to collapse
Man i tried reading that but I don't understand it at all. I'm really no dev. Just wanted to try something. I have a feeling this thread will die very quickly
Sent from my Floyo Tazz using XDA App
Nikolai2.1 said:
Man i tried reading that but I don't understand it at all. I'm really no dev. Just wanted to try something. I have a feeling this thread will die very quickly
Sent from my Floyo Tazz using XDA App
Click to expand...
Click to collapse
It's very technical for sure. If the thread dies, it can sit beside Retro1! Thanks for the work on this. Just keep on having fun and learning new stuff and passing it on. No biggie. I still go back to Retro1 every so often. Stock 1.5 is actually nice and stable and responsive. It just works. No bells and whistles, for sure. But it works and works well.
gnarlyc said:
It's very technical for sure. If the thread dies, it can sit beside Retro1! Thanks for the work on this. Just keep on having fun and learning new stuff and passing it on. No biggie. I still go back to Retro1 every so often. Stock 1.5 is actually nice and stable and responsive. It just works. No bells and whistles, for sure. But it works and works well.
Click to expand...
Click to collapse
Yeah I love the speed and stability of 1.5. Now I found out that there are 2.6.27 kernels for the my touch 3g and Hero that support over clock. How hard would it be to port them over?
Sent from my Floyo Tazz using XDA App
Nikolai2.1 said:
Now I found out that there are 2.6.27 kernels for the my touch 3g and Hero that support over clock. How hard would it be to port them over?
Click to expand...
Click to collapse
Give me a link of were its at real quick im off and on the internet with my phone ill see if i can throw in it and try it out with the tools in the kitchen.
s10onn2o said:
Give me a link of were its at real quick im off and on the internet with my phone ill see if i can throw in it and try it out with the tools in the kitchen.
Click to expand...
Click to collapse
Heres the link to the MyTouch3g/Magic:
http://forum.xda-developers.com/showthread.php?t=681378
Heres the link to the GSM G2 Hero:
http://forum.xda-developers.com/showthread.php?t=669311
Thanks for all your help guys, once I get this ROM finished up ill be sure to make a thank you list
No problam it will be tomorrow maybe before i get back to you cause call of duty comes out tonight and well you know lol i give it about a hour of work now and well see
s10onn2o said:
No problam it will be tomorrow maybe before i get back to you cause call of duty comes out tonight and well you know lol i give it about a hour of work now and well see
Click to expand...
Click to collapse
I want to play that game soo bad!!! haha, well that sounds good. No rush, Im just experimenting with things, and who knows, maybe this will be something big
I will try this out once I'm tired of running the dual boot Rom. I actually miss 1.5 in some ways.
Now is this with or without Sense?
Romparoo said:
Now is this with or without Sense?
Click to expand...
Click to collapse
With, sorry ill update the OP
Okay so i think i might be able to patch the .27 kernel to OC, but it needs a desirec_defconfig file. I have one from the .29 source code, but would I even be to port it over to the .27? Or should I not even try?
Okay so I tried, OC the .27 is damn well near impossible. at least for me anyway
Nikolai2.1 said:
Okay so I tried, OC the .27 is damn well near impossible. at least for me anyway
Click to expand...
Click to collapse
Ok hommie I got a little cod fix so ill see if I can mess anything up lol ill start first thing in morning and let you know what comes up.
Sent from my HATCHET MAN froyo ROM using XDA App
s10onn2o said:
Ok hommie I got a little cod fix so ill see if I can mess anything up lol ill start first thing in morning and let you know what comes up.
Sent from my HATCHET MAN froyo ROM using XDA App
Click to expand...
Click to collapse
I played that game today and its pretty legit. And thanks alot man that sounds great! Im working on porting a Froyo rom right now too, well see how this goes
Nikolai2.1 said:
Okay so i think i might be able to patch the .27 kernel to OC, but it needs a desirec_defconfig file. I have one from the .29 source code, but would I even be to port it over to the .27? Or should I not even try?
Okay so I tried, OC the .27 is damn well near impossible. at least for me anyway
Click to expand...
Click to collapse
Android Builder has a .config that I pulled from the .27 stock kernel. Just look in there. Or install 1.5 stock and pull the .config.
adb pull /proc/config.gz d:\temp (or wherever)
gnarlyc said:
Android Builder has a .config that I pulled from the .27 stock kernel. Just look in there. Or install 1.5 stock and pull the .config.
adb pull /proc/config.gz d:\temp (or wherever)
Click to expand...
Click to collapse
Hmm i pulled the kernel in android builder and i only got a config from the .29 kernel... ill try pulling it from my phone later
Nikolai2.1 said:
Hmm i pulled the kernel in android builder and i only got a config from the .29 kernel... ill try pulling it from my phone later
Click to expand...
Click to collapse
There's a file under the AB folder called 'config-eris.2.6.27'. That's a .config file from a .27 Eris kernel. You can just grab that file without actually running Android Builder if you just want the .config.
gnarlyc said:
There's a file under the AB folder called 'config-eris.2.6.27'. That's a .config file from a .27 Eris kernel. You can just grab that file without actually running Android Builder if you just want the .config.
Click to expand...
Click to collapse
wow i feel smart lol thanks man ill look into it
Didn't see it here so I thought I'd post a link. Can't wait.
http://www.androidcentral.com/cyanogenmod-6-t-mobile-mytouch-4g
Sent from my HTC Glacier using XDA App
Exciting news. Thanks for the link.
Yea, woke up today to find mt4g on clockwork recovery and kmobs twitter pic of a booted, yet very broken cm6. Thus begins the flashwars! All during the black ops release lol.
I'm so ready for this.
I'm permrooted, have custom recovery installed, made a nandroid backup, now all I need is this.
Waiting patiently.......
Amazing news, hopefully they remap the Genius button to Search in that rom.
This right here is one of the reasons im getting rid of my vibrant.
Anyone else notice that its using the stock kernel?
grankin01 said:
Anyone else notice that its using the stock kernel?
Click to expand...
Click to collapse
I don't think that kernel source is available yet for the MT4G.
shineproductions said:
I don't think that kernel source is available yet for the MT4G.
Click to expand...
Click to collapse
Oops, your right its not. I haven't had my Red Bull yet this morning!
shineproductions said:
I don't think that kernel source is available yet for the MT4G.
Click to expand...
Click to collapse
Would the kernel source for the mt4g be required to get C6 running? Or, would it be required in order to run C6 optimally?
floepie said:
Would the kernel source for the mt4g be required to get C6 running? Or, would it be required in order to run C6 optimally?
Click to expand...
Click to collapse
You use kernel source in order to compile a new kernel, although you can still create modded ROMS that use the stock kernel, and you can also create kernel modules to add functionality, until you have access to kernel source.
just when I thought this phone didn't need root. CM pops up his head.. damn it here we go again... Flash flash flash
shineproductions said:
You use kernel source in order to compile a new kernel, although you can still create modded ROMS that use the stock kernel, and you can also create kernel modules to add functionality, until you have access to kernel source.
Click to expand...
Click to collapse
Is that why we don't have overclock ability yet. The G2 processor is kicking our buts. (Keeping it P.G.)
Sent from my T-Mobile myTouch 4G using Tapatalk
Be patient. You'll get bacon bits as soon as kernel source is released.
Niiiice, I am so stoked...
option94 said:
This right here is one of the reasons im getting rid of my vibrant.
Click to expand...
Click to collapse
Lol beat you to it ;-)
Sent from my HTC Glacier using XDA App
option94 said:
This right here is one of the reasons im getting rid of my vibrant.
Click to expand...
Click to collapse
according to this, they will support vibrant:
http://www.cyanogenmod.com/home/whats-up-with-cm
this is what i was waiting for...had CM on my original mytouch, moved up to the 4g and have been waiting...
Definitely excited for this! I'm no sense hater but it is no CM for sure.
Sent from my HTC Glacier using XDA App
I would love to see some customized build for this thing that would keep some of the Espresso things or, better yet, keep HTC framework optimized with CM goodies. This way we can just push things we like to it.
It seems as if a lot of the reason people are hesitant to switch to froyo is the lack of custom kernels. custom kernels provide much better battery life as well as the ability to overclock as well as many other very useful features that create faster and more efficient operating system functions. From personal experience with froyo roms i have noticed the system to be quite slow compared to 2.1 and also i have noticed absolutely horrid battery life. We all know that these leaks may be far from complete but thats not to say that we shouldnt be making them better. It is obvious that Firon and noobnl have the correct information on this matter seeing as they have rooted all of the froyo releases inside of the zImage. If they were kind enough to share the information they have it would be very easy to either port our drivers to a i9000 froyo source or to use backported eclair libraries and use our current kernels. With this being said, I am very sure that this information could be the dealbreaker for froyo roms. With a good kernel comes a good functioning phone.
TO FIRON OR NOOBNL:
Please share your method of extracting the initramfs in order to quickly advance the development of froyo roms and to prolong the necessity for an updated source code
https://github.com/atinm/initramfs-utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
bubby323 said:
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
Click to expand...
Click to collapse
THANKS A lot man
You have tested this on froyo kernels? And technically if we used a correct froyo initramfs combined with a 2.6.29 kernel with backported eclair libraries for certain hard/software aspects we should be able to acheive an eclair kernel on a froyo rom. Ive done it before on other phones
the jump from .29 to .32 is a massive one, but all the power to ya...
shabbypenguin said:
the jump from .29 to .32 is a massive one, but all the power to ya...
Click to expand...
Click to collapse
Ive done it on evos/nexus' and i can confirm that its been done on galaxy s phones. it may be a massive jump in version number and overall base code. but as far as android and our devices go it really hasnt changed too much. actually i can almost guarantee that it will boot just by swapping the kernel inside the zimage. but to get camera and other functions requiring updated drivers we would need older libraries. or we can just patch our board specific files onto a i9000 kernel. but hey. doubting is more fun than doing
bubby323 said:
https://github.com/atinm/initramfs- utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
Click to expand...
Click to collapse
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
help
EnVolved said:
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
Click to expand...
Click to collapse
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
If you want better battery life editing the initram isn't going to do it.Your gonna need kernel source to play with to be able to do anything about battery life.
justlovejoy said:
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
Click to expand...
Click to collapse
There should be only one way to use that script to extract.
./extract_initramfs.sh zImage
and here's the header from the repack script.
usage : ./repack.sh [kernel] [initramfs_direcotry] [kernel source dir] "title of build"
example : ./repack.sh /data/android/initramfs-utils/zImage /data/android/captivate-initramfs /data/android/linux-2.6.32 "title of build"
These are fairly simple shell scripts that only appear complicated because of the use of grep.
Hi
You know maybe already some of my work even if this is my first post in the captivate forums.
Let me introduce you the stock+Voodoo stable kernels.
Those are built injecting Voodoo lagfix inside an original Samsung kernel built specifically for Captivate.
It comes with extensions like "su" and also ClockWorkMod recovery as default recovery.
Voodoo lagfix converts /system, /cache, /dbdata and /data to Ext4 with optimized parameters for speed but also guaranteeing data integrity.
Also, it configures the write behavior of Linux to prevent lag from happening, plus apply some memory management providing a better balance than stock settings.
Designgears help a lot during the development of this new stable release, testing endlessly new experimental code I was writing Thanks!
What it's not: voodoo sound, voodoo sharpness. Those improvements needs kernels built from sources.
Froyo only versions for now, I'll build Eclair version later.
update.zip you can flash with ClockWorkMod recovery (not 2e or 3e)
UCJJ4+Voodoo http://dl.project-voodoo.org/stock+...k+Voodoo-Froyo-I897-UCJJ4-unsigned-update.zip
UCKB1+Voodoo http://dl.project-voodoo.org/stock+...k+Voodoo-Froyo-I897-UCKB1-unsigned-update.zip
.tar you can flash with Odin
UCJJ4+Voodoo http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-I897-UCJJ4.tar
UCKB1+Voodoo http://dl.project-voodoo.org/stock+Voodoo/tarballs/stock+Voodoo-Froyo-I897-UCKB1.tar
Thanks to slm4996 who was the first to test this kernels
Nice work! Testing now. Does this include the sound and color fixes?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Working great. Flashed over perception build 8 with ljl3 modem
slm4996 said:
Working great. Flashed over perception build 8 with ljl3 modem
Click to expand...
Click to collapse
Hehe thanks for the report - I updated the first post.
slm4996 said:
Working great. Flashed over perception build 8 with ljl3 modem
Click to expand...
Click to collapse
Do voice calls work? This is Captivate kernel, thats a telus modem for Vibrant...
Sent from my GT-I9000 using Tapatalk
Great to see CWM integrated
Sent from my GT-I9000 using Tapatalk
Voice calls do not, I was reporting on the kernel functionality.
I'm switching back the radio now.
slm4996 said:
Voice calls do not, I was reporting on the kernel functionality.
I'm switching back the radio now.
Click to expand...
Click to collapse
Ah, OK
Sent from my GT-I9000 using Tapatalk
slm4996 said:
Voice calls do not, I was reporting on the kernel functionality.
I'm switching back the radio now.
Click to expand...
Click to collapse
Voice calls absolutely do work. You clearly had some other issues.
Sent from my brain using Thumbs 2.0.
icezar1 said:
Do voice calls work? This is Captivate kernel, thats a telus modem for Vibrant...
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Well, this is a Captivate modem, designed to work with Captivate more than Frankenstein phones
I did the same for Vibrant kernels if you prefer: http://forum.xda-developers.com/showthread.php?t=870480
The main target for these kernel are users using "standard" ROM, as most user do, with a kernel they can trust.
Guys, decide
Sent from my GT-I9000 using Tapatalk
let me se if i get it this is to be used with stock ROMS only? or i can be used with custom roms like perception, cognition & axura??
Cog and Auxura would probably be ok. I haven't tried it yet though. The "stock" he is referring to, I think, is Captivate based Froyo Roms (ji6, jj4).
do it work with JPU roms like Darky 5.2?
Does not work in axura
is not working with axura 2.2 i have no audio in phone call i can't heard nothing
just in case it matters i have JL3 modem with axura 2.2 any suggestions?
i used the odin version and flash it in pda section of odin is that the correct way to do it?
JEANRIVERA said:
is not working with axura 2.2 i have no audio in phone call i can't heard nothing
just in case it matters i have JL3 modem with axura 2.2 any suggestions?
i used the odin version and flash it in pda section of odin is that the correct way to do it?
Click to expand...
Click to collapse
That is the correct way to flash the kernel. Have you tried reflashing the modem?
majinzen said:
That is the correct way to flash the kernel. Have you tried reflashing the modem?
Click to expand...
Click to collapse
just tried that waiting for boot i will let you know!!!
not working going back to sentirons 1.4.5 sorry!!!!!!!!!!
isn't axura based on vibrant jk2.. -___-;..
this kernel is FOR STOCK FROYO FOR CAPTIVATE.
darkamikaze said:
isn't axura based on vibrant jk2.. -___-;..
this kernel is FOR STOCK FROYO FOR CAPTIVATE.
Click to expand...
Click to collapse
im just trying same kernel but for vibrant in my cappy with axura i let you kn ow if it worked!
it worked BUT the volume buttons at least in CWM are inverted up=down down=up power button working fine for ok
no i only need where to change the soft buttons to match the cappy ones i have them inverted back=home home=back vol up=down down=up and had to turn off the autorotation any suggestions?
Hi, as the topic states, does anyone know where i can download one and flash? my setup on my sig is current.
thanks
So you're trying to run the official kernel with a custom ROM? Why?
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
nomadman said:
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
Click to expand...
Click to collapse
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link. - http://www.filedropper.com/update3-e3671133717dsigned-opal-frg83-from-dmd64e3671133
Phateless said:
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link to my dropbox. - http://db.tt/XHrvInZ
Click to expand...
Click to collapse
IMO, the current ROm im using (TheOfficial) is working wonderfully. I care less about overclocking since I don't play games and dont find the need for the applications I use to be overclocked. Also the UI response on the ROM is incredible.
You are right, until the other ROMs iron out the random battery drain, which I have experiences in both CM7 and pershoot kernels, i wont be using them because i do not like having to restart the phone every time after i charge. ezterry's current kernel always gives me the green screen. however, ez's older kernel doesn't, but I prefer running the latest unmodified kernel.
I'm satisfied using a non-oc kernel and would rather set the mim clock freq. to ~177.
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Phateless said:
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Click to expand...
Click to collapse
lol, thats my problem. I don't. I also have athe official OTA Froyo image for mt3g. but i have no idea how to extract and apply it to the current OS. Thanks for the offer though. i'll try to find a way to do it. was just hoping someone had a flashable official kernel laying around they'de like to share.
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
nomadman said:
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
Click to expand...
Click to collapse
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Phateless said:
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Click to expand...
Click to collapse
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
nomadman said:
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
Click to expand...
Click to collapse
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Shouldn't been since the kernel code is open source, but I'm not sure either. I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Phateless said:
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Click to expand...
Click to collapse
The kernel is open source. I dont think i have a problem there. Its gapps that we can not redistribute. i read that from CM forum.
DonJuan692006 said:
...I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Click to expand...
Click to collapse
thanks! if u can find the link again, i'd be grateful. im on a unix (Mac) environment, so i might be able to do it. if not on Mac, I already have vmware fusion installed and its not a problem slapping on the latest Ubuntu.
I did find a how-to on CM wiki that required a boot.img and fastboot to flash. also found one requiring zimage from a rom. but i could not find the zimage file from the TMO Froyo OTA. lol.
Here's what I was reading. Which is doing the boot.img method.
DonJuan692006 said:
Here's what I was reading. Which is doing the boot.img method.
Click to expand...
Click to collapse
nice! androidcentral was down for maintenance the whole time i was researching yesterday. thanks for the link!
nomadman said:
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
Click to expand...
Click to collapse
Glad I happened to go back a page...
The official kernel is meant to go with 0013 and 28.25 so yes, you should still have the additional RAM, which this phone desperately needs.
2.6.32.9-g94b855e
[email protected]#1 is what my phone says and I just received the OTA update a few days ago. Hope this is what you were looking for!
I've been trying to figure this out all day. I actually have a linux installation already but none of the download links for the perl files work. If you have them please upload them somewhere and I'll make us a flashable AnyKernel update.zip.
I've been trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=667923 but none of the android-dls.com links work