Develop Bugs

[Q] Difference between CM7 nightly and boot179

What is the difference between NIGHTLY and BOOT179 nighties? When would I use either one? Is there a difference how I apply them?
Thanks

Both version include boot.img and devtree.img in the zip.
Nightly doesn't write those file into their relative partition, so it's supposed you've already installed CM7 ( rc or boot version ) or flashed froyo cee version ( 179 ) before flash the zip.
Boot version will write those files, so you don't need to flash froyo sbf if you come from different rom.

How install boot179 nightly?
Like Jordan nightly's? Or i need full wipes? Thanks

achaw said:
How install boot179 nightly?
Like Jordan nightly's? Or i need full wipes? Thanks
Click to expand...
Click to collapse
If you come from a different rom, you'll always have to wipe.

Im already in CM7 jordan nigthly build, 7/20.
Enviado desde mi MB525 usando Tapatalk

achaw said:
Im already in CM7 jordan nigthly build, 7/20.
Enviado desde mi MB525 usando Tapatalk
Click to expand...
Click to collapse
If your base rom is Froyo CEE 2.2.2 ( aka 179 ) or CM7 RC1(v2), you don't need to flash a "boot-cm7".
In few words, you'll have to flash a boot cm7 version only if you know ( or don't know ) you're running a different kernel.

carlo93, Thanks for your answers.
Here's my CM7 "history":
Started with stock US Froyo (3.4.2-107_JDN-9)
flashed JRDNEM_U3_3.4.2_177-005_NORDIC (not sure if this was necessary but did it just in case)
installed CM7 RC1v2
installed cm7-110715-1018-NIGHTLY
If I understand everything correctly then there is not need for me to install a boot179 and I can go with normal nightlies, correct?
The exception would be the latest cm7-110723-1251-BOOT179-4, which includes the latest 179 kernel, in case I would like to try it out.
Also, I've read quite many posts regarding Rom Manager and that it is now supported in CM7.
But I'm still a little unsure regarding:
Can I use ROM Manager if I'm on cm7-110715-1018-NIGHTLY-Jordan? My current bootmenu version is v0.9.7-defy (CWM 4.0.1.0-defy as latest recovery and CWM 4.0.0.7-defy as stable recovery)
Or do I need to install a later nightly?
I found this post from Epsylon3 http://forum.xda-developers.com/showpost.php?p=15665594&postcount=8716
"first time in rom manager you need to click on flash recovery.. that will ask you if you want to use current recovery... answer yes"
I installed Rom Manager 4.3.2.4 and it gives me the choice of CMW 2.x and CWM 3.x as the recovery versions I have manually installed. Which one should I choose or does it matter?
Thanks

I have a similar CM7 history and i recently flashed Boot 179-4.
Its one of the best nightlys i flashed so far and gives me a very good Battery performance. I recommend check it out.

Now we have BOOT-179 and and BOOTSEA nightly. I always install "nighltly" build...should i install BOOTSEA instead?

So we have to flash the boot version with rsd lite? And all our data will be deleted? Not like in nightlys were we its like just an update?
Sent from my MB525

The Boot Nightly are still just an Update. Just wipe Dalvik and normal Cache after you install them.
BTW: Battery Runtime with SEA boot nightly is better IMHO.
Someone tell the developer because I still can't post to the right topic in the right forum....
Is the overclock bug still in cm7-110727-0001-NIGHTLY-Jordan ?

DEFY+ (MB526) - a guide for the beginners

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 !!

Help with Unofficial CM9 for supersonic

Hi I'm new to the xda and I'm wondering how to flash CM9 unofficial incremental 6-27 I know how to flash but the person who made he said flash the stocked kernel please help a video would be great

lreyes15 said:
Hi I'm new to the xda and I'm wondering how to flash CM9 unofficial incremental 6-27 I know how to flash but the person who made he said flash the stocked kernel please help a video would be great
Click to expand...
Click to collapse
The incremental update is not the full ROM, they're just small updates for phones already running the ROM. The full ROM will be about ~100+ MB. Also, you will need to have an unlocked boot loader and a custom recovery. Once you have that knocked out just Download the ROM and put it in your SD card. Make sure you wipe all data after you make a backup of your current ROM. Finally, Flash the ZIP and reboot your phone. One more thing, with the CM9 ROM, you need to download the ICS GAPPS so you have the Market and etc. Enjoy.

css911 said:
The incremental update is not the full ROM, they're just small updates for phones already running the ROM. The full ROM will be about ~100+ MB. Also, you will need to have an unlocked boot loader and a custom recovery. Once you have that knocked out just Download the ROM and put it in your SD card. Make sure you wipe all data after you make a backup of your current ROM. Finally, Flash the ZIP and reboot your phone. One more thing, with the CM9 ROM, you need to download the ICS GAPPS so you have the Market and etc. Enjoy.
Click to expand...
Click to collapse
I know that I said I know how to flash and I just want to know step by step on flashing incremental I have the full rom and I have everything ready but I don't get the part about stocks kernel? I know what kernel is I just want to know what he means by stocked kernel as in the sence kernel or a different kernel

The stock kernel is the kernel included with the rom. If you have flashed a different kernel you must find out which kernel was included with the version of cm9 you are running and download to SD card, then flash. Then flash incremental. Also do not skip incremental. Flash in order of date after your rom download. Example rom- 6272012 incremental-6282012.
I feel more like I do now then I did then.

Thanks
Sent from my PC36100 using xda premium

lreyes15 said:
Thanks
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Try out the Mason kernels and see how they treat you. I think the JMZ CM9 Kernel is the Mason kernel. Also, look for the unreleased Mason kernels as they might include new performance fixes and possibly hardware fixes. I heard a rumor of WiMAX hitting CM9.

lreyes15 said:
I know that I said I know how to flash and I just want to know step by step on flashing incremental I have the full rom and I have everything ready but I don't get the part about stocks kernel? I know what kernel is I just want to know what he means by stocked kernel as in the sence kernel or a different kernel
Click to expand...
Click to collapse
JMZ stated that if you flash a custom kernel after flashing a nightly ROM you will need to flash the SAME custom kernel after flashing the incrementals I believe he has gone back to the evervolv kernel on latest ROMS for compatibility issues
sent from a rooted EVO 4G running Radiance RLS-ONE SENSE 3.5 Anthrax kernel infected!!!!

From MIUI to CM9 . Confused abt GB & Froyo Kernel - Epsilon vs Quarx

I want to u update from MIUI to CM9 in MY DEFY.
My dbts are
1. Whats is difference between Epsilon vs Quarx Builds
2. What shuld i try GB cm9 or Froyo cm9 . (My MIUI currently show kernel as 2.6.32-gb)..
3. shuld i has to flash kernel after Flasing CM9 ROM

Hey
First of all dont use CM9! The project has stopped , Quarx and Epsy are only developing CM10 and its way better than CM9 simply get the latest Build
1.) Theyre both almost the same builds some people say Epsy's is better some say Quarx's is simply try it out(im using quarx he has more updates)
2.) You cant downgrade to the Froyo Kernel once youve been on the GB Kernel
3.) You dont need to flash a new kernel but you need to do a Fullwhipe and after the installation a cache and dalvik cache whipe

Steveletack said:
Hey
First of all dont use CM9! The project has stopped , Quarx and Epsy are only developing CM10 and its way better than CM9 simply get the latest Build
1.) Theyre both almost the same builds some people say Epsy's is better some say Quarx's is simply try it out(im using quarx he has more updates)
2.) You cant downgrade to the Froyo Kernel once youve been on the GB Kernel
3.) You dont need to flash a new kernel but you need to do a Fullwhipe and after the installation a cache and dalvik cache whipe
Click to expand...
Click to collapse
Thanks for the reply ... But i was asking which Version Wuld be suitable for me as i Have MIUI ....
And Dont knw that cm9 has stopped .. But i want a stable ROM and heard CM9 is almost bug free ...
and i dont want wanna try nigty version to jst check the ROM>.

go for the white rabbit. it is based on cm7.2 euro kang but i think has a sort miui theme sort of thing. it is the best rom i have ever used. i tired cm10 very slow and laggy compared to the slim and lean cm7. seriously you wont be missing anything by staying cm7 at least for the time being.

- does your Defy have green or red lens?
you can follow the instructions on http://forum.xda-developers.com/showpost.php?p=29003033&postcount=1
as in previous posts, CM9 is not developing any more, if you want to experience JB go with the CM10 I used both Quarx and Epsylon builds, and Epsylon's was a bit more for me...
however, for the last week I'm using AOKP build which works best (and fastest) in my case, even with Nova launcher

its red bayer module .. i find it as a yellow shade and also with the image size .

[Support] [FAQ] [BL7] working GB-based ROMs for green lens defys

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