Hi,
I'm looking to find the most stable kernel, but it has to be compatible and be able to multiboot with both froyo roms and CM7.2 A9. Is there a kernel like this? Because when I use G3MOD 2.4.1 OC, the CM7.2 A9 never boots, but when i use the CM kernel, froyo won't boot.
Anyone an idea? Or can I make a file to flash the kernel I need ON the phone, without a pc, making it easy to switch between the specific kernels for the rom I want to use?
dafonehacker said:
Hi,
I'm looking to find the most stable kernel, but it has to be compatible and be able to multiboot with both froyo roms and CM7.2 A9. Is there a kernel like this? Because when I use G3MOD 2.4.1 OC, the CM7.2 A9 never boots, but when i use the CM kernel, froyo won't boot.
Anyone an idea? Or can I make a file to flash the kernel I need ON the phone, without a pc, making it easy to switch between the specific kernels for the rom I want to use?
Click to expand...
Click to collapse
I don't think it's possible because froyo uses RFS file system while latest CM7 uses MTD file system. I'm just a newbie so maybe I'm wrong. You should keep searching for an answer because I don't know if my answer is right .
it doesn't necessarily have to be the mtd version. Just alpha 9, the regular one. Isn't it possible to convert the filesystem from the froyo, to matach the CM7.2 filesytem?
I was wrong, sorry. MTD is a partition map, not a file system. RFS is a file system. Sorry for telling you wrong informations.
When I said RFS I should have said BML(BML, like MTD, is a partition map). Froyo is based on BML and so is CM7 alpha9. I think it might work with g3mod recovery and kernel. You can try and see if it is working.
If it helps, here is something about MTD and BML: http://forum.xda-developers.com/showthread.php?t=1699506
Thanks, I was trying G3MOD 2.4.1 which didn't work, but I tried 2.5 and that one worked. But there is one problem: I don't like the touch recovery in G3MOD 2.5. Is it possible to replace the touch recovery in 2.5, with the normal recovery from 2.4.1, and how do you do that? Or should I just try to get used to the touch recovery?
dafonehacker said:
Thanks, I was trying G3MOD 2.4.1 which didn't work, but I tried 2.5 and that one worked. But there is one problem: I don't like the touch recovery in G3MOD 2.5. Is it possible to replace the touch recovery in 2.5, with the normal recovery from 2.4.1, and how do you do that? Or should I just try to get used to the touch recovery?
Click to expand...
Click to collapse
I have found another version which is 3.0, the last one. You can try with this . The link is here: http://forum.xda-developers.com/showthread.php?t=1557323
I think G3MOD final is actually older then G3MOD hybrid 2.5.
G3MOD final isn't a hybrid kernel, so it doesn't support CM7.2 A9.
I guess I'll just have to live with the touch recovery.
But thanks anyways.
I have found a CWM recovery for our phone on the forums. I don't know which version it is but you could try and see if it's working and if it doesn't use touchscreen. The link: http://forum.xda-developers.com/showthread.php?t=2060359 :fingers-crossed:
g3mod link
experiment322 said:
I have found a CWM recovery for our phone on the forums. I don't know which version it is but you could try and see if it's working and if it doesn't use touchscreen. The link: http://forum.xda-developers.com/showthread.php?t=2060359 :fingers-crossed:
Click to expand...
Click to collapse
Could give me the g3mod 2.5 link. Somehow im unable to find it on my pc. I had it b4 but i cant find it. Thanks in advance.
Here's the link buddy: http://forum.xda-developers.com/showthread.php?t=1252698 :victory:
Related
I want to overclock the NS without having to replace the rom. Would this be possible? Are there additional risk associated with overclocking without replacing the ROM?
Thanks in advance!
Yes you can. All you need is root and clockwork recovery. Then download Netarchy's kernel. I know for sure that his kernel works on stock rom since he said so himself. I don't know about Trinity kernel though.
I run stock and I've tried both the trinity stock kernel and netarchy cfs kernel OC @ 1.2ghz. Personally I've had better results on the netarchy kernel.
Sent from my Nexus S
Can I put the stock kernel if I don't like the netarchy kernel? Because I use Bluetooth and wifi always and i just wanted to get a little bit more of my NS!
Make a nandroid backup of the stock rom then flash the kernel. I use netarchy every day and am usually on wifi with my bt earpiece in.
Sent from my Darkginger CM7 Google Nexus S!
I'm having a hard time finding how to flash the kernel (found a lot about how to flash the ROM though).
Would someone link me a FAQ or list some quick instructions on how to go about it?
I have ROM manager installed already (woot!)
Thanks again!
catchsomezz said:
I'm having a hard time finding how to flash the kernel (found a lot about how to flash the ROM though).
Would someone link me a FAQ or list some quick instructions on how to go about it?
I have ROM manager installed already (woot!)
Thanks again!
Click to expand...
Click to collapse
same thing as flashing a ROM.
just make sure if you're flashing a kernel over stock.. make sure its the kernel built for the "stock" rom and not a kernel for CM7 or Bionix etc
catchsomezz said:
I'm having a hard time finding how to flash the kernel (found a lot about how to flash the ROM though).
Would someone link me a FAQ or list some quick instructions on how to go about it?
I have ROM manager installed already (woot!)
Thanks again!
Click to expand...
Click to collapse
Assuming the kernel you want is clockwork compatible, put the zip file of it in your sdcard.
Boot to clockwork recovery either via ROM Mgr (if you're rooted) or via fastboot if you're not.
In Clockwork, find the menu option to install a update/file/zip from sdcard. Select that option, then navigate with the volume keys to the zip file for the kernel. Select it by pushing the power button. Select and answer yes for the are you sure warning. Wait for it to give you a update applied successfully message.
Navigate up to where you can select reboot, and reboot.
You should be on your new kernel.
I WOULD ALWAYS RUN A NAND BACKUP FROM CLOCKWORK BEFORE MESSING WITH THIS STUFF. And ideally, I would keep a copy of that backup on my laptop or dropbox account, not just my sdcard on the phone.
Thanks for all your (very quick) help!
I'm currently running Netarchy's 1.2.2 BFS @ 1.3 and it definitely feels a big snappier with loading some programs
I put today the netarchy kernel 1.2.2 and i have one question...
Where is the VooDoo Improvements? I didn't find the application!
For me the kernel is stable and wifi works even when bluetooth is disabled!
EDIT: Pardon me still being a half'a fricking noob , but it has to do with converting EXT4 back to EXT3. But with faux's kernels there's no need, you can flash right over them. faux's kernels are only mounted as EXT4, while Morfic's convert you to EXT4. A tool/utility is required to covert back to EXT3 so you don't have to deal with restores. I believe the latest CWM solves this and allows you to flash over or back up EXT4. Quote me if I'm wrong.
Sent from a Nexus X by LG
DJ "suMo* said:
Here's my question... How do you go about flashing an updated version of a ROM you're currently on while you have a kernel installed? For example: let's say you're on Trigger or Weapon (G2x) and you have either Morfic's or faux123's kernel installed, and an update comes out for either ROM, what's the trick (or is there one) to flash right over? Because every time I flash right over all goes well but then I always get stuck on the second boot up screen (G2x, blue LG logo). What I've been doing is making a Nandroid of the ROM before I install the kernel, then when the update hits I restore the backup then install the kernel again. Is there a trick to flash right over or is this pretty much the only way?
Thanks.
Sent from a Nexus X by LG
Click to expand...
Click to collapse
Well I personally run the nightlies and Faux Kernel. When a new nightly comes out I just flash over the old one.After the flash- wipe cache, dalvik; then I flash the kernel again and fix permissions.
I guess you can just boot into recovery after you update the rom and then flash your kernel and fix permissions, that should be good enough.
I just rooted, s-off etc, & when I tried to make my back up after root through rom manager it said I needed the latest version of CWM. 5.0.6 I think (the orangish yellow one), but during my soff root process I installed 5.0.8 something (the blue one)? Well I did the backup & it installed the other older cwm. Do I need to change that as I'm going to be selecting an ics rom? Also am I supposed to install the extra now or does that not really matter at this point? Just wondering what to do next. Any advice and or links would help. Thanks to all again, you guys have all been awesome & helpful, it is so great to back in a forum that isn't so hostile! Lol... I won't call any out by name.....
The recovery always stays, you can update it with newer version ofc, but when you choose GB or ICS the only thing that matters is the FIRMWARE.
okay, I just updated back to the most current cwm touch, the blue one. Ive got all my backups in order, now is ext4 better than cwm? does anyone have a reccomendation for wich you use?
androholic said:
okay, I just updated back to the most current cwm touch, the blue one. Ive got all my backups in order, now is ext4 better than cwm? does anyone have a reccomendation for wich you use?
Click to expand...
Click to collapse
4EXT is the one i use and AFAIK it supports the interactive installer, which many DEVs here are using, but can't tell you about CWM!
pretty easy:
what i heard was that cmw cant but 4ext can give u choices if the dev gives u them. like u wanna install 1.2 ghz kernel or 1.5 cmw auto says 1.2 but with 4ext u can choose
Any way to upgrade the CWM in Valhalla black to 5.0.2.8 without using another kernel? Right now it is on 5.0.2.7 and I would like to upgrade if possible.
Thanks for any help in advance.
There aren't any BML kernels that use 5.0.2.8 at the moment. Why do you want it.
No particular reason, just wanted to be on the latest version. Thanks for the response.
Actually hampster kernel has cwm 5.0.2.8 (blue cwm) but some users are having issues with nand backups and going to mtd with that kernel.
sent from my batcave
FBis251 said:
There aren't any BML kernels that use 5.0.2.8 at the moment. Why do you want it.
Click to expand...
Click to collapse
FB, why not rebuild the kernel in vb with my new initramfs?
bhundven said:
FB, why not rebuild the kernel in vb with my new initramfs?
Click to expand...
Click to collapse
Added it to my todo list. The thing is that now I really like your CM7 build.sh and am disliking the BML kernel's build.sh. I might just go ahead and do it with anton's kernel since he has a lot of patches already, or he can do it himself.
Does this thing auto-root? I don't see any references to it in your commit history.
FBis251 said:
Added it to my todo list. The thing is that now I really like your CM7 build.sh and am disliking the BML kernel's build.sh. I might just go ahead and do it with anton's kernel since he has a lot of patches already, or he can do it himself.
Does this thing auto-root? I don't see any references to it in your commit history.
Click to expand...
Click to collapse
I looked at CWM briefly, but I don't know much about our phone boot and recovery process. I don't even understand why recovery has to be build for each device individually and cannot use a single binary and some config and script files.
This is the latest source for the touch recovery:
https://github.com/CyanogenMod/android_bootable_recovery
If we can figure how to build and use it I'll include it in the kernel.
Bryan was messing around with getting a build of it going on CM7. Once touch works, it'll be a lot simpler to include it in BML kernels.
FBis251 said:
Bryan was messing around with getting a build of it going on CM7. Once touch works, it'll be a lot simpler to include it in BML kernels.
Click to expand...
Click to collapse
Yup... again
working on it
AntonX said:
I looked at CWM briefly, but I don't know much about our phone boot and recovery process. I don't even understand why recovery has to be build for each device individually and cannot use a single binary and some config and script files.
This is the latest source for the touch recovery:
https://github.com/CyanogenMod/android_bootable_recovery
If we can figure how to build and use it I'll include it in the kernel.
Click to expand...
Click to collapse
This is because the way recovery works is based on the the BoardConfig.mk and other make variables that are specific to the board (like the size of the partitions, other device features that are enabled, etc...)
You don't want to look at the ICS branch. If you want touch recovery, you need to look at the cm-7.2.0 branch... but it has a lot of weird dependencies and as I've said in this forum already... I got a handle on it. I should have something by or on this weekend.
I finally found the kernel that works for my phone with 5.0.2.8 Blue on it. Seems to work good on my phone, but not really sure where I got it from originally. Any way this helps to make the transition easier?
You can flash AntonX's 1.1.3 Kennel and get CWM 5.0.2.8 I'm running it on Valhalla Black..the blue CWM looks really nice.
My SGS4G is running on GB 2.3.6. I just re-formatted it because I had it stuck on a bootloop last time I tried to flash this kernel. http://forum.xda-developers.com/showthread.php?t=1080871
I don't want to do it wrong again so could someone tell me simply how to flash the kernel? I followed the installation instructions last time
1. Upload kernel to your sdcard
2. Reboot to CWM
3. Flash the kernel using CWM
Click to expand...
Click to collapse
but it got me stuck on a bootloop. Also, it doesn't mention which file to flash because there's Bali v3.3 and Bali v3.3UV. What's the difference?
Also, what do they mean by
NOTE FOR KD1 based ROM users:
There is a possibility your /system partition doesn't get converted to ext4 due to dirty /system partition from the original KD1 stock ROM. If this happen, please follow the instruction below
Click to expand...
Click to collapse
I don't know what's the KD1 part.
Please help and be very specific because I only know a bit about Odin~ (I'm also asking here because I can't post on the development forums so I can't ask the developer)
Use Eollie's 1 click here http://forum.xda-developers.com/showthread.php?t=1822626 That is an old kernel you're trying to flash and 1 clicks are better and easier to use.
drhonk said:
NOTE: this kernel will work with any 2.2.x based ROM. Also if your screen flickers ... please let me know and I'll release the capped version.
Click to expand...
Click to collapse
It pays to read. Lets hope the one click I have in my sig will fix you up.
Bali kernel is for Froyo (2.2) & you say you are on GB (2.3.6). So flashing it will cause a bootloop due to unexpected bootloaders. I suggest you either flash AntonX's basic with a twist or Bhundven's Blast kernel. Both of them are made for GB and have advanced CWM version where backup & restore work.
sent from me