[Q] How to properly install CM9 - Defy Q&A, Help & Troubleshooting

Hello, I got a Motorola Defy (MB525) red lens (Bayer Module). At the moment I'm using Froyo 2.2.1 Retail, without root. This is my first smartphone and I want try CM9 out, but I don't have any experiences about install custom ROMs, I've read many tutorials on the internet, but they are very different, so I would like that you solve those doubts:
1. Should I use build 120705 by Epyson or 120707 by Quarx?
2. Should I use Froyo or Gingerbread build?
3. If I should use Gingerbread build, which kernel should I use?
4. Should I install battery fix?
I MAINLY want to be able to go back to my stock ROM because if something goes wrong my phone still on warranty, what should I do then? After reading many tutorials I though the better way is like this:
1. Root phone
2. Install 2ndInit 2.0
3. Create a Nandroid backup
4. Flash the ROM
5. Flash the kernel (?)
6. Flash gapps
7. Done?
Then if I want everything back, I should just restore the Nandroid backup + uninstall 2ndInit 2.0 + unroot and everything on my phone will be like when I was running Froyo 2.2.1 and warranty will be back? Or should I flash a Full SFB?
Here are the informations at 'About the phone':
System Version: Version.34.4.709.MB525.Brasil.en.BR
Build number: 0
Model number: MB525
Android Version: 2.2.1
Version number: 3.4.2-107_JDNL-9

I'm using epsylon's build and it works flawlessly for me, didn't try quarx's so I can't compare.
If you want to keep downgrade ability you have to use froyo kernel so froyo build too.
For the battery fix afaik it's only needed for Defy+.
In your steps to upgrade you forgot doing wipe of user data, cache and dalvik cache (and also battery stats) before flashing.

What llamatron said PLUS:
You can use a build for Defy, then flash CM7 kernel. Or you can use Defy+ build (works for red lens defy too) and flash the cm9 kernel.
Edit: obviously, in your case, you would have to use CM7/Froyo kernel + defy build.
Proper instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1432100
After your step 3 wipe data as llamatron said. Then proceed with 4,5,6.

Llamatron said:
I'm using epsylon's build and it works flawlessly for me, didn't try quarx's so I can't compare.
If you want to keep downgrade ability you have to use froyo kernel so froyo build too.
For the battery fix afaik it's only needed for Defy+.
In your steps to upgrade you forgot doing wipe of user data, cache and dalvik cache (and also battery stats) before flashing.
Click to expand...
Click to collapse
It is not flashing a kernel that prevents the downgrade ability - it's the full SBF flashing that does this. As long as you stay away from RSD Lite and SBF files, you are safe.
Regarding GB or Froyo, IMHO GB builds are better - faster, smoother, longer battery life. I have a red lens Defy and prefer Quarx's Defy+ builds. The beauty of the red-lensed Defy is that you can try everything - Froyo builds, GB builds and decide which one suits you best. Green-lensed Defy is limited to Froyo builds only and most of Defy+ are limited to GB builds only. If the OP wants, he can try Quarx's latest GB and Froyo builds with fully functional HWA and Apps2SD. Check my thread in General - you will find anything you need, including Battery fix and when should you flash it.

Auris 1.6 vvt-i said:
It is not flashing a kernel that prevents the downgrade ability - it's the full SBF flashing that does this. As long as you stay away from RSD Lite and SBF files, you are safe.
Click to expand...
Click to collapse
That's right, sorry for the mistake I had read the all in one defy guide long time ago and didn't understand well this part apparently

Vitor_Hugo said:
1. Should I use build 120705 by Epyson or 120707 by Quarx?
Click to expand...
Click to collapse
I reccomend you Epsylon's build. I use it on daily basis and hasn't disappointed me so far.
Also check out the new Froyo kernel release kernel-froyo-222-179-4-signed
Oh! And if you'll use both, don't forget to enable HWA. It will perform great!

Thanks, I'll go with Gingerbread builds, now I have more 2 doubts:
1. Would Nandroid backup restore my Froyo ROM successfully from a CM9 Gingerbread build?
2. I saw that there are 2 gingerbread kernels on Auris's topic: CM9 Kernel signed and 4.5.2_DHT-22_kernel. Which one should I use?

Vitor_Hugo said:
2. I saw that there are 2 gingerbread kernels on Auris's topic: CM9 Kernel signed and 4.5.2_DHT-22_kernel. Which one should I use?
Click to expand...
Click to collapse
Use CM9-kernel when first flashing CM9. If you flash 4.5.2_DHT the first time, phone won't boot. You can flash this kernel after the inital boot with CM9 kernel.
Vitor_Hugo said:
1. Would Nandroid backup restore my Froyo ROM successfully from a CM9 Gingerbread build?
Click to expand...
Click to collapse
No. In order to return your phone to stock, you need to flash Stock SBF file via RSD Lite. Before flashing an SBF file, make sure it is the correct one, as there is no downgrade, so if you flash wrong sbf with higher BL version (for example stock 2.3.6), you will never be able to go back to Froyo.

