{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About this guide
In this guide you will find all the information regarding the Motorola Defy. I’ll try to explain as best as I can how this phone works, how to root, install SBFs, and most important: how this stuff actually works so you don’t screw up your phone installing incorrect versions of Roms.
I’ll try to cover the eFuse system found in this phone as well as other Moto phones and how it actually works, this is fundamental to understand why you can’t go back to old stock Roms once updated.
**NOTE** I AM NOT responsible for any kind of damage your phone can suffer**NOTE**
Index
I just bought a Defy, now what?!
Red, Green, Plus. What can I and can not do
Facts
Custom Recovery
eFuse
SBFs
Fixed SBFs
CG Versions
Official SBFs
RSD Lite
Rooting
How to flash
CM7, MIUI, Various Custom Roms and going back to Stock
Common Problems
I just bought a Defy, now what?!
Congratulations on your new phone! Now you need to know what kind of Defy you have!
If you've got a Defy+ then this part doesn’t apply to you, so you can jump to the next one. If not, keep reading.
If you got a new Defy, you could have a SOC or Bayer Defy, the difference between both Defy's is pretty much only the Camera Module, there is really no other difference.
At first it was easy to determine which Defy model you had by just checking the Lens color, RED color meant Bayer module, Green Lens meant SOC Defy; sadly it's not so easy to know which one you have now, since there are SOC Defys with Red Lenses.
The Camera Module is the responsible for receiving the "information" from the lens and then translating that into machine data.
The Bayer module is capable of 720p video Recording and can take better pictures than the SOC module. At the moment is not known if the SOC module is actually capable of making 720p Recordings or if it is just a Driver issue; but for the time being there is no 720p recording for SOC Module.
Almost all SOC Defys will have a Green lens; therefore you will find almost all ROM threads labeled compatible or not compatible with Green Lens. Usually a different installation or a patch is needed to make these roms work on Green Defys.
The are a few ways to check which Module your Defy has, the best one and more accurate one though, is installing Catlog, starting it up and then start the camera. After starting the camera, go back to Catlog app, pause the logging, and search for "camera". There should be a couple entries, one of them should say either SOC or Bayer.
Red, Green, Plus. What can I and cannot do
With the 3 versions on the market, there is some extra caution to be taken.
Green Defy users have to be careful when installing custom Roms since it may not be compatible without doing extra steps like patching or installing extra files. Defy+ must be very careful to what they flash on the phone.
As of today there is no a full SBF** for the Defy+ (found here).
This full SBF is a new CG Version**, with Android 2.3.6. You wont be able to go back to your Stock Defy+ Rom, but at least you wont kill it if something goes wrong.
Most of this Guide is made only for the Defy, either Green or Red lens, and although the Defy+ is pretty much a Red lens Defy, a few things are NOT made for Defy+ users:
CM7, MIUI, Various Custom Roms and going back to Stock***
Common Problems*
Stuff in this list should be read even for Defy+ owners, but they cannot be applied yet to the Defy+s.
*Not all of them apply to the Defy+
**explained later in the Guide.
*** You CAN install CM7 and other Android Versions, the basics explained on this guide just do not apply to Defy+, as well as Downgrade to Stock.Facts
So, let’s start doing a small sum up of what this phone can do.
At first the Defy was presented as a low /med end phone. With 800 MHz CPU, no GPU, 2 Points hardware limited screen. It is well known nowadays that the Defy actually has a PowerVR 530 GPU, TI OMAP 3630 CPU and a screen supporting 10 Point multitouch.
The Defy+ is basically a rebranded Defy, with Gingerbread, 1700mah Battery (instead of 1540mah) and its default CPU speed is 1GHz. It has the same internals as the original: Same CPU/GPU, Memory, Screen and so on.
Defy+ comes always with a Bayer camera module, and so far there are no Defy+ variations.
LOCKED Bootloader, what does this means?
For some people is hell, for others (normally non advanced users) is a pretty cool insurance for their phone. This locked Bootloader thing means there is no (so far) way to rewrite the Stock Bootloader or the Stock Recovery.
When the phone turns on the Bootloader basically starts all the hardware and make your phone come alive.
Then we have the Stock Recovery, this little part of your phone is also locked and cannot be removed or changed from your phone, it will allow you to make Recovery stuff like Full Wipe (Data and Cache) and install Update.zip files.
At first this became a problem, because with a locked Bootloader there is no way to install a Custom Recovery like ClockworkMod or install a new Rom.
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Thanks to this locked Bootloader, is really, really hard to Brick your Defy. Most of the issues seen on the Forums are NOT Bricks, just incorrectly flashed SBFs (more on this later ). With brick one mean the phone has no access to the Bootloader or can’t initialize its hardware, requiring you to use a JTAG to directly reprogram the phone (which I’m not sure is possible on the Defy).
Custom Recovery
A custom recovery is a special "App"** that comes in a separate partition in your phone. This "App"** allows Android Phones to do recovery tasks, like deleting data, installing recovery Zips and so on; The tasks you are allowed to do with Stock Recovery are pretty basic. Here is where Clockwork Mod comes into play.
CWM is a Recovery that allows you to not only do basic tasks but also create Nandroid Backups, Restore Them, Fix Permissions and quite a lot of other useful stuff.
Normally a Custom Recovery is installed by flashing the Recovery Partition in your Android Phone with a Custom Image, but since our Defy comes with a Locked Bootloader, this is not possible. Leaving us without many options to proceed.
And that's why we have 2nd Init, this application is what actually installs CWM in the Defy, it does it by installing it in your internal memory and not in your Recovery Partition and then pointing the Android system to it right after the Stock Recovery boots.
**Is not actually an App, is more like a Linux Console with UI so you can recover.eFuse
Here comes a really important part on how the flashing works and why is problematic for some people, it is not explained anywhere.
It actually took me more than a month before I started modifying my Defy because this information is really scattered around the web and I don’t like to do things I do not understand
So, to the eFuses; this Technology was developed by IBM, is a really cool tech that allows some chips to actually change their internal wiring, and reprogram themselves.
How is this used on the Defy (and the Droid too)?
Well, see this system as a bridge, each time you flash a new update to your phone you burn a bridge, the information went to the other side, but there is no coming back.
Here comes most of the issues we have with the Defy, once you update to a higher version of your Android, there is no way to come back. (There are some tricks, explained later).
This lead us to the next part of the Guide, where I will explain you WHY you can’t go back and how this actually works.SBFs
SBF is how Motorola packs all the information to be Flashed on your phone. Inside this package are a lot of other files, each of these files named with CGXX where XX is a number.
So when you Flash a Full SBF, it takes the phone memory, format it, create the partitions and then copy the information inside these partitions. Each partition corresponds to a CGXX file. Here is where the eFuse thing kicks in.
There are a couple of CG files containing the version number of the Android you are flashing. So let’s say you are on Éclair Stock, first version, no updates no nothing. This version has a Version 1 number. When the phone gets updated, this version changes to Version 2 for example.
Each Android version has each own ID, once you go up, you CAN NOT go back, and this version is in CG31 AND CG39 files inside the SBF.
FIXED SBFs
Is a modified SBF without the CG31 and CG39 files, thus allowing to move between Android Versions freely.
Since the Fixed SBF creates all partitions but /System (CG39) and CDT (CG31), we need to copy System data using a Nandroid Backup or the phone will probably not work using the existing /System.
Nandroid Backup
This is just a .zip file flasheable with a Custom Recovery, this will Delete/Copy all the files in the /System and other partitions (depending on the Nandroid) without formatting or remaking the partition thus not modifying the system layout, eFuse or stuff; this is almost harmless, meaning you CANT brick your phone doing it, though you can make Android not boot and a new SBF or Nandroid would need to be installed.
CG Versions
With that explained let’s get to business with versions:
CG Version 2: SBF 2.21 / 2.34 / Chinese (Éclair) (Defy)
CG Version 3: SBF 2.51 (Éclair) (Defy)
CG Version 4: SBF 3.4.2 (Froyo) (Defy)
CG Version 5: SBF 4.5.0 / 4.5.1 (Gingerbread) (Defy)
CG Version 6: SBF 4.5.1 (Gingerbread, 2.3.5, (Red lens Defy/Defy+) )
CG Version 7: SBF 4.5.1 (Latests Gingerbreads, 2.3.6, (Red lens Defy/Defy+) )
If you try to flash a lower ID version than the one already on your phone, you will just get a Black screen after booting or a screen telling you to flash an official rom.
So, with this in mind, you can now hop between Android versions without screwing up your phone.
If you have an Éclair Defy and would like to keep the ability to downgrade to it, you should ONLY install FIXED SBFs of the Android Version you want to install, and then use the corresponding Nandroid Backup for that Fixed SBF.
For a full list of Roms and their respective CGs go here
Official SBFs
Here is a list of all the Defy Official SBFs and Defy+ Official SBFs that means that they come with ALL CGs, these SBFs put your phone like Motorola sold it to you, just need to keep in mind that going UP in versions with FULL SBFS <WONT> I repeat, <WONT> allow you to go back to an older version.
Knowing this you should be able to test every single Android version out there and being able to go to Stock without issues. Just be sure to understand how CG versioning works and you should be fine.
RSD Lite
RSD Lite is an App used by Motorola to Flash Smartphones. It can revive mismatched Nandroid/Fixed SBFs, Black Screens, failed flashes etc.
Even though is really, really hard to completely brick a Defy, it is possible; a corrupted SBF, power failure on a critical part of the formatting, or some weird issues while creating partitions can lead to a Bricked Defy. If you can, always flash your Defy from a laptop so the power is not an issue, use good cables, and be sure the PC doesn’t go to sleep when is not being used.
Also, when flashing SBFs, is normally advised to put your SBF in your PC Root directory (C:/ ) or whatever it is in your PC and rename it to a short name like Defy.sbf, why? Because sometimes the Path name is just too long and RSD Lite throws errors not allowing the phone to be Flashed.
Rooting
So, what’s rooting and why everyone talks about it.
Phones come “locked” , this means users can only do basic usage of their phones, installing/uninstalling apps, wallpapers and basic stuff. You can see but not touch any System file, or change the actual behavior of Android. Rooting just means you have access to your phone like an Adinistrator, meaning you can access and change system files, delete/create files and folders and so on.
To be able to install Apps like 2nd Init that need to access Android System files your phone needs to be able to write and acess these files.
Thankfully, rooting the Defy is a rather simply and usually harmless task.
How to Root: (NOT for BL7)
Get SuperOneClickRoot
Get and Install Motorola [Drivers ]
Reboot your PC
Turn USB Debugging ON (Settings -> Applications -> Development on your Defy)
Connect your Defy to the PC
Wait for the PC to install any missing Drivers
Click on Root
Let it work, then it will ask if you want to install BusyBox, hit YES
After it finished it will ask to make a test, click cancel and just Reboot your Defy
Done, Defy rooted
How to Root BL7:
Enter Recovery, Wipe Data/Cache
Download this SBF and Flash it
Enter Recovery, Wipe Data/Cache
Download Part1 and Part2 SBF and Flash it
Enter Recovery, Wipe Data/Cache
Recommended ->> New Method to root the Defy: (Thanks TJKV for the tip):
Now there is one method for rooting all Defy and Defy+ devices irrespective of CG signature versions, simply use the Framaroot app to root:
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
How to Flash
Ok! Now that we understand how a lot of stuff works, it’s rather easy to get a new Android version installed on your phone.
For any full SBF the same steps must be always done, just be sure to know what SBF are you flashing and keep always in mind your CG Version to keep the possibility to downgrade in case you need your warranty.
Requirements
Get the SBF you want to flash
- Full SBF: No Nandroid backup needed, always keep CG versioning in mind.
- Fixed SBF: You might need a matching Nandroid Backup.
Get and Install RSD Lite v4.9: There are reports of other versions working, but this one is what I have used.
Get and Install Motorola [Drivers ]
Now to Business:
To Flash full SBFs, here is the standard procedure:
Open RSD Lite: Click on [ … ] Button and select your .SBF (Remember to rename to a short name and put it on root of your PC) and click Open.
Boot your phone into Bootloader Mode (check last section if you don’t know how to do it).
Now connect your Defy to your PC
The START button on RSD Lite should be available now, click and wait.
For Fixed SBFs a slightly different method is needed, it's basically the same but you need to Wipe Dalvik Cache and Data before flashing. Then after flashing you need to enter immediately to Recovery and restore the matching Nandroid Backup. I won’t write a specific way to do it here, since most of these versions require different steps (for Example CM7 or MIUI), so is better to check a specific guide for your Custom ROM or Android version.
CM7, MIUI, Various Custom Roms and going back to Stock.
Now, if you want to go to CM7 or MIUI Roms, there are good tutorials on how to do it. I will just explain here how the procedure works so you know what you are doing and not only follow step 1, 2 and 3, which usually leads to issues if anything goes not exactly as written.
There is no way to flash a full SBF with CM7 or another rom. What is being done in these cases, is just use a base Android, be it CEE, Localized EU, Éclair, whatever.
Quarx recommends using JRDNEM_U3_3.4.3-11_BLUR_SIGN (not anymore, old) 3.4.2-179 CEE Deblur SBF. But this is not NEEDED; I’m running CM7 with German 3.4.2.177-3 and is running perfectly.
Then, restore a Nandroid Backup of a CM7; it will copy all the new stuff into your partitions and won’t remake them, keeping all the signatures, security and stuff intact.
Here is a good Guide to install CM7: How to Flash CM7
To downgrade from any of these Roms all you need to do is install a Full Stock SBF (remember to check CG Versions!) and done, phone back to Stock.
There is another way to install a lower version of Android without using a full SBF, and it is installing a Fixed SBF of a lower Android version, then restoring its matched Nandroid Backup.
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:
Method 1:
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 << File is Back, thanks Ichibanme again!>>
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.
**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))[
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Download this SBF and Flash it.
Root your phone.
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery.
Reboot to CMW recovery, and wipe Data/Cache.
Install CM7 then install Google Apps.
Reboot an go into Stock Recovery (using the vol- button, not from Bootmenu).
Do a Data/Cache Wipe or you won't have any space when you're done.
Flash this Fixed SBF
Reboot into your nice new rom.
Do not Wipe Data anymore or you will have to start again.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
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!
Thanks jebrew for the info.
I installed a Full SBF/installed CM7/other Android version and need my warranty: (!) Ok, this pretty much depends what have you installed and on which zone you are. Try to keep ALWAYS your phone ability to downgrade to whatever version is supported in your region.
For example I have a German Defy, we have SBF 3.4.2 (Froyo) officially deployed, this means all I need to do to go back to Stock and claim my warranty is download the Stock 3.4.2.177-3 version and Flash the full SBF. If your zone only has Éclair officially deployed then you should never ever flash Full SBFs with anything higher than Éclair, only Fixed SBFs, then in case you need your warranty, just Flash your zone full SBF and done, back to Stock and hi2u Warranty.
Full Stock SBFs will put your phone to the state Motorola sells that Android Version. If you install the same SBF you had, it will be like new.
How do I enter Recovery Mode?!: With the Phone off press VOLUME DOWN then, while still pressed, power up the phone and leave VOL key pressed until you see a Yellow triangle, once you see this you are in Recovery now press Vol Up and Vol Down at the same time (if you are in Froyo) and the menu will appear, if you are on Éclair the menu should appear without having to press anything.
How do I enter Bootloader Mode: With the Phone off press VOLUME UP, then while still pressed power up the phone. Keep the Vol key pressed until a black screen with some white letters appear. This is the Bootloader.
After Upgrading to Froyo my Defy is laggy, slow or reboots: (!) This is a common issue when coming from Eclair to Froyo. If this happens to you, just do a full wipe (Delete Data/Delete Cache on Stock Recovery), after that your phone should work correctly.
Stock Froyo sometimes lags and/or freezes the phone: (!) Its caused by the VM consuming all memory, all you need to do is adjust the amount of MB the VM should leave free.
There are a few ways to do it:
Use a terminal emulator, or use GScript Lite to run this:
Code:
su;
vm.min_free_kbytes=8192;
(Not permanent, need to be ran every time you reboot)
Get Sysctl and change vm.min_free_kbytes to 8192.
Get SetVSel and tap on increase vm.min_free_kbytes to 4096.
How do I make/restore these Nandroid Backups everyone is talking about?: Nandroid backups are made using Clockworkmod (CWM). Enter the Custom Recovery, go to Backup and Restore and create your Backup. To restore use the same method but Restore instead of Backup
I downgraded from CM7 to Stock / Installed a new SBF but I'm having bootlops: (!) If this is happening to you, after flashing the Stock SBF, enter in Stock Recovery and do a full wipe (Data/Cache) and reboot.
I have issues with my Battery Readings / Battery charge suddenly Drops: This issue is caused by a cheap battery reading implementation. If you want to know more about it, and how to get more accurate readings on your Defy, please go to: Defy Battery Drops Explained. Thanks jusid for the detailed explanation!
(!) NOT for Defy+
If you find this Guide useful, please remember to click the Thanks button
Thank you for putting all this useful information together. It should be made sticky .
Wish I would've found this post three days ago. But you learn from trial and error. Made alot of errors but looking good now.
Sent from my MB525 using XDA App
This made a very good read thanks for compiling all this information.
djc
great guide,i agree it should be "sticky".
yeah, it definitely needs to be a sticky, would make a lot of defy newbies' life easier
Thanks!!! (button pressed)
Sticky +1
Great Guide, wish it would have been around when I decided to flash my Defy. Sure it will help those is the future. Thanks for taking the time to put all this information is one place.
I to would say +1 for Sticky
This's the great work,
it's easier for the beginner
Thanks
Nice to see people has found usefull my Guide, would be awesome if it became Sticky ><
If you have suggestions, more important information to add, send me a PM and I'll fit the info in there.
Sorry I didn't post it before hehe, took me like 5 days to write everything and make it as simply and understandeable as possible.
Awesome post man!!
If any post deserves to be a sticky,this is it!!
Cheers..
great work.
cg39.smg version 5 for > Gingerbread 4.5.1-128
walter79 said:
great work.
cg39.smg version 5 for > Gingerbread 4.5.1-128
Click to expand...
Click to collapse
Good thanks, added that and the other 4.5.0 as CG version 5.
Corrected some typos and grammar issues I found.
Zephyrot, you made my life way more easier!
A million thanks to you. (xda lets me thank just a post once )
This is awesome, especially for people like me who are fairly new to Android. After spending some time with this thread I may get the courage to try a new rom.
Thank you!
Here's a Q:
Do the various Android 2.2 versions all have a version number of 4?
(I am asking because I am on Froyo 3.4.2-145, and am wondering if I can flash a full Nordic sbf and will be able to go back to my own official Froyo.)
juried said:
Here's a Q:
Do the various Android 2.2 versions all have a version number of 4?
(I am asking because I am on Froyo 3.4.2-145, and am wondering if I can flash a full Nordic sbf and will be able to go back to my own official Froyo.)
Click to expand...
Click to collapse
Yeah, all SBFs 3.4.2 have the same CG version. The ending number, in this case -145 is just for the zone/language it is released.
What I'm not sure is if the 3.4.3 version has a different CG, I <think> they have the same version, and only changes once updated to Gingerbread, but I don't know how to check it out.
In your case there is no issue, since Nordic is 3.4.2-177 and your base -145, same CG
Edit: Searching around the web I found out all 3.4.X should have the same CG version, if anyone can confirm this to add it to the guide would be awesome
Maybe I can get a confirmation for my answer.
I use JRDNEM_U3_3.4.2_179-002_DEBLUR_CEE official rom for basic (with official update).
Does my Defy lack any part of CM7 if I flash directly the latest nightly on it (leave out rc1v2)????
And if lacks than what part(s) is(are) that(those)????
Kernel is the same in this official and rc1v2 too, so I can't find a part that needs from rc version to be up-to-date with CM7 on Defy. I think official rom above and latest nightly is enough, but if not please someone tell me the missing part(s).
Thanks
Thanks for this info, its very helpful for those who are learning... like me
Really well put together. Invaluable to any Defy owners wanting to flash.
Related
Hi,
Newbie here and I realize that this might have been discussed before somewhere but I hope that some of you experience users will be kind enough to guide me anyway.
OK, I've done quite some reading here and recently decided to go ahead and root my ME525 [came stock with Chinese Froyo firmware build: JDGC_1.11.0 Kernel: 2.6.32.9] and that went well. I also installed Titanium backup (TB) and did full and user app only backups. Yesterday, I installed ClockWorkMod (CWM) recovery and I did a full backup (without factory reset).
So, before I factory reset and do another recovery backup [and then try other ROMs] , I would like to know these one or two things:
- Whenever I will need to restore my stuff, is it preferable to recover to a bare backup (i.e.: the backup I will do after factory reset)? or is it jus fine to recover my backup including my apps/settings?
- If the second option of the first question is fine, then what is (or is there) any point of also restoring a full Titanium backup (or user files only - please specify) since everything should have been restored from CWM right?
- What is the deal with with having to flash a "boot_only.sbf" after a change of ROM? Is this (always?) needed after (RSD) flashing a stock sbf file? and would this be needed after just doing a CWM recovery?
I'm asking all this because I don't know where to find the exact sbf files for my Chinese phone...the Chinese Froyo 'stock' file I found had CPU set at 1GHz and that is clearly a sign that this is not 'stock' since mine came in at 800MHz... Others, have already altered the sbf to match US carriers or what not..
So last question: if things go wrong, can I flash that slightly different 'stock' [droid2.2.zip] sbf file anyway, flash the boot_only (needed?) and then just use clockworkmod (and/or TB??) to get back to my stock state or current state?
I know, this is basic stuff and had been covered many times. But not having an official (and exactly same) stock sbf file worries me a little... I don't want to lose my wifi, camera flash or who knows what... and there are all those issues with firmwares incompatibilities or undowngradability...
I just want to cover my butt in case I have to get Motorola service one day (warranty repair...) since I beleive that unroot is (a bit complicated) but possible...
Anyway, sorry for long post and thanks in advance for your help on all this.
http://u.115.com/file/f38db7bb8a
0.26.0 CN froyo
http://u.115.com/file/t355594b48
1.11.0 CN froyo
Hello,
I plan to upgrade my Australian (Telstra) Motorola Defy to an Android 2.2 (Froyo) ROM that is ideally without Motoblur.
I have comprehensively read hundblues of the Defy modding threads through Search, Browsing and Cross-Links on XDA, however there are still a few areas I am still unsure about and feel the need to ask.
I absolutely require downgrade-ability back to the Telstra stock firmware (A variant of 2.21), Because if I become affected by the Speaker issue, then I will need to restore to stock for Warranty.
I am also conscious of using the Chinese 2.2 ROM due to risk of blowing the Camera Flash LED.
Maintaining Downgrade-ability
Higgsy has made a thread how to upgrade to 2.2 (Froyo) without losing downgrade-ability, but I am not clear on a few points, my comments are in blue
Instructions in the thread:
"Follow the process below, This works with the TMobile US and The GB 3.4.2 Firmwares.
It may seem long winded, but it is the only way to get it running with everything working ok and still downgradable/able to flash other .sbf, most notably the cam flash working 100% - fully sync'd and no greeny blue tinge to it.
Need the Chinese 2.2 release – Download Here [http://www.sorensiim.dk/higgsy/.sbf/2.2CN_SBF.zip] Is this the unmodified Chinese 2.2 ROM?
Need the system.img nandroid and boot/devtree.sbf – Download here [http://www.sorensiim.dk/higgsy/TMOB_US_3.42_Files.rar] This must be the "Tmob 3.42 system image(pre rooted)"
Also now added the GB system image+md5 - the one that racca added in the original thread. Download hear [http://www.sorensiim.dk/higgsy/GB_3.4.2_system.img.rar]
• Flash the Chinese .sbf by RSD lite OK I understand that the Chinese 2.2 ROM is downgrade-able, makes sense so far
• Once booted root via superoneclick http://bit.ly/gUzV19 then reboot (make site debugging on)
• Install Clockworkmod recovery app http://bit.ly/dOdhKc , open app, install recovery and then boot into recovery (make sure debugging is off whenever you boot into recovery
• Wipe data/cache in recovery
• Flash the Tmob 3.42 system image(pre rooted) via advanced restore (folder need to be put in goapkrev/backup folder) What makes this 3.4.2 ROM different from the others in that it is still downgrade-able?
• Once restoblue pull battery, put battery back in while holding up to get into bootloader
• Flash the boot/devtree.sbf once its rebooted after this you are done. See below about Camera Flash LED issue
If you want to use the GB release then just restore the system.img from the GB release. Similar to the T-Mobile 3.4.2 ROM, what makes this UK 3.4.2 ROM downgrade-able?
"
If there has been a modification done to the T-Mobile / UK 3.4.2 images provided which makes them downgrade-able, what is it?
Can it can be applied to other 3.4.2 ROMs too (eg: Finland 3.4.2 155-002 which is Blurless).
Based on Which SBF code group prevents downgrade, I am guessing that the CDT(CG31) has been removed from the image (to keep CDT on version 2), but I'm also guessing that this would also screw up SYSTEM (CG39) because that would also need to stay on version 2, when 3.4.2 uses (and needs to be?) version 4 (or else it will screw up the signature?).
Preventing the Camera Flash LED from blowing when the Chinese 2.2 ROM has been used
I seem to have found two theories on this one:
1. Higgsy's 'Devtree' theory (see thread above) that the Devtree in the Chinese 2.2 ROM is causing the issue, and a Devtree copied out of a different ROM should be used. (This leads to more questions: What is the Devtree? Where is it located? How is the Devtree copied out of a ROM? I can't find any information about Devtrees)
There is a followup post in this thread in reference to the Devtree theory which says "I am now having the green light problem after flashing the "flash fix" several weeks ago, can I get the normal flash back using this method?"
I am not sure if this users's reference to the "flash fix" is referring to the 'Devtree' fix or if it was another "flash fix" that they tried. Nor do I know if the user followed the instructions for this "flash fix" correctly, but it is casting some doubt if the Devtree fix is correct or not?
Also in the instructions above, if the T-Mobile or UK 3.4.2 image is flashed after the Chinese 2.2 ROM was installed, wouldn't the non-Chinese Devtree already have been installed?
2. 'build.prop' theory
The post reads:
"I was going through build.prop for some thing else and noticed these settings on my 3.4.2-145 build.
ro.media.capture.flashIntensity=41
ro.media.capture.torchIntensity=25
What are these set to for the Chinese ROM?"
There are no followup posts to this to confirm the values of the Chinese ROM, to confirm that this prevents Camera Flash LED burnout, or to confirm that this doesn't work.
Or use the downgradable method I list in my post (http://forum.xda-developers.com/showthread.php?t=977989).
That way you dont have to flash any chinese firmware and worry about camera/flash issues.
Your ROM seems to be just what I am looking for. I want to be as close to the Stock Android Experience as possible (I've tried Motoblur and it's not for me) and without the bloat.
I have a few questions about the process that Barebones uses, because I think that it's important to learn what I'm actually doing.
"2. Restore your Froyo Nandroid of choice.
Barebones: CEE3.4.2_155-002_DEBLUR.Nandroid.zip"
I guessing that this contains ONLY the SYSTEM partition, which has been taken from the unmodified CEE 3.4.2-155-002 Deblur ROM, as the SBF method would change the version making it un-downgradeable?
"Flash the fixed sbf.
Barebones: Fixed.CEE.3.4.2_155-002_DEBLUR.zip"
I guessing that this "fixed" version contains unmodified CEE 3.4.2-155-002 Deblur partitions PDS, LBL, MISC, BOOT, CACHE, USERDATA & KPANIC, but not CDT (To allow downgrade), SYSTEM (To allow downgrade, it has already been installed at Step 2 instead?) and RECOVERY (To retain Clockwork Recovery)?
"5. Reboot into Froyo; install Clockwork Recovery; copy Barbones to sdcard.
Barebones: Barebones_12-signed.zip"This must be the bit where all the modifications of Barebones itself are made? And hasn't Clockwork Recovery already been installed to the RECOVERY partition from Step 1 or does Clockwork have elements that need to be reinstalled? (eg: in the BOOT/SYSTEM/USERDATA partitions)
"Swype, Gtalk, Voice Commands, GreekIME, CarDock, Recovery, and Easy Installer -> Download update.zip"With the Extras package, can these components be installed separately or are they all installed together? Some of these extras may not be applicable like GreekIME (If the user is not Greek).
Is the Swype in the package the same as the latest Beta from beta.swype.com and isn't Clockwork Recovery supposed to be already installed?
Also, is there a way to reinstall some of the 'Removed' APKs like BlurAlarmClock, Calculator, ClockWidget, DLNA, Quickoffice, WeatherWidget (assuming that these APKs will still work on their own) or will I need to copy them before installing Barebones_12-signed.zip
Finally, you have done a great job so far and it is far better than anything else out there for the Defy at the moment, thank you.
My only bit of [constructive] criticism (and I am by no means ungrateful) is that I think that some of the Added & Value Added features of Barebones (especially the Wallpapers and Sounds) would be more suited to the Extras package (as optionals) to keep in line with the goal rather than being bundled in the Barebones package.
Barebones faqs. . .
Why its downgradable ?
This works is because the fixed sbf has partitions taken out; specifically CG31 (CDT) and CG39 (System). Reason being these are the parts of the sbf that prevent you from downgrading. So, this lets you make up the rest of a 'whole' rom using the nandroid; and bingo Froyo with downgrade.
Barebones.zip ?
Unlike some of the other roms posted here, which are nandroids, this one is based on an update-script. Meaning it just changes a stock rom into Barebones; does not restore a complete system. So a factory reset is not enough.
Why install clockwork a few times ?
Nandroid doesnt come with the app, my rom doesnt come with it; yes clockwork is installed just not the apk, so you need that to boot into recovery. Reason why, defy bootloader is locked - so recovery has to be initiated from within the android os, hence bootstrap.
Update.zip ?
If you read the build info it states that it copies all the extras to the sdcard. While Easy Installer is the only program in that update that get installed automatically. Point being you use it to install whatever you feel is missing and delete the rest.
Other apk's not in update.zip ?
Not my problem, I cant please everyone; and I'm not going to make update.zip's with every apk under the sun. The update.zip is already half the size of my rom, so . . . Barebones ? Maybe use adb to pull /system/app after you restore the nandroid and before Barebones. You could then copy them back to the /system/app folder after Barebones is installed. If you try to install the apk's before Barebones they will be erased by my update-script. To be honest I probably didnt include most of these apk's because they must be installed to the /system/app folder (eg: MediaGallery, BlurAlarmClock). They just wont install to /data/app.
But its not Barebones . . . .*tear
OK I get it guys, my 380kb of extra noise's offends, so wait for v1.3 if its too much. This is my first android phone, I got it in December; I learned to cook this rom in that time (so google and read). So lets face it, I make this rom for my phone; just sometimes other people like it too.
Hope this clears up a few things . . . and enjoy the rom.
I am following this forum closely since few months, and think I should do more with with my Defy now! I have already rooted my phone but I am still on stock Eclair. I really, really want to try CM7 but though I am quite tech-savvy, there are some things which I am still unable to get into my head! So I need someone to help me, in plain English, with the following:
1 If I install CM7, or any ROM, and then decide to go back to stock, can I?
2. I guess I can using a nandroid backup, right? BTW, what is nandroid backup?!
3. AFAIK, nandroid backs up the current ROM so that if things go wrong it can be reverted, right? If yes, how to perform a nandroid backup on Defy? How easy is it? How much of space does it take in the SD card?
4. What is sbf, recovery etc.? Why are they needed? What are the specific versions I need based on my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Offtopic:
5. If I perform a 'Factory Reset', will I lose root?
Please help me understand all these; from what I have read so far everything seems so confusing!!
1. CM7 requires Froyo(2.2) based SBF in order to install. So you must be on official Froyo(released via your phone over OTA by your network) or have flashed Froyo. Once you FLash or upgrade your phone through either of these methods, you cannot downgrade back to 2.1. In the case of official it is not problem, and because official 2.2 is being rolled out, you can probably safely upgrade by flashing one of the stable official SBF's from any of the versions offered on the forums, you probably want to look for ROM users from your country to get an idea if the SBF the ROM is based on works in your region without much hassle.
2. Others will need to answer the Nandroid thing, I know as much as I use Nandroids to make a back up of MY phones state as a way to go back to how my phone was prior to me messing with it, but I am not clear on how you can use a Nandroid from another persons phone on your own. I always just flashed the latest SBF that was Deblured. I am currently using the most recent "Nordic" SBF and CM7, I flashed the SBF and installed the CM7 zip file from recovery.
3. See #2
4. SBF as far as I know is the actual firmware that the phone uses, this set of code tells the phone what does what when it comes to the phones hardware. The files have a base Android on them that they work from which can be with Blur or without Blur(Motorolas GUI shell for Android). So some SBF's come with 2.1, some with 2.2 and soon 2.3.
The Android version is the software side of things, and this can vary depending on how the ROM you are using is made(I think) This is why your SBF will have different numbers associated with it(because these SBF's vary from carrier to carrier and from country to country, some have Blur, some do not, some are set up for particular GSM ranges for 3G etc) and your Android will have a separate number.
It is a bit confusing and my knowledge is kind of limited so I may in fact me kind of mixed up on some of these things. Take what I say with a grain of salt.
Recovery is a small app that allows you to use a custom recovery(which is not included with Motorola phones) which is a method to insall ROMs. You need to root and install recovery to start making real changes to your phone.
Hope some of this information helps, I have bricked my phone quite a few times learning how to modify it and I would suggest going ahead and trying things and making a few mistakes so you know how to unfuck your gear as some of the kind contributors have mentioned before.
Fear not, go forth and flash that little bugger to it's full potential.
abhi.eternal said:
I am following this forum closely since few months, and think I should do more with with my Defy now! I have already rooted my phone but I am still on stock Eclair. I really, really want to try CM7 but though I am quite tech-savvy, there are some things which I am still unable to get into my head! So I need someone to help me, in plain English, with the following:
1 If I install CM7, or any ROM, and then decide to go back to stock, can I?
2. I guess I can using a nandroid backup, right? BTW, what is nandroid backup?!
3. AFAIK, nandroid backs up the current ROM so that if things go wrong it can be reverted, right? If yes, how to perform a nandroid backup on Defy? How easy is it? How much of space does it take in the SD card?
4. What is sbf, recovery etc.? Why are they needed? What are the specific versions I need based on my phone:
Offtopic:
5. If I perform a 'Factory Reset', will I lose root?
Please help me understand all these; from what I have read so far everything seems so confusing!!
Click to expand...
Click to collapse
i'm new too but not new to Android...
1. Yes. And you can downgrade to 2.1 again. I did!
2. The clue is in the name, all your phones current data, apps and rom are stored on the nand memory within your Defy. The Nandroid backup takes a snapshot of all this data and stores the information from each partition on your sdcard.
3. Nandroid backup is easy. I recommend the 2nd init auto installer...that also installs recovery (custom) and is needed for cm7. Backups vary in size...mine are usually around 450mb.
4. SBF's are just official rom files, in a format readable/flashable with RSD Lite. You are on the same version as i started on. The order i went in was...
Code:
1. Root.
2. Install 2nd init. recovery installer. http://forum.xda-developers.com/showthread.php?t=1032212
3. Boot into recovery and select Backup/Restore and make a backup.
4. Download a 2.2 fixed sbf like the nordic one.
5. Download CM7. (Place in same directory as your nand backup. sdcard/clockworkmod/backups.)
6. Boot into 2nd init menu and select to boot 2nd init by default.
7. Select custom recovery and restore the cm7 nandroid.
7.5. Wipe data from custom recovery.
8. Reboot Defy while holding volume up.
9. Plug in usb and start up RDS Lite. Select fixed sbf you downloaded and press start. Once finished it will boot into CM7. (I had to pull battery after RDS Lite finished)
5. I don't think you lose root as i'm sure superuser is installed to system partition which isn't wiped when factory reset.
Oh also just for future reference. If you ever mess up (no recovery possible) or need to restore for warranty just look for the 2.51 full sbf for your region or operator and flash it with RDS Lite. You end up with a factory fresh phone and can start again
just the kind of post i need this, just one question,
you say backup/restore, I have installed 2init, but I cant see this option. Does this have a different name, or am I totally looking at the wrong menu?
ahh got it, i just needed to mess first
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Do you not get an error message? What is your current rom?
Jakethepeg said:
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Click to expand...
Click to collapse
For flashing with RSD you MUST be in bootloader mode.
Hold down volume up as you boot the phone, you will get some white text on a black screen. After this, plug your phone in via USB to your comp, once RSD reads it, load the sbf, and then start the flashing process and wait until it is completely finished and either boots your phone, or instructs you to boot manually.
The text on the phone will change as the process starts.
Hi Erra
thanks for that, I have been trying to flash in bootloader mode but I still get the message unable to flash.
Ephumuris, I am using stock uk 2.51
Are you using the latest version of RSD Lite?
You installed the motorola drivers?
Sent from my Defy on CM7.
Jakethepeg said:
really stumped,
I am trying to install the leaked froyo uk build. I have installed the moto drivers and the rsd lite.
I put the .sbf in the rsd lite and connect my phone.
It sees my phone fine, but when I try to flash it just fails straight away.
I have tried enable/disabled usb debugging , but that makes no difference. Have tried wipe, but again no change,
what am I doing wrong?
Thanks in advance
Click to expand...
Click to collapse
Would RSD Lite even recognize the phone without drivers installed?
From where can we get the latest version of RSD Lite?
Ok tried again, for the first time, managed to make a nandroid backup, (something that also wouldnt work ).
Still getting an error though, when I try and flash, interestingly though, my rsd lite, doesn't seem to be able to load roms, with their full name, (i have to shorten it to uk.sbf or something along those lines).
Tried to flash the froyo uk tmoby leaked rom (11 version), and the error message I get is Failed flashing process (0x7100); phone connected.
Version I am on for rsd lite is 4.9 multiflash/ multi flex.
Thanks again for all your help and patience
Feel such a noob with this, I never had this many issues with my old xm5800
the version of rsd lite is compatible with 2.51 isnt it?
Or do i need to grab an older version, just noticed this got released in march.
ephumuris said:
i'm new too but not new to Android...
1. Yes. And you can downgrade to 2.1 again. I did!
2. The clue is in the name, all your phones current data, apps and rom are stored on the nand memory within your Defy. The Nandroid backup takes a snapshot of all this data and stores the information from each partition on your sdcard.
3. Nandroid backup is easy. I recommend the 2nd init auto installer...that also installs recovery (custom) and is needed for cm7. Backups vary in size...mine are usually around 450mb.
4. SBF's are just official rom files, in a format readable/flashable with RSD Lite. You are on the same version as i started on. The order i went in was...
Code:
1. Root.
2. Install 2nd init. recovery installer. http://forum.xda-developers.com/showthread.php?t=1032212
3. Boot into recovery and select Backup/Restore and make a backup.
4. Download a 2.2 fixed sbf like the nordic one.
5. Download CM7. (Place in same directory as your nand backup. sdcard/clockworkmod/backups.)
6. Boot into 2nd init menu and select to boot 2nd init by default.
7. Select custom recovery and restore the cm7 nandroid.
8. Reboot Defy while holding volume up.
9. Plug in usb and start up RDS Lite. Select fixed sbf you downloaded and press start. Once finished it will boot into CM7. (I had to pull battery after RDS Lite finished)
5. I don't think you lose root as i'm sure superuser is installed to system partition which isn't wiped when factory reset.
Click to expand...
Click to collapse
When is the time to do full wipe??
Oops i missed that. Straight after the step of restoring the cm7 nandroid.
Step 7.5. Wipe data from custom recovery.
hi guys, i just recently bought my defy, i am aware that it is on android 2.1 eclair.
1. i wanted it to be on froyo, question is, do i need to ROOT it?
2. my current location is saudi arabia, what version do i need? and if i travel, say asia, will the "upgraded" froyo still work?
3. is there any simple way to be in 2.2 froyo? ( i am now confused on many and different steps/guides here on xda)
i just dont want it to be on eclair.. please help..
thanks in advance!
I did an upgrade to Froyo 2.2.2 Nordic release.
No root.
1. there is no need to root the device just to upgrade it, only if you want to flash an unofficial rom. if there is an official OTA update, simply go to settings > about phone and check for updates, and download/install it, or you could try downloading motorola software update from the official site, and try that!
2. it depends, but afaik you will have no problem, as long as the gsm frequencies match, you'll be fine.
3. what do you mean? simple way to update? or simple way to use?
process? shall i download the "rom" and then install it directly?
if there is an OTA update, then yes, just download and install directly. if you can't find anything from your phone, try from your computer with motorola software update!
so meaning if it is official android 2.2 froyo update from motorola itself, there's no need for rooting? [the easiest way for me =)]
however, if i opt for an unofficial version of android, rooting is needed? [this is my nightmare, i really can't follow or what to follow]
are the "stock" here http://forum.xda-developers.com/wiki/index.php?title=Motorola_Defy#Guides.2C_How-Tos_.26_Tutorials official (no rooting needed)?
yep, exactly, because for an unofficial update you have to use rsd lite, and that works with rooted phones only.
EDIT: sorry, my bad, apparently you CAN flash an sbf with rsd lite without root, dunno why i thought you can't.
Root isn't neccesary for RSD either, only for nandroid restores.
@agent__orange You can flash any SBF with RDS Lite without rooting the phone. You'll need to root the phone in order to install ClockworkMOD Custom recovery (tenfar's recovery or 2nd Init). This app will help you to back-up your current system (create nadroid backups) and also will allow to apply nandroid backups.
The safest way to upgrade your phone is by applying a nandroid backup and then flashing a fixed SBF. This way you'll keep you downgradability(that means you can always go back to your stock system which I assume is Eclair).
There are few steps to do in order to update to Foryo and preserve downgradability:
- install ClockworkMOD recovery
- wipe cache, data, dalvik cache
- install the nandroid
- reboot phone in bootloader
- apply fixed SBF
You can find more details on this topic [(7) How to install CM7 and keep downgrade-ability? (Froyo or Eclair) ]
PS: you can always use the search function, it won't bite I promise
i did lurk for a while here on defy threads...its just i've got confused already with many many methods or process to do. =)
thanks so much for the response..let's say i dont want to go downgrade, so all that i need is the OFFICIAL ROM (froyo, i really wanted that cm7 though..sigh)..
1. download official rom (from pc)
2. transfer to defy
3. install
is this correct?
In order to transfer it to Defy you'll need to download also the RDS Lite v4.9 app which will allow you to write the SBF to your phone. Moreover I strongly recommend you to wipe the data before flashing the SBF using the stock recovery (power phone by pressing Vol Down+ Power, then wipe data/factory reset, cache and dalvik cache). Then you can go into bootloader (start the phone using Vol Up+Power) connect your phone to pc and flash the SBF.
I did that quick update with an unofficial rom;
1/
Downloaded the ROM, in my case 3.4.2_177-Fixed.NORDIC_DEBLUR.sbf
2/
Loaded that file in RSDLite v4.9
3/
Removed battery from Defy and put it together again
4/
Conect the USB-cable
5/
Pusched VolumeUp and PowerOn for aprox 1 sec. Continue hold the VolumeUp and a black screen appears with some text like "conected OK" ...dont remember exactly...
6/
RSD Lite will now identify Defy
Hit "Start" in RSD Lite and the install will begin. 5-10 minutes and thats all.
NO ROOT
You don't need to take out the battery, but it's recommended to wipe everything (data,cache) before flashing a new SBF.
thanks guys, i'll try that out..btw, where can i find the RSDLite v4.9? sorry noob...
You can download RSD Lite 4.9 from here.
thanks!
also i have read about "locking the screen" (power button + slide), and heard about an app that only uses "slide" only (so not pushing power button everytime), what is it?
is the "slide-screen-lock" can be installed on defy without rooting/upgrading?
guys, i have updated to 2.2, my located now is at saudi arabia, if i go to singapore in the future, will my phone still work there?
I don't know which baseband is used in Singapore, but with a program like baseband switcher you can go wherever you'd like and your phone will work. You'll only have to change the baseband accordingly.
thanks a lot!
Hi, I have a problem, cannot find a solution and hope you can help.
I Installed CM7 using this guide: http://forum.xda-developers.com/showthread.php?t=1054447
It worked perfectly! a few days ago I realized that I have to restore my phone to send it to warranty, and here is where my problems started.
The first thing I did I try to flash SBF from here http://www.and-developers.com/sbf:defy(3.4.2-107 TMobile US Blur) using RSD Lite v4.9 and all I get is a black screen, then try both (JORDN_U3_6.19.0 Blur Tmobile and JORDN_U3_6.36.0 Blur Tmobile) with the same results.
then I decided to follow this fix
How to fix it:
1.Download this SBF and Flash it
2.Root your Phone
3.Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
4.Download and install this Nandroid Backup
5.Enter Recovery, Wipe Data/Cache
6.After wiping, turn off your phone
7.Turn it on and get immediately into Bootloader mode
8.Flash this Fixed SBF
9.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.
Click to expand...
Click to collapse
I was able to do everything until step #4 and get an error message when trying to install the back up. I have been trying to get this to work for at least 3 complete days(noob) and I'm going crazy. Please help me...
The phone is in working condition but I need to have it back to stock for warranty purposes.
Thanks,
Miguel.
(Motorola Defy T-mobile USA)
miguelco01 said:
Hi, I have a problem, cannot find a solution and hope you can help.
I Installed CM7 using this guide: http://forum.xda-developers.com/showthread.php?t=1054447
It worked perfectly! a few days ago I realized that I have to restore my phone to send it to warranty, and here is where my problems started.
The first thing I did I try to flash SBF from here http://www.and-developers.com/sbf:defy(3.4.2-107 TMobile US Blur) using RSD Lite v4.9 and all I get is a black screen, then try both (JORDN_U3_6.19.0 Blur Tmobile and JORDN_U3_6.36.0 Blur Tmobile) with the same results.
then I decided to follow this fix
I was able to do everything until step #4 and get an error message when trying to install the back up. I have been trying to get this to work for at least 3 complete days(noob) and I'm going crazy. Please help me...
The phone is in working condition but I need to have it back to stock for warranty purposes.
Thanks,
Miguel.
(Motorola Defy T-mobile USA)
Click to expand...
Click to collapse
0)Enter Recovery, Wipe Data/Cache, Wipe Cache
1) Install deblur 3.4.2_177-005_nordic (bootloader works even when phones are dead)
And the correct steps after the above one are
2) Root it
3) 2nd Init
4) Clock World Mod
5) Install Nandroid
6) Unroot
But let me tell you that it would be very difficult to downgrade to your stock version coz your kernel version of stock used for cm7 and later rom are different.I recommend you to try other sbf but before any upper sbf flash please don't forget step 0.
root_toor said:
0)Enter Recovery, Wipe Data/Cache, Wipe Cache
1) Install deblur 3.4.2_177-005_nordic (bootloader works even when phones are dead)
And the correct steps after the above one are
2) Root it
3) 2nd Init
4) Clock World Mod
5) Install Nandroid
6) Unroot
But let me tell you that it would be very difficult to downgrade to your stock version coz your kernel version of stock used for cm7 and later rom are different.I recommend you to try other sbf but before any upper sbf flash please don't forget step 0.
Click to expand...
Click to collapse
root_toor Thanks a lot for your response but the problem that I'm having is not that the phone is dead, the phone is in working condition right now after flashing JORDN_U3_97.21.51.rar in step 1.
I'm trying to get my phone back to stock, and while trying this fix: http://forum.xda-developers.com/showthread.php?t=1216982 I got stuck in step 4. which is to install 2011-06-11.14.14.27.zip nandroid backup. I still don't know if this is relevant to my main problem anyway.
So if I install deblur 3.4.2_177-005_nordic and follow your steps is it going to help me revert back to stock? if so in step 5) which nandroid do I need to install?
Or I should just try to install other sbf
Thanks!
Have you tried to use the Froyo 2.2 CEE sbf?
I always use this sbf when I got myself in trouble lol..
WHOA WHOA WHOA! I hate to burst your bubble dude but you just screwed up by flashing JORDN_U3_97.21.51 This is a chinese eclair with CG39.smg and CG31.smg ver=5... Not cool considering stock US Tmobile has ver=4. They will be able to tell you have blown an efuse and brought it up to level=5.
For everyone who says you cannot downgrade back to stock US Tmobile Eclair after flashing any Froyo sbf are misinformed. This is not true, stock US Tmo Eclair contains ver=4 just like all Froyo sbf's and can easily be flashed back to ( I have done it a thousand times trust me!! ) US Tmo is actually on official froyo now but there is no sbf for it. The only US Froyo sbf is the leaked 3.4.2.107-4 and is not the official Froyo which is 3.4.2.107-9. Flashing JORDN_U3_97.21.51 was the absolute worst thing you could have done! You can still get to official US 3.4.2.107-9 (34.4.9) by restoring a nandroid of 3.4.2.107-9 and then creating a fixed sbf yourself from leaked US froyo 3.4.2.107-4 by depacking the sbf, removing CG39.smg and replacing CG31.smg with CG31.smg that is ver=5 and repack it and flash. I'm actually not sure what CG31.smg you should use in this case?? Either the one from JORDN_U3_97.21.51 or the one from the full 2.3.4 sbf??? these are the only CG31.smg's that are ver=5.
The problem is that now that you have flashed JORDN_U3_97.21.51 Your CG31.smg MUST ALWAYS now be at ver=5 or above or your phone will never boot! This creates a problem for warranty because your US defy should contain one at ver=4......IF THEY ACTUALLY CHECK INTO IT THAT IS!! I would imagine that it is pretty easy for them to identify if they do look to see which level of Code Groups have been flashed. Good luck dude and let us know how it goes! While I'm thinking about it I should also mention that not only is your CG31 at level=5 but so is your CG39.smg, this is why you MUST restore a NANDROID of froyo because all froyo sbf's have CG39.smg at level=4. CG39.smg is the Code Group of the actual system. JORDN_U3_97.21.51 is the ONLY known Eclair which has CG levels=5. Once you flash a higher level of Code Groups it is PERMANENTLY burned and CAN NOT be reversed. When you tried going from CM7 back to stock you should have WIPED DATA/CACHE in STOCK recovery and then flashed JORDN_U3_6.36.0 and you would have been good to go. JORDN_U3_6.19.0 was a very early build of eclair for US defy with CG=3 and when they released an Eclair update (2.1 update 1) they changed to CG=4. You must ALWAYS wipe in stock recovery prior to flashing ANY sbf or there is a very high chance you will boot loop or black screen. I know it's too late now but I'm simply trying to help you understand what went wrong. Who knows if they will even check to see if you have flashed a higher Code Group or not????? Hopefully not