Hey there,
I´ve got a problem with rsd light (5.3.1) recognizing my Defy. It always tells me that my device is just an Omap3630. I have installed all Motodrivers (5.1) and tried various versions of Rsd light....
I have no idea how to proceed. I´m currently on Froyo 2.2.2 DACH and wanted to update to Cm7 but without loosing downgrade ability...And that´s why i need rsd light. I´m on Win7 64bit.
Please help me :-(
Edit:
Just installed USB Dev. drivers und activated usb debugging and it worked ! But as soon as I boot into Bootloader rsd keeps telling me Omap3630 ... Where´s the problem ?!
OK USB debugging works when system is booted and Rds says MB525. But can I flash in this Situation with phone booted ?
i am always flashing ...it doesnt matter...after flash it will show either MB525 or MB526.
you are good to go.
Hm okay ...
Assuming that i come from 3.4.177.3 and will flash cm7 nightly. Will I be able to return to previous version i had, with a backup i created with Systemrecovery ( nandroid) ?
Klin03 said:
Hm okay ...
Assuming that i come from 3.4.177.3 and will flash cm7 nightly. Will I be able to return to previous version i had, with a backup i created with Systemrecovery ( nandroid) ?
Click to expand...
Click to collapse
Yes, you can also flash a full sbf of froyo instead of fixed sbf + nandroid.
The only thing you have to do is wiping data/factory reset from stock recovery just before flashing froyo, when you want to remove CM7 ( but probably you won't do it ).
Related
Hi there
Ive had my defy for a few months and i think it is bricked. it will not turn on and when plugged into a computer the white led shows. Rsd recognises it and i can flash it, but after flashing it it still does not boot. I cannot get into bootloader or recovery.
I was using my friends fully charged battery..
P.S:im in the uk
Please help
Charlie
What rom have you been using ? It looks like you have flashed 2.21 or 2.34 while you had had 2.51 before or you was trying to direct downgrade from 2.2 froyo to 2.1 eclair.
Use another sbf for the flash maybe that is the problem
Sent from my MB525 using Tapatalk
choudu1 said:
Hi there
Ive had my defy for a few months and i think it is bricked. it will not turn on and when plugged into a computer the white led shows. Rsd recognises it and i can flash it, but after flashing it it still does not boot. I cannot get into bootloader or recovery.
I was using my friends fully charged battery..
P.S:im in the uk
Please help
Charlie
Click to expand...
Click to collapse
Make sure you use a compatible boot/devtree loader. Try the 2.1, the 2.51, and the Tmobile 3.4.2-107 available elsewhere on this board.
It's nearly impossible to brick the Defy.
Not to hi-jack the thread - just don't want to start another one for an identical issue. I am running into exactly the same problem though I have the USA version - not UK.
Here is what I did:
To start, I had the stock USA ROM (My wife has the same phone so I can get specific details on stock build after I get home from work, if needed)
1. Rooted with superoneclick
2. Installed Custom Recovery (http://forum.xda-developers.com/showthread.php?t=875233)
3. Installed Milestone Overclock & Overclocked
4. Made backup to my SD Card of current image (using SW from step 2)
5. (On PC) Installed RSD Lite
6. Downloaded 2.34.1 Central Europe ROM (.sbf) and copied into Prog. Files for RSD Lite. Device showed up in RSD Lite so I clicked “Start.” RSD Lite created image, then copied image over – phone display changed to saying “SW Loading” or something like that. When the load finished executing, the phone went to reboot and all I got was the same little white light (up by the presence sensor) that was on steady for the phone – appears to be bricked. I was still able to access bootloader mode last night so I tried flashing other ROMS – (two others to be precise) – but to no avail. Now (next day) I can’t get RSD Lite to recognize my phone – the battery was kind of low so maybe it died and having it plugged in via USB is not charging it?
Un-bricked!
Charlie,
Don't know if you were able to get your phone back yet, I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
basically i it flashes fine. i got a new battery for it. on rsd lite it says "pass" but the phone does not boot i cant get it into bootloader or recovery
I have my phone in similar situation, I was trying to update to Froyo/( KR 3.4.2-72) from stock german eclipse (2.51) and now i am with a white LED when i power on.
I flashed many roms 3.4.2-xxx......and stock 2.51 with RSD lite 4.9, it shows finished but doesnt restart itself, it stays with the white LED.
SWDL.txt shows
04/20/11 02:40:35 000012fc Phone.cpp 451 0 ERROR Generic failure when sending command.
04/20/11 02:40:35 000012fc Phone.cpp 1557 0 ERROR GetPhoneID failed: ERROR.
and sometimes
04/20/11 02:45:11 00000230 Phone.cpp 451 0 ERROR Generic failure when sending command.
04/20/11 02:45:11 00000230 Phone.cpp 1767 0 ERROR GetDRMVersion failed: SendTC failed: ERROR
Is it because the bootloader is corrupt? or ??
Can someone provide with a defy booatloader? and is it sufficient to flash this loader by rsdlite?
Thanks a lot!! (btw i have enough battery from a friend)
The problem is the boot loader version. You cannot use the froyo kr build on top of 2.51 eclair.
You have always to flash sbf which have more recent bootloader, or otherwise use nandroid backups and fixed sbf. You can find a sticky post in the development section
Sent from my MB525 using XDA App
and use the latest RSD Lite to flash!
Mcdomms said:
The problem is the boot loader version. You cannot use the froyo kr build on top of 2.51 eclair.
You have always to flash sbf which have more recent bootloader, or otherwise use nandroid backups and fixed sbf. You can find a sticky post in the development section
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Thanks a lot! I learnt the above as a lesson!... not on (nearly)stock rom... but after one week of brick like situation. Accumulated some guts.. will try nandroid backup od froyo kr...
Thanks for the help guys. But I took my defy back to cex. They sent it off for repair and apparently they could not fix it so now I got a milestone as a replacement. Well at least now I can enjoy gingerbread on cm7
Sent from my Milestone using XDA App
Hi there, I'm having some trouble flashing my Defy. Here's what happened:
1) Bought my phone today. Installed a couple of apps (Foursquare, Twitter client, 1 or 2 others).
2) Rooted, then installed 2nd Init. Reboot twice, 2nd Init was working fine, I was able to get into ClockWorkMod Recovery with no trouble.
3) The main reason I wanted to flash a new ROM was to record videos at 720p, using Hancock's ROM 720p port. So, decided to get Barebones v1.5.
4) In the thread, it says: "If Your Coming From An Eclair Build Please Flash The Korean sbf, 3.4.2_74-Stock.KR_BLUR.sbf, Beforehand"
5) Downloaded and flashed the SBF using RSD Lite (already had Motorola's drivers and Android SDK installed, so no trouble here, too).
6) Flash the mentioned SBF with apparently no issues. But, when RSD reboots the phone, it simply shows nothing on the screen, nor does the screen light turns on. It looks like the phone is off, it simply does not boot.
7) When plugged to PC, RSD still recognizes the phone. Tried to flash the SBF again, with the same results (when RSD is flashing the SBF, the screen turns on with the "FW Update - In progress" message). RSD is still recognizing my phone, so I'm still able to flash SBFs.
So, what should I do? It looks like my phone is in bootloader (since RSD is recognizing the phone), but with screen/screen lights off. Should I try another SBF? Is my phone bricked? Thanks for your help!
P.S.: Some useful information: I'm not new to the ROM Flashing universe. Had been flashing my phones since I had a SonyEricsson K550i, at late 2008. Already flashed some ROMs to my HTC Magic, but it has none of these downgrade-locks or any stuff like these. So, I'm completely able to follow instructions on ROM/SBF/whatever flashing, and I'm 100% sure I followed all the instructions correctly.
I am facing the same situation after i flashed my defy to 3.4.2-155 deblur: I try to flash it back to China retail version, which is its original rom, but it happened the same thing, black screen, even RSD cannot recognize. The thing i do is flash the 3.4.2-155 twice, though mine cannotbe flashed back, but it is no longer brick now. Hope my experience could help.
Sent from my MB525 using XDA App
mys_721tx said:
I am facing the same situation after i flashed my defy to 3.4.2-155 deblur: I try to flash it back to China retail version, which is its original rom, but it happened the same thing, black screen, even RSD cannot recognize. The thing i do is flash the 3.4.2-155 twice, though mine cannotbe flashed back, but it is no longer brick now. Hope my experience could help.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Thanks for sharing, bro. Got the situation under control here, just flashed an american SBF and got things working. I think I just got a corrupt download or something like this.
on tinhte.vn, in my country Vietnam. Google search
"It's cause of the update a couple of weeks ago. You just need to find the leaked 2.2 t-mobile sbf. Flash that with rsd lite and it will boot right up. Just google leaked 2.2 defy sbf and you should find it. Make sure you extract it and point rsd lite at the actual sbf file and after about 10min. All will be well. "
vuhothang said:
on tinhte.vn, in my country Vietnam. Google search
"It's cause of the update a couple of weeks ago. You just need to find the leaked 2.2 t-mobile sbf. Flash that with rsd lite and it will boot right up. Just google leaked 2.2 defy sbf and you should find it. Make sure you extract it and point rsd lite at the actual sbf file and after about 10min. All will be well. "
Click to expand...
Click to collapse
Thanks, man, already solved my problem flashing a different SBF. Now I'm up and running on Barebones v1.5 with 720p video recording
In case of stuck in startup
try
Pull battery,
put battery back in holding the VOL-Down until the android pops up...
press VOL-Up and VOL-Down at the same time.
Next screen is for wiping and updating.
Wipe Data/Cache
K3n H1mur4 said:
Thanks, man, already solved my problem flashing a different SBF. Now I'm up and running on Barebones v1.5 with 720p video recording
Click to expand...
Click to collapse
hy..can you please post some screenshots on barebones..thx
I've tried several sbf now. But no one works. RSD lite shows "finished" and "pass", but the Defy stays dark. No reaction on pushing the power-button. only rds lite still recognizes it. any ideas?
The only sbf that works for my Defy is the following one for Defy+ http://forum.xda-developers.com/showthread.php?t=1385868
This means you have flashed a SBF that is not allowing a direct downgrade (flashing another SBF with wrong CG codes => Defy won't boot). Unfortunately at the moment there is no workaround to go back to Froyo or other GB versions that have CG31,CG35,CG39 code lower than 6 and CG47 lower than 3.
This happens wen users are not paying attention to warning messages.
Have you wipe DATA/cache before flash the SBF?
Use the latest driver and RSD.
BL=?
Few days ago I moved from HTC Desire to Defy.
I did root it, installed 2ndInitRecovery. After rebooting I couldnt get defy booted from 2ndInit and ended upu bith black screen. Still dont know why but I uninstalled 2ndinit and ended up stuck on motorola logo, I still can get into bootloader thou.
When tried this solution:
http://android.modaco.com/topic/324...ering-bricked-firmware-on-your-motorola-defy/
RSDLite can see phone connected but there is no info about it (IMEI etc)
and updade doesnt start.
Anyone to help?
if you are on eclair froyo or leaked gingerbd try to set normal boot on sndinit
trouble is that I uninstaled 2ndinit recovery
if rsd can still see it and u can get into bootloader just flash a different rom onto it,i had similar and then flashed the uk 2.2 retail it came str8 back to life!(then i installed CM7...)
miguelsanchez79 said:
Few days ago I moved from HTC Desire to Defy.
I did root it, installed 2ndInitRecovery. After rebooting I couldnt get defy booted from 2ndInit and ended upu bith black screen. Still dont know why but I uninstalled 2ndinit and ended up stuck on motorola logo, I still can get into bootloader thou.
When tried this solution:
http://android.modaco.com/topic/324...ering-bricked-firmware-on-your-motorola-defy/
RSDLite can see phone connected but there is no info about it (IMEI etc)
and updade doesnt start.
Anyone to help?
Click to expand...
Click to collapse
What version of RSD Lite are u using??
I had the same problem no IMEI or other info only N/A when i used the latest RSD Lite problem was solved.
Win 7?
I have been through the same problem and was wondering what os you were using?
I had very little success with win7 x64, I had to get virtualbox and create a win XP virtual machine to make it work.
Also, in order for RSDlite to see your phone, you have to turn the phone on while pressing the volume up button, that'll get you to the bootloader and then RSDLite will see it.
I suggest you use this SBF: JRDNEM_U3_3.4.2_179-002, it is the CEE one and I found it was the easiest SBF to allow custom rom and such (linky)
I hope that helps.
Good luck!
RSD have never seen my phone (i mean model, IMEI etc) but it still worked without any problems
Im using 5.3.1 version. The only info I got is
Bootloader version: v0x000910
Ap Die ID: 18100005cdf767010000dcff0200
Rest of details is N/A
Status: connected.
rak500 said:
I have been through the same problem and was wondering what os you were using?
I had very little success with win7 x64, I had to get virtualbox and create a win XP virtual machine to make it work.
Also, in order for RSDlite to see your phone, you have to turn the phone on while pressing the volume up button, that'll get you to the bootloader and then RSDLite will see it.
I suggest you use this SBF: JRDNEM_U3_3.4.2_179-002, it is the CEE one and I found it was the easiest SBF to allow custom rom and such (linky)
I hope that helps.
Good luck!
Click to expand...
Click to collapse
Thanks for your suggestions. Im using xp (had to find one as Im using linux distros). I will have another go.
miguelsanchez79 said:
Im using 5.3.1 version. The only info I got is
Bootloader version: v0x000910
Ap Die ID: 18100005cdf767010000dcff0200
Rest of details is N/A
Status: connected.
Click to expand...
Click to collapse
As long as the phone shows up in the device list on RSDLite and that you can put your Defy in bootloader mode, you should be good to go.
RSDLite never gave me accurate details about the phone when I had these issues but I was always able to flash SBFs.
I did manage to flash SBF and root my defy. The only problem is that I cant download anything from market.
Any suggestions?
If you try to download from a GPRS or 3G network, disable the download from wi-fi only tab from settings and data management.
miguelsanchez79 said:
I did manage to flash SBF and root my defy. The only problem is that I cant download anything from market.
Any suggestions?
Click to expand...
Click to collapse
Allready signed out of google talk and then sign in again?
miguelsanchez79 said:
I did manage to flash SBF and root my defy. The only problem is that I cant download anything from market.
Any suggestions?
Click to expand...
Click to collapse
Go to recovery wipe cache/data
Sent from the Nerd Herd using Tapatalk
Go on the CM7 thread. End of first post and download the latest google apps from there, reboot in custom recovery (CWM recovery or SndInit recovery) and flash the zip.
Re. your bootloop problems:
did you turn off usb debugging after installing Sndinit and did you reboot 2 times (1st boot --> normal then 2nd at blue led, volume down?) ??
If you would have followed the FAQs of CM7, you would have had no such problem....
The current situation with my Defy
was using a rooting 3.3.11 uk froyo version some thing happenned to my defy last night the battery wont charge any more
1 Major issues is Micro usb port isnt working tried to format the cell Via RSD LITE 4.9 in bootloader but windows detects the device as a UNKNOWN devices no RSd lite is not the way to bring back my phone
So All i need is a 2.2.2 SEa OFFIcal UPdate.zip to be flashed via Stock recovery or else plz guide me if there is any other way to recover my Defy
my Cell is in warrenty too but i rooted it and installed CM7 earlier and my M logo is replace with the google CM7 logo so plzz help help me with the logo restoration for the stock recovery
pritesh_100_in said:
The current situation with my Defy
was using a rooting 3.3.11 uk froyo version some thing happenned to my defy last night the battery wont charge any more
1 Major issues is Micro usb port isnt working tried to format the cell Via RSD LITE 4.9 in bootloader but windows detects the device as a UNKNOWN devices no RSd lite is not the way to bring back my phone
So All i need is a 2.2.2 SEa OFFIcal UPdate.zip to be flashed via Stock recovery or else plz guide me if there is any other way to recover my Defy
my Cell is in warrenty too but i rooted it and installed CM7 earlier and my M logo is replace with the google CM7 logo so plzz help help me with the logo restoration for the stock recovery
Click to expand...
Click to collapse
its not bricked as far as my knowledge .....
go to recovery wipe cache /data and wipe dalvik cache......
and go to bootloader and check rsd lite ...did it detected it ....use rsd lite 4.9.....
if dis doesn't work ....after above install a fresh nightly build of cm7 ....and then check ......
do this if you more than 70pc battery .....or you can try on luck.......
if battery dies out buy a universal charger to charge ....and then start over......
its hard to brick defy.....don't worry
jassi32 said:
its not bricked as far as my knowledge .....
go to recovery wipe cache /data and wipe dalvik cache......
and go to bootloader and check rsd lite ...did it detected it ....use rsd lite 4.9.....
if dis doesn't work ....after above install a fresh nightly build of cm7 ....and then check ......
do this if you more than 70pc battery .....or you can try on luck.......
if battery dies out buy a universal charger to charge ....and then start over......
its hard to brick defy.....don't worry
Click to expand...
Click to collapse
okk.. thankz,.. i will try that 70% thing and connect it to my PC hope it detects the motorola flash interface Any other assistance will e helpfull too
Can any 1 giude me through for making update.zip ( which can work in stock recovery ) from a SBF/ nanroid backup SEa 2.2.2
pritesh_100_in said:
okk.. thankz,.. i will try that 70% thing and connect it to my PC hope it detects the motorola flash interface Any other assistance will e helpfull too
Can any 1 giude me through for making update.zip ( which can work in stock recovery ) from a SBF/ nanroid backup SEa 2.2.2
Click to expand...
Click to collapse
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 [32bits] [64bits]
Now to Business:
To Flash full SBFs, this 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, is basically the same but you need to Wipe Dalvik Cache and Data before flashing. Then after flashing you need to enter inmidiatly to Recovery and restore the matching Nandroid Backup. I won’t write a specific way to do it here, since most of this version require different steps (for Example CM7 or MIUI), so is better so check for the guide for your Custom ROM, or specific Android version.
How do I enter to the Recovery?!:
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.
How do I enter to the Bootloader:
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.
Hi,
I have one Defy M525.
I was using the Froyo 2.2.2
JRDNEM_U3_3.4.2_179-6.1_BLUR_SIGN_SIGNED_USAJRDNEMARAB_HWp3_Service1FF .sbf
Then i flash the new Gingerbread:
CM9-NIGHTLY-120317-Defy.zip
+ CM7_Kernel-signed.zip
and gapps-ics-20120317-signed.zip
Its ok here.
I realise that i need to go again to Froyo with blur to import all my contacts on my Blur account and i did this:
Wipe data/factory
Wipe Cache
Then with RSDLite5.6 i flash one firmware.sbf (fixed SBF), i think i did a mistake here but the phone still work with cyanogenmod.
Then with RSDLite5.6 i did the full SBF flash of:
Android 2.3.3 "Gingerbread" !!BETA!!
4.5.1-112 Orange GB Blur
(shadow-112_ORANGE.sbf)
After the process was completed and appear "PASS", the phone normally restart in this fase. The phone was down and never wake up.
I had good battery level in that moment.
Now my Defy is off and i try turn on and NOTHING happens.
Try turn on with Power up and buttom up (+) to enter on bootloader mode to flash again but NOTHING happens.
There is any chance of some serious prob happens flashing this ROM?
On last flash there is any chance of battery goes out?
Someone can help me?
THANK YOU!!!
Try to flash the first sbf that you flashed....
Herpderp Defy.
EmoBoiix3 said:
Try to flash the first sbf that you flashed....
Herpderp Defy.
Click to expand...
Click to collapse
I guess u did not read 100% my post (or my english is bad
My phone is dead and i just can't turn it on to flash anything.
Big light.
I start read "Defy bricked" posts and i found it:
http://forum.xda-developers.com/showthread.php?t=940119
Then i read this "...If I fire up RSD Lite 4.9 and plug in the phone, it does recognize something."
Was the light. I started RSDLite and connect the phone to PC and the RSDLite recognize the phone. .
I flash again my last good ROM:
Froyo 2.2.2
JRDNEM_U3_3.4.2_179-6.1_BLUR_SIGN_SIGNED_USAJRDNEMARAB_HWp3_Service1FF .sbf
and the same happens but at least i have access to my Defy via RSDLite.
The phone was restarting but nothing happens like the last time after flash de 2.3.3 Orange 112 sbf.
Now i have access to bootloader. I flashed the fixed SBF 2.3.4_4.5.1 134.
I try to turn on the phone or enter in CWM but doesn't work.
The phone go direct to Bootloader and appear the errors:
Bootloader
09.10
Err:A5,70,39,00,27
As i had Gingerbread 2.3.6 vers. installed i guess my solution is do one Full SBF flash with 2.3.6 but i have M525. Can i do it?
Some ideia now?
You have messed up a lot of stuff! Just stop there, for Christ sakel!
You should have never flashed 2.3.3 and 2.3.4 full SBF's as there is no downgrade after that. However, if you flash 2.3.6 full SBF, you won't be able to even root your Defy as BL7 SBF's are still unrootable.
Flash the 2.3.4 SBF that you have already flashed, then if phone doesn't boot, just open stock recovery and wipe data/cache and dalvik.
Auris 1.6 vvt-i said:
You have messed up a lot of stuff! Just stop there, for Christ sakel!
You should have never flashed 2.3.3 and 2.3.4 full SBF's as there is no downgrade after that.
Click to expand...
Click to collapse
Yes, i realise that too late. I made a full sbf 2.3.3 flash with
4.5.1-112 Orange GB Blur (shadow-112_ORANGE.sbf )
I will flashed the 2.3.6
ROM 4.5.1-134-DFP-132 - O2-Germany full Blur
and its done.
The phone is on fire again.
Thanks!!!!