I recently tried to flash CM 7.2 stable from cyanogenmod site. After flashing was stuck in boot loop. This same happened when i installed CM9.0 RC1. There the culprit was the cm kernel and flashing fxp 126 kernel for cm9 solved it. I guess same is the problem here. So can someone upload the fxp 125 kernel for cm7.2? thanks
EDIT: Wrong kernel
If you still need it.....
http://www.mediafire.com/?esj79u3mcdigo6k
Cheers
Related
Do the popular roms like cyanogen nightly and hyperdroid come with a kernel in the flash or do they just leave the kernel intact?
if i upgrade my rom version from say nightly X to nightly Y do i need to reflash the kernel each time?
No the rom comes with the kernel build in.
From where can i get CM 7.2 and CM 9 by epsylon3? and with which kernel?
zed_fauji said:
From where can i get CM 7.2 and CM 9 by epsylon3? and with which kernel?
Click to expand...
Click to collapse
http://defy.wdscript.fr/
defyplus is with 2.3 kernel
and jordan-night is with froyo kernel.
but there is no kernel in the zip. you should flash it with recovery frome this
http://defy.wdscript.fr/kernel/
which combination will the green lens work?
worked with the cm7.2 cm72-120102.0338-NIGHTLY-Defy.zip and CM7 kernel
can I now install cm9 kernal and green lens will work?
there is still no solution in cm9 for green camera
Latest CM 7.2 build for Defy+ from Epsylon3 has a couple of issues with the camera for me: quality is very poor (taking photos or recording) and screen orientation is 180ยบ. So, it's basically like use the latest Quarx's CM9 build for Froyo: camera doesn't work xD
I resolved to return to CM7 kernel, flash 7.1.0-11, flash latest 7.2 build (January 02) and flash Gapps again
Greetings!
hey i successfully rooted my defy plus dfp 231 bl7 i used coustom recovery v5 to install cm9 by fuzz "swank" it's cool but has bugs like no "move to sd" and evn shows insufficient storage error.
is there any solution to that.
or any other roms suggestion. :laugh:
Custom roms:
CM9 defy+ nightlies by Quarx
CM9 kangs by FuZZ (based on above)
CM9 defy+ nightlies by Epsylon3 (not preferred. Eppy focuses on the defy builds (froyo kernel))
CM7 defy+ nightlies by Quarx
CM7 whiterabbit plus edition (based on above)
CM9 kangs by FuZZ (also based on Quarx)
MIUI Scotland defy+ (2.3.7) brand new MIUI android 2.3.7
Various defy+ MIUI v4 builds
Various modified stock roms (e.g. ms2ginger)
Sure there are some more, but I don't remember them all. These are the most important ones
Roms by quarx: Quarx2k.ru
Roms by epsylon: defy.wdscript.fr
Most roms have threads
Good night (yawn)! sent from my Defy+
fiskenigaten said:
Custom roms:
CM9 defy+ nightlies by Quarx
CM9 kangs by FuZZ (based on above)
CM9 defy+ nightlies by Epsylon3 (not preferred. Eppy focuses on the defy builds (froyo kernel))
CM7 defy+ nightlies by Quarx
CM7 whiterabbit plus edition (based on above)
CM9 kangs by FuZZ (also based on Quarx)
MIUI Scotland defy+ (2.3.7) brand new MIUI android 2.3.7
Various defy+ MIUI v4 builds
Various modified stock roms (e.g. ms2ginger)
Sure there are some more, but I don't remember them all. These are the most important ones
Roms by quarx: Quarx2k.ru
Roms by epsylon: defy.wdscript.fr
Most roms have threads
Good night (yawn)! sent from my Defy+
Click to expand...
Click to collapse
would they work for dfp 231 bl7
I had some strange problems with proximity sensor with CM7 (and BL7).
Ms2Ginger is running just fine at the moment :good:
As long as you don't install some Defy roms (with Froyo kernel) everything should work - with or without bugs
ftpankaj said:
would they work for dfp 231 bl7
Click to expand...
Click to collapse
No. I just wanted to list a lot of roms that will not work on bl7 because I don't like you
Of course they will work! Well, I haven't tried them on bl7 since I'm bl6 with bl5 defy+ kernel, but these are all defy+ roms. Good luck! Just remember not to flash kernels e.g. Walter's kernel as it's for bl<6 and will brick your phone!
sent from my Defy+
i have some proximity sensor problems on my defy and im currently on cm 7.2 stable. people have told me that it might resolve itself by changing roms.
so i want this one: http://forum.xda-developers.com/showthread.php?t=1353003
so.. when i was on 2.1 i flashed froyo 2.2.1 and then CM 7.2
am i supposed to do the same? or do i simply move it to my sd card and flash via recovery?
Hi all,
I'm testing the CM10.2 nighties on my Razr M from two weeks. Everything seems stable but I want to try it with the SmartassV2 governor that the CM kernel is missing. I started searching for alternative kernels (like Aaaagh's one) and I noticed that the actual CM10.2 kernel is v.3.0.96: wasn't Android 4.3 supposed to have the 3.4.62 version instead? If so, why Cyanogemod is stuck with th old 3.0.96 version? I've searched for answers but I've find none...
Is it possible that every CM10.2 build has the old kernel, or is this happening only with the Razr M build?
Maybe I'm just missing somenthing...
j27h said:
Hi all,
I'm testing the CM10.2 nighties on my Razr M from two weeks. Everything seems stable but I want to try it with the SmartassV2 governor that the CM kernel is missing. I started searching for alternative kernels (like Aaaagh's one) and I noticed that the actual CM10.2 kernel is v.3.0.96: wasn't Android 4.3 supposed to have the 3.4.62 version instead? If so, why Cyanogemod is stuck with th old 3.0.96 version? I've searched for answers but I've find none...
Is it possible that every CM10.2 build has the old kernel, or is this happening only with the Razr M build?
Maybe I'm just missing somenthing...
Click to expand...
Click to collapse
3.4 kernel for MSM8960 isn't quite available yet.
Hopefully Moto will update to 3.4 if we ever receive official 4.2 (or 4.3)
You can contribute and follow the progress (dev wise) at http://forum.xda-developers.com/showthread.php?t=2243410 and http://www.droidrzr.com/index.php/t...lopment-0610-android-booting-firmware-issues/
Ok, everything isclear now! Thanks for the quick response!
Basically we've two options:
1) use the 3.0 kernel with backported 3.4 funcions (the one integrated in the CM builds)
2) use a 3.4 kernel (like Aaaargh's or others) non totally adapted to our device
And all this because we're still stuck with Android 4.1.2 thanks to Motorola/Google/Verizon...
At this point, I think te safest thing is to keep using the 3.0 kernel... Apart for the new governors/schedulers, why soul I prefer a 3.4 kernel (maybe this is a silly question too...)? Are they usable/stable even if they're not exactly matching our device?