You could try to restore 2.1 rom and flash 2.51 odr 2.21 bootonly.
We should work on openrecovery it should replace boot.img with signature
[ROM] T-Mobile froyo firmware 3.4.2 leak (new, signed)
- Thread starter Simplestas
- Start date
We should work on openrecovery it should replace boot.img with signature
FYI
Apparently there is an update coming up for the US T-Mobile Defy. They made it availible to for some 500 folks yesterday(I missed it) to do some testing so it should be going public soon. Here's a link to some info about the update. Not a OS upgrade btw so no Froyo with this update.
http://www.motorola.com/staticfiles...Blur_Version.3.6.360.MB525.T-Mobile.en.US.htm
Apparently there is an update coming up for the US T-Mobile Defy. They made it availible to for some 500 folks yesterday(I missed it) to do some testing so it should be going public soon. Here's a link to some info about the update. Not a OS upgrade btw so no Froyo with this update.
http://www.motorola.com/staticfiles...Blur_Version.3.6.360.MB525.T-Mobile.en.US.htm
I had the zip-file here somewhere. However in order to use it you need a T-Mobile US 3.6.190 boot, which I don't have.
Here is a nand backup from this rom: T-MOBILE.US.3.4.2.NAND.BACKUP.rar
- factory resetted
- rooted via SOC
- nothing more
After applying this backup you have to flash the bootonly.sbf posted by bihariel above.
Keep in mind that you can use this rom only when you have/create a motoblur account!
- factory resetted
- rooted via SOC
- nothing more
After applying this backup you have to flash the bootonly.sbf posted by bihariel above.
Keep in mind that you can use this rom only when you have/create a motoblur account!
You can install Launcher2 via a zip --> factory reset --> bypass motorblur
1. Flash T-Mobile ROM
2. registration for motorblur needed
3. root
4. install clockwork recovery
5. copy attached zip to root of sdcard
6. wipe via clockwork recovery
7. install attached zip
Last edited:
I've got the problem that i don't get any mobile connection with my german Defy. The only thing i can do is a Emergency Call.
Any solutions?
Any solutions?
Thank you for the tip but it only worked for a few seconds. Now I've got the same problem like before.
And for everybody who hates branded software: Don't use it. So much crapware. I hope there is a cleaned Version on the way.
And for everybody who hates branded software: Don't use it. So much crapware. I hope there is a cleaned Version on the way.
fantastic, now i have new toys to play withThis is T-Mobile Android 2.2.1 rom 3.4.2 from January 20. Full Blur!
http://www.multiupload.com/ZZ4TU8W7UQ
YOU CANNOT DOWNGRADE AFTER FLASHING THIS FIRMWARE!!!
You need to wipe before flashing!
Source is some guy at russian forum. He seems to have phone with unlocked bootloader and t-mobile developer network access
I am not responsible for this.
Okay, it could be a noob question, but: if I'm restoring this nandroid backup and applying the bootonly.sbf, can I go back to 2.1? Or is it just the same as flashing the ROM via RSD Lite?
I would try the defy_2.2_boot_only.sbf pulled from the china rom file and not the boot only pulled from this rom and see if they work together. That way if they work you can revert back if you have to use the boot from this rom them you will be stuck at that firmware like the 2.51 firmware.
So the point is to keep away my Defy from t-mobile bootonly.sfb.
I'm afraid this nandroid backup won't work with chinese bootonly... But I'll give it a try, downloading now.I know how to use superoneclick. I was asking if it worked on this ROM. But thanks for the link.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone