Database Info

Motorola Backflip MB300 BIG PROBLEM

Well hello everyone to start off, i was trinketing around with rom manager and i think i flashed the original droid recovery and 2.5.0.1 into my phone on accident. now when i try to start the phone i get a white M and thats it tryed to boot into recovery only thing i can get to is the holding power and j and d down to get the usb flash init screen which is blue. can someone direct me in the ways of the force and help me bring this phone back to life or am i screwed? I have the j_rodd recovery image on the sdcard but adb wont pick it up as a device.

It is same with me...
Diremaker35 said:
Well hello everyone to start off, i was trinketing around with rom manager and i think i flashed the original droid recovery and 2.5.0.1 into my phone on accident. now when i try to start the phone i get a white M and thats it tryed to boot into recovery only thing i can get to is the holding power and j and d down to get the usb flash init screen which is blue. can someone direct me in the ways of the force and help me bring this phone back to life or am i screwed? I have the j_rodd recovery image on the sdcard but adb wont pick it up as a device.
Click to expand...
Click to collapse
I have problem with my Motorola MB300 ME600. when power even power + up OR power + down it only display and to M logo and make sound (has vib)... I can connect to fast boot even RSD. Help me! Plz....

CyanogenVietNam said:
I have problem with my Motorola MB300 ME600. when power even power + up OR power + down it only display and to M logo and make sound (has vib)... I can connect to fast boot even RSD. Help me! Plz....
Click to expand...
Click to collapse
firmware for your device.
You need to download these things...
RSD Lite 4.5.7
AT&T Stock Android 2.1 Blur v3.0.1390 - Original SBF by Skrilax_CZ @ ModMyMobile
And if you're doing this and haven't attempted root yet, or would just like to wipe your device through and through, HERE are the Moto USB drivers. Make sure to get the correct installer for x86 or x64.
Install your USB Drivers (if you haven't already)
Install RSD Lite
Turn off your backflip
Plug the USB cable into the phone and computer
Open the keyboard and press J+D+Power simultaneously and let up when you see the blue recovery screen with the black moto batwings. In the bottom left corner of the screen it will say in white letters "USB init mode"
Now when the phone boots to the recovery screen, Windows will begin installing a driver for the MSM720x flash recovery mode.
After the driver has successfully installed, open RSD Lite
Upon opening RSD Lite, you should notice ONE connected device in the table below. If not, post what you did exactly and we can help
Now that the device is showing in RSD Lite, click the "..." browse button to point to the Android 2.1 Blur 3.0.1390 image you downloaded earlier
Once that's selected, press start to start flashing your phone.... DO NOT UNPLUG UNTIL IT'S FINISHED.
Once finished, it will reboot itself and you should be presented with the Android Setup after a minute or two.

[DEV TIP]How I Got Out Of A Semi-Brick

I almost had a heart attack last night doing some kernel work. This is what happened, and how I got out of it.
I had just finished compiling a kernel I was working on and was excited to flash it and give it a run. So I built the boot.img and did
Code:
adb reboot bootloader
I got into the bootloader and
Code:
fastboot flash boot [B][I]boot.zip[/I][/B]
fastboot reboot
Working quickly, a got a little sloppy. Most unfortunately, I had a boot.zip in the same folder as the boot.img so boot.zip got flashed to the boot partition. Upon reboot, I got the usual splash screen but the upper left hand corner indicated I was in "RSD Mode 3". I pressed and held Vol up + power to get into bootloader but that was unresponsive. All I could do was press Vol Down + power which brought me back to the same state. I was unable to issue fastboot commands from here as well. This is what I did to fix it.
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful

good post I'm sure this will help devs in the future

way to stay calm under pressure lol. good info.

Small world, I used to live in Fontana for 25 years and moved to NY couple of years ago Oh and thanks for the tip

Ran into this today, i had a similar, but different experience..hope this helps
Once i got into the RSD 3 mode, fastboot commands were basically dead...all i would get was <waiting for device>...
in order to get out, i had to hold BOTH VOL+ and VOL- and Power at the same time, then as soon as the screen turned off, I had to press VOL- and power at the same time to get to a 'regular' looking boot screen. I saw regular because there was no text at the top ofthe screen; however fastboot commands would work here. Because i FUBAR'd a kernel install, i just did
fastboot flash boot boot.img
fastboot reboot
and voila...it was alive again
a bit scary though

Ok, so I definitely know the heart attack feeling, and hopefully someone here can help me out. I got my Xoom today(wifi), and went looking for a root. I found a link to a root here that -said- it worked for both 3g and wifi models(found out later that it doesn't, obviously). So, I flashed the boot image, and came up with the RSD message. At that point all fastboot and adb capability was lost, and I can't seem to get it back.
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
No other button combinations seem to do anything. Holding Power+VolDown doesn't do anything from any mode, and Power+VolUp+VolDown acts just like Power+VolUp.
In any mode, I can't issue fastboot or adb commands. Fastboot simply says <waiting for device> for anything. I tried the advice above, to queue up a "good" boot.img (from here at xda), but it doesn't recognize it on a reboot from/to any mode I can get to. I've tried each about 20-30 times now, and I'm about ready to test the thing's shatter-resistance with my fist, so any help here would be -greatly- appreciated.

Quick update to previous post: Resolved!!
My advice? If you get stuck unable to fastboot or adb in linux, try it in windows. I hadn't booted into win for over a year, so it never occured to me until I saw someone mention it in the Tiamat thread. Even a fresh JDK/SDK install in Ubuntu didn't work for me. I didn't have any tools or SDK's installed in my winXP partition, but after a quick install, it worked first time, so now I'm the happy owner of a rooted Wifi Xoom with SD card.
Once again, the XDA forum saves the day. I love this place.

I recommend everyone keep a backup copy of their system.img around just in case too. I was going nuts after messing with my framework-res.apk file to get SMS working (for the verizon web account activiation message). I used root explorer, and BAM! crash, crash, FC, FC, then stuck at the moto logo at boot. I couldnt get it back with just a boot.img flash. I went for broke and found a post of the HI66 system.img. it was HUGE, dont know if thats what I needed. but flashed that and I was back in business as nothing else was working and couldnt get ADB to take to push the old framework-res.apk.

I have a similar issue. I have tried for over three hours now to understand why I cannot reboot into fastboot. It seems lika I have lost both fastboot and NVflash. Only RSD mode and a logo screen without text. Can't shut it down with powerbutton or factory reset. I tried to root it with a 3g boot.img whitch was terribly wrong on a wifi-only xoom and I'm now trying to flash a stock wifi boot.img. It just sits there on the M dual core screen.
What can I do from RSD mode 3?
EDIT: I have a feeling that it has freezed on that logo screen. I want to try a hard reset and the only way for me is to try to first shut it down then power it on again. Don't know if it helps but it is silly to be unable to stop it. How can I shut it down?

I've tried all the suggestions above with no luck
Will try a windows machines tonight to see if that will help, but I fear I will need to send my Xoom back to mfg for rework

may seem a stupid suggestion but what if you let the battery go dead. it will turn off. Then connect to power supply and do a fast boot restart, holding power button and vol down.
Just a thought!

I will try but I think I already tried that. It seems like boot and recovery is dead. I tried to flash the 3g .sbf file today. Thought that an already bricked tab couldn't be more bricked and perhaps it would restore the recovery or boot but RSD Lite couldn't do it. It's unvisible for a computer. I've tried both win7 and my Arch Linux box. The device is dead. Hopefully they wont have to replace the motherboard. I'm sending it for repair on Monday.

mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.

dogma444 said:
mines bricked also says
failed image lnx 0x0002
starting rsd mode 2
i can get it in the fastboot protocol mode with the - button and power but cmd window says waiting on device. my started after i did an fastboot oem lock with a bad kernel.
Click to expand...
Click to collapse
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock

orionshock said:
iirc the Failed Image lnx 0x0002 is due to locking the boot loader with custom stuff.
Unplug xoom usb
boot into fastboot
plug in xoom usb
fastboot oem unlock
Click to expand...
Click to collapse
Man that just sound to easy to work. ADB has no clue the device is.....wel, a device! Its like my xoom de-evolutionized to a primitive state and is suffering from tourrets. Anyway command typed in adb gives you back < waiting for device >. I've tried just about all the techniques here on the forums. And the people who claim to have been brought back to life are not victims of this "RSD mode 2" Im pretty sure this is like a failsafe if you blow up the original bootloader, 3. IDK though, pretty sure they are going to require some hardware replacements. Im not sure people are recognizing the degree of our bricks. These are what appear to be real BRICKS. no "soft" ness up in here. straight up cement

http://forum.xda-developers.com/showthread.php?t=1041192
adb wait-for-device && adb reboot recovery
tried this command and seemed pretty slick but, still nothing

Same thing here, was there any solution?

Give this a try:
http://forum.xda-developers.com/showthread.php?t=1079784

Please, I have same problem, but I can just reset it by pressing and holding Vol Up + Power On. When I press Vol Down + Power Down, nothing happens. If I press Vol Down when it restarts, it doesn't show me the message but shows the Motorola Dual Core logo and stops. Even in this situation I can't comunicate via usb. Now it just turn off when the battery is totally low.

I CAN boot into fastboot mode and issue fastboot commands from CMD. apparently mine is booting into RMD 3 mode or whatever it's called. when I boot normally (just hold down power button, I get the moto dual-core screen, and then it boots into the Clockwork Recovery Mod... PLEASE HELP

Stuck at Motorola logo and RSD mode 3

I'm new to Xoom but gave unlocking and rooting a go. That was todays mistake! I flashed a 3g version of boot.img. Then I tried to flash back to stock img-file. Found out that it also was a 3g img-file. Flashed once more. Now it was a wifi-only boot.img. Now I'm stuck at the Motorola Dual Core logo with Starting RSD mode 3 written in top left corner. I can't shut this thing off or anything else but rebooting back to same screen. I really don't know what to do. I bought it yesterday from a man that bought it in the US a week ago so I can't go to the shop and I don't think there are any shop that can flash it for me because it's not available here in Sweden yet. Please help. I have RSD Lite installed and the correct drivers for the Xoom installed. I'm used to ADB but it can't find the device and fastboot doesn't see it either.
Edit. I can't go into fastboot mode.

Grab the wifi's boot.img off of here:
http://forum.xda-developers.com/showthread.php?t=1017398

http://forum.xda-developers.com/showthread.php?t=973355
This might be helpful. Not sure.

Don't worry you are in good company, even BRD had the same problem. Here's how he fixed it:
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
Click to expand...
Click to collapse
Edit: Same advice as linked above by milehighclubAV8R

That doesn't do it. Propably it's some stupid misstake from me but I cannot do this because of " I pressed Vol Down + power until the screen went black". It wont get black. When I press Power + Vol down nothing happens. Am I doing something wrong. I have tried holding the buttons for about 30 seconds and nothing happens.

Did you just press the buttons or did you also enter the fastboot code as suggested?

First cmd command then pressing the buttons. When I reboot using power + vol up it starts into RSD mode 3. When rebooting it with power + vol up then vol down when black it starts into the logo screen without any text in the upper left corner. Can't even shut it down with long press on power button
Can I pull the battery? On my Galaxy S that's the way out if I get in a boot loop or need to redo a failed flash.

Not AFAIK, the unit is sealed and can't access the battery to pull it.
Perhaps ask in this thread - http://forum.xda-developers.com/showthread.php?t=973355, there may be more technical people seeing it there than in the general section.

OK. I will do that. Thank you for trying to help.

Press power+volume up. Hold it til it restarts. Let go of both buttons once you see the motorola logo then just press volume down once, and you should be then able to cycle through 3 different modes. Press volume down to cycle to different modes, volume up to select. Hope that helps.
Sent from my Xoom using XDA Premium App

Sorry but I can't cycle through anything. There are two modes. Either "Starting RSD mode 3" or nothing and RSDLite can't communicate with it so I belive that my xoom is dead. Sending it in for repair tomorrow. I'm giving up.

mine is stuck in the rsd mode 2. if i push and power and the up it will boot cycle if i the down button it says it is the the flashboot protocol mode, but i cannot get it to respond from the cmd window. my computer doesnt think its connected. i have the correct mot drivers. any help or is it bricked

Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.

This might work or it might not.
I had a bricked xoom too. no matter what fastboot i entered it wouldnt recognise it. all it would say is "waiting for device"
This is what i did.
Turn the xoom off
Do not connect you USB cable yet
Fastboot reboot-bootloader
It should say "waiting for devices"
Now plug your xoom
Turn on the xoom.
When you see the Motorola logo press volume down till you see "fastboot protocol"
Press volume up.
It recognise my xoom that way

couldnt turn mine off. let the battery run down. plugged it into power booted it up. no help. bricked

stevenege said:
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
Click to expand...
Click to collapse
I have to admit, I'm one of them. Sure is a nice way to tell Moto to hurry the F up. I can't say I felt great about it but I wasn't about to lose $600 either.

me to one of them

shipped mine back to the factory today. not sure what they can do to it. is there such a thing as a force flash or will they have to replace the firmare chip to make it work? unstable combo tegra and honeycomb, aint messin with mine anymore.

i just recovered mine from this. i flashed recovery with clockwork mod:
at the rsd 3 screen with the usb attached
fastboot flash recovery recovery.img
held the volume down while pressing the power off on until fastboot started flashing the recovery
fastboot reboot
xoom started in clockwork mod, did a restart and it worked
****This happened after attempting to load recovery from rom manager without flashing new recovery image.***

Did you happen to mention in your explanation about what went wrong with your xoom anything about unlocking or relocking?

Bricked stuck on RSD mode 3

Hi everyone, so my father's tablet booted and bricked itself, it was working fine for about 2 months since last update. he says it froze on lock screen, he forced a reboot and then the problem happened
Problem:
Motorola xoom tablete MZ604 (wifi only) is stucked on Motorola Logo with "starting RSD mode 3" , if I press & hold " Volume Up & Power" it rebootss back into the same screen. If I press & hold "Volume up & power" then release and press Volume Down, it sticks at the Motorola Logo but without the "starting RSD Mode 3 ".
Already tried
Cant turn it off, get to fastboot or recovery options.
when displaying the Starting RSD mode 3, if I connect the tablet to my pc I hear the Dond dong and I can see the computer running the Motorola flash interface driver on the device manager BUT no adb devices are listed on command prompt or anything on Computer but C:..
I even tried bridgeing ( I believe that's the correct word in english) the micro usb cable so line 1 and 4 had the voltage, ( I saw this as a solution for having the "factory cable" ) but NO RESULT
all sort of combination of pressing volume and power buttons for 20 secs. no result
Background info
I was able to unlock it, root it , and I was running team eos wingray and the gpu OC and all that sweet stuff for several weeks my pc has the sdk tools and google usb driver package all updated.
Im desperate please HELP

mate, i literally just had this problem, right now! Was trying to do some fastboot stuff and something went wrong (obviously because otherwise i wouldn't be here). The way i solved it was:
Hard reboot it (power and volume up)
Then as the splash screen comes (even a bit before) keep pressing the volume down button repeatedly. With me the RDS mode 3 onwire thing then didn't come up, turns out it was in fastboot mode when I connected it to the PC to see if was in luck. Turns out I was. Then I fastboot flashed a recovery.img and now it's all gravy.
Hope this works for you

Need help with xoom, possible brick

First,
I really want to thank everyone for their support in this forum. Everyone has been amazing.
I was trying to bring my MZ601 back to stock yesterday. Something bad happened during fastboot and asked me if I wanted to unlock my device. Then the screen locked up and didnt do anything. I rebooted the device and now it gets stuck in a boot loop with the EOS symbol (last rom I installed). When I enter recovery there is nothing there, all of my data is gone.
Worse the device is not recognized on my computer nor can it be found in adb fastboot. I have updated motorola drivers, but I think the device never gets past a certain point in order to be found.
Can somebody please help me.
Thanks,

Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).

demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
Hi,
Thanks for the tips. Unfortunately, it seems that I have caused the entire sd card partition to be erased. That mean when I trry to fastboot my device is not recognized. Also, i cannot add anything to my xoom through usb. I have tried to flash through the external sd card, but to no avail. What do I have to do?

What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.

dfib1 said:
What does your xoom show up as when plugged into your pc APX? Can you boot into fastboot mode. with power off press power and volume down until you see fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply to my message.
Unfortunately I cannot find my device when it is plugged into my computer (PC). It does not show up on my computer nor in the device manager. I can start the fastboot protocol on my device by rebooting, but I also cannot find my device in ADB.
Thanks for the reply, but I am still very stuck.

are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app

ndanl said:
are you sure your device is in fastboot ? did you reinstall the drivers, try with another usb cable, adb shoud see the device after the drivers were installed correctly ...
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
I did everything I have done before. I have setup android sdk, java, and motorola drivers on two different PCs. Both fail to find my device when i type ADB devices nor does ADB reboot bootloader work. I tried the different cable, but that also did not work.

Hi,
I see that your problem is quite hard, try doing this:
1 - Force your tablet to shut down (vol+ + Power)
2 - Turn on while holding the vol- button
3 - Keep pressing vol-
4 - Plug on your PC and try fastboot devices, adb won't work!
5 - If 4 didn't work, keep trying until it does
6 - Install a Stock ROM (so you will solve your problems)
If the above don't work, contact me via PM, so we can talk easily (maybe GTalk or something like this). Good Luck
~XxLordxX
"This Story Ends Where It Began" - Octavarium (Dream Theater)

XxLordxX thank you!!!
I took your advice and just used fastboot. Then I flashed the stock rom I wanted to use. My xoom is back up and running. I really appreciate the tip.
Also thank you to everyone that responded in the post, again, that is why I love coming here.

demunted said:
Pretty impossible to brick XOOM's but i'll ask the basics. Can you get into recovery from a cold boot? Can you get into fastboot from a cold boot?
By the sounds of it you've just corrupted your rom or tried to re-unlock the device which would cause the entire sdcard partition to be erased.
Boot XOOM into Recovery, Fastboot, or RSD mode
So you need to get into Recovery to backup your XOOM (you do nandroid don't you?). Or perhaps you were working on creating new levels of awesome and something happend and you find yourself staring at the Motorola Dual Core boot screen with your XOOM refusing to boot any further. Fear not, you are only a few clicks away from finding your way back into recovery or fastboot goodness.
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
You can also choose from Fastboot protocol support and RSD mode by using the same method but instead selecting their respective menu prompts.
Note:
If your XOOM is caught in bootloops or you find yourself stuck in RSD mode or Fastboot Protocol support you can hardware reboot your XOOM by pressing and holding Volume Up + Power until the tablet reboots (usually a few seconds but could be longer).
Click to expand...
Click to collapse
I have this problem now but I don't know what to do. Please help me out