Database Users

[Q] Leaked BL6 Froyo SBF to allow Froyo Kernel ICS on Defy+ ?

I've been reading the thread in the dev forum about the leaked Chinese sbf that is Froyo based but with BL6 - http://forum.xda-developers.com/showthread.php?t=1486731
I was thinking - would this allow a Defy+ owner with either a BL5 or BL6 flashed sbf to flash the chinese BL6 Froyo SBF and then install Quarx Froyo Kernel builds of ICS?
It's been a while since Epsylon's Gingerbread ICS builds have been updated and was wondering if this would be an opportunity for us Defy+ owners to hop onto the Froyo kernel builds. Perhaps even could be the precursor to development of ICS for both the MB525 and MB526 being merged into one build so the dev's can pool together and work on just the one build.
I've only just got my Defy+ so am not well clued up on this- would be grateful for other more experienced owners take on the above before I try and brick my phone!

I think you can use this if you haven't flashed a bld 7 rom. Keep in mind that it is a bld 6 rom so you can never flash a bld 5 rom afterward directly. Also, there aren't many people who have tried it No garanty.
But with a defy+ you can always flash a bld 6 defy+ rom if it didn't work.

I think my Defy+ was last flashed with a BLD5 rom so will have to think carefully if I want to go up to 6 first. I've snagged the Chinese SBF and a Froyo 2.2 CEE Nandroid so will keep an eye on that thread and see what feedback comes of trying this. I did notice one person has already tried this and says their running WIUI which I could never try being on a >=BLD5 rom.
I would like to check what BLD my current ROM has me set at. Is there a way to examine the sbf to find this out? I've tried googling for an answer but am struggling to come up with anything.

In settings > about phone you can find the build number.
You can find the links to the threat of you rom here:
http://forum.xda-developers.com/showthread.php?t=966537
If there isn't a threat, there is a script to check for the version.

Thanks for the heads up on how to find the smg build number.
I split the sbf with http://forum.xda-developers.com/attachment.php?attachmentid=550748&d=1300980924 and ran the smg checking script from http://forum.xda-developers.com/attachment.php?attachmentid=835336&d=1325246979 against the files and found the last time I flashed my phone I must have already upped my BL to 6.

Then you can try the sbf without risk (apart form losing data of course) as you can always just flash your current rom again and you'll be back.

Why FroYo Kernel?

I have one question.
Why use the froyo kernel at all?
Upgrading ALL defy/defy+s to the latest (rootable, 1321 or 139 preferred for simpler root) 2.3.6 GB kernel would simplify rom/kernel development for the devs. Since more and more defy+s are in use they can simply drop development for the froyo kernels and focus on the GB kernel, since now all defys, whether the old one or + would be running 2.3.6. Any current devs (if they want to retain current status) would just have to switch to GB kernel support for their rom once and keep it that way.

Because the SOC module (green lens) is compatible only with the Froyo kernel.
Upgrading to the Gingerbread kernel means that the camera will be unusable for those Defys.
Forgot to add: Having a locked bootloader sucks.
Trimis de pe Defy CM9

So all defys are not equally upgradable to GB (kernel)?
What kinda BS policies are these from Moto? Locked BL they have their reasoning about not wanting users to hard-brick the phones, but what reason to not allow officially updating to GB for ALL defys?

Unfortunately, no, not all Defys can be upgraded to the Gingerbread kernel and still be fully functional (exception being the Greenbread mod). And the devs can't do anything about it because of the locked bootloader.
Regarding Motorola and it's policies - it's all about the money. Outdated phone -> unhappy people -> they buy a new, updated phone -> happy Motorola.
Trimis de pe Defy CM9

Using Froyo makes sense for those, who want to keep the warranty and have to stick to the highest officialy available version. I had to update because CM roms work only with Froyo upwards.

vap_66 said:
Outdated phone -> unhappy people -> they buy a new, updated phone -> happy Motorola.
Click to expand...
Click to collapse
They buy a new, updated phone from someone else. By keeping the Defy stuck on Froyo they've made a lot of people decide never to buy any product from Motorola again.

