Would anyone be willing to suggest a way to install the OC kernel for CM7 to /rom, using the new boot menu?
I may be misunderstanding what's possible, but it'd be ideal for me to be able to use RomManager to update the rom, but automatically use the OC kernel.
I opened the OC kernel zip, but didn't see the second image to use. Which seems right, as you would want to use the new system image.
Make a link?
Aloha,
cap
Related
I know it's not really related but Im getting frustrated.
Is it possible to install CM7 on the primary partition and use stock 1.2 on the 2nd using only the internal memory?
I don't know how to do it cause CM7 always installs on the 2nd partition.
Using CWR, is there a option where it asks you on which partition to install what ROM?
I've read the dualboot thread but I'm really stuck.
Thanks
Here is the deal:
Go here: http://forum.xda-developers.com/show....php?t=1050520
Download the rom the KEEPS cwm.
Flash that.
Now boot into cwm and flash this rom:http://dl.dropbox.com/u/20480343/ecl...hable-v0.2.zip
Now flash custom rom to first partition.
Dun!
Click to expand...
Click to collapse
Hi, I hav done exactly the way you described - used phiremod 6.1 as latest step.
But after flashing phiremod 6.1 nothing works (stock and p-mod just stops at the load logo.
do you have some hints?
-dualboot with stock 1.2 is working (before flashing primary)
-before starting to flash stock 1.2 I deleted syystem , data and cache - after not.
First the links are not working from your quote. Second I don't want phiremod but CM7
I have the setup as stated above in the title.
I'd rather use the newest nightly, can you do this and dual boot? I tried it but nightly 87 seemed to overwrite the Multi U-Boot option and Dual booting was gone.
My next question, If I have to stay on 7.0.3, what is the overclocking Kernel to use? Trying the 052311 (I think that was it?) killed the CM7 partition.
Stock is on the SECOND partition. I am using the newest version of CWM. 3.2.0 I think it is.
I'm having a hell of a time trying to get any custom roms working. at best i can get cm 10 working if i install cm7 through CWM first. other than that i havent been able to successfully get a working rom.
i first get 2ndinit installed. then i delete all cache, data and delvik. then install the custom android from zip along with custom gapps, but after i restart from there my screen goes black with a red light and i have to flash my sbf just to get my phone working again.
am i missing something? whats this kernel i keep seeing around the forums? I could never find a solid post discussing them.
i guess overall what im asking is, is all i need on my phone the 2ndinit, new android rom, and gapps?
and if thats all i need. then what am i doing wrong?
thank you!
also i have a Defy red lense. heres the "about phone" before i did any rooting or anything at all
System version
Version.34.4.9MB525.T-Mobile.en.US
Model number
MB525
Android version
2.2.1
Baseband version
EPU93_U_00.58.00
Kernel versIon
2.6.32.9-g8431013
[email protected] #1
BP?ex version
usajrdntmob1b4b5de1039.0r
APflex version
GAS_NA_JORDANFROYOTMO__P015
Build number
3.4.2-107_jdn-9
ok im definitely missing something., i just wiped all data, cache and delvik cache and did a complete system restore and its backing up files i thought were wiped.. what am i doing wrong?
using bootmenu 2 beta, and bootmenu JB recovery 5.7.0 jordan.
i cant even get my old roms/backups to work :\
Jellybean uses EXT4 file-system. Whereas CM7 uses EXT3, Stock uses YAFFS2.
Harry GT-S5830 said:
Jellybean uses EXT4 file-system. Whereas CM7 uses EXT3, Stock uses YAFFS2.
Click to expand...
Click to collapse
ok. cool. any programs in particular to load up to do the proper format in BL? or just use the standard bootloader 2.0 beta?
My nexus is rooted using the nexus toolkit and I'm running 4.2.1 rooted with motley kernal. How would I go about updating to the latest software whilst keeping the root and upgrading the kernel?
If you use custom recovery with a backup then easy - restore boot (kernel) and system, then install ota update zip file.
http://forum.xda-developers.com/showthread.php?t=2148337
u can use this 4.2.2 factory image, flash via CWM or TWRP. Your data will be preserved.:good:
Kernel
BelzIgoh said:
http://forum.xda-developers.com/showthread.php?t=2148337
u can use this 4.2.2 factory image, flash via CWM or TWRP. Your data will be preserved.:good:
Click to expand...
Click to collapse
Will the kernel still be compatible with the newest update.
Jordydaman said:
Will the kernel still be compatible with the newest update.
Click to expand...
Click to collapse
Flashing a ROM over the top of your existing ROM will replace both the /system partition and also the boot partition.
Meaning - your Motley Kernel will get blown away and replaced with whatever boot image the ROM dev provided (stock kernel and ramdisk, I suppose). But you can certainly just re-install the Moltey kernel anytime thereafter.
If you have market apps that try to perform random kernel tweaks as soon as the ROM boots, you might be in for some surprises up to and including bootloops. The safest thing to do - if they have an "apply at boot" toggle, is to turn that off before you commence flashing.
As always, take a full nandroid backup before you begin. You can always go back that way.
I've been using matrix for awhile and while its good I want to try others but I heard its not safe to flash custom kernels to other custom kernels without going back to stock. Is this true? Also how long does it take to see how well a kernels performs? I flashed franco yesterday and im thinking to flash faux or trinity tomorrow
Cjshino said:
I've been using matrix for awhile and while its good I want to try others but I heard its not safe to flash custom kernels to other custom kernels without going back to stock. Is this true? Also how long does it take to see how well a kernels performs? I flashed franco yesterday and im thinking to flash faux or trinity tomorrow
Click to expand...
Click to collapse
the only kernel that is recommended to flash your rom and new kernel after is the franco kernel. it includes its own tweaked ramdisk(franco tweaks). so to be safe, its best to flash your current rom(and gapps) with the new kernel, dont wipe anything(dirty flash), so that the new kernel can grab your roms ramdisk instead of francos. its safe to flash over francos, but his tweaks might mess with the new kernel tweaks. its safe to flash any other nexus 4 kernel on top of each other.
Yep. Flashing faux on top of Franco screwed my phone up. I flashed a ROM before flashing faux but I didn't boot it up first I think that was my problem. Anyways it was stuck in boot loop forever and going into recovery to delete data and system only froze the phone (first time that ever happened to me). Then after hard resetting my recovery was just stuck on twrp screen when booting up. Kept messing around for 2 hours couldn't get **** to work and tried to adb pull some files off my phone because all I could think of at that time was fast boot flashing stock image. However USB debugging was off and it wouldn't even boot into android so that was a fail. Ended up losing all my data still bummed about that but moral is be safe than sorry flash that reset and boot into android then back to recovery to flash the newer kernel
Sent from my Nexus 4 using xda app-developers app
otariq said:
Yep. Flashing faux on top of Franco screwed my phone up. I flashed a ROM before flashing faux but I didn't boot it up first I think that was my problem. Anyways it was stuck in boot loop forever and going into recovery to delete data and system only froze the phone (first time that ever happened to me). Then after hard resetting my recovery was just stuck on twrp screen when booting up. Kept messing around for 2 hours couldn't get **** to work and tried to adb pull some files off my phone because all I could think of at that time was fast boot flashing stock image. However USB debugging was off and it wouldn't even boot into android so that was a fail. Ended up losing all my data still bummed about that but moral is be safe than sorry flash that reset and boot into android then back to recovery to flash the newer kernel
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
damn thats sucks. so after im done with Franco I should flash stock kernel and stock rom before going over to a new kernel? Also how do I flash by rom? Im using stock rom btw
Well in faux's thread there's a link for a "reset kernel" which is basically a stock kernel flash that then boot up into android and then go back to recovery and flash whatever kernel. Usually this is only needed after using Franco kernel. Faux and Franco are the only kernels I've ever used. I like Franco more seems smoother to me with good battery.
Flashing the ROM wouldn't be necessary if you flash the reset kernel or vice versa. Roms have their own kernel so it would overwrite Franco's (just boot up the ROM once after flashing it which was my mistake) but since you're on stock I would just download that kernel which is ~5mb vs. 350mb rom
Sent from my Nexus 4 using xda app-developers app
otariq said:
Well in faux's thread there's a link for a "reset kernel" which is basically a stock kernel flash that then boot up into android and then go back to recovery and flash whatever kernel. Usually this is only needed after using Franco kernel. Faux and Franco are the only kernels I've ever used. I like Franco more seems smoother to me with good battery.
Flashing the ROM wouldn't be necessary if you flash the reset kernel or vice versa. Roms have their own kernel so it would overwrite Franco's (just boot up the ROM once after flashing it which was my mistake) but since you're on stock I would just download that kernel which is ~5mb vs. 350mb rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What if i go from Franco to Matr1x or Trinity do I still have to reflash stock kernel or is it only from franco to Faux?