Database Info

[GUIDE] GUIDE to get the official US T Mobile OTA

If you were impatient and flashed a leaked SBF like and still wants to get the official update, here is a shord guide for you. I examined the 6.36.0 sbf and the code groups for CG31 and CG39 are the same as the leaked froyos so i flashed it on my phone running CM7 and it booted After it i downloaded the OTA let it install and now i am on the official 2.2. I can change it with the CM7 anytime i want and if i have to take the phone to the service restore it to stock 2.2 So step by step
1. If you are on any leaked froyo download the latest us eclair sbf(JORDN_U3_6.36.0) from http://www.and-developers.com/sbf:defy
2. Boot into the stock recovery and wipe
3. Boot into the bootloader and install the SBF from point 1
4. Let the phone reboot then go throught the motorola blur registration then setup a wifi connection.
5. Download the OTA (settings->about) and if the download finished let it reboot and install the update.
6. Enjoy stock untouched 2.2 T mobile froyo

hi is this only for US people or will it work in UK as well?

It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App

Does it supports 720p video recording!!

vick33 said:
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
What is the version number after the update?

Anyone can upload nandroid and sbf ?

It came out as OTA so no sbf available. Every version is the same as it was with the test update... it is android 2.2.1 34.4.9 they did not changed anything from the test update so i am not satisfied at all...
Sent from my MB525 using XDA App

Can i send in my defy for service with this rom?
Edit: I guess this rom is official. Read this thread. http://forum.xda-developers.com/showthread.php?t=1044980 .Cool stuff. Thanks for the heads up!

I tried flashing this and now my phone wont turn on i needed this so i can return it to T-Mobile with a stock ROM, but now my phone won't even turn on. Tried removing battery and putting back in, no matter how long i press the power button, it wont even turn on. help plz

On which rom were you before? Did you wiped before flashing the sbf? I have done it myself many times.

i was on CM7 and i wiped and flashed like u said. it might be my phone.
EDIT:
well nevermind, looks like the screen is fried. it seems to have flashed but the screen wont display anything cause when i plug it in to the computer, i hear the little beep and the LED notification appears, but no display.

you cant burn the screen like that. If it beeps then you are ok. You should try flashing the nordic sbf for example, fom it i have gone fortth and back to the us froyo the way i described.
so what should you do:
1remove your battery and while putting it back hold volume up.
2 start RSD lite and connact your phone
3 if it is connected flash the sbf.
If the PC does not sees the defy then your battery is flat. Charge it with an external or try mcgyver, you cant brick defy with flashing.

Will this work if you flashed the 2.2 OTA then used a custom froyo ROM. I basically want to take this phone back to stock.
I thought we couldn't downgrade.
Sent from my MB525 using Tapatalk

i was on nordic when i did the things i written. Got back the official now i have done it from other custom roms like CM7, but wipe in the stock recovery before trying it. I dont have any problem but seems like someone had so be careful.

I'll give it a shot because my nandroid restore is buggy.
Will post results.
Sent from my MB525 using Tapatalk

It would be interesting if it wont work for you. Cg-s for the us eclair are same as for the froyos
Sent from my MB525 using XDA App

Finally a way for US users to return to FULL STOCK regardless of firmware
It worked!!!
I was on barbones 1.5.1 then went to a backup nandroid version of my original stock rooted. Was kind of buggy so I decided to try this
1. Wiped everything using the stock recovery
2. Bootloader and flashed nordic 2.2.2 and "skipped" the automated setup until the phone desktop appeared then waited until RSD said the phone "passed".
3.Wiped everything using the stock recovery again
4. Bootloader and flashed 2.1 JORDN_U3_6.36.0 then pressed "start" at the motoblur screen and waited until RSD said the phone "passed".
5. I then entered my motoblur info and "skipped" everything until I was at the android desktop. After syncing was finished (waited about 5 min) I proceeded to "Download the OTA (settings->about->system updates) and after the download finishes let it reboot to install the update"
Thanks "vick33" nice find!
Note:
I could not update the kindle app without it giving me unsigned package errors. My solution was to root and uninstall the oem kindle app.
Then unroot and perform a factory reset. The oem kindle app did not restore and I was able to install the latest kindle without errors.
No other issues have been found.
*** CONFIRMERD TO WORK ***Another solution maybe to update the kindle app prior to updating the phone to 2.2 via OTA. Possible the better way to go considering it does not require rooting or removal of a system installed bloatware.

i mean the screen doesnt show anything. screen is black, idk whats wrong with it. im not saying the sbf had anything to do with it, just saying the screen went out. i just turned it in anyways, so ill be getting a new one soon.

Problems moving to Humble 1.35