Auris 1.6 vvt-i said:
No. In order to return your phone to stock, you need to flash Stock SBF file via RSD Lite. Before flashing an SBF file, make sure it is the correct one, as there is no downgrade, so if you flash wrong sbf with higher BL version (for example stock 2.3.6), you will never be able to go back to Froyo.
Click to expand...
Click to collapse
Sorry, but why on your CM9 Thread you do recommend to make a Nandroid backup?
I've been reading CM9 topics and I came to the conclusion that it still unusable for me, so I'll try CM7.2 stable and wait for CM9 RC1.
Will gapps 20120429 works on CM7.2 or is there another version for CM7.2?

Related

[Q] New Defy: full (Froyo) SBF or stick to fixed SBFs?

Hi, I just picked up a new Defy (MB525). I'm new to the Android scene so I'd like to stick to stock for a while before diving into CM7 / MIUI / etc.
I don't want to stay on Éclair. So my question is, should I flash the full stock Froyo or should I flash the fixed stock Froyo + nandroid backup Éclair CG? Does it matter either way? It looks like all the custom roms need Froyo as a starting point anyway...
Also, is there any negative impact in paring fixed stock Froyo + nandroid Éclair CGs? Intuitively it feels... wrong somehow... like running an updated program with outdated dlls
Thanks in advance.
pinmelon said:
Hi, I just picked up a new Defy (MB525). I'm new to the Android scene so I'd like to stick to stock for a while before diving into CM7 / MIUI / etc.
I don't want to stay on Éclair. So my question is, should I flash the full stock Froyo or should I flash the fixed stock Froyo + nandroid backup Éclair CG? Does it matter either way? It looks like all the custom roms need Froyo as a starting point anyway...
Also, is there any negative impact in paring fixed stock Froyo + nandroid Éclair CGs? Intuitively it feels... wrong somehow... like running an updated program with outdated dlls
Thanks in advance.
Click to expand...
Click to collapse
Fixed froyo sbf with froyo nandroid.
Sent from my MB525 using xda premium
I'am in the same position, I'd like to know answer to this question too.
What is considered to be "optimal" starting point for custom ROMs?
Thanks!
grannyrogers said:
Fixed froyo sbf with froyo nandroid.
Click to expand...
Click to collapse
Thanks for the reply. Just to confirm, you mean update to full stock froyo SBF, then use the froyo nandroid CG backup for all future fixed SBFs, correct?
That means there's no way to return to eclair, right? (not that i'd want to... )
First of all you need to root your defy then just download sndinit apk for defy and install recovery and after that download nandroid backup of froyo and install it using recovery then run install fixed sbf and your ready to go u just retained your downgradeability and you can now go to eclair any time but don't flash full sbf of froyo u'll loose your downgradeability

[Q] Playing around with ROM / Custom ROM / Kernel

