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.

CM9 can't get past welcome screen

Hello,
I appreciate everyone here is from quite a technical background. I'm quite a noob with these things but hopefully this isn't a massive issue.
I have a HTC sensation (I'm in the uk) and I have been using cm7 for many months. I've just decided to download cm9 and install and everything was going smoothly until I get to the welcome screen.
I try to change English (USA) to English (uk) but this freezes the phone and makes it reboot. I go through this motion over and over again. Any ideas please?
When I updated to cm9, I assumed my phone was already s-off (to be honest I still don't know what this means but thought I did it when I installed cm7) so all I did this time was download cm9 and gapps to the root folder of the SD card. Then I opened rom manager, flashed clockwork recovery and went into recovery mode. I then wiped the data on the phone, wiped the cache, installed cm9 and then gapps and now I'm here!
Any ideas anyone? Many thanks in advance.

Repoman123 said:
Hello,
I appreciate everyone here is from quite a technical background. I'm quite a noob with these things but hopefully this isn't a massive issue.
I have a HTC sensation (I'm in the uk) and I have been using cm7 for many months. I've just decided to download cm9 and install and everything was going smoothly until I get to the welcome screen.
I try to change English (USA) to English (uk) but this freezes the phone and makes it reboot. I go through this motion over and over again. Any ideas please?
When I updated to cm9, I assumed my phone was already s-off (to be honest I still don't know what this means but thought I did it when I installed cm7) so all I did this time was download cm9 and gapps to the root folder of the SD card. Then I opened rom manager, flashed clockwork recovery and went into recovery mode. I then wiped the data on the phone, wiped the cache, installed cm9 and then gapps and now I'm here!
Any ideas anyone? Many thanks in advance.
Click to expand...
Click to collapse
Hi,
Once you are s-off,you do not lose it,unless you manually switch it on in fastboot.
Did you update your firmware before installing the new ROM?

malybru said:
Hi,
Once you are s-off,you do not lose it,unless you manually switch it on in fastboot.
Did you update your firmware before installing the new ROM?
Click to expand...
Click to collapse
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)

Repoman123 said:
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Click to expand...
Click to collapse
Hi,
The best guide on firmware update is HERE
Substitute ARHD for CM9.

Repoman123 said:
Hi, many thanks for your reply. No I didn't update the firmware, I don't think it states this in the update instructions on the CM website - I assume I was supposed to update firmware?
What should I do now, considering the phone is in this silly loop (welcome screen to off to welcome etc...)
Click to expand...
Click to collapse
The post above mine links to the best guide to get CM9 booting.
But in the mean time if you don't have the time to figure all that out (it's not hard, but it can take a little while your first time because you'll be extra careful and read all the instructions 100 times before each step) you can revert back to a Gingerbread ROM. I assume that's where you started, so if you have the Gingerbread firmware you can boo any Gingerbread ROM. That will only take about 5 minutes. So if you're in a rush to get a working phone right now just do that and it'll boot right up.

haha yes i read the instructions several times, although it's quite clear, to a newbie it's still very complicated! managed to get through it though and in hindsight that thread is pure awesomeness.
managed to get cm9 working now so will spend some time messing around with it.
thank you for all of your help.
ps. yes i began using gingerbread (stock) but i didn't have a ROM to hand and I wasn't sure if I can just download and install any rom (stock or not) willy nilly without having to do several different things to my phone so i just tried to get cm9 sorted. hopefully won't have to update rom now for some time.
thanks again!!

[Q] What's wrong with the OTA?

I flashed a couple roms on my Nexus S but didn't like them so wanted to go back to stock. So to make sure I get the original update I flashed 4.0.4 on it. I set my phone up and everything and got the notification that there's an OTA. Of course I let it install. Phone shuts down, starts installing, CWM asks me if I want to run the untrusted file, I select yes and get a Status 7 error. What could cause that? Is there a way I still can get 4.1.1 as an OTA or do I have to flash a 4.1.1 ROM?

http://forum.xda-developers.com/showthread.php?t=1572307
Sent from my Nexus S using xda premium

Thanks.

Interesting 1st attempt

Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.

uwais27 said:
Hey guys, I'm new to the community and I just wanted to post my 1st experience with rooting etc and follow up with a few questions!
A bit of background on my device: I've had my NS for just over 3 years now and I just recently decided (when I bought my Xperia V) that I'd like to play around with it a bit. To my knowledge, my device was one of the 1st in the country and a test dummy, and I purchased it from a friend who was working and testing for Samsung at the time. It was not linked or affiliated to Vodacom (who, if I'm correct, was the only network provider to offer the NS in S. Africa) or any other carrier for that matter. So basically due to the lack of link to any carrier, I've never received any updates or notifications to update, and have been running my stock 2.3.5 for 3 years!
Anyway, my story from yesterday was a huge learning experience. I decided that I wanted to root my NS and possibly try out a new kernel before deciding whether or not I wanted to install a custom ROM. I followed this link and managed to root my NS, install CWM recovery and everything was working pretty well using UPDATE-SuperSU-v1.65.
http://forum.xda-developers.com/showthread.php?t=2034264
However I think I flashed the wrong kernel (marmite_v9.1) or for some other reason messed up, keep in mind that I was still running my stock GB which the phone came with. Either way, I was stuck on the Google boot screen for more than an hour. I fired up into fastboot and then recovery, but couldn't boot from there (I just realized that I DIDN'T make an actual backup ). To top it off I wiped the device (another great idea) and the device wouldn't boot into fastboot, giving me a "fastboot mode no boot recovery img" message. Somehow through flashing the CWM I managed to get the device into the correct fastboot mode, and eventually after digging for a few hours I managed to find this (stock?) soju GB ROM download, and managed to flash the boot and system images using fastboot, for some reason " fastboot flash userdata data.img" refused to flash. http://forum.xda-developers.com/showthread.php?t=478820
Anyway, I managed to get back to GB 2.3.5, but get this, after about half an hour on charge, I was given an update to ICS 4.0.4 which I obviously jumped at, and to top it off, I also have JB 4.1.1 available. My NS has finally seen the light of ICS and JB!!
I have a few questions for those who have used ICS and JB though. On the NS, does stock JB provide a notable difference in battery life and speed? With it's hardware, is it capable of handling ICS and JB effectively?
Also, which version of marmite would be compatible with ICS? From what I've picked up, marmite 9.1 is compatible with JB, but is it compatible with ICS too, and if not, can someone please point me in the right direction for kernel(s) which work with ICS (not just marmite).
Second, are the Oxygen and Rasbeanjelly ROMs still up to date? When searching for Oxygen for NS on the forum, the most recent version I find is this which was posted over a year ago: http://forum.xda-developers.com/showthread.php?t=1605273
And this for Rasbeanjelly (among others): http://forum.xda-developers.com/showthread.php?t=2028718
When checking out fitsnugly.euroskank, I don't see anything for the NS. . But maybe I'll consider a shot at the PA and CM ROMs and try them both in a few days
Finally, and this 1 is way over my head, but how does CWM work? If I do a wipe before flashing a ROM/kernel, won't that wipe my backups? Do I need to partition my sd before wiping, or does CWM do that for me, and if it not, does wiping not touch the backups?
Anyway, thanks in advance, and I hope I haven't asked too many questions which have been answered before. If I have, please bare with me and point me to the correct discussion(s) and I'll go bug some other people.
Click to expand...
Click to collapse
Follow the link in my signature for a ROM review... I've heard debates over the best versions for battery life, but JB in my opinion is far superior to ICS... Oxygen is a great ROM, but it won't get more updates and kernels/mods ect.. Are harder to obtain.. It may be a bit challenging to do, but I'd use 4.1.2 JB (follow my chart) or skip to 4.3 JB (Mokee or Slimbean)
Sent from my Nexus S using xda premium

good flashing

uwais27 said:
On the NS, does stock JB provide a notable difference in battery life and speed?
Click to expand...
Click to collapse
Speed yes. Battery life no.
uwais27 said:
With it's hardware, is it capable of handling ICS and JB effectively?
Click to expand...
Click to collapse
There are stutters here and there. You need to overclock to obtain "optimal" ICS and JB performance. JB is smoother than ICS.
uwais27 said:
Second, are the Oxygen and Rasbeanjelly ROMs still up to date?
Click to expand...
Click to collapse
No.
uwais27 said:
If I do a wipe before flashing a ROM/kernel, won't that wipe my backups?
Click to expand...
Click to collapse
No.
uwais27 said:
Do I need to partition my sd before wiping,
Click to expand...
Click to collapse
No.
uwais27 said:
....does wiping not touch the backups?
Click to expand...
Click to collapse
Normally it does not. Unless you select "wipe external sd card"

How to back to stock ICS 4.0.4 from OMNIROM 4.4.4 bigpart?

Hi all,
I am using OMNIROM 4.4.4 bigpart in my old EU Wingray XOOM 32GB but I have lots of performance and stability issues (browser crashes, apps freezing, very slow system....). After reinstalling it I still have problems and I want to check if it's due to the device itself...
To test that, I would like to go back to the stock Android 4.0.4 ICS that I was using in my European xoom before the jump to EOS, CM and OMNI.
Could anybody help me on how to go back to stock? Where to download the stock rom? how to remove bigpart? Is it really required to remove bigpart to install the stock rom?
Thanks for any help given.

The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.

valent|n0 said:
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
Click to expand...
Click to collapse
Thanks a lot for answering.
So... I have to download the original Honeycomb software, "reflash it" and update until I get 4.0.4 or 4.1.2 ...
My doubt is ... do I have to "undo" the "bigpart"? Or will the stock firmware install perfectly in my "bigpart" xoom?
Thanks!

the bigpart issue I am not to sure of

Of course you need to undo BigPart. It's well document in Xoom Android development section of this forum.
You need to flash the non-big-part TWRP (2.8.0 or other), wipe everything, reboot intot TWRP, format Data, wipe everything again, reboot into TWRP again. Then you can flash original image using fastboot.

Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)

machina77 said:
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
Click to expand...
Click to collapse
... Sorry

jkd said:
... Sorry
Click to expand...
Click to collapse
Eh?

I didn't find anything in forum, could somebody help me how can i go back from bigpart to stock partition?

I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.

nomadman said:
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
Click to expand...
Click to collapse
I just flashed mine from omni bigpart back to stock 3.1 cause my 1yr old daughter can't keep her hands off my phone...was time consuming researching how to do it. But it works perfectly...I wound up running some script somebody wrote and it pretty much did everything for me... not in front of my PC at the moment but if you are still fighting it PM me and I'll give ya everything you need...