that is true. the bl lock stops us from changing kernel.
Sent from my MB525 using xda premium

This means that there is Froyo source, but not the driver source for the green lens ?
At this moment, if I want to improve my Defy (green lens, original Froyo 2.2.2), what firmware is the best?
It should support everything (3G, 2G, HSDPA, WI-FI, camera for both photos and video recordings, GPS, sensors and so on).
I'm a newbie and for me it's a bit confusing to see a mod called, e.g., "[ICS] CM9 Android 4.0.4 for the Defy (Froyo kernel)" (there are others, this is only the first I've found... )
ICS is ICS, Froyo is Froyo.
What I gain and what I loose with an ICS "Froyo Kernel"?
Is it ICS or Froyo painted with ICS dust ?

vap_66 said:
Because the SOC module (green lens) is compatible only with the Froyo kernel.
Upgrading to the Gingerbread kernel means that the camera will be unusable for those Defys.
Click to expand...
Click to collapse
Well, I've just upgraded to WIUI 2.4.20 (GB) and now I've GingerBread (2.3.7) full working.
My Defy has a green lens and the camera is working, both for photos and videos.
Have I missed something about the thread?

Are you sure WIUI changed your kernel? ROMs and kernels can play mix'n'match.

Motorola has locked the bootloaders of defy
Thus we can only use motorola signed kernels.
Defy has a froyo kernel and defy plus has GB kernel. Both signed by motorola.
Only these to can be used in custom roms. Even in ics and even in jelly bean (Android 5.0) we will have to use these kernels as long as motorola doesnt unlock the bootloader. Froyo build of ics means ics that runs with froyo kernel. GB kernel works only with red lense cameras of defy and all defy+. So only froyo build will work for green lens defy.

^^
This was exactly why i was confused. Do you mean the green lens Defy cannot be officially upgraded (either OTA or RSDLITE) to GB ? And the red lens Defy can be upgraded to GB?

rogier666 said:
Are you sure WIUI changed your kernel? ROMs and kernels can play mix'n'match.
Click to expand...
Click to collapse
Maybe you're right...
Android Version 2.3.7
Kernel Version 2.6.32.9-gb08c3c8
But the 2.3.7 version is GingerBread, whilst the 2.6.32 kernel version is Froyo.
So what's the point ?
The mods are always Froyo but with GB features ?

Defy with green lens can be upgraded to gb kernel but many features inculding cam may not work.
The gb kernel was extracted from defy+. As defy+ has only red lens the gb kernels works with defy red lens also.
Fully functional green lens gb kernel will be possible only when defy gets an official gb update (highly unlikely) or when the defy bootloader is unlocked(higly unlikely too).
---------- Post added at 04:05 PM ---------- Previous post was at 03:58 PM ----------
defy green lens with gb kernel may end up in a bootloop.
so thread with caution.
Flashing an GB sbf will prevent you from coming back to Froyo(Downgrading).
Always try to flash using CWM to keep downgrading options alive

Are there no "fixed" GB SBFs to keep downgrade options alive?

No defy owner should upgrade to gingerbread kernel by flashing an sbf. Our bootloader can load the gingerbread kernel, the gingerbread bootloader can't load the froyo kernel.
So when you flash the sbf you can ONLY use gingerbread kernel based ROMs from then. Otherwise you can just flash the kernel you want from the recovery.
It would even be wise for defy+ owner with bl5 and 6 to flash the bl6 froyo ROM so that they can use both builds by just flashing the right kernel.
About official gingerbread: they are for the defy+. Officially the defy has no gingerbread ROM. For some countries the defy even stays on eclair. Although it would have cost Motorola 5 min to replace the camera and battery drivers. Only problem is money for Motorola and the operators.
Sent from my MB525 using XDA

[Q] New Defy owner, somewhat lost!

I recently bought a UK Moto Defy (MB525, red lens) from Orange on PAYG. I want to remove the simlock and flash an ICS ROM on the phone, but am very confused as to what I should be doing. I tried to follow the all-in-one beginners guide, but I didn't understand parts of it. From what I understood, if I flash certain ROM versions, I will never be able to flash ROMs of a lower android version, unless if is a 'fixed' SBF - is this correct? And if that's the case, I first need to make a Nandroid backup of my current stock ROM so the new ROM that I want to flash can use the CG31 and CG39 files?
Attached is an image showing the info on my current (stock) ROM.

You have Froyo (2.2), do NOT flash a full SBF. With what you have now you can use almost all the ROMs here.
Trimis de pe Defy CM9

vap_66 said:
You have Froyo (2.2), do NOT flash a full SBF. With what you have now you can use almost all the ROMs here.
Click to expand...
Click to collapse
Okay, but which kernel version should I choose if I want to install ICS (and also which ICS ROM, Defy or Defy+)?

Since you have a Bayer module (red lens) you can use both kernels. The Defy ROMs are compatible only with the Froyo kernel. The Defy+ ROMs are compatible only with the Gingerbread kernel. Also, that seems to be the recommended kernel (GB) by the other guys (they reported better battery life, better performance in 3D, etc). Not sure here, but you need a battery fix. Better ask around before.
Trimis de pe Defy CM9

So I can safely install a Defy+ GB kernel and ROM on my Defy SB525 (and retain the ability to go back to an earlier ROM version)? If so, does that mean that these CM7 and CM9 ROMs are 'fixed' SBFs?

Anyone...?

You're confusing ROM and SBF. CM7 and CM9 aren't SBFs at all, they're just custom ROMs. The only way you'll lose downgradability is if you flash a higher version full SBF, but you don't need to worry about SBFs if all you want to do is install custom ROMs—you just need to root your phone. However, I don't recommend installing an ICS-based ROM for Defy, as they're experimental and lack things like hardware acceleration.

cm7 and cm9 are not fixed sbf but zip files...
and you will retain downgradibility unless you flash a full sbf through rsd ....
See Youtube channel onestopdefy..
It will help you install cm7 and cm9

Thanks guys! As for ROMs, are there any in particular that you can recommend? Ideally, i'd like to try ICS, but anything that makes full use of the Defy's hardware (i.e. 720p video recording) with good battery life would be good.

If you want something that makes full use of the hardware, the ICS builds aren't the way to go, but you could always try CM9 and revert to another ROM if you don't like it.
I'd recommend you start with CM7.1—it's basically the "standard" custom ROM, because it's the latest most stable and well-supported. If you like it and when you feel like taking the next step, see this thread. You don't typically have to wipe your data to switch between CM ROMs, so it's painless.

CM doesn't have 720p recording... If you want to have 720p I would recommend some modded stock moto rom, like MS2Ginger.
Sent from my MB525 using XDA

Thanks everyone for the help so far, it has really helped to clarify everything.
One last question: Is MS2Ginger an SBF ROM? And if so, if I flash it, will it affect my ability to flash to other ROMs like CM7/CM9?

Every custom rom is a. zip file you can flash from CWM! so basically you can jump from one custom rom to another by going into CWM, make a wipe data/cache and wipe dalwik cache, and install rom as .zip! (you don't even need to wipe data if you want just updating a cm nightly with a newer one.)
You can only lose your downgradeability, if you flash an official sbf from moto with a higher be number !
Sent from my MB526 using XDA

Today I flashed MS2Ginger 3.0 but am having a problem. I need to remove the SIM lock using the softunlock method detailed in the Defy General forum.
My stock defy had the correct baseband version (EPU93_U_00.59.01), but after installing MS2Ginger, the baseband got changed to EPU93_U_00.61 - I ran the Baseband_change(EPU93_U_00.59.01).zip in recovery, which said that the baseband had been changed successfully. I then ran GB_Defy_softunlock_v1.3(EPU_U_00.59.01).zip, which reported that the simlock had been removed. Finally, as per the instructions in the softlock thread, I rebooted once with the standard SIM card, shut down the phone, installed my new SIM card, but still get the sim unlock prompt on startup.
Does anybody know how I can change the baseband version back to the default one in MS2Ginger? I tried posting in the MS2Ginger thread but it requires me to have >10 posts to reply...

Anyone? I just need to know how to change the baseband in MS2Ginger...

[Q] Need help choosing ICS rom...

I've been reading, and re-reading, and re-re-reading, and now that I finally have my nexus one working with wifi-calling again (for international use), I'm willing to give up the wifi calling on the defy and go into a non-stock TMobile ROM. Since I did like the ICS roms on the nexus one, I think I'm going to go with one of the new CM9 ones.
Based on what I read, I think I understand a few things, but also have questions:
1) Kernel - It's the software underneath the ROM. Think device drivers. I would assume that since I'm on the latest TMobile ROM for the Defy, I'm on Froyo. I have a red lens (tested with logcat), so the question is: Is there any benefits to upgrading to the GB kernels? If I don't like the ICS/CM9 kernels, will it allow me to run CM7.2 kernels and be happy?
2) Quarx vs Epsylon ROMs. I see all these bug threads, and separate threads. Etc. Etc. What's the difference between them? And will the question from the kernel allow me to enjoy differences between the two builds? There's just way too few/many threads on these ROMs, and I'm confused with which one has which bugs and which one stands where. There seems to be 2 builds for each person's ROMs, but when you go into their download sections, it's also different dates with different "fixes", with different mirrors carrying different versions. And when I'm trying to figure out which one has bugs that I can live with, the bugs are in one consolidated thread, for every combination of kernel/ROM.
So the question is - Where can I get info on the latest pros/cons of each ROM and which kernel is needed to support it?
Anyways, point is, I'm lost. I'm hoping to push off the purchase of a galaxy nexus. I like the Defy. I like how I can treat it like junk but still work. I wish I can do inductive charging on it, but it is what it is.
Help???