I am currently on Froyo Kernel 2.6.32.9, using MIUI ROM from Will5.
What I would like to achieve:
1. I want to try the Stock UK GB ROM (with Kernel that fix the multitouch thing) for some time, play with the motoblur stuff
2. I would like to still be able to install custom ROM (CM7/9 and MIUI) after I play enough with stock ROM
What I think I understand:
1. Only CH GB Kernel that fix the multitouch issue, so I would have to flash this kernel / ROM.
2. CH GB doesn't have GApps & MotoBlur, so I would need UK GB ROM to have this
3. After flashing CH GB, I can reflash Asia WWE Froyo to get back to Froyo
4. After flashing UK GB, I cant get back to either Froyo or CH GB
5. CM7 & 9 Can use CH GB Kernel, while MIUI must use Froyo only
So the question is:
1. If I install CH GB, can I restore santiemanuel's NANDROID backup (http://forum.xda-developers.com/showpost.php?p=19926327&postcount=408) onto it? will this give me a UK GB Stock ROM with CH GB Kernel?
2. If the answer to #1 is no, then is there any way to achive #1?
3. Anyone know if #1 step is downgradeable to Froyo? (I would only need this when I want MIUI back)
thx
I think the answer to your question should be yes. Though don't blame me if it isn't possible to downgrade or you brick your phone
The steps to do so might be:
1. Install CH GB from sbf using RSDLite.
2. Flash UK GB nandroid back up from santiemanuel.
3. Extract the attached CH GB kernel sbf using 7-zip and flash it using RSDLite.
Please do a complete fresh install if you wanna give it a try.
Though it seems harmless, do it at your own risk.
OK, I got issue. I am now stuck with CH GB, because I cant restore UK GB's Nandroid as I am using bootmenu 0.8.6 (and I think the Nandroid made from bootmenu 1.0.4 based on the file name). I have tried the bootmenu 1.0.5 twice, but only to have bootloop and re-doing from scratch (from flashing sbf) both time.
Is there anyone can tell me how to use the bootmenu 1.0.5? I have installed it, then when I run and choose menu #1 then restart, I got bootloop. I dont know what each menu are for as I dont understand chinese.
The version of bootmenu should not matter. However the version of CWM can matter. So what you need to do probably is flash the CWM 5.x.x coz that might be the one with which the nandroid back up has been created.
You can find CWM 5.x.x somewhere in the forum I suppose or from Koush's website.
Sent from my MotoA953 using xda premium
sahilarora911 said:
The version of bootmenu should not matter. However the version of CWM can matter. So what you need to do probably is flash the CWM 5.x.x coz that might be the one with which the nandroid back up has been created.
You can find CWM 5.x.x somewhere in the forum I suppose or from Koush's website.
Sent from my MotoA953 using xda premium
Click to expand...
Click to collapse
thank you, I managed to restore the nandroid backup using bootmenu 0.8.6 available in Endless7's "How to instal cyanogen/miui" thread. I have the bootmenu's files with me all the time, I just didnt test it because I though need higher version of bootmenu >.<
now I have managed to get UK GB running with CH kernel (or so I think), play around for 2 days, doesnt like it
I am now using Tezet's CM7 for GB kernel, but I want to go back to MIUI (I love the fancy themes), so I tried to flash (yes using RSD lite) the Froyo sbf, but alas, RSD Lite doesnt recognize the UK Froyo sbf (http://and-developers.com/sbf:milestone2, 2.2.2 Froyo UK). When I choose this sbf, RSD Lite didnt show the file info like it supposed to, and I dont think this is related to non-downgradeable issue as I havent plug my phone to USB.
does anyone tried the UK 2.2.2 Froyo before? does it work?
or, when you guys need to return to Froyo sbf, which one do you choose?
you cant go back to froyo from official gingerbread, once you've updated your stuck
DreadPirateDan said:
you cant go back to froyo from official gingerbread, once you've updated your stuck
Click to expand...
Click to collapse
I didnt use UK GB sbf, I only use the chinese one which "should" be downgradeable.
But my issue now is RSD lite doesnt recognize the UK Froyo 2.2.2, it might because of broken download of mine or the file is broken to begin with. It will takes me half day minimum (and 1/3 of my monthly data plan) to download that 300MB+, so if anyone can let me know if the file is broken or not before hand, that would be very appreciated.
You can flash UK Froyo 2.2.2 over CH GB as far as I know. I even think I have tried this with success (I mean flashing UK Froyo 2.2.2 over CH GB retail, though it was quite a while ago).
If RSDLite does not recognize it, it could be some other issue. I don't know if it can be linked to a broken download. You can try to download it again or if you are sure that the download is okay, you can try a different computer. May be a friend's PC.
Good Luck!!
Edit: And before you do that, can you post a screenshot of your phone's 'About' menu, showing the CH kernel version.
Attached is screenshot of my phone. I have tried downloading the UK 2.2.2 froyo again, but still rsd cannot recognize. I tried with pc running windows 7 x86 and Laptop running windows 7 x64, both cannot
EDIT: i am using RSDLite 4.9, what version were you using when you're able to get RSD Lite to recognize that UK 2.2.2 Froyo Sahil?
Sent from my A953
Update:
I managed to download hongkong (AsiaRet 2.2.2 Froyo) (thx to a friend of mine), which can be recongnized by RSD lite. unfortunately, I cant flash it, error 0x0017 (iirc) and FAIL shown.
So i guess its not true that I can go back to Froyo if I only flashed CH GB using RSD Lite?
btw, a question not related to above matter: is there any app that can give me quick settings on status bar (like the one in CM or MIUI, when I pull the status bar down) that works on stock rom? unavailability of this feature is why I hate stock rom the most
That's pretty strange. I was quite sure that CH GB was downgradable. Even Tezet said so if I remember correctly. Did you do all wipes?? May be try the wipes from Moto recovery once i.e. if you can access it.
The architecture in GB was changed in some way which made it not support those notification toggles. There is a software by J4velin (a dev from xda itself) which does provide it but it isn't exactly the same thing. Search with that name in market.
Edit: And I was asking for the screenshot when you had UK 2.3.4 and CH GB kernel. You posted screenshot with CM I suppose. And you can try changing the RSDLite version, may be 5.6
Sent from my MotoA953 using xda premium
alexyie said:
Update:
I managed to download hongkong (AsiaRet 2.2.2 Froyo) (thx to a friend of mine), which can be recongnized by RSD lite. unfortunately, I cant flash it, error 0x0017 (iirc) and FAIL shown.
So i guess its not true that I can go back to Froyo if I only flashed CH GB using RSD Lite?
btw, a question not related to above matter: is there any app that can give me quick settings on status bar (like the one in CM or MIUI, when I pull the status bar down) that works on stock rom? unavailability of this feature is why I hate stock rom the most
Click to expand...
Click to collapse
please reboot your computer and phone and try again.this issue sometimes will happen.
sahilarora911 said:
That's pretty strange. I was quite sure that CH GB was downgradable. Even Tezet said so if I remember correctly. Did you do all wipes?? May be try the wipes from Moto recovery once i.e. if you can access it.
The architecture in GB was changed in some way which made it not support those notification toggles. There is a software by J4velin (a dev from xda itself) which does provide it but it isn't exactly the same thing. Search with that name in market.
Edit: And I was asking for the screenshot when you had UK 2.3.4 and CH GB kernel. You posted screenshot with CM I suppose. And you can try changing the RSDLite version, may be 5.6
Sent from my MotoA953 using xda premium
Click to expand...
Click to collapse
sorry for the mistaken screenshot
I'm back to UK GB with CH Kernel, but dont have screenshot app with me
System Version : 64.1.22.A953.Retail.en.GB
Model Number : MotoA953
Android version : 2.3.4
Baseband version : EPU93_U_00.60.00
Kernel version : 2.6.32.9-g5db7937
[email protected]#1
Build number : MILS2_U6_4.1-22
Are you a 100% sure that you can't downgrade?
Sent from my MotoA953 using xda premium
If by CH GB you are reffering to ROMS such as ms2ginger, blurless and argen2stone, then I can personally confirm that yes you can down grade back to froyo as I have done this several time.
The froyo version I use is Optus AU if it's of any relevance. (there's only one)
I always just use the latest version of RSD lite available, I've only ever ran into that error once. All I remember doing was rebooting and changing the USB slot I used.
Failing that you could try the Linux method of flashing since it's meant to save you when all else fails.
Edit: Just to add, if it were me in your shoes I'd be trying everything to avoid flashing official gingerbread, no way do I wanna get tied down to that beast D:
Even I'm almost 100% sure that CH GB is downgradeable. I have flashed it using RSDLite and then flashed back UK Froyo 2.2.2. (Almost since it was a long time ago )
sahilarora911 said:
Are you a 100% sure that you can't downgrade?
Sent from my MotoA953 using xda premium
Click to expand...
Click to collapse
Yes, with the above configuration (which I think is UK GB ROM with CH GB Kernel), using RSD Lite v.4.9 on Win7 32 Bit PC, I cannot revert back to Official AsiaRet 2.2.2 Froyo (I tried 4times, even right after clean instal using your first instruction on 2nd post).
However I cannot try the UK 2.2.2 Froyo as my RSD Lite cannot recognize it.
I will try to look for a newer / older version of RSD Lite and see if it can somehow recognize the UK sbf and try that again.
DreadPirateDan said:
If by CH GB you are reffering to ROMS such as ms2ginger, blurless and argen2stone, then I can personally confirm that yes you can down grade back to froyo as I have done this several time.
Click to expand...
Click to collapse
no, by CH GB Kernel I meant the SBF, by UK GB ROM I meant Nandroid backup (see post #1)
DreadPirateDan said:
Edit: Just to add, if it were me in your shoes I'd be trying everything to avoid flashing official gingerbread, no way do I wanna get tied down to that beast D:
Click to expand...
Click to collapse
dont blame me for wanting fix on mutitouch bugs
Yeah but what I'm saying is once you put the official one on there is no going back and that kernel has the multi-touch bug.
Now I get what you mean, you have taken the official gingerbread and just gotten the system backup from somewhere, restored that, and are then flashing the CH kernel in RSD lite. Correct?
I hope there isn't something in place that detects whats going on in the system backup then, you could potentially be stuck on it
No. Just read carefully what he written...
1) he flashed chinese GB SBF - which should be downgradeable (even I read that several times there)
2) the he restored nandroid backup (we can't write into /boot right? So he restored /system, but stayed in the Chinese GB kernel, which does not suffer from the multitouch bug...)
3) so he had UK GB /system with Chinese GB kernel (best kernel for M2 as far as I know)
But now he is unable to downgrade back - which is strange, because nandroid should not break e-fuse or something like this (it just restores files onto /system) and Chinese GB SBF should be downgradeable...
Do you get it now?

