Develop Bugs

Help...Defy stuck in bootloop

I have a stock 2.1 defy with the 2.51 rom (i think). all the mod i did was root the phone using super one click, the phone ran fine for a few months until i experimented with titanium backup and deleted google talk etc. i found out that (too late)doing this would cause the android market to stop downloading and updating my apps. To remedy my situation i tried installing google talk service.apk back to system apps. first by copying the file to my sd card and pushing it to the system file using terminal emulator. after rebooting my phone is now bootlooping. i tried removing the battery and just after i insert it it would go immediately into the bootloop phase. tried using recovery (volume down+power) and wipe cache and reset, still no go. last resort i tried is after wiping i tried installing cm7 but the installation was immediately aborted. please help, right now im close to tears, i didn't know that it was this hard to mod a defy. my previous phone was a wildfire and modding it was pretty easy.

What happens when you turn the phone on? Does it start in the bootloader? Is it stuck in Motorola Logo?

Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
Sent from my Life Proof Defy on CM7

juanplopes said:
What happens when you turn the phone on? Does it start in the bootloader? Is it stuck in Motorola Logo?
Click to expand...
Click to collapse
the phone turns itslef on automatically when i insert the battery, white moto logo first then bootloops in motoblur animation.i can go into bootloader mode by pressing up and power before inserting the battery. i just wished i hadn't played around with titanium backup. i already downloaded the necessary files to flash a new firmware. hope i learn to do it properly.

javi422 said:
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
Sent from my Life Proof Defy on CM7
Click to expand...
Click to collapse
i tried wiping the cache/data numerous times under recovery mode to no avail. now im crossing my fingers that my battery isn't that drained for me to flash a new firmware.

Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
You can also do the battery hack/trick
Sent from my Life Proof Defy on CM7
Click to expand...
Click to collapse
i tried wiping the cache/data numerous times under recovery mode to no avail. now im crossing my fingers that my battery isn't that drained for me to flash a new firmware.
Click to expand...
Click to collapse
Sent from my Life Proof Defy on CM7

Hi I have the same problem,I just tried to flash the Barebone 1.5 ROM.
My Defy was stock,I just root it and made a backup with clockmod before I did as discribed here:
Installing (Rom wipes data/cache partitions)
1. Copy Barbones to sdcard: Barebones_15-signed.zip.
2. Boot into recovery (make a backup ?) and restore nandroid: 3.4.2_177-Nand.NORDIC_DEBLUR.zip.
3. Still in recovery, select install zip from sdcard -> choose zip from sdcard -> Barebones_15-signed.zip.
4. Reboot system, first boot will take time as it builds the dalvik cache; wait for the background to load, and enjoy Barebones.
- Use Easy Installer to install any apk's you feel are missing.
- Removed.Stock.Apps.zip
-- Removed Apps Must Be Copied To /system/app Manually - Remember To Set Permissions & Reboot
To downgrade back to Eclair; just flash the Eclair sbf you where using beforehand; thats it.
Click to expand...
Click to collapse
after Reboot it just shows Motorola,I can access Recovery Menu stock one and custom,tried wipe restore factory settings and wipe cache but nothing helped!

What version where you coming from ? Eclair or Froyo ?
Btw factory reset and wiping the cache doesnt do anything in these situations.
Did you restore the Nandroid provided ?
Also cant lie only thing I did not test was coming straight from an Eclair build.
I used the Korean Froyo sbf as a starting point; but I'm testing it now.

Got it alive again with this steps.
No wonder why u're stuck on motorola logo.
Let me break it down for you.
Make sure you have motodrivers installed or install them here.
And install the RSD Lite too Here
Turn off your phone, hit the power+volume up together.
Wait till u're in the bootloader.
Open the RSD Lite, u phone should be detected so u click on "..." select the .sbf u downloaded from here
And flash it.
Wait till is over, and your phone should be good again.
Click to expand...
Click to collapse
I used this .sbf
But I still don't know what went wrong,I did exactly as discribed in the TUT I postetd above!?

Well if you flashed that sbf you wont be able to downgrade back to Eclair anymore.
However; yes doing that will fix it.

Is it not good that I flashed this .sbf? I got the phone just 2 days ago I think it already had the newest firmware etc.!?
EDIT: But something is wrong with my Wlan connection it is very slow and always loses connection

