Database Users

[Q] Really Bricked Defy

Current Situation:
When I say bricked, I mean BRICKED in all caps. The phone is completely unresponsive. If I try to turn it on – no good. If I try to put it in bootloader mode – no response. If I hold the volume button down and depress the power – no menu displays. I get no ‘M’. I get nothing. Except…
If I fire up RSD Lite 4.9 and plug in the phone, it does recognize something. Under model it displays “S Flash OMAP3630”. If I load up an sbf file (I’ve been following Higgsy’s incomparable “How To” guide - http://forum.xda-developers.com/showthread.php?t=853674 and using the generic UK sbf file he recommends) and depress “Start” within RSD Lite, the phone will display “SW Update In progress…” in white blocky text. RSD Lite says it’s executing and, after several minutes will display a Status of “Finished” and a Result of “PASS”. On the phone, the screen goes dark but a white notification light displays. While the phone is still plugged in, I can depress the power button on and off and RSD Lite will recognize it’s there (if it’s on) or not recognize the phone is there (if the power is toggled off).
Note that the battery is fully charged.
I’ll give you a little background info:
Background:
I purchased Defy phones for my wife and me for Christmas. Her’s is working fine, is unrooted, and has only a few apps beyond stock (Angry Birds of course!). But of course I had to play with mine. All went well until I (stupidly) installed the latest T-Mobile update which removed my root access. This was not acceptable to me as I had overclocked my phone for performance purposes. I had a really hard time getting root access back until I at last found a version of SuperOneClick that did the trick.
By this time I had reset the phone back to factory settings. So I thought “Well, I might as well flash some cool ROM”, so I flashed a Gingerbread themed Froyo cooked up for the Defy. Unfortunately, it didn’t work (for whatever reason). I was stuck at the dreaded ‘M’.
Next I started following Higgsy’s guide (as mentioned above) but I guess I screwed something up because now the phone is totally unresponsive except as detailed above.
So where do I go from here? Some possibilities:
Flash T-Mobile 2.2 test sbf?
Link?
Flash Original SBF?
Link?
I’ve still got my wife’s phone which is working perfectly fine. Is there a way to copy files from her phone to my dead phone and get some life?
Do you guys have some other steps you’d recommend?
I’d really like to get my phone working again and would much appreciate the help. Many thanks in advance.
(Note that I’m a Noob so please don’t assume I know anything!)
(Yet another note: I'm in the USA.)

Which .sbf's and in which order did you install them?
The same happened to me after I'd flashed the 3.4.2 sbf, then tried to downgrade back to 2.34. it went blank and I had to reflash 3.4.2 again.
If you've flashed 2.51 or 3.42 then you can't downgrade from them. So the fix would be to flash the same rom again.

I have the same problem and this how i fix it
1.http://forum.xda-developers.com/showthread.php?t=892026&highlight=low+battery your phone will show in rsd lite
2.flash http://forum.xda-developers.com/showthread.php?t=933555 with him you get a error that can not be installed
3. disconnect phone from USB and remove the battery
4. Replace the battery in the phone and power up, and phone immediately go into the bootloader
5. Flash bootonly http://forum.xda-developers.com/showthread.php?t=899450
6. and finaly flash http://forum.xda-developers.com/showthread.php?t=922430
it works for me
sorry for bad english

Solved
I flashed http://forum.xda-developers.com/showthread.php?t=922430 per your suggestion and I'm now up and running. Thank you.

Motorola Defy bricked
hi
i have a question about my defy. The white led is still shining but there is no connection to the pc. I connected via USB-cable.
pls HELP!!!!!

I have a similar issue as the OP..
I originally rooted the phone using simpleoneclick... then I overclocked it using setvsel...
it was running fine for an hour or so, and then I ran quadrant (several times over the course of the hour) and the final time, it rebooted during the middle of a test, and then it would just keep looping the bootup moto logo and "android" screens.
at that point I could still enter the bootloader and recovery screens. I tried wiping data and resetting to factory defaults with no avail.
Finally I followed a thread on flashing a new rom to the phone with RDSLite and the uk rom. After getting it to finish flashing and it showing a 'Finished' and 'PASS' status as the OP mentioned, te phone now no longer responds. Power button does not trigger the screen to go on, regardless of if I try to press the volume buttons with it or not.
The only response I get from it is when it is connected to the computer, the white led turns on, and the computer (and rdslite) recognizes it. I can still flash it with rdslite and the screen turns on displaying the SW update In progress message...
but that's about all I can get it to do.
Any help and advice would be greatly appreciated
edit: I should also mention that after the uk 2.21 rom I've also tried the china 2.2.1 roms.... Should I also try flashing the 2.51 uk version as well?

Okay, I tried a few more roms and this one "JRDNEM_U3_3.4.2_117-00..." has everything back up and running...
however now i'm running into the issue of apps that i've 'downloaded' not actually installing...

bricked
same problem here. rsd can detect my phone but still failed flashing. i changed and renamed the /sbf but still doesnt work... please help

MB525 Defy Bricked
MB525 Defy bricked and rsd cannt detect my phone failed . ... please help
its dead. Actually i uninstalled busybox and in this process all the system files also deleted by busybox. now phone is not starting. if anyone can suggest. I was using MIUI rom. can any one make it alive again.
[email protected]
. ....please help

Same problem here, but my phone is only detected by a friend's laptop. I think I have to flash Defy+ rom

try to flash sbf use rsd

If your phone is detected by RSD Lite, then you have an easy fix in just flashing a new sbf. If it's not detected and you can't charge your battery, you're going to have to use the MacGyver method.

if sbf doesnt work u better send it to warranty

Well. On my computer the phone isn"t even recognized. Maybe because some RSD Lite files are missing and it need them to detect bricked defy (i did reinstalled RSD Lite)

If it's recognised on your friend's computer but not on yours then it means that you probably have the versions of the motorola drivers or rsd lite that have problems.

white led solution
hope for defy with only white led light turning on. This assumes that you have already have mototola drivers and RSD lite installed.
Background : I only had defy one day when I decided to flash it with miui. I bricked on the first time with bootloops. Did research and got drivers and rsd lite. managed to find three stock t mobile roms and flashed to stock Tom, then flashed miui, since then I've been switching between miui and cm7.
Problem : After a few months of use, I decided to flash stock rom to see how the battery life would be like. Bricked it the first time with bootloops. I thought I had flashed it with wrong rom because the first time I flashed back to original rom I did not delete the roms that I thought were the original roms. So after first failure I tried to flashed with the other roms I had. after the third rom it would not go into bootloader, only white led would turn on. Tried macguiver, did not work so save your usb cable, don't mess with it ain't gonna work.
Two part solution: I realized that when I plugged phone with usb I would hear the usb tone on win 7. When to device manager and saw the other device or something like that was appearing and disappearing when I would connect and disconnect phone. I clicked it and it said Motorola device or something like that, it was sensing my defy! defy drivers were wipe out due to bad flash. I had mototola drivers so I clicked on update and searched for mototola drivers on hard drive. I had rsd lite on and it recognized the defy after driver update, even though the bootloader screen was not on and just the white led was on.
decided to flash rom that have me bootloop and it flashed it but still gave me a bootloop., by the way, the update part of bootloader showed up after a while.
Second part of solution: googled problem and found out that the phone has a stock recovery. its the robot with the triangle exclamation mark. when you get to it you have to touch the extreme lower right hand corner of the screen to get to where you can wipe data and cache. when you start wiping data / cache you have to press on ok?? on lower left hand of the screen repeatedly until wipe is complete. then reboot and tada it boots up to stock tmo USA defy.
this is the stock rom I used : JORDN_U3_6.36.0
F Y I
if you ever try to flash a rom and it just bootloops, just go into stock recovery and wipe data and cache and you should be able to boot into android.

I'm Mc Gayvering my phone. Just tried a led directly connected to USB and fried it
This is my last hope

Is your phone worked?
I have the same problem. I try many ROM,But all of them dosn't work.
When I put in the battery,it shows Bootloader,When i flash a ROM use RSD，the phone always display SW Update In progress... Then the RSD's status is error verifying code group XX(XX=32/33/39/40 etc.) checksums.
What should I do?
THS.

Help :mad :
Hello, I'm having a problem with my Motorola Defy, he is not popping no FBS. he is not linking a black screen, but the white light is on, but when I try to install the SBF appears SW Uplidate im Progress .. can someone help me

wesleybinho said:
Hello, I'm having a problem with my Motorola Defy, he is not popping no FBS. he is not linking a black screen, but the white light is on, but when I try to install the SBF appears SW Uplidate im Progress .. can someone help me
Click to expand...
Click to collapse
dude this is all same **** u flashed wrong sbf.
flash the sbf service flash higher or same version which came by default wid ur phone.
flashes here http://and-developers.com/sbf:defy

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

[Q] ERR:A5,69,35,00,27 after SBF

This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!

It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App

Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.

what rom was the phone running when you had the original issue?

Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.

I have the same Problem with my Defy+ what can i do?

I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.

Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.

Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.

Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!

Motorola Bravo HARD BRICKED

Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens

ssfirme said:
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
Click to expand...
Click to collapse
Press both volume buttons on the screen with the android and exclamation mark. That'll take you to stock recovery where you need to wipe data and factory reset.
If you have to flash the sbf again, try using sbf_flash on Linux. It'll flash in times where RSD won't recognize your phone.
Linux Live\sbf_flash tut
sbf_flash binary is in attachments
Only use Defy 2nd-init for recovery
(and once its installed, steal /system/bootmenu/* and /system/bin/bootmenu from Defy CM9 from June 5th on up -- touch bootmenu is pretty awesome; replacing the bootmenu isn’t for the feint of heart.)

the only problem is i dont have linux i have windows 7

Use rsdlite sri I don't have a link on me
Sent from my Galaxy Nexus using XDA

Had same type of problem on Friday. Followed this post http://forum.xda-developers.com/showthread.php?t=1559109 now I'm back up and running.

ssfirme said:
the only problem is i dont have linux i have windows 7
Click to expand...
Click to collapse
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.

ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone

yes i have it in bootloader mode

Did you install everything before plugging phone in?

Try uninstalling everything motorola related and reinstalling just the drivers....On a previous Win7 install nothing was recognized, but on a reinstall of the entire system it worked fine and still does. I still recommend the Linux way over RSD because it will flash your phone regardless, provided you can access the loader.
I still haven't gotten native tethering to work with Windows, but then again, I quit trying sometime around December or January.

ssfirme said:
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
Click to expand...
Click to collapse
This is for all those people who are having trouble flashing with RSDlite in Vista & WIndows 7.
If I am right, RSD lite does not seem to recognize the sbf file after you select it and instead the "start" button remains grayed out.
If that's the case, here the solution:
I had a similar problem and sucessfully used the command line parameters for RSDlite to force a flash. I managed to get a signed/unsigned firmware installed.
You need to copy the firmware you want to flash into the RSDlite directory in your program files folder.
Make sure you are in bootloader mode first.
Then, open command prompt and "cd" to the RSDlite directory
eg:
> cd C:\
> cd Program Files
> cd motorola
> cd RSDlite
>
now for the flashing type:
> SDL.exe -f xxxx.sbf -t 2
where xxxx.sbf is the firmware you are flashing to the phone.
flashing will begin shortly afterwards.
It worked for me, but in the end, show FAIL STATUS.

skeevy420 said:
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
Click to expand...
Click to collapse
Thank you sooooooooooooooooo much!
After several hours of messing with my brothers Bravo, I finally got it working by following your instructions.
Really: I'm speechlees man.

hard bricked my phone
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes

dzdonce said:
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
Click to expand...
Click to collapse
Not sure if this will help since I did not watch the video myself, but a quick Google search gave me a video describing how to take a Motorola USB cable and modify it to unbrick a phone. I did not watch the video yet so I don't know how relevant it is to your problem. But just by looking at the video preview it looks like the difficulty level may be pretty high... Here is the link:
http://m.youtube.com/watch?v=XwwI_6doBWk
Sent from my LG-D415 using XDA Free mobile app

[Q] I broke my Tf101

Hello everyone This is my first time posting so I hope this is in the correct spot.
I have a Transformer TF101.
I rooted it months ago and can not remember what method I used.
I installed CyanogenMod 10 and everything was fine.
I did an update to one of the nightly builds and now my Transformer is stuck in CWM.
When I plug it into my Windows 7 pc it comes up with a unknown device code 43. I have tried it on several other devices having vista and xp and the same thing happens.
For the heck of it I tried placing the stock FW on the SD card but the transformer does not see it.
I tried placing it in adb mode but the pc still comes up with unknown device.
I have factory reset, wiped cache, and delvik, it is just stuck on CWM.
Can anyone help me with this or did I just totally break the thing? Thank You.

what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager

Broke my TF101
scottyf79 said:
what did you use to flash the rom?
Try doing a cold boot......volume down and power (like you would to boot into recover) but release the keys when the white writting comes up on screen and press nothing.
use v+ and v- to toggle and select the Android or let it kick in itself.
sounds like youve used rom manager [/QUOTE
Thank You Scotty: That did get me back so it boots up. None of my computers will see it. Wondering if maybe the cable took a dump. I did use rom Manager. At this point I would like to bring everything back to stock and start over. Any suggestions on how to bring back to stock with sync cable not working?
Click to expand...
Click to collapse

best just to get the sync cable and use one of the tools available to make sure it gets done right.
just dont use rom manager bud.....:good:
try this to see if you can fix the recovery loop
Recovery Loop fix with terminal emulator