Hard unlock Sim

I have asked to my telecoms operator the unsimlock code for my Defy, it said is yet unlocked but it is not
I have flash a full sbf 2.3.6. Before it was a 2.3.4.
Motorola can't give any code.
Is there a way to show to the operator that is still locked? Or a non paid way to have the unlock code (it's free with my operator)
I know that is a way to have a soft unock but only with cm7 or miui.
But i prefer a hard unlock for motorola rom.
THX.
Defy+ / 4.5.1-134_DFP-139 / 45.0.1390.MB526.Retail.en.FR
Bouygues telecom fr.
Always complain in a retail center. Take your defy, show him, let him call to services. Be persistent, not rude.
Indeed you could use a softunlock for CM7 or MIUI, don't know if you could for stock.
Thx for the answer. I have try this morning the softunlock with cm7 Nightly ( the only one cm7 i can install) but don't work . I think that the softunlock is only for 2.2.
Could you please try to install the nightly again and then flash the zip from my latest post on that threat?
Edit:
The zip
http://forum.xda-developers.com/attachment.php?attachmentid=908455&d=1329605492
Also you can try to write at russian forum - motofan.ru ( i'm not able to post link there...)
Just write IMEI and your model to them, probably you'll receive unlock code.
If you won't, only way is patch.
labsin said:
Could you please try to install the nightly again and then flash the zip from my latest post on that threat?
Click to expand...
Click to collapse
Thx. i have try but don't work anymore. I have flashed the cm7 zip, then, before reboot, flashed your zip. Trying to change baseband too but don't work.
Hellmanor said:
If you won't, only way is patch.
Click to expand...
Click to collapse
Yes, but for the moment not possible to find any patch for 2.3
Witch CM7 version are you using? Could you attach the files in defy_simlock_originals on your sdcard?
Could do the froyo for bl6 patch it from there and re install cm7
teamwork makes the dream work
labsin said:
Witch CM7 version are you using?
Click to expand...
Click to collapse
cm72-120127.0846-NIGHTLY-Defy+.zip
others don't work because of a 2.3.6 full sbf.
labsin said:
Could you attach the files in defy_simlock_originals on your sdcard?
Click to expand...
Click to collapse
Sorry but i don't understand what you want to say.
Could do the froyo for bl6 patch it from there and re install cm7
Click to expand...
Click to collapse
Do you mean to follow this way below? But i'm afraid this way don't work with Defy+?
Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))
How to Install CM7 after Installing a Full Gingerbread SBF: (!) Ok, first of all do all the steps above on "Installed full Gingerbread SBF and can’t go back to another rom"
Root your Defy (Using SuperOneClick 1.7 and not 1.9).
Install SystemRecovery from GoAPK. If you install 2nd init, you'll just get into a boot loop and have to start over.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM7 .Zip and then gapps zip file. DO NOT wipe again, you'll just go back to 2.2.2 CEE (if you accidentally do this, you can pick up again from step 3).
profit!
Click to expand...
Click to collapse
Yes it works with Defy+ if you are on a bld6 rom (not for the bld7 roms)
My patch from a couple posts back makes a copy of the patched file on your sdcard in the folder defy_simlock_originals. Could you post them here?
Don't know if the module works with the gingerbread kernel. That's why it is a good idea to try to get CM7 with froyo kernel. It's also handy if you wan't to install other roms (WIUI ...)
But could you fist give those files? Maybe i've made a mistake again ^^.
Edit:
Sorry you don't have the right guide. That one is for bld5 downgrade.
Here is for bld6: http://forum.xda-developers.com/showthread.php?t=1486731
labsin said:
My patch from a couple posts back makes a copy of the patched file on your sdcard in the folder defy_simlock_originals.Could you post them here?
Click to expand...
Click to collapse
Again, thank you for your help and time
(I have put .txt for upload)
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
labsin said:
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
Click to expand...
Click to collapse
Ok i'll try tomorrow
labsin said:
The file is similar to the normal defy one as far as I can tell that must have done it... So prob. faullt of different kernel. You could try to downgrade and use CM7 on froyo kernel.
Click to expand...
Click to collapse
I have change the kernel with THIS METHOD
after, try with WIUI 2.2.17: no network; then with update-cm-7.1.0-11-Defy-signed: no network, even when changing baseband.
So, if all that i have made is right, maybe it's not fault of kernel.
Other difference between MB526 and MB525?
You get 'no network' all the time, even with the sim from the right provider, also without the patch?
I think you're the fist to try on a defy+. Maybe look to the Russian fora...
edit: And can you tell me what your Baseband version is? (in settings > about)
edit2: If it is EPU93_U_00.59.01 Try it after installing RC1.5 from here: http://www.defy-cm.net/jordan-cm7.1-RC/
labsin said:
You get 'no network' all the time, even with the sim from the right provider, also without the patch?
I think you're the fist to try on a defy+. Maybe look to the Russian fora...
edit: And can you tell me what your Baseband version is? (in settings > about)
edit2: If it is EPU93_U_00.59.01 Try it after installing RC1.5 from here: http://www.defy-cm.net/jordan-cm7.1-RC/
Click to expand...
Click to collapse
no network only with wrong provider: with the patch no code ask, but no network even with other baseband.
Yes it is EPU93_U_00.59.01 (cm7.2 working on defy+ as well)
with RC1.5 no boot after files install, stuck on google logo.
Now i have flash fix sbf to use 2.3.6 rom because of no battery problems and better battery life. So i'll wait and ask again to my operator.
Now baseband is EPU_U_00.60.03
Do you think if i'm able to put a official operator rom it will see that is no desimlocked? i don't have made backup of my official rom (newbie mistake ) so i have ask here if it's possible with this method.
Blocking by TI OMAP 3630
I have read this:
Blocking the Bootloader by TI OMAP 3630
Why and how is it locked Defy?
While Linux is Open Source Motorola keeps the Defy the locked bootloader. Why?
For commercial reasons of course: avoid too many warranty returns from sorcerer's apprentices who brické their phone, for example (although care is denied you still have to manage the folders!) But also the traders (who manage some of the guaranteed returns, but not that ... we shall see below).
So Motorola maintains bootoader of our favorite phone is not locked and ready to unlock the last views of Roma making the switch to SBF rootage and even more difficult. But the fact how this lock is it made?
Unlike other phones (other brands, but also other brand models *) easy to unlock, the Defy is equipped with a TI OMAP 3630 chip that manages its technology via "M-Shield technology 'in this block. So we did not do a software problem but rather a problem if one CPU is addressing this release.
This technology also manages the simlockage phone which also explains why the operators are far from favorable to the release of Defy.
No one arrived today to crack this lock: it should have the tool from Texas Instruments where he provided to authorized repairers to put the Motorola Defy mode "SE" (Systems Engineering) for this.
* These phones using Qualcomm chips or other, do not bénéfiecient techonologie the M-Shield and are much easier to unlock.
Click to expand...
Click to collapse
(Google trad) Or here in french
stucked at jrdan u97.21.51
I am new at this my defy went dead when tried to upgrade to 2.2 did not have backup. I searched the web and only jrdan u 97.21.51 will work and canot go back or change any more to any other roms. tried the rsd lite to flash diferent roms and nothing works. tried rom manager and 2ndinit recovery and nothing i get black screen. Is there anyway to get out of this? Please help
sion123 said:
I am new at this my defy went dead when tried to upgrade to 2.2 did not have backup. I searched the web and only jrdan u 97.21.51 will work and canot go back or change any more to any other roms. tried the rsd lite to flash diferent roms and nothing works. tried rom manager and 2ndinit recovery and nothing i get black screen. Is there anyway to get out of this? Please help
Click to expand...
Click to collapse
Wrong thread i think.
Have you try a wipe cache and data in stock recovery before rsdlite? see here how to do with Froyo

