Hi,
I (foolishly) tried to upgrade to Telstra Defy (build #JRDNEM_U3_2.26.0) to Pays-Rom ([ROM] Pays-ROM Defy v5.1 Froyo with Ginger feeling [3.4.3-11 based!]). I played with it briefly, couldn't get Clockwork Recovery (defy version) to run, and so wanted to go back to the original Telstra soft (from http://and-developers.com/sbf:defy)
I've used RSD Lite to restore that telstra soft before (from Chinese froyo) and it worked fine. However, when I do it now (after having used RSD to apply the 3.4.3-11 Motorola SBF from this thread ) then I get a blank screen - not even a Moto logo - when I try to boot (like this guy I think).
I reflashed back to the 3.4.3-11 Motorola SBF and the phone is booting happily again. However, I don't really want to be stuck on this - particularly since I can't actually get System Recovery (i.e. Clockwork Recovery) to go so can't seem to install Pays-Rom.
The magic question is: by upgrading to 3.4.3-11 from the Pays-Rom pack, have I removed my ability to go back to my original rom? If not, can anyone think what I may be doing wrong with my downgrade to kill the phone?
Cheers.
Was asking why system recovery was not working - answer was because I had failed to disable USB debugging. Oops. Main problem remains though.
If you flashed a full SBF, then you can't go back to 2.1. It's not bad as you think, since 2.2 in every country is about to be released. When this happens you will need only a nandroid backup...
Sent from my MB525 using Tapatalk
I have done a similar thing, flashed 3.4.2_155-002 and now cant downgrade back to the default Telstra rom. Not to concerned at the moment as I am using Color ROM from here, http://forum.xda-developers.com/showthread.php?t=1021742. It is based on this SBF, 3.4.2-155-2 deblur. Just follow the installation instructions and you should have no trouble. Very fast and deblurred. every thing works fine on my Defy, including clockwork recovery.
Only problem I may have is not being able to downgrade to stock if the phone has to go back to telstra for anything.
Hope this helps.
Cheers.
Related
Ok, so i installed one of the custom ROMs available and started using it. However, it always reboots my Desire every time I use my app (sometimes it restarts itself when I'm trying to input simlock code after power up). So maybe (I thought) its a bad flash of the custom ROM. I did full wipe and re-flash it but still no luck.
So i decided to install a different custom ROM (full wipe again before installing) - and it still reboots itself! So now I'm thinking - maybe i did a bad root of my Desire?? What do you think? And should I just re-root again to solve this issue?
NOTE
ROM (before rooting): FroYo OTA (ASIA Region)
Radio: 5.09*
Rooting tool: Unrevoked 3.21
Goldcard?: Yes
Hi, i'm from Argentina, Latin America and i want to change my stock ROM but I have a few questions about it. So i decide to ask first before make a mistake.
My Defy specs are:
System version: Blur_Version6.14.7.MB525.Personal.en.AR
Firmware version: 2.1-update1
Number version: JORLA_U3_6.14.7
Should I use RSD Lite first to flash with the .sbf file an get an Stock ROM with a different number version (mine is JORLA and yours is JRDNEM) and then try Recovery or can i just skip RSD Lite and change mi ROM using Recovery?
My other question is, in case that i can change my ROM, what's the better choice 2.21 or 2.34. And what ROM do you recommend? i wanted to try Vanilla 1.01 or Clean 2.34 blurless Rom jit/deodexd but i don't know, maybe there are better roms.
Well, that's all. Hope you can understand what i tried to say.
Cheers.
If you are not sure what you ARE doing don't do it until you have enough research and knowledge about flashing, rooting or debranding/installing new firmware. Or else your going to become an idiot like me spending 3 days to get my firmware to work correctly.. Each day I bricked my phone, and also had boot loops. So before I went to bed I just used RSD Lite 4.9 to flash a working fresh ROM, because I 2.2.1CN (China) still had bugs and I was still trying to fix it. So when I tried to fix it, it bricked!
But I would use RSD lite 4.9 to flash your desired ROM. I recommend 2.2.1 because 2.34 is more of a test, I THINK it has more bugs. I currently have 2.2.1CN, I have a T-Mobile USA Motorola Defy.
Thanks for your suggestion but i already change the ROM to a Custom one.
I've some experience with RSD and flashing phones because i used to have an Motorola Rokr E2 (Linux).
After all, i did not try RSD Lite only used Recovery and all is working fine.
I'm using Vanilla w/Eclair 1.0.1's HanderExploit. The only issue is that i can't import contacts from my SIM Card.
There's the option to import, but when i press to import it does nothing, can anyone help me solve this issue?.
I can't use Europeans ROM because i have no signal (different GSM band).
Cheers.
At first I had the same problem too, but I opened up the dialer and put familiar phone numbers and some of my contacts displayed on the screen to dial. But they still weren't in my address book. I think I got it working by opening the CONTACTS app from menu. And pressing the four squares ion bottom. And pressing import usim. Then back at the contacts app, at the top pressing all contacts changing it to address book. That worked for me
There's a new Vanilla ROM with Froyo. So it seems that Vanilla w/Eclair 1.0.1 is outdated. I'll give it a chance.
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
xnoruk said:
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Even for me CM7 Beta 6 didn't worked... well but I am happy to be on Leaked Orange GB 2.3.3 with Blur..
It's definitely an improvement on the original ROM! It supports proxy over wifi (although I haven't tried it yet), although GPS + android Market don't work... but I suppose it's much better than having a bricked phone!
I'm also on the leaked 2.3.3 orange rom and everything seems to work great so far (using it for 1 week now).
I've had a problem with the market too in the beginning. The market needs a google account to work and I couldn't add this account to motoblur from the beginning, where you setup motoblur, so the market wouldn't work for me. I did a wipe data/factory reset, rebooted and this time I could add the google account. Not a single bug, FC, reboot or anything like that so far (ok 1 "bug" to be honest, the signal bars stay empty but the 2g, 3g and hdspa indicators work). I've also used gps navigation without problems and the camera too without the fixes in the forum, but you may want to try the fix from walther79 for gps (http://forum.xda-developers.com/showpost.php?p=14046494&postcount=388).
I haven't tried myself but they say it can be downgraded. If you carefully follow this guide (http://forum.xda-developers.com/showthread.php?t=1054447) and use the sbf mentioned in that post you should be able to install cyanogenmod 7 succesfully. Use this guide for flashing: http://forum.xda-developers.com/showthread.php?t=853674
If you want to wipe data and cache before flashing (suggested) you could use clockwork OR the standard recovery (http://www.hardreset.eu/motorola_defy_hard_reset_soft_reset_en.html). Though you should hold volume up + volume down after you see the droid instead of tapping the touchscreen. There is also a chance clockworkmod will work after you've done a wipe data/factory reset.
Ok i flashed the Orange 2.3.3 SBF but my Camera with a red lens don't work and now i have no signal bars so i wanted to go back to 2.2...
Flashed 2.2 but it won't load passed the red Moto Logo, reflashed 2.3.3 Orange and hey ho is working again but how do i go back to 2.2?
I have tried loads of sbf's but same issue remains, tried 2.1 but get a black screen nothing else again flashing 2.3.3 Orange and phone boots...
Can anyone help me get my phone back to 2.2 actually it's my wifes phone and if i don't get it sorted i am so sleeping on the sofa tonight!
AFAIK, flashing full leaked gingerbread sbf would get you stucked without downgradability.
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.4 - XDA Premium
It's cold down here on me sofa
2.3 can already be rooted. Check the 2.3.4 thread. Root and use open recovery to go back to 2.2
Sent from my MB526 using XDA App
Well i got somewhere, i flashed 2.3.4 before you replied but got that rooted, installed 2nd init and the camera mod along with modding the build.prop to get motoblur working and removed the live wallpapers....
End result working 2.3.4 so happy.
Read the Defy Beginner's Guide (very first post), at the end you find how to solve your issue and how to go Back to Froyo. Following a similar procedure you can install CM7.
I had been led to believe that you could not go back to 2.3.4 from 2.3.6. After the problems with my sms contacts here I decided to try and flash a different ROM, first CM7.2 with fixes by shark107 got stuck on the red M logo at the boot screen, tried reflashing and clearing everything. Couldn't sort it so went to recover to MS2Ginger Lite. Accidentally selected the backup for the stock ROM on the 2.3.4 and to my surprise recovered and seems to be working just fine.
Have I entirely misunderstood the concept of not being able to go back from 2.3.6 or is this a little unusual?
2.3.6 can not downgrade only if you flash the full sbf file.
Sent from my awesome Moto Defy: Rooted Gingerbread 2.3.6 - XDA Premium
Right, so I flashed MS2Ginger Lite 2.0 for Defy+. This included flashing the "fixed" sbf supplied by walter79. In Settings>About Phone it then showed Android 2.3.6 instead of 2.3.4 which is what was on it when I got it. I then had troubles with the contacts and SMS so tried flashing another ROM (CM7.2 fixed for Defy+). This got stuck in a boot loop so I went to restore back to Ginger Lite but mistakenly selected my original ROM nandroid.
On another note I have now flashed MS2Ginger 2.1 deblur for Defy+ (working just fine) and Settings>About Phone is now showing Android 2.3.4 and Model Number as MB525 NOT MB526 as it should be????
I've obviously got a lot to learn about all this Android lark. I'm a carpenter so I'm much more used to fixing things by hitting them with a big hammer, I doubt this will help my situation at the moment though.