I doubt it came with Froyo seeing as they are all leaked builds.
http://forum.xda-developers.com/showthread.php?t=966537 <- Read up
Just means you cant go back to Eclair.
Ok so you wifi is slow ? Are you even using my rom now; because you flashed 3.4.2_155-Stock.CEE_DEBLUR.sbf.
I cant see your phone so you have to tell me what your using.

Yes I just flashed the sbf nothing else,and before I just did what I read in the instructions from the Barebone 1.5 Thread.
1. Copy Barbones to sdcard: Barebones_15-signed.zip.
2. Boot into recovery (make a backup ?) and restore nandroid: 3.4.2_177-Nand.NORDIC_DEBLUR.zip.
3. Still in recovery, select install zip from sdcard -> choose zip from sdcard -> Barebones_15-signed.zip.
4. Reboot system, first boot will take time as it builds the dalvik cache; wait for the background to load, and enjoy Barebones.
- Use Easy Installer to install any apk's you feel are missing.
- Removed.Stock.Apps.zip
-- Removed Apps Must Be Copied To /system/app Manually - Remember To Set Permissions & Reboot
Click to expand...
Click to collapse
I tried this sbf before 3.4.3_11-Stock.UKTmobile_BLUR but it always failed thats why I tried the other one

So your not using my rom now - the sbf overwrites everything.

Ok sorry Im a noob^^ I just wanted to have all this blur stuff removed etc and your rom seems just perfect for me.
I have problems now with the phone and I really wished I would never had tried this.
I cant boot into recovery mode anymore with clockworkmod, I rooted my phone again installed clockwork but the screen stays black after the Motorola Screen came up when I try to make a recovery boot with clockwork.
cause I wanted to restore the backup I did with clockworkmod before I messed it all up,would that make my phone like it was before or not!?

I doubt you will be able to get back to your backup simply cause I dont think its Froyo.
So do this:
1. Boot into bootloader (power + volume up).
2. Flash 3.4.2_155-Stock.CEE_DEBLUR.sbf again.
3. While its rebooting after flashing hold volume down to goto stock recovery.
4. Do a factory reset.
5. Root your device using superoneclick http://forum.xda-developers.com/showthread.php?t=913709
6. Reboot.
7. Install 2nd Init Recovery http://forum.xda-developers.com/showthread.php?t=1032212
8. Reboot twice (to finish installing recovery).
9. Reboot into recovery - wait for blue led then hit volume down.
10. At this point you can try to restore your backup or flash a rom of your choice.
If you try your backup and it does not work you will need to start this process over.

Ok thank you so much fritolays for your help! I will try this tomorrow and post back if I had success or not!
greetz!
EDIT: Couldn't wait to try it and it worked! I took the risk and tried to install your rom again (restoring my backup didn't worked anyways 'cause clockworkmod didn't find the backup but it was still in the same folder it got stored before) works like charm as far as I could test it. But now I really have to go to sleep!
Big thanks again fritolays without your quick help I would still try to get my Defy to work without any success! and THANKS! for this great rom!!!
EDIT2: I don't know why but I have problems with the phone since yesterday when I first flashed another ROM,I always have Network Connection Problems now! I can't download anything from the market if I get to the market! 'cause normally it says no network connection! It worked fine for like 20minutes after I got it to work with ur method u told me above then it suddenly took very very long to download an app. Never had these Problems before,I also have very bad Phone Signal and most of the Time I can just make Emergency Calls and I turned Internet Connection OFF for mobile network (like I did before when it was stock) but sometimes I still can go online with Wlan turned off so this is really ****ed up 'cause I have no internet plan with my mobile phone!
But with your ROM the phone is really flying,I did a Benchmark Test before and got 1100 Score and by just putting your ROM on my Defy without any overclocking or something like that I got 1275 Score!
EDIT3 I found the direction it was clockworkmod/backup/ now
I did a wipe factory reset and a cache wipe and now restoring it I really hope everything is like it was before all this!
Ok this got me to the Bootloop Problem again so I did again all the steps u told me and instead of restoring ur ROM I restored my backup wich was now in the right direction,but it is also ended up in Bootloop!
EDIT4 If I try all this with ur ROM it works,is it because of the Froyo .sbf I flashed that I can't get my backup working!?
I get this Error Message after my phone booted with ur ROM maybe that is one of the Problems I have? "Sorry,the process android.process.media got suddenly closed try it again" I had to translate it so maybe the message is a bit different in english but thats what it says generally.
So everything worked great again,I go into Market to download TitaniumBackup (like I always did) then as always I apply the new Busybox Install TitaniumBackup suggests everytime I start it and the Wifi gets slow already by downloading Busybox. Then I tried to go to the Market again and Network Error, I get the feeling it has something to do with this app or the Busybox installation TitaniumBackup is doing!?
I don't know what it is but it alwys messes something in my phone up and I get Wifi Probs!??
EDIT5 I tried another ROM now "xd1 ** new ** ver 1.2" and everything worked fine! I downloaded Quadrant and a Antivirus App just to test it and everything was alright so I tried TitaniumBackup again (the Free Version as always) and guess what the download got fast till 42% then stuck and now I can't download anything again from Market it is very slow and then the downloads got canceled! wtf is wrong with this app!? I need it for all my Apps 'cause I did a backup with this app but since I flash custom ROMS it always does this bull**** when I download it from market!?