[Q] Defy (green) stuck on Android 2.1-update 1, want to go to 2.2

I am preparing to move my defy to CM7.2 (or any custom rom) and I am currently stuck on Android 2.1.
I've read and researched everything about flashing and backup and what not... What I understand is:
1. If I flash a full SBF of a Android 2.2.x ROM, I won't be able to downgrade (I don't really need to as I am out of warranty anyways)
2. If I flash a FIXED SBF of 2.2.x or 2.3.x, I will need to also flash a nandroid backup. The problem is that I cannot find a pair of these to download (given all of the mediafire/etc links are now dead).
3. I really need a 2.3.x kernel to go to CM7 or CM9, most (all?) of these won't let me downgrade back to 2.2 (which if fine provided the 2.3.x stock rom I flash is rootable and will let me do wifi tethering).
My defy is green lens US Tmobile with Blur. I would probably be totally happy with a non-blur 2.2 or better rom. My motivation for this is that I need some apps that are 2.2+ :/
Thanks in advance for any help or guidance!!!
KevinAndEarth.com said:
I am preparing to move my defy to CM7.2 (or any custom rom) and I am currently stuck on Android 2.1.
I've read and researched everything about flashing and backup and what not... What I understand is:
1. If I flash a full SBF of a Android 2.2.x ROM, I won't be able to downgrade (I don't really need to as I am out of warranty anyways)
2. If I flash a FIXED SBF of 2.2.x or 2.3.x, I will need to also flash a nandroid backup. The problem is that I cannot find a pair of these to download (given all of the mediafire/etc links are now dead).
3. I really need a 2.3.x kernel to go to CM7 or CM9, most (all?) of these won't let me downgrade back to 2.2 (which if fine provided the 2.3.x stock rom I flash is rootable and will let me do wifi tethering).
My defy is green lens US Tmobile with Blur. I would probably be totally happy with a non-blur 2.2 or better rom. My motivation for this is that I need some apps that are 2.2+ :/
Thanks in advance for any help or guidance!!!
Click to expand...
Click to collapse
Yep what you told is pretty much correct! Just make sure you flash the correct SBFs (since it is greenlens).. And you may request to whoever uploaded to reupload the files.
For point 3.) CM7 and CM9 are available for Froyo kernel too.(And those are more frequently updated) So you can do a 2.2 SBF flash.
Moreover should you flash a fixed SBF you can always downgrade...
Happy flashing
you are awesome at answering my questions again! thanks =)
I now remember that CM7 + 9 can work with the froyo kernel, is there any reason to go to GB? I want to take this step by step... first is to get a working 2.2 version (deblured, since I am out of the country and had problems getting blur to reregister last time).
is there really any reason to go back to 2.1 if I go to 2.2?
i'll go beg on the ROMS thread to see if I can get one. Thanks!
Since you have a green lens (SOC) you should stay on the Froyo kernel. Do not go with the Gingerbread kernel because you won't be able to use your camera (except for the Greenbread mod, if I'm not mistaken, but you should stay away from it since it's a fix for a problem not an improvement).
I don't see any reason to go back to 2.1, especially because 2.2 was officially released and is covered by warranty. Since using ICS I won't even go back to 2.3 .
Trimis de pe Defy CM9
KevinAndEarth.com said:
you are awesome at answering my questions again! thanks =)
I now remember that CM7 + 9 can work with the froyo kernel, is there any reason to go to GB? I want to take this step by step... first is to get a working 2.2 version (deblured, since I am out of the country and had problems getting blur to reregister last time).
is there really any reason to go back to 2.1 if I go to 2.2?
i'll go beg on the ROMS thread to see if I can get one. Thanks!
Click to expand...
Click to collapse
Welcome Good to know I could be of help..
vap_66 said:
Since you have a green lens (SOC) you should stay on the Froyo kernel. Do not go with the Gingerbread kernel because you won't be able to use your camera (except for the Greenbread mod, if I'm not mistaken, but you should stay away from it since it's a fix for a problem not an improvement).
I don't see any reason to go back to 2.1, especially because 2.2 was officially released and is covered by warranty. Since using ICS I won't even go back to 2.3 .
Trimis de pe Defy CM9
Click to expand...
Click to collapse
Ya even I feel the same! Since it is green lens better not go to GB. What is the need when you have so many option of ROMs (just get an awesome CM7 nightly or CM9!)..
So now all I need to do is find a good deblured android 2.2 SBF =)