Hey guys, I just came from Humble 2.2. I decided to switch back to Humble 1.35 Froyo because of its better battery life & kernel (plus voodoo!). As you know, 2.2 includes the EP1F update. So, I followed danalo's instructions for how to downgrade to ED1 and upgrade to EE4 again. Then, I flashed Humble 1.35 with Odin3 v1.7. It passed, but when I try to boot, it just hangs at the Samsung logo (with no sexy robot voice)...please answer ASAP, I'm getting really nervous

If you have problems with a flash you could always just try reflashing. I've never bootlooped my phone so I can't help you through experience but a lot of the time a simple reflash fixes these problems.

I have boot looped my old evo. It was fixed each time by clearing the caches/factory reset and reflashing the rom.

quantim0 said:
I have boot looped my old evo. It was fixed each time by clearing the caches/factory reset and reflashing the rom.
Click to expand...
Click to collapse
Can't get into CWR, and I've already tried reflashing.

Well, I got it working back on this stock Odin package http://forum.xda-developers.com/showthread.php?t=1116867 and when I reflashed 1.35 it did the same thing. Redownloading Humble now, see if that fixes anything.
Edit: Okay, I'm definitely not going insane. It's doing the same thing. What gives?

if its converting to EXT4 it can take up to 5-8 minutes..especially if you cleared cache and dalvik..even if there is no voice I would wait at least that long before you panic.........

I don't think the 1.35 Odin package flashes absolutely everything required to run, as if you're expected to be rooted, cwm etc already before flashing. So i propose flashing the 3rd Odin package in the link above, and then flashing to 1.35. Don't have any time to test this, will do it in the morning
Sent from my SCH-I510 using XDA App

same here. I had to flash 1.2 though odin, which gives you everything (root, kernel & rom) and then install 1.35 zip from cwm.
Sent from Droid Charge HUMBLE 1.35

kvswim said:
I don't think the 1.35 Odin package flashes absolutely everything required to run, as if you're expected to be rooted, cwm etc already before flashing. So i propose flashing the 3rd Odin package in the link above, and then flashing to 1.35. Don't have any time to test this, will do it in the morning
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
+1. This is what you have to do. I had to do the exact same thing last night.

make sure you are using odin 1.7 or higher to flash also

I had that happen once when I flashed a friend's Charge and flashing this package over top fixed it.
http://forum.xda-developers.com/showthread.php?t=1092114

Infinity rom stuck on galaxy boot

I had the infinity Tom installed from before the fp1 update. I tried loading the newest infinity rom from 3-20 and phone got stuck on galaxy boot animation . I Odin my phone back to edp then let it take the factory update then Odin cwm and used cwm mounted system cleared data and installed infinity rom boot phone and get stuck on galaxy. I tried waiting about 10min pulled battery and still stuck. I tried the whole process over and same outcome. Am I missing something? Thanks

I'm assuming you are RFS since you odin'd back to stock and took the OTA?
Also I don't know if it matters, but Infinity hasn't been updated to the latest OTA. You could try out Eclipse 2.0 or Tweaked 2.0, which are already updated to FP1.

it does matter. u cant run ep4 roms on an fp1 kernel. like he said, tweaked 2.0 or eclipse 2.0 r the only custim roms u can run at the moment. if u want infinity u need to go back to ep4 and dont update.
Sent from my SCH-I510 using XDA

thanks for the clear up, after reading some more i ws heading in that direction but was not sure. thanks again

Soft brick/boot loop

I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"
I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.
Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.
Thanks!

Hmm... was there anything going on at the time of reboot? Very curious.
Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?
Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found here (just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!

Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.
I'll try all those files this time on fresh downloads, might have been something corrupted.
thanks again!
UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...

Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.
Sent from my SCH-I510 using xda premium

I had something similar happen to me just a week ago. I was on stock debloated deodexed and odined to tweeked and it bootlooped, Odin said successful but nothing was happening just Samsung logo. I knew there was no problem with tweeked cause I used the same file b4 and it worked fine. Tried to Odin back to stock ep4 same Samsung logo Odin still said it was successful. So I changed cable and made shure I was not moving phone or cable while it was doing its thing. It worked. Then updated to fp1, cwm superuser then Odin to tweeked. Everything ok. I figured the only problem of my was that the cable was a bit loose when I plugged it in the phone, the connections in the phone I guess were not getting the full contact as they should have. So try making shure you connect/plug in cable all the way and don't touch it while Odin is doing its job. You might also need to flash the stock ep4 file. Sorry could not help more. This worked for me, now on tweeked 2.2 n no problems.
Sent from my SCH-I510 using xda app-developers app

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy

If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?

If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham

Yeah, you can still fix it. No need it to bring to samsung

Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?

random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.

cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!

Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!

random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!