update..got my defy unbricked by following Higgsy's step by step method. installed a 2.51 SEA sbf in the process. love the phone without blur. now im thinking of upgrading to a froyo rom, which do you guys think is the best? based from reading the posts here i'm more confused than ever. sbf's here and 2nd init that??? not to mention a fixed sbf?? i really can't understand these terms and the more i read the more i got confused. Could you guys help me in laymans terms the proper process for upgrading to froyo and which rom is you think is best??

is it necessary to root defy when upgrading to froyo?

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!

[GUIDE] All-in-One Defy Beginner's guide

{
"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.

Back to stock

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

Need to flash my phone, but have a question...

So here's the scenario. Hopefully I don't leave anything pertinent out...
Galaxy S3 w/Sprint. Phone is rooted but has the stock ROM on it. The phone doesn't need to be rooted, but I figured something like wifi tether might come in handy at some point. I rooted it such a long time ago I honestly don't remember how I did it. However, the screenshots of the Odin program look somewhat familiar so I'm guessing it was something with that.
When I boot into recovery mode, it says CWM-based recovery v5.5.0.4 and has the standard CWM menu.
This, of course, means I can't get the OTA update that came out a few months back.
So, in order to get the stupid prompt to stop bugging me to update, I need to flash the phone with something. I'd be fine using an updated version of the Stock ROM, or would be happy to put something like CM10 on there. I don't want anything experimental so I'd go with the stable version.
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!

1.It depends on your likings. Play with different ROMs.
2.Just a wipe before to flash the ROM.No need to wipe photos and videos.
3.Yep.Put the ROM on your SD card,wipe your phone and then flash it.
Hope that helps
Sent from my GT-I9300 using xda app-developers app

kelemvor33 said:
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!
Click to expand...
Click to collapse
1) The standard answer is: try them all out and see if you like one or the other. But I'll be nice and also say that if you're looking for something stable, I'd recommend The People's ROM. It's a TW-based ROM with a lot of customization, but it's very stable and has a large user base. They're always willing to help someone out (as long as you search before asking).
2) It really depends what you're flashing. I always recommend what I call a "so fresh, so clean-clean flash," which means wiping /data, wiping /system, and cache and dalvik cache. You won't lose your photos, but you will lose all apps and their associated data (save games, etc). The reason I recommend wiping system (which others might not suggest), is that different ROMs have different mods associated with them, and as an end-user of the ROM, you have no idea if your previous ROM is leaving behind files in /system that won't play nicely with your new ROM. So I typically wipe system as well as data and the caches.
3) You're in luck. I have a previous post that explains #3 is pretty good detail. Since you have verified that you have CWM, you can skip the first section where I talk about that. I have quoted it below:
kay131108 said:
ok..can u pls be a little more specific..i if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
And lastly, you don't have to lose all your apps. You can use Titanium Backup (TiBu) to restore your apps. You just have to be careful not to restore any system apps, as they tend to not play well between Roms. I have quoted my previous post about TiBu down below so you can review some features/warning about TiBu.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"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"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse