{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This FAQ is intented for new users who are learning to use ROMs, SBFs and Multiboot.
Kernels, what the hell are they?
What is kernel?
Kernel is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components). All Android phones use the Linux Kernel.
What kernels do we have for Defy?
Motorola Defy/Defy plus currently have two kernels. Both of them are modified Linux Kernel 2.6.32 and both of them were made by Motorola.
What are Defy and DefyPlus kernels?
DefyPlus kernel was made by Motorola for the Gingerbread firmwares(2.3.x), mainly for the Defy Plus phone, Defy don't have an official GB update. Defy kernel was made for Froyo firmwares(2.2.x).
What are the other names for Defy kernel?
CM7 kernel, Froyo kernel, 2.2 kernel etc.
What are the other names for DefyPlus kernel?
CM9 kernel, GB/GingerBeard kernel, 2.3 kernel etc.
Why don't you use these other notations?
Because they are all flawed and don't distinguish properly between the two kernels. For eg. CM9 currently have two types of builds, one made by epsilon3 for DefyPlus kernel and the one made by Quarx2k for Defy kernel. In case of the Froyo/GB notation, a new user may think that all GB ROMs (CM7, MIUI etc.) uses GB kernel, which is not true. Hence the new less confusing nomenclature for the kernels.
What are the differences?
Many, one being the support for Green lens camera.
How can I get these kernels?
Download DefyPlus kernel here and Defy kernel here.
How do I install these?
From CWM recovery.
What is CWM recovery?
ClockWorkMod recovery is a custom recovery for Android instead of the stock android recovery with many added features (eg. Nandroid backups.). In most other phones its installed in your phones recovery partition. However that's not possible in Defy because the recovery partition is locked. But still our dev's have managed to load it via 2nd init bootmenu.
What is 2nd init bootmenu?
It is basically a technique to bypass the locked recovery and bootloader. 2nd init loads after the Defy bootloader is loaded but it loads befor the Android system loads. Thus enabling us to create Nandroid backups etc.
How do I install the 2nd init bootmenu?
You can find it in here.
Kernels and ROMs and SBFs (or Kernel compatibility).
What is kernel incompatibility?
This means you have flashed a wrong kernel for the ROM that you intent to use.
What is it's symptom?
Phone usually gets stuck in the splash image (the red moto logo).
How do I avoid this?
Always research and find out what kernel is the a ROM using before installing it. Especially while flashing nightlies.
How do I fix it?
You can fix it from CWM by flashing the correct kernel. If you don't have a working CWM, flash your sbf file via RSDlite.
What ROMs are compatible with the Defy kernel?
CM9 Defy by epsylon3, CM7, CM7.1, CM7.1.5 RC, CM7.2 nigthles for Defy, MIUI, WIUI and much more, I haven't added those because I haven't tested those.
What ROMs are compatible with the DefyPlus kernel?
CM9 DefyPlus by Quarx, CM7.2 nightlies DefyPlus .
What SBFs are compatible/coming with the Defy kernel?
All Froyo/Defy 2.2.x SBFs.
What SBFs are compatible/coming with the DefyPlus kernel?
All GingerBerard/DefyPlus 2.3.x SBFs.
Is there a list of all ROMs/SBFs? If so where can I find it?
Yes. It's right here and here.
Multiboot and Kernel compatibility
What is multiboot?
Its the state of having two bootable ROMs (2nd init and 2nd boot) in your Defy. You can select the OS to boot from 2nd init boot-loader. More details here.
Where is the 2nd init ROM installed?
In your NAND.
Where is the 2nd boot ROM installed?
In /mnt/sdcard/fsimages .
What is NAND?
NAND is your phone's flash memory/ internal memory (1.3GB Defy, 2GB DefyPlus).
What is the significance of kernel compatibility in Multiboot?
You can only use one kernel for both ROM. So the ROMs that you are using should be compatable with the same kernel. This is ROM compatibility.
What ROMs are compatible?
All Defy/Froyo ROMs/SBFs are compatible with each other. Similarly all DefyPlus/GingerBeard ROMs/SBFs are compatible with each other.
Can I multiboot an SBF and a Custom ROM?
Sure you can. You can have the SBF as 2nd init and ROM as 2nd boot.
Can I have an SBF as 2nd boot?
No, you cant. But you can have an Nandroid backup of an SBF as 2nd boot.
Can't I just install a new kernel for the other OS in case of incompatibility?
Well, you cant.
I'm using a Defy and I have flashed/upgraded 2.3.x GingerBeard/DefyPlus SBF. Can I flash a Defy kernelvia CWM?
You cant.
Why not?
Defy has a locked bootloader. You have blown an efuse that won't permit you to downgrade to that kernel.
I'm using a GingerBeard/Defy kernel/sbf. Will I burn an efuse if I flash the DefyPlus kernel via CWM?
No, you wont. Efuses blow when you upgrade your firmware via RSDlite. CWM can't blow efuses.
Is all this safe?
No, it's not safe. You are doing this at your own risk.
Will I void my warranty?
No, not if you are using CWM. You can always revert to the stock SBF using RSDlite.
What is my stock SBF?
It is the SBF that Motorola/Your Provider have made for your area/country. It's device/country/provider specific. Look for it in the SBF thread.
Can I kiss you?
Well, only if you are a girl. If you are a guy you can always click on that thanks button.
How to use CWM?
Using RSDlite.
Note : The Eclair kernel (for Android 2.1.x) was intentionally left out to make the FAQ less confusing.
post reserved
reserved post
Wow!
edit what roms are compatible? has wrong answer...
u wrote froyo rom/sbf which is wrong cuz cm7 is gb...
same for gb too...
cm9 for d+ can't be used with cm7 for d
Sent from my MB526 using xda premium
just add few more questions
1. What is nand ( i m new to multiboot so are other new users)
2. what is cwm
3. methods to install cwm
4. list of sbfs ( defy , defy+ ) since generally new users get confused and end up flashing defy plus rom and end up now able to downgrade .
you can also provide preferrable links as wel please edit if u like my suggestions
Kernals?
We have 2.1 kernel also.
And add link to kernel.org
can't not cant
joydeep1985 said:
just add few more questions
1. What is nand ( i m new to multiboot so are other new users)
2. what is cwm
3. methods to install cwm
4. list of sbfs ( defy , defy+ ) since generally new users get confused and end up flashing defy plus rom and end up now able to downgrade .
you can also provide preferrable links as wel please edit if u like my suggestions
Click to expand...
Click to collapse
1st post edited. I'll add preferred links later. Thanks.
Borowik13 said:
Kernals?
We have 2.1 kernel also.
And add link to kernel.org
can't not cant
Click to expand...
Click to collapse
I'm doing this for charity. Don't command me.
Excellent job there! This should be a sticky
Sent from my 1Ghz CM7 + CM9 Defy
nogoodusername said:
edit what roms are compatible? has wrong answer...
u wrote froyo rom/sbf which is wrong cuz cm7 is gb...
Click to expand...
Click to collapse
Here you are confusing android version with kernel name. I will have to come up with better names for the kernels. Defy kernel/Defy plus kernel maybe.
nogoodusername said:
same for gb too...
cm9 for d can't be used with cm7 for d
Click to expand...
Click to collapse
You are right about that. But I'm sure I typed in cm7.2 for defy plus and cm9 for defy plus. If you check the links they are right. Maybe the "plus sign" disappered when adding the hyperlinked(I'm sure of that now cuz it disappeard in this post too. Werid!). I should proof readed anyway. Will edit the post tomorrow cuz I can't edit such a big post from phone. Thanks.
edit: done
I did make a video tutorial about it ... So those who need it can view it
Hi!
I have a huge problem!!! Please help me guys! I flashed this SBF ( http://forum.xda-developers.com/showthread.php?t=1472086 ) and my battery doesn't work. What is the solution for this? I wish I had a usable Defy with a stock rom. But the most important is the usability!
Thanks for your help! Have a nice day!
Janimano01 said:
Hi!
I have a huge problem!!! Please help me guys! I flashed this SBF ( http://forum.xda-developers.com/showthread.php?t=1472086 ) and my battery doesn't work. What is the solution for this? I wish I had a usable Defy with a stock rom. But the most important is the usability!
Thanks for your help! Have a nice day!
Click to expand...
Click to collapse
think ure pretty much gone now ..... try contacting walter now .. pehaps he could have something ...
Great guide ! Simple and to the point. There's so much info in these forums it can get confusing. Another multi boot configuration that works on Defy Green lens/Froyo kernel/ is Wiui v4 + CM9 or CM7. The new wiui v4 build is sweet!
I think you need to do a bit more research,
We have more than one type of froyo kernel for defy, we commonly refer to the defy Nordic kernel (179-4) with some tweaks done by eppy, multi boot has updated ,
It works as a basic guide but there's a few simplifications that just aren't true
teamwork makes the dream work
Just helping here
i've a channel all about this stuff .. So in case youre having some doubts , then i may probably help you ... Its up to you ... Just saying
just a quick THANK YOU!
I am a NOOB and its true: there's so much info out there, its very confusing.
This sums it up very clear & 2 the point. Most helpfull to get my bearings.
and to all the "teachers" here, this guy is doing it for nope,nada,niente,niks. be grateful, remarks about wrong grammar is just....
Defy plus kernels link broken can anyone help plz
Links to both kernals are not working. Please fix it.
Sent from my MB525 using Tapatalk 2
I have a question I wanna to ask long time again.
So if I want to flash a ROM to my NAND I use Stable Recovery to do it?
on the other hand, if I want to flash a ROM to my sdcardI use Custom Recovery to do it?
Thanks.:cyclops:
When You flash a Custom Rom (like Quarks, Codename Android....), it will allways be flashed in the Phone memory. Roms can be flashed in stable and custom recovery.
DO NOT FLASH IN STOCK RECOVERY!
Related
This 2nd init created a lot of confusion about one thing: Custom Kernel Loading.
So let's try to answer this question. Please don't create more confusion, if you know then answer, else don't.
Is the 2nd init method capable of loading custom kernel?
Yes
This is the only way to install and run other type of kernel like the one used by CM7.
Until Moto will unlock the bootloader, this is the only way.
adyrafy said:
Yes
This is the only way to install and run other type of kernel like the one used by CM7.
Until Moto will unlock the bootloader, this is the only way.
Click to expand...
Click to collapse
you're refering to cm7 as in CM7 for defy by quarx? because there we use motorola's kernel
So theoretically stock gingerbread can now be ported to defy?
confusedfella said:
So theoretically stock gingerbread can now be ported to defy?
Click to expand...
Click to collapse
Definitely. As CM7 is stock Gingerbread with additions and tweaks galore.
Custom kernels cannot be used. I believe the stock kernel is good enough. With custom kernel modules.
Sent from my MB525 CM7 beta 4.1
50 REM Thanks for the clear answers.
100 DONT: $fff_"I like my kernel real crispy - but I'll wait 'till they are almost done."
101 REM "RC from Quarx anyone?
102 +"Give the guy some fries with that, would we?"
105 +"Thumbsup Quarx!"
106 REM "no confusion intented"
110 Goto END
adi4motion said:
This 2nd init created a lot of confusion about one thing: Custom Kernel Loading.
So let's try to answer this question. Please don't create more confusion, if you know then answer, else don't.
Is the 2nd init method capable of loading custom kernel?
Click to expand...
Click to collapse
where is blog
No offences to Quarx and the wonderful cyanogen mod team.After 3 months (a month on stable cm7 release),I realised that cm7 is very unprofessional in spite of the fact that it runs faster and is lighter than stock rom.However after rolling back to stock rom last night I found it is much productive and stable than cyanogen.Just rooted 3.4.3 -36 and removed certain unnecessary stock apps.And I have started liking moto widgets.Waiting for cm9.Will update info about battery experience in stock rom.Till now no difference in stock and cm7.
Well.... Custom rom's aren't for everyone! I'm a flashing junkie myself I switch roms atleast once a week and still can't ever decide what I like the most. I like stock froyo roms for some reasons. In fact just today I went to stock nordic froyo, did a little theming with UOT kitchen. It's nice that everything just works but I swear I get way more random screen freezes and even an occasional full blown freeze and/or reboots with stock rom's. I think I'm going back to CM7 or who knows what starting tomorrow because Moto's software just plain sucks in terms of stability if you ask me. You win some and you lose some I guess. CM7 has it's qwerks and problems but even so, I think it's better than stock. Just my $0.02
EDIT: On a side note. I do TRULY believe that ALL the problems we have with our custom rom's are 100% due to a locked bootloader meaning we are stuck with MOTO's crap ass kernel's and we can't build and compile our own custom kernel
I have the opposite opinion: like u I use CM7 since about 3 month, updating to latest nightly regularly. I went back to stock froyo for some testing.
Only 1 day, but it has felt much longer: blur is very annoying, less customization, much less smooth and less reactive interface. No powerwidgets in pulldown menu, no 1% battery. I was extremely happy to go back to cm7.
Btw, using 111204 nightly and it is really really good, could be cm7 final for me now that the effort has gone to cm9. I will stay on this nightly as long as it need for CM9 to mature (supporting green lens may take a while...) Thanks Quarx and Epsylon for this great rom
Sent from my MB525 using XDA App
@root_toor ... can you list down the unwanted softwares of stock rom 2.2.2
Even I find the stock rom more stable... specially camera green lens is better reactive in stock rom.
waiting for cm9.i like it.
I agree about power control in notification but 1% battery? Check this out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Besides what about the connected player (better than most players with sap manager ).More importantly call and messaging app is way better than that of cm7.And I use a blurless stock rom.
Sent from my MB525 using Tapatalk
To start with I removed DLNA, Homesync, Quickoffice,File manager by quickoffice,and many other system apks.After rooting my phone I installed Bomb that task from market for app killing.And yes for 1% battery use circle battery widget.Either use root explorer or a freeware called Super Manager.
Sent from my MB525 using Tapatalk
its all just a matter of preference really! I understand why people like stock, but like I said I swear it's not as stable IMO. I get lots of unexplained freezes. I do like connected music player too but I always just install it on the custom roms I use anyway, I have a white themed CMP I use. I'm gonna try the 111204 nightly like gkai suggests because honestly I haven't used it yet so I will give it a go. But I can guarantee I will still bounce around from rom to rom like I always do
After using cm7 for months - I switched back to stock ROM - Tried MIUI - found it better (professional) than cm7.Although CM7 is a hacker's paradise, I still found the need to install 2.3.4 GB (Stock ROM) since I wanted to experience 2.6.32.9 GB kernel.
Conclusion
CM7 - Fastest
MIUI - Rich UI and iPHONISH feel (missed the app drawer as of the latest MIUI version)
STOCK FROYO - By far the most stable ROM.If you updated with latest FROYO, you can root your phone with either OneClickRoot 1.7 or 2.3 and above.
STOCK GB - Yet to try (however beware you cannot downgrade to STOCK FROYO,CM7 OR MIUI since they are based on FROYO kernel 2.6.32.9 while this runs on GB kernel 2.6.32.9)
CM7.1.0 and MIUI failed for me in regular use... it hungged when you actually need phone to talk. it hung when u actually need to take pic... the auto focus also fails sometimes in night.
with stock roms , its more stable but just a bit slow...
so if you root and overclock the stock to 1 GHz , and remove useless softwares, it makes the defy best phone.
Unless we have a kernel of GB, its no point to install a GB with a kernel of a froyo.
Just a bit of input from me as I was a regular user of CM7 from RC0 onwards.
CM7 was quite a bit faster (than when I previously had a leaked froyo installed) & has some great features as standard but I also had one big issue that I couldn't solve & that was the well known Android OS/Suspend bug. It would frequently continue to use CPU & not go into deep sleep correctly maybe several times per day.
So in the end I decided to install the official UK froyo 2.2.2 sbf & to this I have:
rooted,
installed 2nd init,
overlcocked to 1000mhz & undervolted slightly,
flashed the 1% battery mod so the Defy now reports in 1% steps even in the Moto battery menu,
also deblurred the stock UK ROM using Walters deblur mod.
All this has resulted in a very stable ROM with no lag, freezing or rebooting (non of which I ever had on CM7 either I have to add) however I also now don't have the Suspend bug on the froyo build so I'm happy.
Also I use widgetsoid for the toggles in the pull down menu & Launcher Pro & have also frozen some Moto things that I don't need.
So to summarise I did really like CM7 & if it were not for the issue I had then would still be using it & getting ready for CM9 (which I may still try at a later date) but the official froyo with the extra things I've added is more than up to the job for me.
I have used stock FroYo, cm7, Miui, wiui and ms2ginger and for me the best one is ms2ginger .. battery life as compared to stock FroYo and cm7 , it is much better in ms2ginger
Sent from my MB525 using XDA App
I like cm7 most
and i just tried cm9 which semms to be even better
@sp8y you are absolutly right. I am also doing same thing
can you give us all the links(for mods) to make it the way you are using
popcorn1122 said:
@sp8y you are absolutly right. I am also doing same thing
can you give us all the links(for mods) to make it the way you are using
Click to expand...
Click to collapse
Yes no problem
Here's Walters deblur thread - http://forum.xda-developers.com/showthread.php?t=1215798
1% battery step mod - http://forum.xda-developers.com/showthread.php?t=1113249
Patched gmail notification mod for Launcher Pro - http://forum.xda-developers.com/showthread.php?t=1199518
2nd Init bootmenu (I use version 1.7B) & use the CPU settings menu for overclocking/undervolting with the Smartass governor -
http://forum.xda-developers.com/showthread.php?t=1032212
http://forum.xda-developers.com/showpost.php?p=16721202&postcount=168
http://forum.xda-developers.com/showpost.php?p=17032162&postcount=3
Need Root for most of these mods but I just used Superoneclick.
Hope that helps
Thank you so much, I will use this tonight and stop all modding experiment till stable CM9 arrives
popcorn1122 said:
CM7.1.0 and MIUI failed for me in regular use... it hungged when you actually need phone to talk. it hung when u actually need to take pic... the auto focus also fails sometimes in night.
with stock roms , its more stable but just a bit slow...
so if you root and overclock the stock to 1 GHz , and remove useless softwares, it makes the defy best phone.
Unless we have a kernel of GB, its no point to install a GB with a kernel of a froyo.
Click to expand...
Click to collapse
Well I've been working since past 12 hours (from scratch) customizing GB 2.3.4-134_DFP-10_2 (Debluring + modding BlurHome.apk launcher for appearance).And I must say , this is the best stock ROM I've come across so far.
sp8y said:
Yes no problem
Here's Walters deblur thread - http://forum.xda-developers.com/showthread.php?t=1215798
1% battery step mod - http://forum.xda-developers.com/showthread.php?t=1113249
Patched gmail notification mod for Launcher Pro - http://forum.xda-developers.com/showthread.php?t=1199518
2nd Init bootmenu (I use version 1.7B) & use the CPU settings menu for overclocking/undervolting with the Smartass governor -
http://forum.xda-developers.com/showthread.php?t=1032212
http://forum.xda-developers.com/showpost.php?p=16721202&postcount=168
http://forum.xda-developers.com/showpost.php?p=17032162&postcount=3
Need Root for most of these mods but I just used Superoneclick.
Hope that helps
Click to expand...
Click to collapse
Apparently 2.3.4-134_DFP-10_2 overclocks MB525 between ~800 - 1000MHz
Thanks again for links but the stock ROM I'm testing has no errors.All I need now is on how to go about editing BlurHome.apk in GB.
@root_toor , I had the same question of using BlurHome.apk in GB like CM7.1
But as they are on different framework, you cant install the BlurHome.apk excep on stock GB of Motorola.
and what exactly are you trying with 2.3.4-134_DFP-10_2?
popcorn1122 said:
@root_toor , I had the same question of using BlurHome.apk in GB like CM7.1
But as they are on different framework, you cant install the BlurHome.apk excep on stock GB of Motorola.
and what exactly are you trying with 2.3.4-134_DFP-10_2?
Click to expand...
Click to collapse
Well the following
Debluring
Trying to customize stock Launcher
Adding Reboot option in Power Button Tray
Optimization for decent performance (battery)
Last resort is Launcher PRO (not ADW - very unstable)
Basically I'm working on one of the most stable GB ROM for MB525 with least "custom mods"
I won't be adding 720p mod as the stock camera rom is giving me better image output than FROYO and CM7.
So mostly a minimalist ROM (1% custom , 99% Stock) for stability.
hi all
I wonder if the gingerbread kernel can work quietly on my defy mb525 green lens module BAYER. I currently have the CM 7.2 nightly with linux kernel 2.6.32.9 (stock froyo 2.2.2) and I'm wondering if this rom is actually compatible with gingerbread kernel, and then everything would work .
in my case, the greenbreadmod lead the camera to work without problems on the cyano?
thanks for your support
yea you can use gb kernel on defy...
defy can work perfectly on froyo and gb kernel but defy+ cannot work on froyo kernel!
Gb kernel on mb 525 have problem with camera and battery
Sent from my MB526 using xda premium
hey guys can any of you answer this thread about kernels
http://forum.xda-developers.com/showthread.php?t=1554173
N34S said:
... my defy mb525 green lens module BAYER....
Click to expand...
Click to collapse
Do you have green lense or BAYER module? I think you are confusing things. Green lense is SOC module and red lense is BAYER module.
I think so, but i read the log "Detected BAYER device" and 720p does not work. looking better on lamp i see that the lens is green.
Tanzior said:
Gb kernel on mb 525 have problem with camera and battery
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
sure it have problem with battery? i want to do this upgrade for improve the battery life, and to make the phone more responsive.
I read that greenbreadmod allows operation of the green lens camera on the gb kernel. by that I could also record video after this upgrade? it's compatible with the cyano?
up
I read the 3d started from chachoi : I liked the arpith.fbi's answer, but would like more information about what actually rom works on that kernel and if I can run it with 2nd-boot. I did a test with walter74's 109_DPP-4.5.3-11-kernel, but does not start on CyanogenMod 7.2 (and in fact I riflashed the cm7 kernel signed to return to normal). so there is a gingerbread kernel that works on CM 7.2? (If needed, I would be willing to change even though Rom for having these features.)
up
nobody can answer me??
N34S said:
up
I read the 3d started from chachoi : I liked the arpith.fbi's answer, but would like more information about what actually rom works on that kernel and if I can run it with 2nd-boot. I did a test with walter74's 109_DPP-4.5.3-11-kernel, but does not start on CyanogenMod 7.2 (and in fact I riflashed the cm7 kernel signed to return to normal). so there is a gingerbread kernel that works on CM 7.2? (If needed, I would be willing to change even though Rom for having these features.)
Click to expand...
Click to collapse
see i will try to explain in simple words..kernels in android is like BIOS in a computer..it can run only on one kernel at a time..if u r dual booting, u can use only one kernel..either froyo or GB..u cant run one ROM with froyo kernel and another ROM with GB kernel..
Walter's kernel is GB kernel while CM7.2 uses froyo..tats y it dint start..
remember 2nd-boot is like a virtual OS, it has same BIOS(it uses same kernel)..
arpith.fbi said:
see i will try to explain in simple words..kernels in android is like BIOS in a computer..it can run only on one kernel at a time..if u r dual booting, u can use only one kernel..either froyo or GB..u cant run one ROM with froyo kernel and another ROM with GB kernel..
Walter's kernel is GB kernel while CM7.2 uses froyo..tats y it dint start..
remember 2nd-boot is like a virtual OS, it has same BIOS(it uses same kernel)..
Click to expand...
Click to collapse
got it
so if i want to exploit the kernel gb I'll have to switch to one of the defy+ roms for defy. What about the GGL Rom? seems to be a great rom for green lens defy
if you have bayer module than your lens is red. and it does not matter that you can see it green.
Quarx's CM7 Defy+ builds (http://quarx2k.ru/cm7-nightly-defy+/) work perfectly fine with the GB kernel and the battery life is actually better than with the Froyo kernel (at least for me).
You need to install the attached battery fix though since Quarx'x build include the battd for the Defy+. Credits go to Auris 1.6 vvt-i for posting this in the CM9 thread.
The best kernel seems to be 4.5.3-109, which can be downloaded from Walter's MS2Ginger thread.
N34S said:
got it
so if i want to exploit the kernel gb I'll have to switch to one of the defy+ roms for defy. What about the GGL Rom? seems to be a great rom for green lens defy
Click to expand...
Click to collapse
GGL uses froyo kernel as it is for green lens users..
twa_priv said:
Quarx's CM7 Defy+ builds (http://quarx2k.ru/cm7-nightly-defy+/) work perfectly fine with the GB kernel and the battery life is actually better than with the Froyo kernel (at least for me).
You need to install the attached battery fix though since Quarx'x build include the battd for the Defy+. Credits go to Auris 1.6 vvt-i for posting this in the CM9 thread.
The best kernel seems to be 4.5.3-109, which can be downloaded from Walter's MS2Ginger thread.
Click to expand...
Click to collapse
nice thanks...if the greenbreadmod will work with the camera app of the defy+'s cm7.2?
EDIT: i have just installed the defy+ cm7 and 4.5.3-109-DPP11 walter74's kernel. soon i'll test also the battery. the camera still work, but how to change the telephone model in the telephone details? it will compromise the mb525 hardware on supported applications?
Red lens mb525
Cm7.2
Just switched to cm7.2 from pikachu edition. (figured I check it out) I'm guessing I have a froyo kernel. If I wanted better battery life and smoother gaming would the gb kernel be better to flash or just stay on froyo?
(not the right post but figured I ask it instead of creating a new thread)
V6 supercharger is it worth it.?
how to get the battey % I flashed the battery fix zip yet t shows only "?" icon in place of battery
so is there any rom with bg kernel for green lens (soc)??? if yes than i would like to get a link for it
As the number of DEFY+ owners slowly reaches the number of regular DEFY ones, it's becoming an every day thing to see someone brick his DEFY+ because he flashed a Froyo only ROM. I'm not mad about the fact, I know that it's all confusing when you're doing it for the first time and that's why I'm going to try and make things a bit easier.
1. Introductory information
DEFY+ = Overclocked Bayer lens DEFY and a higher capacity battery
*If you haven't read it already, read the great All-in-One Defy Beginner's guide written by Zephyrot!*
1.1 Downgrading / "bootloader version" issues
-DEFY+ comes with "bootloader version" 6 or 7. What does "bootloader version" mean? Every Motorola .sbf file is made up of many code groups (short: CG) which contain different part of the phone's operating system (kernel, system files, multimedia files etc.). Those code groups are signed by Motorola (otherwise they would make the phone unable to boot when they are flashed) and one part of that signing is a version number. When you flash a .sbf on your phone you cannot flash one that contains CGs signed with number lower that those that have previously been on your phone.
*Only the latest 2.3.6 Motorola ROM's are signed as version 7*
2. Gingerbread ROMs
-Gingerbread ROM's can be flashed on to every DEFY+ that you can root and install 2nd on. No need to worry about kernels, because these ROM work on the Gingerbread kernels and, as you know, every DEFY+ comes with Gingerbread pre-installed.
1. CyanogenMod 7.2 by Quarx - download
2. CyanogenMod 7.2 by Epsylon - download
3. CyanogenMod 9 by Quarx - download
4. CyanogenMod 9 by Epsylon - download
5. CM7 WhiteRabbit Plus Edition by TweetyPeety - download
6. MS2Ginger v3 by walter79 download
3. Froyo ROMs
-These ROM's are meant to work with a Froyo kernel, which is actually quite easy to get to:
..::Guide for flashing a DEFY+ down to Froyo (bl6 only)::..
*My plan for this thread:
-List of all ROM's that include DEFY+ support by the author
-A bit of information on every ROM mentioned
-Guide for installing every ROM on the DEFY+ (Gingerbread or Froyo)
-Battery fixing (so you can charge your DEFY+ battery to 100%) on any ROM
-Overclocking
-A list of version 6 and version 7 Motorola ROM's
Battery fix to the Quarx's CM9 18th march build.
i upgraded to Quarx's CM9 nightly and i had a problem with the battery..The percentage was constant..No matter how much i charge or discharge.
So i went for the defy red lens battery fix..now the battery status is displaying correctly but the battery charges only till 81%.
Any fix ?
krishna.kowshik said:
i upgraded to Quarx's CM9 nightly and i had a problem with the battery..The percentage was constant..No matter how much i charge or discharge.
So i went for the defy red lens battery fix..now the battery status is displaying correctly but the battery charges only till 81%.
Any fix ?
Click to expand...
Click to collapse
According to my experience, the unofficial Defy+ CM7.2 and CM9 builds are running very well with this SBF, its Android version is 2.3.6. I flashed it and have no such problems with Quarx's CM7.2 and CM9 ROMs. No battery and camera fix is needed for the latest builds.
Goose-T said:
According to my experience, the unofficial Defy+ CM7.2 and CM9 builds are running very well with this SBF, its Android version is 2.3.6. I flashed it and have no such problems with Quarx's CM7.2 and CM9 ROMs. No battery and camera fix is needed for the latest builds.
Click to expand...
Click to collapse
i was on stock 2.3.4 initially..later flashed CM7.1 and CM7.2 before flashing CM9 build by Quarx. and i have a battery charging problem. Is that SBF from moto ?
krishna.kowshik said:
i was on stock 2.3.4 initially..later flashed CM7.1 and CM7.2 before flashing CM9 build by Quarx. and i have a battery charging problem. Is that SBF from moto ?
Click to expand...
Click to collapse
I think that Android 2.3.4 and 2.3.5 versions are so uncommon on the Defy+, that almost no one uses the kernels from these as a basis for custom ROMs. That SBF is an official Motorola firmware, if you are familiar with RSD Lite and your phone's bootloader version is 6, you should flash it, and your problems will be gone with CM. Make a nandroid backup first in case of warranty problems. After flashing you will have to root it and install 2ndInit again.
Goose-T said:
I think that Android 2.3.4 and 2.3.5 versions are so uncommon on the Defy+, that almost no one uses the kernels from these as a basis for custom ROMs. That SBF is an official Motorola firmware, if you are familiar with RSD Lite and your phone's bootloader version is 6, you should flash it, and your problems will be gone with CM. Make a nandroid backup first in case of warranty problems. After flashing you will have to root it and install 2ndInit again.
Click to expand...
Click to collapse
Pretty long procedure..what does stock rom have to do with custom roms?After installing the Quarx's latest nightly i flashed the CM9 kernel..Without flashing the CM9 kernel it gets stuck at the boot logo.There should be a battery fix for this.
krishna.kowshik said:
Pretty long procedure..what does stock rom have to do with custom roms?After installing the Quarx's latest nightly i flashed the CM9 kernel..Without flashing the CM9 kernel it gets stuck at the boot logo.There should be a battery fix for this.
Click to expand...
Click to collapse
Read this, and you will understand. In a nutshell: the kernel is responsible for the battery issue, and the kernel in your Android 2.3.4 is not fully compatible with CM7.2. The CyanogenMod builds for this phone do not contain the kernel, they use the official one that sits on your phone since you've bought it. One cannot simply change kernel on a Defy+ (locked bootloader and digital signature), the safest way to do it is to flash an official SBF with RSD Lite, which will contain the good, CM-compatible kernel.
Goose-T said:
According to my experience, the unofficial Defy+ CM7.2 and CM9 builds are running very well with this SBF, its Android version is 2.3.6. I flashed it and have no such problems with Quarx's CM7.2 and CM9 ROMs. No battery and camera fix is needed for the latest builds.
Click to expand...
Click to collapse
Goose-T said:
I think that Android 2.3.4 and 2.3.5 versions are so uncommon on the Defy+, that almost no one uses the kernels from these as a basis for custom ROMs. That SBF is an official Motorola firmware, if you are familiar with RSD Lite and your phone's bootloader version is 6, you should flash it, and your problems will be gone with CM. Make a nandroid backup first in case of warranty problems. After flashing you will have to root it and install 2ndInit again.
Click to expand...
Click to collapse
`
All European DEFY+ come with 2.3.5 pre-installed! And I use one of the 2.3.5 sbf's as a basis for all Gingerbread ROM's and have no problems, just like you.
Please stop telling people to flash that 2.3.6 sbf! It's okay as I can see that it's version 6, but nevertheless, sbf flashing is not really a pleasant experience for the beginners and is considered an advanced technique. I know that it's actually a piece of cake, but it won't solve his battery problem. It won't solve anyone's battery problem, because it's called by one file only - battd.bin. Nothing to do with kernel version.
niksy+ said:
`
All European DEFY+ come with 2.3.5 pre-installed! And I use one of the 2.3.5 sbf's as a basis for all Gingerbread ROM's and have no problems, just like you.
Please stop telling people to flash that 2.3.6 sbf! It's okay as I can see that it's version 6, but nevertheless, sbf flashing is not really a pleasant experience for the beginners and is considered an advanced technique. I know that it's actually a piece of cake, but it won't solve his battery problem. It won't solve anyone's battery problem, because it's called by one file only - battd.bin. Nothing to do with kernel version.
Click to expand...
Click to collapse
what do u suggest niksy ? any fix under development ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:19 PM ----------
Goose-T said:
Read this, and you will understand. In a nutshell: the kernel is responsible for the battery issue, and the kernel in your Android 2.3.4 is not fully compatible with CM7.2. The CyanogenMod builds for this phone do not contain the kernel, they use the official one that sits on your phone since you've bought it. One cannot simply change kernel on a Defy+ (locked bootloader and digital signature), the safest way to do it is to flash an official SBF with RSD Lite, which will contain the good, CM-compatible kernel.
Click to expand...
Click to collapse
The battery was working completely fine when i was on CM7.2 RC1. No issues at all..and as far was CM9 is concerned i have flashed the CM9 kernel and using the latest Quarx build.
niksy+ said:
`
All European DEFY+ come with 2.3.5 pre-installed! And I use one of the 2.3.5 sbf's as a basis for all Gingerbread ROM's and have no problems, just like you.
Please stop telling people to flash that 2.3.6 sbf! It's okay as I can see that it's version 6, but nevertheless, sbf flashing is not really a pleasant experience for the beginners and is considered an advanced technique. I know that it's actually a piece of cake, but it won't solve his battery problem. It won't solve anyone's battery problem, because it's called by one file only - battd.bin. Nothing to do with kernel version.
Click to expand...
Click to collapse
Then why do I have no problem with the battery display without applying any battery fix? I'm using Quarx's CM7.2, and also tried CM9.
Goose-T said:
Then why do I have no problem with the battery display without applying any battery fix?
Click to expand...
Click to collapse
That goose-t, even i dont know..but i'm pretty sure that it has nothing to do with the stock rom or kernel or the sbf which you are talking of.i've sent a mail to quarx regarding the problem.Hope he works out a solution.
Goose-T said:
Then why do I have no problem with the battery display without applying any battery fix? I'm using Quarx's CM7.2, and also tried CM9.
Click to expand...
Click to collapse
Why don't I have any problems with the battery? My base sbf is 2.3.5 and I haven't applied any battery fix.
Why didn't I have any problems with the battery when I used MIUI Pikachu Edition? It had Froyo as a base.
Kernel version has nothing to do with the battery charging problem. (added on 5th of July: this may not be correct :/ The confusion around the problem is still here.)
Quarx himself owns a DEFY+ and that's why his ROMs are DEFY+ compatible. The battd.bin file that he put's in his Gingerbread ROM's (defy+ builds of CM7.2 and CM9) contains the information about the capacity of a DEFY+ battery, not standard DEFY.
Goose-T said:
Then why do I have no problem with the battery display without applying any battery fix? I'm using Quarx's CM7.2, and also tried CM9.
Click to expand...
Click to collapse
Goose-T...i had no battery problems or any other problems when i was using CM7.2...i'm facing a battery prob on Quarx's CM9(18th march build).
krishna.kowshik said:
what do u suggest niksy ? any fix under development ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:19 PM ----------
The battery was working completely fine when i was on CM7.2 RC1. No issues at all..and as far was CM9 is concerned i have flashed the CM9 kernel and using the latest Quarx build.
Click to expand...
Click to collapse
krishna.kowshik said:
Goose-T...i had no battery problems or any other problems when i was using CM7.2...i'm facing a battery prob on Quarx's CM9(18th march build).
Click to expand...
Click to collapse
What is that with "i have flashed the CM9 kernel"? Quarx's CM9 worked for me flawlessly without any kernel update.
Goose-T said:
What is that with "i have flashed the CM9 kernel"? Quarx's CM9 worked for me flawlessly without any kernel update.
Click to expand...
Click to collapse
i tried installing CM9 without the kernel update, but i was getting stuck on the boot logo. then i found a thread that said you have to flash the CM9 kernel after flashing CM9 rom. I did and it worked except the battery problem.
krishna.kowshik said:
i tried installing CM9 without the kernel update, but i was getting stuck on the boot logo. then i found a thread that said you have to flash the CM9 kernel after flashing CM9 rom. I did and it worked except the battery problem.
Click to expand...
Click to collapse
Your DEFY+ has an old 2.3.4 ROM and those ROM's have a kernel that is actually working the same as Froyo kernels. That's why you needed to flash CM9-kernel to get Quarx's DEFY+ CM9 working. (CM9-kernel = one of the Motorola's Gingerbread kernels)
What came to my mind is that your phone might actually be a DEFY flashed to a very early 2.3.4 ROM and then sold as DEFY+. That would explain why official CM7.2 RC1 charged your battery to 100%. That ROM is meant for standard DEFY and for Froyo kernel.
Please reply to my PM or write your battery model here!
How did CM7.2 RC1 work on his defy+???
Sent from my MB526 using XDA
niksy+ said:
Your DEFY+ has an old 2.3.4 ROM and those ROM's have a kernel that is actually working the same as Froyo kernels. That's why you needed to flash CM9-kernel to get Quarx's DEFY+ CM9 working. (CM9-kernel = one of the Motorola's Gingerbread kernels)
What came to my mind is that your phone might actually be a DEFY flashed to a very early 2.3.4 ROM and then sold as DEFY+. That would explain why official CM7.2 RC1 charged your battery to 100%. That ROM is meant for standard DEFY and for Froyo kernel.
Please reply to my PM or write your battery model here!
Click to expand...
Click to collapse
They can actually do that ? Damn MOTO !! i got my phone fully sealed within a Moto defy+ box..Niksy+ can they actually do that ? i mean..how can they ??
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
kadavil said:
How did CM7.2 RC1 work on his defy+???
Sent from my MB526 using XDA
Click to expand...
Click to collapse
i just flashed the CM7.2 RC1 for defy on my defy+ and cleared the dalvik cache..and it worked like a charm !!
krishna.kowshik said:
They can actually do that ? Damn MOTO !! i got my phone fully sealed within a Moto defy+ box..Niksy+ can they actually do that ? i mean..how can they ??
Click to expand...
Click to collapse
I thought you might have bought a second hand one... But your battery model is correct, and you say you bought it sealed in a box. Don't worry, it must be an MB526 (DEFY+)!
kadavil said:
How did CM7.2 RC1 work on his defy+???
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Old 2.3.4 builds are known to work as base for Froyo ROM's
But the weird thing is that his battery won't charge to 100% on ROMs with the correct battd.bin for DEFY+, but it does on the ones with a battd.bin for a standard DEFY!
@krishna.kowshik Try this:
1. Open the CM7.2 RC1.zip, go to system/bin/ and then extract file battd.bin
2. Install RootExplorer on your phone (Accept the SuperUser permissions)
3. Copy that battd.bin file you extracted to somewhere on your memory card
4. Open RootExplorer, copy the battd.bin from where you've put it, go to root/system/bin press Mount R/W button, then paste the battd.bin, overwrite the previous one and finally press Mount R/O button.
5. Exit everything, turn off phone, enter custom recovery, Recovery > Custom > Advanced / Clear battery stats
6. Restart phone
Your phone should charge to 100% now! But, there's no guarantees. DEFY+ is a strange thing There are many MANY of those battd.bin files available, and some work for some people, some work for others...
Let us know if it worked!
niksy+ said:
I thought you might have bought a second hand one... But your battery model is correct, and you say you bought it sealed in a box. Don't worry, it must be an MB526 (DEFY+)!
Old 2.3.4 builds are known to work as base for Froyo ROM's
But the weird thing is that his battery won't charge to 100% on ROMs with the correct battd.bin for DEFY+, but it does on the ones with a battd.bin for a standard DEFY!
@krishna.kowshik Try this:
1. Open the CM7.2 RC1.zip, go to system/bin/ and then extract file battd.bin
2. Install RootExplorer on your phone (Accept the SuperUser permissions)
3. Copy that battd.bin file you extracted to somewhere on your memory card
4. Open RootExplorer, copy the battd.bin from where you've put it, go to root/system/bin press Mount R/W button, then paste the battd.bin, overwrite the previous one and finally press Mount R/O button.
5. Exit everything, turn off phone, enter custom recovery, Recovery > Custom > Advanced / Clear battery stats
6. Restart phone
Your phone should charge to 100% now! But, there's no guarantees. DEFY+ is a strange thing There are many MANY of those battd.bin files available, and some work for some people, some work for others...
Let us know if it worked!
Click to expand...
Click to collapse
Alright..I'm working on it ...Hope it works ..
---------- Post added at 11:29 PM ---------- Previous post was at 10:43 PM ----------
Well guys...Quarx replied back to my mail asking me which kernel i have used..i've given him the details. Looks like he will fish out a solution !!
KUDOS to QUARX !!
Hi @ all.
I want to start a support thread for all those unlucky ones who flashed a BL7-sbf on their green-lensed defy.
NOT the Defy+ or red lens, because the green one is the one for real trouble.
I am aware that you can always install a CM10 by quarx, but I wanted to have a more smooth and stable solution.
You should verify, that you are on a BL7. If you don't know what that means, you should not be here, Do not use these rooting instruction unless you know, you are on BL7. If you're questionning here, what are advantages, or disadvantages, or how you can find out what BL you have, please leave NOW.
This thread is for those who know what's cookin'.
I cannot stress this enough - be sure. search the forums. Don't flood this with useless questions.
I'll try to keep the first posts updated regularly, so that there should be no reason to read the whole thread everytime.
Now let's get started:
1. As far as I know, Froyo is no longer an option.
So, your options start with GB ROMs plus the camera fix. Please comment if they work and how.
I am sure somebody already built such roms.
2. You can also use a 2ndboot-based CM7 build like ms2ginger.
I don't know how many of those exist.
3. What I need you for:
Please add your own rom, when you know it's working on BL7.
Please add the rom you're using, when you're on BL7 with working SOC cam.
Questions:
It would be really helpful to know if ANY GB ROM will work with the camera fix.
It would also be helpful to know, if we should use custom MB525 or MB526 builds as base rom.
Working Roms:
1. MS2Ginger
2. tbc.
3. tbc.
First try (all flashed via custom recovery):
1. I managed to get a working CM 7.2, from early may 2013 with GB Kernel. (cm72-20120506-NIGHTLY-Defy+.zip)
2. Rooted via Defy+ BL7 method (sig)
3. Sndinit 2.3 (you should use 2.0, because some said they had problems with the 2.3 version) i am writing this a week later, so I hope this is correct
5. camera did NOT work
What I did NOT get to work (yet):
1. update-CyanMobile-eXperience-Defy-20130502-Release.zip
2. WajkIUI_multilang_3.1.27.zip
3.
Unfortunately "not working" means usually no more bootups, no way to get into custom recovery for restoring or reflashing, so you'll have to start all over again:
1. Flash first sbf (sig)
2. Flash second sbf for root (sig)
3. Install SndInit 2.0
4. boot into recovery
5. flash your new flavour
...tbc
for supporters
If someone managed to get a custom ROM to work, please provide following informations:
Build# of the "wrong" sbf
sbf's used for root (there are already 2 known combinations, CN & CEE)
used SndInit (should be greater than 2.0 i guess)
full flash instructions
which recovery used for wiping
which one for flashing
how many reboots
approx. duration of the process
ROM Version and build
Information about 2nd boot or 2nd init and when to set it
Does the camera work?
Please, ONLY BL7 stucking ROMs, this is a special thread for special cases.
reserved
reserved.
THK For start this thread.
I am on DFP231 BL7 Green Lens.
By flashing rooted SBF BL7 AND quarx CM10 (2nd boot)
Camera Work.
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20130409-NIGHTLY-mb526.zip
But my Battery not work.
first CM7 known to work
Look here:
jalal-jap said:
THK For start this thread.
I am on DFP231 BL7 Green Lens.
By flashing rooted SBF BL7 AND quarx CM10 (2nd boot)
Camera Work.
http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20130409-NIGHTLY-mb526.zip
But my Battery not work.
Click to expand...
Click to collapse
Thanks, but this thread is GB-based ROM's only.
I wanted to have a snappier / more responsive / smooth ROM instead of feature-rich slow/laggy ones. - See OP.
To clarify: 2.3.x-based ROM's only.
Thanks anyway.
mobilefirmware.com/index.php?route=product/category&path=7618_7654
Jó ez a defy+
retekevo said:
mobilefirmware.com/index.php?route=product/category&path=7618_7654
Jó ez a defy+
Click to expand...
Click to collapse
Bizony-bizony
erdnuesse said:
Thanks, but this thread is GB-based ROM's only.
I wanted to have a snappier / more responsive / smooth ROM instead of feature-rich slow/laggy ones. - See OP.
To clarify: 2.3.x-based ROM's only.
Thanks anyway.
Click to expand...
Click to collapse
Last CM7 ROM`s Epsy is custom kernel & camera work.
But that rom have a wifi bug.
http://defy.wdscript.fr/defy-cm7-releases/
Sorry For english.
defy
ToMpI97 said:
Bizony-bizony
Click to expand...
Click to collapse
jo de melyik megy onnan ?
jalal-jap said:
Last CM7 ROM`s Epsy is custom kernel & camera work.
But that rom have a wifi bug.
http://defy.wdscript.fr/defy-cm7-releases/
Sorry For english.
Click to expand...
Click to collapse
M on build number 4.5.1-134_DFP-231, (BL7) Unable to install any of the custom gingerbread Rom, You said Epsy Last Rom worked for you... can u tell me which ROM and what was the wxact procedure. M stuck on stock ROM.. It's laggy and battery hungry.. So please any one can assist me out of here.
Niteeshkanungo said:
M on build number 4.5.1-134_DFP-231, (BL7) Unable to install any of the custom gingerbread Rom, You said Epsy Last Rom worked for you... can u tell me which ROM and what was the wxact procedure. M stuck on stock ROM.. It's laggy and battery hungry.. So please any one can assist me out of here.
Click to expand...
Click to collapse
last Cm10.1 Quarx is good.
http://quarx2k.ru/cm10.1-nightly-defy+/2.6.32/cm-10.1-20130607-NIGHTLY-mb526.zip
CM7--> Set default boot to 2ndboot
http://defy.wdscript.fr/jordan-nightly/CM72-20121126-NIGHTLY-Defy.zip
CM9--> Set default boot to 2ndboot
http://defy.wdscript.fr/defyplus-cm9/CM9-NIGHTLY-121118-Defy+.zip.md5sum
http://forum.xda-developers.com/showthread.php?p=15073332
Confirmed working. :good:
Well, sorry for huuge delays, but I am now on MoKee 34.1 because Rom lags or responsiveness is no longer an issue on Android 4.3
(OK, i missed some features as well)
I might remove the restriction of GB based Roms, but basically every 2nd Boot Rom works so i might collect only Rom trees, no single versions. Any opinions on this?
Sent from my MB526 using xda app-developers app
I have BL7 and i have blocked for few days in rom 2.3.6 4.5.1-134_DFP-231.
Then i have rooted it by install fixed sbf, and found a good sbf MistyOS-BL7-4.1.2.sbf (if any one want it i will upload it)
this fixed sbf install CM10.1 and u can make it a start point to install CM10.2 and CM11
Now i have CM10.2 work fine, just battery charger only with computer