Basically both devs each made 2 seperate builds one for red lense defy and one for green lense. They use different camera modules so they need different support. Seeing as you have red lense you should go with those (defy+ roms).
The defy cm9/gb kernel was taken from the defy+ and is needed for the defy+/red lense roms to work. To try the defy/green lense roms you need the cm7/froyo kernel which is from the regular defy.
Cm7 uses the froyo kernel and you can just reflash the froyo kernel if you want to go back to it.
About quarx and epsylon I think quarx supports the red lense better.
If you use quarxs defy+ roms on a reqular defy then you need to flash a battery fix.
Sent from my MB526 using XDA

epsylon and quarx has different camera modules so that they can split the work. merging of this build will most probably be done when stable release of cm9 is released. Quarx has a better working camcoder but his last build for green lens was long back. If u have green lense go for epsylon froyo kernel.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

[Q] is there a fixed SBF for Jelly beans for DEFY +

Hi Guys,
I am planning to upgrade my defy from stock ROM to JB.
Is there any SBF available that is fixed than full.
Fixed ROM does not burn the e bridge inside the phone so that I can downgrade the phone to stock.
But with FULL ROM , it burns the bridge and thus I Would not be able to downgrade the phone.
Any info or suggestion would be helpful.

You got the right idea about flashing higher SBF will get you stuck and can't downgrade.
But you have a bit misconception about SBF, those SBF files are "Stock" roms from Moto. Defy has 2.2.2 froyo stock rom as the newest (they abandon it) Defy+ has 2.3.6 gingerbread the most (got abandoned too).
So, there're 2.2.2 SBFs for Defy mb525, and 2.3.6 SBFs for Defy+ mb526, but no "ICS or JellyBean SBF for Defys".
We use SBF only for reverting back to Stock.
Fixed SBF are usually a patch to get a custom rom work without breaking it, not a custom rom itself.
You should read more about SBF and Custom roms. http://forum.xda-developers.com/showthread.php?t=1216982
If you want Jellybean roms, you must use custom roms. Custom roms didn't use SBF to install (as you know, it burn the bridge).
Instread we use 2ndinit/bootmenu to workaround and install custom roms without touching the bridge.
If you interested to try JB, read this http://forum.xda-developers.com/showthread.php?t=1795647

Thank you.
I had mistakenly mentioned sbf for custom ROM. My bad.
So, is there any ROM that is fixed and not full for jb?
Sent from my MB526 using xda app-developers app