Newbie in need of help...

First off, thank you all, especially the developers for all the help you're providing and your hard work.
Now, I am a newbie with Android. I've managed to get a running start and flash Blackberries and WM phones in the past...
But it seems like Android is a little bit over my reach... Been reading for 2 days, flashing, installing sbf's and noting pleases me.
My phone is a used Defy, bought with CM9 installed and the camera not working. The previous owner installed the SBF on the defy, and it stopped working as it's said many times. It was a 4.0.4 android version installed, but I was hoping to install the CM10 jelly bean. Bricked it a few times, but managed to reinstall this SBF: DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
Now my Defy is running the stock android version with motoblurr, but the camera still doesn't work, as you expected.
Now, all I want is: If I still can't use the camera(the previous owner said my defy has green lens, no way to know for sure), at least it could do is run Jelly bean version, and if it's possible overclocked and with ICS(or how's that hardware acceleration patch called?).
If anybody has time to walk me through it, I will be more than grateful.
Stuff from about phone that might help:
System version: 45.0.2310.MB526.NonEFIGSRetail.en.EU
Model number: MB526
Android version: 2.3.6
Baseband version: EPU_U_00.60.03
Kernel version: 2.6.32.9-ge281b6e
[email protected] #1
Built number: 4.5.1-134_DFP-231
Hi,
first of all:
the model number mb526 is for the defy+. The Defy got the number mb525.
is the phone rooted? and when, is the cwm (clockworkmod) installed?
when your phone boots up, does the led lights blue?
Sent from my GT-P7500 using XDA Premium HD app
Hello, and thanks for the fast reply.
It is rooted, and I know it's defy mb525.
I had installed sndinit2.3. The led then turned blue. I flashed it afterwards with rds lite and now I dont think I have any recovery mod installed.
As I know, defy+ models only have red lense camera Moduls.
so you flashed a defy+ sbf on a green lens defy. that's why camera doesn't work.
But no problem.
The best way is to download a froyo sbf for the defy at
http://forum.xda-developers.com/showthread.php?t=966537
the Nordic is good for installing custom rooms.
flash the sbf via rdslite.
After that, root the phone, install 2nd init and then you can easily install custom rooms.
Sent from my GT-P7500 using XDA Premium HD app
Well, he flashed his Defy with a Defy+ SBF. So the model number shown in the 'About' option will be MB526 and not MB525. AFAIK, there is no way to make the camera work now.
And he cannot flash froyo SBF as the Defy is flashed with SBF having BL7 and cannot be downgraded.
Sorry, I forgot that a downgrade doesn't work.
In that case, you have to use the custom Roms for the defy+
a good start is, to download a cm7 build defy-cm.net
boot your phone and when the led turnes blue, pressing the volume down key.
you should get into the recovery menu. I wipe data/cache and the install zip from sd (before you have to copy the
downloaded rom on the sd of your phone).
After cm7 is running, go on and download the latest jb rom of quarx. install the same way as cm7.
that's it.
Sent from my GT-P7500 using XDA Premium HD app
marco.michel said:
Sorry, I forgot that a downgrade doesn't work.
In that case, you have to use the custom Roms for the defy+
a good start is, to download a cm7 build defy-cm.net
boot your phone and when the led turnes blue, pressing the volume down key.
you should get into the recovery menu. I wipe data/cache and the install zip from sd (before you have to copy the
downloaded rom on the sd of your phone).
After cm7 is running, go on and download the latest jb rom of quarx. install the same way as cm7.
that's it.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
Well, I kinda did that, but... after I flashed the CM10 jb, the phone starts (the sound of new drive connected in windows led me to believe that), but noting comes up on the defy's screen... restarted...but nothing...
So then I flashed back to the SBF previously mentioned...
Donno if there is a difference between sndinit and CMW...
Should I try it with CMW?
paulielciu said:
Well, I kinda did that, but... after I flashed the CM10 jb, the phone starts (the sound of new drive connected in windows led me to believe that), but noting comes up on the defy's screen... restarted...but nothing...
So then I flashed back to the SBF previously mentioned...
Donno if there is a difference between sndinit and CMW...
Should I try it with CMW?
Click to expand...
Click to collapse
I guess you flashed a ROM intended for Defy (for Froyo kernel, and yours is GB kernel). Try flashing CM10 ROM for Defy+.
andr0idfreak said:
I guess you flashed a ROM intended for Defy (for Froyo kernel, and yours is GB kernel). Try flashing CM10 ROM for Defy+.
Click to expand...
Click to collapse
+1
One the one side, your hardware is a mb525 - defy but on the other side you're firmware an bootloader is a mb526 - defy+.
so you can only use roms for a defy+ - using a rom for the defy causes the error you got.
Sent from my GT-P7500 using XDA Premium HD app
andr0idfreak said:
I guess you flashed a ROM intended for Defy (for Froyo kernel, and yours is GB kernel). Try flashing CM10 ROM for Defy+.
Click to expand...
Click to collapse
The CM7 that's needed to install CM10 should be also for defy+?
Also, don't I have to follow the steps for defy +? Meaning flashing CM9, and then CM10 JB?
Yes, you can flash CM ROMs for Defy+ only, with battery fix as the battery is 1500mah which defy+ has 1700mah.
andr0idfreak said:
Yes, you can flash CM ROMs for Defy+ only, with battery fix as the battery is 1500mah which defy+ has 1700mah.
Click to expand...
Click to collapse
Last question... Should I use CMW or sndinit 2.3? If CMW is the way to go, how do I uninstall the sndinit 2.3 recovery mod or how's it called?
You will have to install 2ndinit to get CWM.
paulielciu said:
The CM7 that's needed to install CM10 should be also for defy+?
Also, don't I have to follow the steps for defy +? Meaning flashing CM9, and then CM10 JB?
Click to expand...
Click to collapse
yes, the CM7 should be also for defy+.
The steps for flashing are the same. But as you have a defy+ now, you need some extra tweaks like battery patch and maybe camera patch. Some of them are included in the actual roms. battery patch is needed because of the different types of battery between defy and defy+.
Sent from my GT-P7500 using XDA Premium HD app
Thank you guys. I managed to update my Defy to 4.1.1 JB. At least it's running the latest version of android.
Now I'll try to overclock it... Hope I don't brick it...
paulielciu said:
Thank you guys. I managed to update my Defy to 4.1.1 JB. At least it's running the latest version of android.
Now I'll try to overclock it... Hope I don't brick it...
Click to expand...
Click to collapse
Its already overclocked to 1Ghz
Sent from my MB525 using xda app-developers app
ppero196 said:
Its already overclocked to 1Ghz
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
Yeah, but I tweaked a little bit the voltage, as my battery is a little bit dry...
paulielciu said:
Yeah, but I tweaked a little bit the voltage, as my battery is a little bit dry...
Click to expand...
Click to collapse
For vsels there is this app
http://forum.xda-developers.com/showthread.php?t=1815142
Sent from my MB525 using xda app-developers app
Back again here.
Question as usual.
Is there any chance I can downgrade if I take my defy to a service? Can they do it with some cool toys?
Just reflash your stock SBF using RSDLite and it will be back to how it was when you bought it.

Categories

Resources